HP 9000 rp5405 Servers - Manual (Page 236)

NOTE:
For more information on the underlying functions used by the advanced operations, see “ Advanced
operations and corresponding P9000 RAID Manager commands ” on page 245.
The advanced operations are as follows:
• Takeover operation , page 236
• Swap operation , page 237
• Force-split operation , page 237
• Takeover-recovery operations (resync and recreate) , page 238
CAUTION:
Take note of the following points:
• Advanced operations can be performed per copy group or per copy pair.
• Because the copy pair status cannot be retrieved in the event of a failure, it is not confirmed prior
to executing an operation. (Under normal circumstances, copy pair status confirmation is required
and is performed by the Device Manager agent.) In this instance, an error message is created
based on the information sent from the agent and is output for the Change Copy Pair Status task.
• Takeover and swap operations cause the target copy pair or copy group to be treated as a different
copy pair or copy group after the operation. See “
Alert settings and volume switching ” on page 242
for more information.
Related topics
• Restoring an application replica from the Replica History , page 400
• Advanced recovery use cases , page 239
• Recovering a copy pair configuration definition file (takeback) , page 242
• Alert settings and volume switching , page 242
Takeover operation
The takeover operation is used to switch to the secondary site when there is a failure at the primary.
The resulting copy pair status depends on the environment where the takeover operation is executed.
If the takeover operation is executed when there is damage to the primary site, or a failure in the
primary site storage, the status of the secondary site will be Split (SSWS). In all other cases, the primary
volume and secondary volume of the copy pair are switched. You can check the execution results
based on the copy pair status and the relationship between the primary volume and secondary volume
that make up the copy pair.
NOTE:
Regarding pair status:
• If the copy pair state cannot be obtained from the Device Manager agent, the state is Unknown.
• When a failure occurs, it might not be possible to obtain the copy pair state of the target copy
pair. After the operation, the copy pair has a split primary volume, and a writable secondary
volume. As a result, the aggregate copy pair status is Suspend.
Managing pair life cycle 236