Point-in-time recovery using the RECOVER utility

Within certain limitations, the RECOVER utility can use system-level backups that you created by using the BACKUP SYSTEM utility for object-level recoveries.

The BACKUP SYSTEM utility invokes the DFSMShsm fast replication function to take volume level backups using FlashCopy®. The RESTORE phase of the RECOVER utility is faster if you use these backups, because Db2 table spaces and index spaces can be restored by using FlashCopy. You might need to change some utility control statements to use FlashCopy technology for the LOAD utility, the REORG utility, and the REBUILD INDEX utility.

If any of the following utilities were run since the system-level backup that was chosen as the recovery base, the use of the system-level backup by the RECOVER utility is prohibited:

REORG TABLESPACE
REORG INDEX
REBUILD INDEX
LOAD REPLACE
RECOVER from image copy or concurrent copy

In these cases, the recovery terminates with message DSNU1528I and return code 8.

Note: The RECOVER utility can use a system-level backup, even if the REBUILD INDEX, RECOVER, REORG, and LOAD utilities ran after the system-level backup was created. The RECOVER utility has been modified so that you can use system-level backups, even if a data set has moved since the backup was created.

For a partition-by-growth table space, a point-in-time recovery is not allowed if the recovery period includes REORG TABLESPACE deleting empty partitions. REORG TABLESPACE can delete the highest numbered partitions if they are empty and the REORG_DROP_PBG_PARTS subsystem parameter is set to ENABLE or if the DROP_PART YES keyword is specified.