If you specify a volume used in cascade copy as the copy source and then execute a Concurrent OPC by the swsrpmake command, it may not be possible to preserve the sequence of data updates across multiple volumes.
In this case, an error message is displayed and the command terminates in an error.
If the error cannot be resolved by responding to the message, we recommend you change the operating method of Advanced Copy or reconfigure the system.
If you cannot change the operating method of Advanced Copy or reconfigure the system, create a file (check.ini) that sets the sequence of data updates across multiple volumes. Then, disable sequence preservation before you retry Concurrent OPC. The sequence of data updates is not preserved across multiple volumes.
Create check.ini in the following path of the server on which to execute the swsrpmake command:
In a non-cluster environment
/etc/opt/FJSVswsrp/data/DEFAULT |
In a cluster environment
/etc/opt/FJSVswsrp/logicalNodeName/data/DEFAULT |
Section Name | Key Name | Value |
|---|---|---|
[check] | ConcurOPCCascade | Set preservation of the sequence of data updates across multiple volumes. |
[Example for disabling sequence preservation]
[check] ConcurOPCCascade=No |
Point
For any of the below ETERNUS Disk storage systems, Concurrent OPC can be executed regardless of sequence preservation of data updates. However, the sequence of data updates is not preserved across multiple volumes.
ETERNUS DX80 S2 (for earlier than V10L30 firmware)
ETERNUS DX90 S2 (for earlier than V10L30 firmware)
ETERNUS DX400 S2 series (for earlier than V10L30 firmware)
ETERNUS /DX8000 S2 series (for earlier than V10L30 firmware)
If the SnapOPC+ replication process is stopped, the deletable snap generations and the results of the swsrpcancel command vary depending on factors such as the firmware version of the storage device and the volume type of the copy destination volume. Refer to "6.1.1.3 Deletable SnapOPC+ Snap Generations" for details.
To prevent necessary sessions from being stopped, confirm that the target storage device, its firmware version, the volume type of the copy destination volume, and the snap generation are all correct before stopping SnapOPC+.
