resyncremoteflash

The resyncremoteflash command (formerly called the incremoteflash command and associated with the incremental FlashCopy process) increments an existing remote FlashCopy pair that has been established with the -record and -persist parameters.


>>-resyncremoteflash--+-------------------------+--------------->
                      '- -dev--storage_image_ID-'   

>-- -conduit--LSS_ID--+----------+--+-----------+--------------->
                      '- -record-'  '- -persist-'   

>--+----------+--+-----------+--+--------------+---------------->
   '- -freeze-'  '- -tgtpprc-'  '- -tgtoffline-'   

>--+--------------+--+------------------------------+----------->
   '- -tgtinhibit-'  '- -seqnum--flash_sequence_num-'   

>--+----------------+------------------------------------------->
   '- -srcss--SS_ID-'   

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

Parameters

Note: When a pair is established with the -record and -persist parameters, the pair initially synchronizes and then a record of all data that is written from the host to the source is maintained in the source volumes. When the resyncremoteflash command is issued on the pair, the new data that is written to the source is copied to the target. The specified parameters in this command replace the parameters in the existing relationship. In order to keep the initial -record and -persist parameter values, the -record and -persist parameters must be specified using the resyncremoteflash command.

-dev storage_image_ID: (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes or you do not specify a value for the devid variable in your profile file.; Example: IBM.1750-68FA120
-conduit LSS_ID: (Required) Specifies the source logical subsystem (LSS) of an existing remote mirror and copy relationship that is to be used as a means for communicating with the remote storage image. The source volume IDs that are specified in the SourceVolumeID:TargetVolumeID parameter, must serve as secondary volumes in a Remote Mirror and Copy relationship in which one of the conduit LSS volumes serves as a primary volume.; When you use this parameter, you must specify a fully qualified LSS ID. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only).; Example: IBM.1750-68FA120/00
-record: (Optional) Specifies that the changed tracks on both volumes within a FlashCopy pair be recorded. Select this parameter if you intend to use the resyncremoteflash command again with this pair. The -persist parameter is automatically set in the code when the -record parameter is specified.
-persist: (Optional) Specifies that the FlashCopy relationship be retained after the background copy completes. The FlashCopy relationship between the source and the target volumes remains indefinitely until you issue a rmremoteflash command. This parameter is automatically set in the code when the -record parameter is specified.; Specify this parameter along with the -record parameter if you intend to use this volume pair with the resyncremoteflash, reverseremoteflash, or setremoteflashrevertible commands.
-freeze: (Optional) Specifies the Freeze Consistency Group condition. This option causes the source volume to be busy (Queue Full status on Open Systems) to all host I/O operations until a FlashCopy Consistency Group Created command is received. All writes to the source volume are queued by the host and are written after the Consistency Group Created command is complete.; During the busy condition, the source volume reports Queue Full for fixed block volumes and busy status for CKD volumes.; The busy condition can also be reset by an extended long busy timeout (default 120 seconds). The timeout condition affects all FlashCopy source volumes that are contained within a respective logical subsystem and that are established or modified with the -freeze parameter.; Note: This parameter is used in conjunction with other processing steps for purposes such as backups, testing, or recovery solutions. The use of this parameter ensures that volumes on the target LSSs are consistent with the source LSSs volumes.
-tgtpprc: (Optional) Allows the FlashCopy target volume to be a remote mirror and copy source volume.
-tgtoffline: (Optional) Causes the resyncremoteflash command to be rejected if the target volume is online for host system access.; Note: This parameter applies only to count key data volumes.
-tgtinhibit: (Optional) Prevents host system write operations to the target while the FlashCopy relationship exists.
-seqnum flash_sequence_num: (Optional) Associates the FlashCopy relationships that are established with the specified sequence number. You can use this sequence number as an identifier for a relationship or group of relationships. Only the relationships that are modified successfully by the resyncremoteflash command are assigned the specified sequence number, leaving the ones that fail with the previous one (if they were previously specified).; This parameter is not supported for machine type 2105.; Example: 0010
-srcss SS_ID: (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. The subsystem ID is a four-digit hexadecimal number in the range (0001 - FFFF). When this parameter is used, all source volumes must be designated within the same logical subsystem.; This parameter is required for IBM System Storage™ Enterprise Storage Server versions 2.4.0 and 2.4.1.; Example: FF10
SourceVolumeID:TargetVolumeID . . . | -: (Required) Specifies that a remote FlashCopy relationship for the source and target volume pairs be incremented with the designated IDs. 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,; A FlashCopy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy 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 FlashCopy pair ID: IBM.1750-68FA120/0001:IBM.1750-68FA120/0004; Example of a shortened version: 0001:0004; Example of multiple pairs: 0001:0004 0003:00FF 0008:000C

Example (1750)

Invoking the resyncremoteflash command

dscli>resyncremoteflash
 -conduit IBM.1750-68FA150/10 IBM.1750-68FA120/0100:IBM.1750-68FA120/0200

The resulting output

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0  
DS: IBM.1750-68FA120

Remote FlashCopy volume pair 0100:0200 successfully resynchronized.
 Use the lsremoteflash command to determine copy completion.

Note: This message is returned before the copy completes.