Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Backout to forward recovery

The backout recovery strategy of the Recovery Management solution is dramatically faster than most traditional forward recoveries.

This is shown in the figure, Point-in-time recovery (forward recovery versus BACKOUT).

A backout recovery does not require image copies to perform a point-in-time recovery. Instead, it backs out the 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.

When you specify the backout to forward recovery strategy (BACKOUT AUTO) BMC AMI Recovery Manager generates JCL for BMC AMI Recover to perform a backout recovery for objects in the object set. If the backout request fails or is invalid for any object, BMC AMI Recover automatically goes on to perform a forward recovery for that object. BACKOUT AUTO is a feature of the Recovery Management solution and requires the solution password. When you are using a Recovery Management password and do not specify BACKOUT on the OPTIONS statement, a point-in-time recovery defaults to BACKOUT AUTO. (If you are not using a Recovery Management password, a point-in-time recovery defaults to BACKOUT NO.)

BACKOUT is not valid for:

  • LOB spaces

  • NOT LOGGED spaces

  • Hash spaces

For more information about BACKOUT, see the  BMC AMI Recover for Db2 documentation Open link .

Point-in-time recovery (forward recovery versus BACKOUT)

Was this page helpful? Yes No Submitting... Thank you

Comments