This section describes how to prepare the backup volume.
The backup unit of AdvancedCopy Manager is a slices. In AdvancedCopy Manager, the device which stores the transaction data used as the candidate for backup is called the transaction volume.
The backup volume size must be exactly the same number of bytes as that of the transaction volume.
The number of backup volumes is determined by whether snapshot fast backup or synchronized high-speed backup is performed:
Backup | Number of required backup volumes |
|---|---|
Snapshot fast backup | Number of backup generations |
Synchronized high-speed backup | Number of backup generations + 1 |
When backup policies have already been set for multiple transaction volumes, the registration of a backup policy for a newly registered transaction volume requires that the following number of backup volumes be registered beforehand:
Backup | Number of required backup volumes |
|---|---|
Snapshot fast backup | Total number of backup generations in the registered backup policies + number of generations in the new backup policy being set |
Synchronized high-speed backup | Total number of backup generations in the registered backup policies + number of registered transaction volumes + number of generations in the new backup policy being set + 1 |
For information on configuring a backup volume, see "4.4.7 Setting the operation type for a device".
Note
Do not configure AdvancedCopy Manager to backup a system slice or a slice where AdvancedCopy Manager is installed.
Note
Slices must be allocated for backup volumes in the following manner:
Create slices without a VTOC.
No slice may be duplicated on the same disk.
In a backup volume, there is no need to create a slice for a whole volume, such as slice2.
Point
If the number of backup volumes that can be prepared in synchronized high-speed backup is only the number of preservation generations, the backup operation can be carried out by saving the backup volumes to secondary media, such as tapes.
To do this, follow the procedure below:
Start backup synchronization.
Confirm the equivalency maintain status.
Execute backup.
Save the backup volumes to secondary media.
Delete history information.
Return to step 1.
Be aware that, if any history information is deleted for any reason, the restore execution command cannot be used to restore data from the period beginning with the time of deletion until the time the next backup is completed inclusive. In this event, the data must be restored directly from the secondary media where applicable.
Note
Note the following points when performing backup to a backup volume in a cabinet that is not the same as the cabinet containing the transaction volume.
The ETERNUS storage system must support the REC or ROPC function.
Both cabinets must be connected to an FCRA (FC Remote Adapter).
Since data flows only from the Initiator side to the Target side through an FCRA connection, FCRA connections must be established in minimum sets of two. In a backup operation involving an ETERNUS storage system that does not support the ROPC function (and only the REC function can be used), backing up data to a backup volume in a cabinet containing no transaction volume is impossible since the backup operation uses the ROPC function during restoration.
