The
symclone create commands defines the clone copy session requirements and sets the track protection bitmap on the source device to detect which tracks are being accessed by the target host or written to by the source host.
Data begins copying in the background when the clone session is activated and a full copy will become available to the host. While background copying, the state of the device pair is
CopyInProgress. When the operation completes, the state goes to
Copied. However, once the session is activated, the data is available immediately to the target host.
Examples
To create a clone copy session between source device and target device in group
ProdDB, enter:
symclone -g ProdDB create
Rules and restrictions
The following rules and restrictions apply to a clone copy:
The target device is made
Not Ready to its host and placed on hold status for clone copy session activity. This prevents other control operations from using the device.
The device pair state transitions from
CreateInProgress to
Created when complete.
A device pair cannot be verified that it is in the
CreateInProgress state. After the copy session completes, issue a
symclone verify -created command to verify that the clone pair is successfully created.
If a copy session is created and not activated, it can be terminated. However, the data on the target device should be considered invalid.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\