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

The BACKOUT option invokes the backout strategy for point-in-time recovery by using log points (TORBA, TOLOGPOINT). This strategy assumes that spaces are undamaged and that you require a reset to a specific point in time. The spaces and the log records between the point in time and the current point are used to back out to the required state. LOGSORT is required to properly order the log records.

Note

The space must 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 LOB spaces or for spaces having a logging attribute of NOT LOGGED.

If you do not specify BACKOUT on the OPTIONS command, BMC AMI Recover uses the value of the BACKOUT installation option (BACKOUT=AUTO), which has a default value of AUTO. If you are not using a Recovery Management for Db2 password, point-in-time recoveries use a standard forward recovery.

The BACKOUT option causes all point-in-time recoveries specified in the SYSIN to use the backout strategy. If the BACKOUT option is specified on the OPTIONS command statement and all of the RECOVER command statements in the SYSIN are for a recovery to the current point in time, the BACKOUT option is ignored.

If you specify the BACKOUT option on the OPTIONS command statement and the SYSIN contains at least one object being recovered to a specific point in time, all objects being recovered in the SYSIN must be recovered to a point in time. If none of the objects are being recovered to a point in time, BACKOUT on the OPTIONS command statement is ignored. For a detailed discussion of the backout recovery strategy, see Strategies for point-in-time recovery.

Note

If a table space is recovered to a specific point in time by using BACKOUT and an associated index is recovered without specifying a TOLOGPOINT, TORBA, or TOCOPY keyword in the same SYSIN, the index is recovered with BACKOUT to the same point in time as the table space.

ValueDescription

BACKOUT AUTO

BACKOUT AUTO supports the Recovery Management for Db2 backout to forward recovery feature.

The BACKOUT AUTO option invokes the recovery strategy in which all of the PIT recovery requests are first executed using the BACKOUT option. If any BACKOUT request fails, forward recovery is performed for the objects that were not backed out. This automation produces the fastest possible recovery with minimal intervention and is only available using the Recovery Management for Db2 solution.

Note

  • The BACKOUT AUTO option requires a Recovery Management for Db2 solution password.

  • Generate BACKOUT AUTO syntax by using the BMC AMI Recovery Manager for Db2 component of the Recovery Management for Db2 solution.

For more information BACKOUT AUTO recovery, see the Recovery Management for Db2 documentation .

BACKOUT NO

BACKOUT NO specifies that you want to perform standard forward point-in-time recoveries.

BACKOUT YES

BACKOUT YES invokes the backout strategy for point-in-time recovery by using log points (TORBA, TOLOGPOINT). This strategy assumes that spaces are undamaged and that you require a reset to a specific point in time. The spaces are used with the log records between the point in time and the current point to back out to the required state. Using BACKOUT may enhance the performance of a point-in-time recovery significantly. However, if the backout recovery fails, BMC AMI Recover stops with an error. (As opposed to BACKOUT AUTO, which will move to forward recovery if the backout recovery fails.) For more information, see Using BACKOUT.

The following restrictions apply:

  • The space must be current as of the last logged activity and not damaged in any way. Multiple-data set, nonpartitioned spaces must have all data sets scanned (DSNUM ALL).

  • No LOAD or REORG events can exist between the log point specified and the current log points. For indexes, no REBUILD INDEX events can exist in this range.

  • No prior point-in-time recovery with a START_RBA greater than the log point requested and a PIT_RBA less than the log point requested can exist.

  • BACKOUT may not be requested with LOGONLY or LOGAPPLY ONLY.

    Note

    BACKOUT uses only logs and spaces but requires that the spaces be current. The LOGONLY and LOGAPPLY ONLY options imply scanning log records going forward by using a space restored to a previous state.

  • Change accumulation files are not allowed with BACKOUT because they are not properly ordered. Output accumulation files are also not supported because they are defined from the point of the last image copy to the current point.

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

Comments