failbackpprc

Parameters

-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, which includes the storage image ID, for the source volume IDs that are defined by the Source_Volume_ID:Target_Volume_ID parameter.

Note: The use of the failbackpprc command requires that this parameter reflect a role reversal. The value for this parameter must be the original primary site which has been repaired and is ready to once again become your primary production site. For example:

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

  (1750) dscli>failbackpprc -dev IBM.1750-685FA120
  -remotedev IBM.1750-68FA150  
  0100:0200 0101:0201 0102:0202 0103:0203

-remotedev storage_image_ID

(Optional). Specifies the target storage image ID, which includes manufacturer, type, and serial number. The -remotedev parameter identifies the remote storage unit that contains the target volume IDs that are defined by the SourceVolumeID:TargetVolumeID parameter. The -remotedev 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 failbackrpprc 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.
• Original secondary site (Site B) has a value of (1750) IBM.1750-68FA150 with volumes 0200, 0201, 0202, 0203.
• The following failbackpprc command is correct:

  (1750) dscli>failbackpprc -dev IBM.1750-685FA120
  -remotedev IBM.1750-68FA150  
  0100:0200 0101:0201 0102:0202 0103:0203

-type mmir | gcp

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

mmir

Metro Mirror maintains the remote mirror and copy relationship in a consistent manner by returning the I/O write completion status to the application 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. I/O write completion status is returned to the application 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.

-cascade

(Optional) Specifies that the remote mirror and copy target volume can also be a remote mirror and copy source volume of a different remote mirror and copy volume relationship.

-suspend

(Optional) Specifies that the remote mirror and copy relationship be suspended when the task completes.

Notes:

1. This parameter is not valid for a Global Copy (Extended Distance) remote mirror and copy volume relationship.
2. This parameter is not valid for a Metro Mirror (Synchronous) remote mirror and copy volume relationship that is established with the No Copy option activated.

-tgtonline

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

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

-resetreserve

(Optional) Specifies that a remote mirror and copy relationship be established when the volume on the secondary logical subsystem is reserved by another host. If this parameter is not specified and the volume on the secondary logical subsystem is reserved, the command fails.

Note: This parameter applies only to fixed block volumes.

-tgtread

(Optional) Specifies that host servers be allowed to read from the remote mirror and copy target volume. For a host server to read the volume, the remote mirror and copy pair must be in a full-duplex state.

Note: This parameter applies only to Open System volumes.

-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.

Note: The source and target volumes are restricted to one LSS for the source and one LSS for the target when you specify ss_IDs.

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.

Note: The source and target volumes are restricted to one LSS for the source and one LSS for the target when you specify ss_IDs.

Example: 0010

SourceVolumeID:TargetVolumeID . . . | -

(Required). Specifies the remote mirror and copy volume pair IDs for the source and target volume pairs that are to undergo failback processing. The original values (before the disaster) return with the source volume IDs equal to the A volumes and the target volume IDs equal to the B volumes.

This parameter 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 volume 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 (for 1750) , 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-68FA120/0100:IBM.1750-68FA150/0100

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