Skip to Content

Recovery using cumulative incremental image copies

By using BMC AMI Copy, you can merge incremental image copies while retaining the previous incremental copies in SYSIBM.SYSCOPY (BMCXCOPY for incremental index copies) by specifying CUMULATIVE YES KEEP YES. If you specify these options for an incremental copy, the previous copy is registered as ICTYPE=i. This copy is referred to as a cumulative copy. For incremental copies of table spaces, to make this copy available for IBM Db2 RECOVER you must run the BMC AMI Copy RECALL job to set ICTYPE=I.

Related topics

Serialization-and-concurrency-issues

Using-incremental-index-image-copies

If a space is recovered to the current point, 

BMC AMI Recover

 ignores incremental copies with ICTYPE=i. If a space is recovered to a prior point in time, 

BMC AMI Recover

 recognizes any incremental copies with ICTYPE=i that would be useful for the recovery.

For example, if you are recovering to a cumulative incremental copy, BMC AMI Recover treats the cumulative incremental copy as a true copy (ICTYPE=I). If you are recovering to a specific log point and a cumulative incremental copy exists prior to that log point, BMC AMI Recover merges the cumulative incremental copy with the full copy before applying the log. Fallback processing also recognizes cumulative incremental copies and uses those copies as necessary.

For more information about the CUMULATIVE, KEEP, and RECALL options, see BMC AMI Copy for Db2 documentation.


 

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

BMC AMI Recover for Db2 13.1