failoverpprc

The failoverpprc command is used only with disaster recovery processing. This command is used in the disaster recovery processes associated with sites using Metro Mirror, Global Mirror, or Metro/Global Mirror processing. The failoverpprc command succeeds even if the paths are down and the volume at the production site is unavailable or nonexistent.


>>-failoverpprc--+-------------------------+-------------------->
                 '- -dev--storage_image_ID-'   

>--+-------------------------------+-- -type--+-mmir-+---------->
   '- -remotedev--storage_image_ID-'          '-gcp--'   

>--+-------------+--+-----------+--+----------------+----------->
   '- -tgtonline-'  '- -cascade-'  '- -srcss--ss_ID-'   

>--+----------------+------------------------------------------->
   '- -tgtss--ss_ID-'   

>--+-SourceVolumeID:TargetVolumeID--+-------+-+----------------><
   |                                '-. . .-' |   
   '-" - "------------------------------------'

Parameters

The failoverpprc command is used in the Global Mirror and Metro Mirror disaster recovery processes with the following results:

In a Global Mirror failover recovery process, the failoverpprc command initiates failover processing of B volumes to A volumes. This causes the B volumes to become the primary volumes and the A volumes to become the secondary volumes. The effect is that the Global Copy state of the B volumes changes from secondary to primary and suspended.
In a Global Mirror failback recovery process (production is returned to the local site), the failoverpprc command initiates failover processing from A volumes to B volumes. This causes the A volumes to become the primary volumes and the B volumes to become the secondary volumes.
In a Metro Mirror disaster recovery process, failover processing to the Global Copy secondary volume causes the secondary volumes to become primary volumes and immediately suspends these volumes. When you run a Global Copy failover, the B volumes are the primary volumes and the A volumes are the secondary volumes. This action changes only the Global Copy state of the secondary volumes from Target Copy Pending to Suspended. The failoverpprc command changes a secondary device into a primary suspended device while leaving the primary device in its current state. This command succeeds even if the paths are down and the volume at the production site is unavailable or nonexistent.

Note: When you specify the subsystem identifier (SSID), the source and target volumes are restricted to one LSS for the source and one LSS for the target.

-dev storage_image_ID

(Optional). Specifies the source storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified source volume ID.

Note: The use of the failoverpprc command requires that this parameter reflect a role reversal. The value for this parameter must be the original secondary site. For example:

Original primary site (Site A) has a value of (1750) IBM.1750-68FA120 with volumes 0100, 0101, 0102, 0103.
Orignial secondary site (Site B) has a value of (1750) IBM.1750-68FA150 with volumes 0200, 0201, 0202, 0203.
The following failoverpprc command is correct:
(1750) dscli>failoverpprc -dev IBM.1750-685FA150
-remotedev IBM.1750-68FA120
0200:0100 0201:0101 0202:0102 0203:0103

-remotedev storage_image_ID

(Optional). Specifies the target storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified target volume ID or if you use the -dev parameter.

Note: The use of the failoverpprc command requires that this parameter reflect a role reversal. The value for this parameter must be the original primary site. For example:

Original primary site (Site A) has a value of (1750) IBM.1750-68FA120 with volumes 0100, 0101, 0102, 0103.
Orignial secondary site (Site B) has a value of (1750) IBM.1750-68FA150 with volumes 0200, 0201, 0202,0203.
The following failoverpprc command is correct:
(1750) dscli>failoverpprc -dev IBM.1750-685FA150
-remotedev IBM.1750-68FA120
0200:0100 0201:0101 0202:0102

-type mmir | gcp

(Required). Modifies one or more existing remote mirror and copy volume relationships as either Metro Mirror or Global Copy relationships.

mmir: Metro Mirror maintains the remote mirror and copy relationship in a consistent synchronous manner when the updates are committed to the target. This process becomes slower as the physical distance between source and target increases.
gcp: Global Copy maintains the remote mirror and copy relationship in a nonsynchronous manner when the updates are committed to the source. Updates to the target volume are performed at a later time. The original order of updates is not strictly maintained.

-tgtonline

(Optional). Establishes a remote mirror and copy volume relationship, including when the target volume is online to host systems.

This parameter applies to S/390 or zSeries volumes. It does not apply to Open Systems volumes.

-cascade

(Optional). Specifies that the PPRC target volume can also be a PPRC source volume of a different PPRC volume relationship.

-srcss ss_ID

(Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF.

This value is required for the IBM System Storage™ Enterprise Storage Server versions 2.4.0 and 2.4.1.

Example: 0010

-tgtss ss_ID

(Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF.

This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1.

Example: 0010

SourceVolumeID:TargetVolumeID . . . | –

(Required) Specifies the remote mirror and copy volume pair IDs of the source and target volumes that must have their relationships changed so that the target volumes (B volumes) become the source volumes and the original source volumes (A volumes) become the target volumes. This results in the following conditions:

The source volumes (B volumes) show as a suspended host.
The target volumes (A volumes) show as a suspended target and they are accessible for mounting.

This parameter also accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces.

A remote mirror and copy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume.

The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF).

If you specify the dash (-), this parameter information is automatically supplied.

Example of a fully qualified pair: IBM.1750-68FA150/0100:IBM.1750-68FA120/0100

Example of a shortened version: 0100:0100

Example of multiple pairs: 0101:0101 0102:0102 0103:0103

Example (1750)

Invoking the failoverpprc command

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

The resulting output

A confirmation message is presented for each remote mirror and copy pair that is successfully suspended.