The OPC(One Point Copy) function of ETERNUS disk storage systems is used to copy data from a transaction volume to an unused backup volume.
To perform a snapshot fast backup, take the following steps:
Execute swstbackup (Backup execution command) ((1) in the figure below). The following processing will be performed:
If backup volumes under generation management exist for all the generations, the oldest backup volume will be assumed to be unused.
An unused backup volume will be selected from the unused backup volume management area.
Data on the transaction volume will be copied to the selected unused backup volume ((2) to (4) in the following figure).
Backup carrier information will be set.
Figure 4.2 Snapshot fast backup processing
The snapshot fast backup is completed as soon as you confirm the execution of the backup. The actual data copying will be performed internally by the OPC function of ETERNUS disk storage systems.
The QuickOPC function of the snapshot high-speed backup creates a snapshot image by only copying the data updated since the start of previous backup. This reduces the time for physical copying significantly.
For information on the QuickOPC function, see "Chapter 6 Backup Operation by the QuickOPC Function."
Note
If all the generations of backup volumes are being managed, and if no backup volume can be obtained from the unused region in the backup volume management area, backup copies cannot be created.
When the transaction volume is a volume group, copy processing by the OPC/ROPC functions of ETERNUS disk storage systems is performed for the entire physical disk comprising the volume group. Therefore, when two or more logical volumes exist in a volume group, the data contained in all logical volumes is backed up (refer to the following figure).
Note
When using a volume group for backup operation, care needs to be taken with the following points:
When the transaction source volume is a volume group, construct a logical disk whose size matches that of the transaction volume, in a volume group different from the transaction group, and register this volume group whose physical disk size is the same as the transaction volume as the backup volume.
A "4.4.10.1 Describing a device map file" is created to describe the pairing of matching transaction and backup volumes. For details, refer to "4.4.10 Preparing a device map file". A "Device map" is mandatory if you are backing up using a volume group unit.
In backup processing, since the LVM configuration information on the backup volume will be rewritten for the LVM information on the transaction volume, LVM configuration information is restored in the processing after backup. For more information, see "Appendix A Pre-processing and Post-processing of Backup and Restoration".
When backing up a volume group using an account with Administrator authority for backup, modify the scripts used for backup pre-processing and post-processing to unmount/mount all logical volumes in the volume group. For more information, see "Appendix A Pre-processing and Post-processing of Backup and Restoration".
When two or more physical disks exist in the volume group which is registered with a transaction volume, the backup operation will results in an error.
Figure 4.3 Transaction volume and backup volume for two or more logical disks
