The device operation type must be set before backing up in a Storage Server. This involves the following:
Defining the volume to be backed up as a transaction volume.
Preparing backup volumes. Prepare as many partitions, each with the same size as the transaction volume, as required for the backup type, and define them as the backup volumes:
Backup operation type | Number of required backup volumes |
|---|---|
Snapshot fast backup | Number of backup generations |
Synchronized high-speed backup | Number of backup generations + 1 |
Use "11.2.1.3 acmdevinfoset (Device information setting command)" for this operation.
The following execution example registers a device (/dev/dsk/c1t1d0s6) as the transaction volume and a device (/dev/dsk/c1t2d1s6) as the backup volume.
[For Solaris]
# /opt/FJSVswstc/bin/acmdevinfoset -t /dev/dsk/c1t1d0s6 acmdevinfoset completed # /opt/FJSVswstc/bin/acmdevinfoset -b /dev/dsk/c1t2d1s6 acmdevinfoset completed # |
Note
For notes on setting the device operation type, refer to "Setting the operation type for a device" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
Point
The information on the registered transaction volumes and backup volumes can be referenced using "11.2.1.4 acmdevdisp (Device operating status display command)".
Point
If no more backup volumes than the number of preservation generations can be prepared for synchronous high-speed backup, you can implement backup operation in combination with the backup history deletion function.
The operation procedure is as follows:
Start backup synchronous processing
Confirm the equivalency maintenance status
Execute backup (to both disk and tape)
Delete disk backup history information
Return to step 1
If restoration occurs before completion of the next backup after history information is deleted, backup data is restored from tape because disk history information is not available.
