Making copies for remote recovery sites

To provide insurance against physical disasters to a data processing center, some installations take one or more image copies of the table space to a remote recovery site that usually houses redundant system resources.

For table spaces, this scenario requires making a copy of the Db2 catalog and other items and taking them to the remote recovery site, along with one or more of the BMC AMI Copy copies of the table space.

Related topic

Using-multiple-copies-in-recovery

For index spaces, the image copies are registered as described in Creating-index-backups. A copy of the appropriate registration table can be taken to the recovery site to track the index backups.

Important

For a full discussion of the requirements for performing a standard Db2 disaster recovery, see the 

BMC AMI Recovery Manager for Db2 documentation

.

Use the RECOVERYDDN option to designate an image copy for recovery site usage. For table spaces, the BMC AMI Recover (or IBM Db2 RECOVER) utility uses the recovery site copies if the Db2 subsystem initialization parameters indicate that the utility is executing at the recovery site.

Alternatively, existing BMC AMI Copy users can use the COPYDDNn installation option to specify which COPYDDN data sets are recovery site copies. This simplifies Db2 migration if copies have already been taken off-site.

Important

We recommend using RECOVERYDDN syntax instead of the COPYDDNn installation options to specify recovery site copies.

 

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