HP P6000 Replication Solutions Manager User Guide (T3680-96089, October 2012)

Explanation / resolution
This can occur if a DR group pair is suspended while the intersite links are unavailable. When the
intersite links become available again, both DR groups are identified as the source. The
source-source identification continues until remote replication is resumed.
This can happen when:
• The DR group pair is suspended while the intersite links were unavailable. See Suspension
state.
• The DR group pair is failed over with the suspend-on-failover action while the intersite links
were unavailable. See Suspend on failover.
• Auto suspend mode is enabled while the intersite links are unavailable. See Auto suspend on
link down.
To resolve this issue
1. Use HP P6000 Command View to resume the suspended DR group pair.
2. After resuming the DR group pair, perform a manual refresh of the DR groups. See Low-level
refreshing DR groups.
The source and destination DR groups are correctly identified.
NOTE: While the incorrect source-source identification exists:
• The GUI Actions menu correctly shows only actions that are appropriate for the true role of
the DR group (source actions for the true source and destination actions for the true destination).
• In the CLUI, issuing a Show DR_group command on the "new source group" shows it correctly
as a destination and only destination operations can be executed.
Invalid DR group settings—Failsafe on unavailable member with synchronous replication
Problem
When attempting to use CLUI commands to disable the failsafe on unavailable member, the
replication manager logs the message:
Failed to set failsafe for DR Group, group is currently :failsafe is
already enabled.
Explanation / resolution
You can use GUI actions or CLUI commands to create a DR group pair with the following invalid
configuration: failsafe on unavailable member enabled with synchronous remote replication I/O
mode. Attempting to disable the failsafe on unavailable member in this invalid configuration results
in an error.
To resolve this issue, use the GUI or CLUI commands to set a valid configuration. To retain an
asynchronous I/O mode and disable the failsafe on unavailable member:
1. Change the remote replication I/O mode to synchronous.
2. Change the failsafe on unavailable member to disabled.
3. Change the remote replication I/O mode back to asynchronous.
Job instance fails with get error lock message
Problem
A job instance fails with a message: get error lock failed.
Explanation / resolution
Too many job instances that interact with a specific enabled host may be running simultaneously.
To resolve the problem, reduce the number of running job instances that involve the enabled host.
Troubleshooting 33