Making Instant Snapshot copies
BMC AMI Copy works with DSNUTILB to generate certain catalog and directory Instant Snapshot copies of the following spaces:
- DSNDB06.SYSCOPY/SYSTSCPY
- DSNDB01.DBD01
- DSNDB01.SYSDBDXA
- DSNDB01.SCT02
- DSNDB01.SPT01
- DSNDB01.SYSDBDXA
- DSNDB01.SYSUTILX
BMC AMI Recover for Db2 also works with SUF or XBM to perform very fast recoveries using Instant Snapshot copies. For more information about the recovery of Instant Snapshot copies, see the BMC AMI Recover for Db2 documentation and the BMC AMI Recovery Manager for Db2 documentation. The data sets created by Instant Snapshots are always cataloged in the ICF catalog. These data sets are VSAM linear data sets and are physical copies of the original Db2 data set.
Instant Snapshots are specified in BMC AMI Copy by using the DSSNAP option on the OUTPUT command, which has the following valid values:
- DSSNAP NO, the default, indicates that standard copies--not Instant Snapshots--are made.
- DSSNAP YES makes Instant Snapshots.
DSSNAP AUTO makes Instant Snapshots if possible, but falls back to a standard copy if necessary (for example, XBM or the required hardware is not in place).
If the Instant Snapshot is a local primary, it will be registered in SYSCOPY. Otherwise, it will be registered in BMCXCOPY, as Db2 utilities only support local primary Flash Copies.
The COPY IMAGECOPY command makes standard full image copies from Instant Snapshot copies (COPY-IMAGECOPY-command). BMC AMI Copy selects the primary copy to use as the source for COPY IMAGECOPY based on the value specified for the ATRBA or ATLOGPOINT option.
So in addition to making quick copies for local recoveries, Instant Snapshots enable you to make standard image copies for disaster recovery or migration.
Note that BMC AMI Copy turns off COPY-pending status if only an Instant Snapshot is made, even though Db2 might not be aware of the copy.