HP P6000 Replication Solutions Manager 5.3 Release Notes (T3680-96402, May 2011)

Replication manager jobs
Unmounting a Windows host volume job during I/O
If you attempt to perform an unmount operation from the Host Volume tab, either by running a job
command or right-clicking a host volume and selecting Unmount, the host volume will unmount
immediately. To prevent this, make sure the host volume is not being used before performing any
unmount operations.
Available options are not displayed properly after virtual disk failure
The replication manager and HP P6000 Command View user interfaces do not properly display 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. HP P6000 Command View displays
only the Detach option.
Resolution: Detach the link between the mirrorclone and the source virtual disk in HP P6000 Command
View, and then restart the replication manager.
Name not unique error when creating virtual disk
If you make storage-related changes outside the replication manager, they are not reflected immediately
in the replication manager database. This can lead to failures when attempting user interface actions
or running jobs in the replication manager.
For example, if you create a virtual disk using the replication manager, later delete that virtual disk
using HP SSSU, and then use the replication manager to create a new virtual disk with the same name,
the operation fails and a message is displayed, indicating that the new disk name is not unique.
Resolution: Immediately after making storage-related changes outside the replication manager, perform
a Global Refresh in the replication manager to ensure that the changes are reflected in the replication
manager database.
Too many concurrent DR group creation jobs
When creating multiple DR groups, some jobs fail during the CreateDrGroup step. The message
Storage system lock error is displayed in the events pane.
Resolution: Do not create more than three DR groups concurrently.
Multiple SetNotificationPolicy job commands may fail
When setting email notification for a job that contains more than one SetNotificationPolicy
job command, you only receive notification for the last command set. For example, if the job contains
the following commands, you will only receive email notification for a job failure:
SetNotificationPolicy ( "[e-mail]", "john.smith@my
company.com", JOB_STARTED_OR_STOPPED)
SetNotificationPolicy ( "[e-mail]",
"[e-mail]", JOB_FAILED )
Resolution: If you experience this problem when using multiple SetNotificationPolicy job
commands, use only one SetNotificationPolicy job command at a time.
Aborted job appears to hang
When a job is aborted, the replication manager waits for all pending operations within that job to
complete. If an operation to the remote system, such as EnableHost, cannot be cancelled, the aborted
job appears to hang.
Resolution: The job abort completes when the remote operation completes or when you restart the
replication manager service or the enabled host.
HP P6000 Replication Solutions Manager 9