Available options are not properly shown after virtual disk failure
The replication manager and HP Command View EVA do not properly show the available options for a
mirrorclone after the source virtual disk has failed. The replication manager displays only the Fracture
option, but you will not be able to use it, and HP Command View EVA displays only the Detach option.
Resolution: To resolve this issue, detach the link between the mirrorclone and the source virtual disk in HP
Command View EVA and then restart the replication manager service.
DR group name guidelines
HP recommends that you assign unique names to DR groups. Duplicate names are supported for DR
groups on different arrays, but they are not supported for DR groups on the same array. DR group names
are case sensitive in HP Command View EVA, but are not case sensitive in the replication manager. In
rare cases, this can lead to issues in the replication manager. For example, if you use HP Command View
EVA and create two DR groups, DRgroupA and drgroupa on the same array, there will be no problem in
HP Command View EVA, but actions and jobs in the replication manager involving either of these DR
groups may fail or result in unexpected behavior.
“Name not unique” error when creating virtual disk
If you perform storage-related operations outside of the replication manager, those storage changes are
not immediately reflected in the replication manager and could lead to failures when attempting user
interface actions or running jobs in the replication manager. For example, if you create a virtual disk
using replication manager and later delete the virtual disk using the Storage System Scripting Utility
(SSSU), then use the replication manager to create a new virtual disk with the same name, the operation
will fail with a message stating that the new disk name is not unique.
Resolution: Immediately after performing storage-related changes outside of the replication manager,
perform a Global Refresh in the replication manager to ensure the changes are reflected in the replication
manager database.
Too many concurrent DR group creation jobs
Symptom: When creating multiple DR groups, some jobs fail during the CreateDrGroup step. The
Storage system lock error event is listed in the event pane.
Resolution: Do not create more than three DR groups concurrently.
Multiple SetNotificationPolicy job commands may fail
Symptom: When setting e-mail notification for a job that contains more than one
SetNotificationPolicy job command, it is possible you will only receive notification for the last
command set. For example, if the job contains the following commands, you would only receive e-mail
notification for a job failure:
company.com", JOB_STARTED_OR_STOPPED)
company.com", JOB_FAILED )
Resolution: If you experience this problem when using multiple SetNotificationPolicy job
commands, only use one SetNotificationPolicy job command at a time.
An aborted job appears to hang
When a job is aborted, the replication manager waits for all outstanding operations within that job to
be completed. It is possible that an operation to the remote system, such as EnableHost,cannotbe
cancelled and the aborted job will appear to hang.
Resolution: The job will abort completely when the remote operation completes or if you restart either the
replication manager service or the enabled host.
HP StorageWorks EVA replication software consolidated release notes 9