HP P6000 Replication Solutions Manager 5.5 Release Notes (T3680-96067, June 2012)

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.
Job scheduler does not handle Daylight Savings Time properly
The job scheduler handles Daylight Savings Time (DST) correctly in the replication manager unless
you try to schedule a job on the day that DST changes (spring or autumn). For example, if DST begins
on Sunday at 2:00 a.m., and you try to schedule a job that day, one hour is added to the time. (The
job scheduler increments the scheduled jobs by one hour.)
Resolution: If you want to schedule a job on the day that DST changes, you must set the job one hour
earlier than required. However, if you try this procedure on any day after the day that DST begins,
the job scheduler will work as expected.
Clarification of WaitDrGroupSynchronizationTransition job command
The description of the WaitDrGroupSynchronizationTransition job command states that the
job is halted until the I/O mode of the DR group is changed. However, the job behavior is as follows:
• If the DR group is in enhanced asynchronous mode and you change the mode to
synchronous, the job waits until the state of the log is merging (log running down), not
until the I/O mode has changed to synchronous.
• If the DR group is in asynchronous mode and operating normally, the job does not wait.
HP P6000 Replication Solutions Manager 7