HP P6000 Replication Solutions Manager Administrator Guide (T3680-96069, June 2012)

To resolve an offline state condition for a dynamic disk in Windows 2008, run diskpart, and
then issue the san policy=OnlineAll command on the host. Then, reboot the host and run
the instant restore job.
Instant restore host volume name changes
Replication is performed by specifying the host name and host volume name. If a host volume
name changes, the replica repositories will not be available on the host volume's Instant Restore
wizard. This can happen with Linux after a reboot or with any operating system on which a virtual
disk is unpresented and then presented with a new LUN.
From the Virtual Disks pane, perform an instant restore on each virtual disk that is affected.
Error during instant restore
If a virtual disk is presented to multiple hosts, and a job execution error occurs during an attempt
to perform an instant restore on a host volume in any of the hosts, you must manually mount the
host volume on each of the hosts on which it was presented.
Replication manager logs
The replication manager server and host agents generate log files that track and record activity in
the replication manager software. These detailed event log files can be helpful to HP support
personnel when troubleshooting replication jobs. Before contacting HP support, collect the replication
manager server and host agent logs.
Depending on the problem, you may need to collect other logs. For example, if a Java error occurs,
you may need to collect the Java console logs. If the problem is related to HP P6000 Command
View, you may need to collect HP P6000 Command View logs.
Synchronizing replication manager log files
To ensure the usefulness of the replication manager logs, synchronize the array clocks to the
management server. See “Synchronizing management servers and arrays” (page 25).
HP recommends that you synchronize the time of the HP P6000 Replication Solutions Manager
server to each HP P6000 Replication Solutions Manager host agent to ensure that the analysis of
the server host agents is meaningful.
DR group log sizes
See the HP P6000 Enterprise Virtual Array Compatibility Reference for the default and maximum
log sizes for a synchronous or asynchronous DR group on arrays.
Enhanced asynchronous mode log disk space
If you are using the HP EVA4x00/6x00/8x00 series, and change a DR group from enhanced
asynchronous mode to synchronous mode, the disk space allocated for logging cannot be reduced.
When using HP P6000 Continuous Access Enhanced Asynchronous replication, the full log disk
space is reserved when you first enter enhanced asynchronous mode. Even if you switch to
synchronous mode and remove a DR group member, the reserved log disk space is retained by
the array for future use.
To return the reserved log space to the disk group, delete the DR group, and then re-create it. A
full copy will occur.
For XCS 6.1xx with HP Command View EVA 7.0, the reserved log size can be changed by setting
the maximum log size after returning to synchronous mode.
Minimum asynchronous replication log size
If you change the write mode of a DR group to enhanced asynchronous (between arrays running
XCS 6.000 or later), the following error message can appear if the log size is too small:
Replication manager logs 43