This section provides notes on snapshot backup operation.
Number of Required Backup Volumes
Snapshot high-speed backup requires as many backup volumes as the number of specified backup generations. Accordingly, snapshot backup is disabled if:
All the specified number of generations have been backed up, and
There is no new volume that can be used as a backup volume.
Simultaneous Backups
Performing snapshot high-speed backup simultaneously with the same transaction volume specified will perform two backups in parallel.
However, performing snapshot high-speed backup simultaneously more often than the number of preservation generations will cancel the backup operations starting from the oldest one. In other words, you cannot perform more simultaneous backups than the specified number of generations.
SDX Object Backup Operation
If the transaction volume is an SDX object, the backup operation may encounter a hardware problem. In this case, change the backup operation as follows:
Start the Web Console. For more information, refer to "3.4.2 Starting the Web Console".
Fetch all the device information from the Managed Server whose backup operation you wish to change. When you fetch device information, the system will detect a device with the same name as an SDX object whose backup operation can no longer be continued. Move the device to the [Additional instruction device] field. For information on fetching device information, refer to "3.4.4 Fetching device information on a Managed Server". At this time, do not delete the original SDX object that is displayed in the [Device not detected] field.
Set the added SDX object as a transaction volume. For more information, refer to "3.4.6 Setting the operation type for a device".
Set a backup policy for the added SDX object. For more information, refer to "3.4.7 Setting a backup policy".
After specifying the added SDX object, perform the backup.
Notes on combining cascade copy and Concurrent OPC in operation
If you specify a volume used in cascade copy as the copy source and then execute a Concurrent OPC by swsrpmake (Replication creation command), it may not be possible to preserve the sequence of data updates across multiple volumes.
In this case, an error message will be 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 will not be preserved across multiple volumes.
Create check.ini in the following path of the server on which to execute swsrpmake (Replication creation command):
In a non-cluster environment
<Environment directory>\etc\repl\data\DEFAULT |
In a cluster environment
<Environment directory for logical node>\etc\repl\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 will not be preserved across multiple volumes.
ETERNUS DX80/DX80 S2 (for firmware version numbers before V10L30)
ETERNUS DX90/DX90 S2 (for firmware version numbers before V10L30)
ETERNUS DX400/DX400 S2 series (for firmware version numbers before V10L30)
ETERNUS DX8000/DX8000 S2 series (for firmware version numbers before V10L30)
