Initiating failover processing for B volumes to A volumes

Complete this task to perform failover processing for B volumes to A volumes so that the B volumes become the primary volumes and A volumes become the secondary volumes. The Global Copy state of the B volumes changes from secondary to primary and suspended. This is the next step after you obtain a status of your Global Mirror transactions in the Global Mirror failover recovery process.

The failover task cannot be done unless you have completed the following:

Ended Global Mirror processing
Obtained the reports that help you determine the status of your Global Mirror transactions before the disaster occurred

Recovery failover processing on the Global Copy volume pair ends the A-to-B volumes extended distance relationship and instead creates a B-to-A volume Global Copy relationship. Therefore, failover processing to the Global Copy secondary volume turns the secondary volumes into primary volumes and immediately suspends these volumes. Because the B volumes are the now the primary volumes and the A volumes are now the secondary volumes, the Global Copy state of the secondary volumes has changed from Target Copy Pending to Suspended.

To initiate failover processing of the B volumes to the A volumes, perform the following step. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables.

Issue the failoverpprc command to change the Global Copy state on the B volumes from secondary, target pending to primary, suspended. Enter the failoverpprc command at the dscli command prompt with the following parameters and variables:

dscli>failoverpprc -dev storage_image_ID -remotedev storage_image_ID SourceVolumeID:TargetVolumeID

Example

dscli>failoverpprc -dev IBM.1750-68FA150 -remotedev IBM.1750-68FA120
 0100:0100 0101:0101 0102:0102 0103:0103

Note: Unlike most other commands, the storage_image_ID and SourceVolumeID:TargetVolumeID values are reversed for the failoverpprc command, because the command is issued directly to the remote server. You must place the values for the remote server first and the values for the original primary server second. This reversal (where the remote server is no longer the primary server) can have the following results:

The source volumes become suspended
The target volumes become suspended and they are available for mounting

A confirmation message like the following one is generated for each Global Copy pair that is changed and moved to a suspended state.

Remote Mirror and Copy pair IBM.1750-68FA150/0100:IBM.1750-68FA120/0100 
successfully suspended.

All B volumes must successfully process the failoverpprc command before you can move on to the next step which involves analyzing the FlashCopy relationships and initiating the appropriate commands.