Recommended practices for making incremental image copy practices
We recommend the following practices for making incremental image copies.
Options for making incremental copies
The options you choose when making incremental copies determine the efficiency of the process.
We recommend the following options:
- If your full image copies are made using RESETMOD YES, use FULL AUTO (or CHANGELIMIT or FULL NO) READTYPE AUTO and RESETMOD NO for your incremental copies.
- If your full image copies are made using RESETMOD NO, use FULL NO READTYPE FULLSCAN and RESETMOD NO for your incremental copies.
- If you want to make merged incremental copies, use CUMULATIVE YES. If you do not want to merge the copies, use CUMULATIVE NO.
- If you use SHRLEVEL CHANGE, use QUIESCE AFTER to establish a good recovery point, if you anticipate that you might need to recover to a prior point-in-time.
- For partitioned spaces, image copies should be made either by table space or by partition but not by both.
Restarting an incremental copy job
For compatibility with IBM Db2 COPY, BMC AMI Copy does not allow a phase restart for incremental copy jobs.
When you use IBM Db2 COPY in the original execution of an incremental copy job, some modified-page indicators might be reset. If the job is restarted at the beginning of the failed phase, those pages with reset modified-page indicators are not included in the copy, so making the copy invalid.
RESTART(PHASE) or NEW/RESTART(PHASE) are not allowed for an incremental image copy; instead, use any other suitable restart parameter. Restarting-a-failed-BMC-AMI-Copy-job provides information about recommended restart procedures.