BACKOUT recovery
A backout recovery backs out log records to undo or redo the changes that occurred between the selected point in time and the current point.
This method returns the spaces and indexes to the required state without the overhead of restoring image copies, or rebuilding or restoring indexes. A backout recovery does not require image copies to perform a point-in-time recovery. In most cases, the BACKOUT recovery strategy is dramatically faster than traditional forward recovery. For more information about the BACKOUT option, see the BMC AMI Recover for Db2 documentation.
BACKOUT recovery requires that spaces be undamaged and not be in RECP, RECP*, RBDP, RBDP*, PSRCP, PSRBD, GRECP, WEPR, or STOPE status or have an LPL range. BACKOUT also cannot be used for the following spaces:
- LOB spaces
- NOT LOGGED spaces
You can also use BACKOUT when you choose IBM Db2 RECOVER (DSNUTILB) as the recovery utility. The default value is NO. BACKOUT with DSNUTILB has the same restrictions as BACKOUT with BMC AMI Recover.
If DSNUTILB is selected as the recovery utility and the Db2 version is less than Version 10, BMC AMI Recovery Manager changes BACKOUT to NO and continues.
When you specify the backout to forward recovery strategy by using BACKOUT AUTO, BMC AMI Recovery Manager generates JCL that causes BMC AMI Recover to perform back out recoveries for eligible objects and forward recoveries for any objects that cannot be backed out. This strategy provides the fastest possible recovery of your objects. The BACKOUT AUTO strategy is a feature of and is the default value for the BMC AMI Recovery for Db2 solution and requires a valid Recovery Management for Db2 solution password. For more information, see the Recovery Management for Db2 documentation.
Related topic