Making copies from the log and earlier copies

You can use BMC AMI Recover to make updated image copies from typical recovery resources such as earlier copies, change accumulation files, and Db2 logs.

The following figure shows BMC AMI Recover using a full copy, multiple incremental copies, a change accumulation file (created by using R+/CHANGE ACCUM for Db2), and Db2 log files to produce an updated full image copy.

Related topics

Recovering a dropped table space or table

Moving-an-application-to-another-subsystem-with-index-rebuilding

GUID-6C5150CD-2250-4131-B928-FB7701B2CBBC-low.pngDuring an OUTCOPY ONLY operation, BMC AMI Recover writes the output to a sequential image copy data set instead of a Db2 space. This process allows you to make copies without accessing the Db2 space or interfering with normal Db2 access in any way. If you elect to end the process at any of the following points, BMC AMI Recover registers the new copy, if it is registered, as a SHRLEVEL REFERENCE full image copy:

  • The log point of a SHRLEVEL REFERENCE incremental copy
  • The log point of a quiesce point
  • The log point of the last -ARCHIVE MODE(QUIESCE) command
  • The last successful subsystem shutdown (in a non-data sharing environment)

In all other cases, BMC AMI Recover registers the new copy as a SHRLEVEL CHANGE copy.

This section provides examples of using the BMC AMI Recover product to create image copies.


 

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