Registration of Instant Snapshots

BMC AMI Copy registers a local primary Instant Snapshot copy as a FLASHCOPY in the SYSCOPY table. A separate entry for a local primary copy is not created. If a local backup copy is specified, either as an Instant Snapshot or standard copy, it is registered in BMCXCOPY.

Important

BMC AMI Recover and the IBM RECOVER utility (see IBM Knowledge Center) can recover using an Instant Snapshot if it is compatible with FlashCopy. BMC AMI Recover can recover using Instant Snapshots even if they are not compatible with FlashCopy (for example, EMC SNAP).

If the Instant Snapshot is an Online Consistent Copy, it will be registered in BMCXCOPY.

Local backup, recovery primary and recovery backup Instant Snapshots are registered in the BMC BMCXCOPY table with an STYPE of V. They are not registered in SYSIBM.SYSCOPY because they are not in the standard format for copies and cannot be used by standard Db2 utilities.

Related topics

COPY-IMAGECOPY-command

COPY-IMAGECOPY-support-for-online-consistent-copies

Operational-considerations

OUTPUT-syntax-options-common-to-disk-and-tape-data-sets

Registering-copies

Registration-of-copies

If a backup copy (LB or RB) is produced, including those made using the COPY IMAGECOPY command, and its associated primary copy (LP or RP) is an Instant Snapshot, and as such, is registered in BMCXCOPY, the backup is also registered in BMCXCOPY, even if it is a standard copy. Likewise, if backup copies (LB or RB) are requested as Instant Snapshots, any associated primary copies (LP or RP) are registered in BMCXCOPY, even if they are standard copies. However, if COPY IMAGECOPY is used to make a new primary copy (LP or RP) when the existing primary copy is an Instant Snapshot, the Instant Snapshot is changed to a backup copy (LB or RB) and the new primary copy is registered in SYSIBM.SYSCOPY.

If an LP copy is an Instant Snapshot and an RP copy is a standard copy, then the LP copy is registered in SYSCOPY as a FLASHCOPY and the RP copy is registered in SYSCOPY.

COPY IMAGECOPY of an Instant Snapshot generates a standard copy in IBM Db2 SYSTEMPAGES YES format and registers the copy in SYSIBM.SYSCOPY with the correct oldest version in the OLDEST_VERSION column. However, COPY IMAGECOPY does not produce an IBM Db2 copy or determine the oldest version for a DSNUM integer or DSNUM DATASET Instant Snapshot copy of a multi-data-set, nonpartitioned index space.

Important

You can use IBM Db2 RECOVER (see IBM Knowledge Center) to recover the sequential copies made by copy image copy of IBM FlashCopy or Online Consistent Copy.

The following table gives some registration examples that result from Instant Snapshot requests. 

Copy request

Registered in SYSCOPY

Registered in BMCXCOPY

DSSNAP YES for LP copy only; COPY IMAGECOPY for LB/RP/RB

FC

RP, RB

LB

DSSNAP YES for RP copy; DSSNAP NO for LP/LB/RB

LP, LB

RP

RB

DSSNAP YES for LB/RB; DSSNAP NO for LP/RP

None

LP

LB

RP

RB

DSSNAP YES for LP copy only (INDEXES YES); COPY IMAGECOPY for LB/RP/RB

FC for table space and index space

RP and RB for table space and index space

LB for table space and index spaces

DSSNAP YES for LP copy only (INDEXES YES)

FC for table space and index space


DSSNAP YES for LP copy only; COPY IMAGECOPY for a new LP copy

FC, LP


If either a local primary (LP) or a local backup (LB) is requested with DSSNAP AUTO and the Instant Snapshot fails (and standard copies are made), all of the copies made are registered in SYSCOPY.

For Instant Snapshots, the DSNAME column of BMCXCOPY will contain the VSAM data component data set name (not the VSAM cluster name).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*