HP StorageWorks Replication Solutions Manager V1.1 Release Notes (T3687-96026, June 2005)

2. If the status is failed (red), use HP Command View EVA to check the status of the DR group (see
HP Command View EVA online help)
3. In HP Command View EVA, issue a resume command to resume the D R group.
NOTE:
Inthereplicationmanager,thefailedDRgroupstatusdoesnotchangeuntilthenextautomaticor
manual refresh.
Second snapclone of the same storagevolumeorhostvolumefails
The second snapclone of the same storage volume or host volume fails and the replication manager logs
a message like: Copy type CLONE not available or no resource bundle
This can occur when you run and then quickly rerun the same job.
This issue can also occur bec ause the replication m anager database was not refreshed after the first
snapclone was completed. When the second snapclone is requested, the replication manag er encounters
the out-of-date normalization status in the database and fails the requested snapclone action
Resolution: you can make multiple snapclones of a source volume. However, only one snapclone
can be in the normalization (unsharing) phase at one time. If the second snapclone action is started
too soon, the action can fail.
Maximum DR Group log si ze error
If you enter an invalid value, the replicatio
n manag er logs an error and does not set the m aximum log
size for the DR group.
Resolution: valid values are from 136MB to 2TB. Acc ept or enter zero (0) to apply the firmware default
size algorithm.
Storage error when running more than two jobs accessing the same array
Running more than two jobs simultaneously on the same array can return the following error on the third
and any other jobs: Data replication failed- device error. Data replication
failed for <job>. Borg error code 600017. Error cannot create object.
Storage system lock error.
The first two jobs run successfully, but additional jobs fail.
Resolution: Avoid running, or scheduling to run, m ore than two jobs that a ccess virtual disks on the
same array at the same time.
Capture System command fails in CLUI
RSM CLUI Capture System command fails with the following error: XL041>c sys 500 Command
Failure java.lang.OutOfMemoryError XL041>
As the data (logs, database, config files, etc) tha t is being retrieved from the server grows large enough,
this comma nd fails. Unless the logs a re cleared, this state will remain until the n ext replication manager
release. Thelistoffiles and directories that are retrieved are in the hostagent/config dir in
apropertyfile named cluiframework.scp.
Resolution: manually retrieve the files from the server if this issue arises.
HP StorageWorks Replication Solutions Manager 1.1 release notes
7