administration facility. The backup duplex copy is created at the same time as the backup copy.
Each copy will contain a single
‘A’ copy: | ‘hlq.Gnnnnn’ |
‘B’ copy: | ‘hlq.Bs.Gnnnnn’ |
‘C’ copy: | ‘hlq.Cs.Gnnnnn’ |
‘D’ copy: | ‘hlq.Ds.Gnnnnn’ |
where | ‘hlq’ is the |
| during Archive Manager database definition processing (see |
| “Define Archive Manager databases” on page 27). |
| ‘s’ is the storage level |
and | ‘nnnnn’ is the sequence number of the dataset within the |
| Archive Manager database. |
Objects are always written to storage level 0 when first migrated to tape. They may subsequently be moved to other storage levels via execution of the Archive Manager object management utility.
Archive Manager also provides a facility (via its database administration process) to automatically control the tape cartridge devices to be used to create each copy during the object migration or backup process
(eg) | ‘A’ copy to primary library location. This copy of the database |
| will be used for normal production access. |
| ‘B’ copy to offsite location. This copy of the database will be |
| used for disaster recovery purposes. |
| ‘C’ copy to alternate onsite location. This copy of the database |
| will be used for recovery after loss of an individual volume. |
| This location may be in another library storage module, for |
| automated recovery access, or on a |
| eventual shelf storage. |
Note that if duplexing during archival is enabled for the Archive Manager database, then a duplex tape volume will be created concurrently with the primary tape volume during database update processing. In some circumstances (e.g. if the duplex volume is created at a remote offsite location) it may not be necessary to execute the Archive Manager database backup utility. Refer to the Archive Manager User Manual for full information on these considerations.
Archive Manager database recovery
90 | DB2 Manager User Guide |
| StorageTek Proprietary |
