| BMC AMI Recovery Managerdefault | |
|---|
| | Specifies the recovery point, as follows: Current—recovers to the current time If you do not specify a recovery strategy, BMC AMI Recovery Manager uses the most recent full and incremental copies to recover the spaces, then applies log records to make the spaces current. If you are using BMC AMI Recover, you can specify Log Sort to merge the image copy records with the log records before they are applied to the spaces. Image Copy—recovers to a specified full or incremental image copy that is registered in SYSIBM.SYSCOPY This option is used in conjunction with the Full copy only and the Copy or quiesce fields. Important DFSMS concurrent copies that are registered in SYSIBM.SYSCOPY are counted as an image copy.)
|
| | Quiesce—recovers to a specified quiesce point that is registered in SYSIBM.SYSCOPY by the DB2 QUIESCE command This option is used in conjunction with the Copy or quiesce field. Important The RBA for the quiesce point is not the same for all objects unless Db2 performed a quiesce on all of the objects in the object set at the same time. - Common recovery point— recovers to a valid previous recovery point for a number of objects in the current object set. BMC AMI Recovery Manager analyzes the log to locate valid recovery points for objects in the object set within a specified date and time range, then displays the recovery points as a list. From the list, you can perform the following tasks:
- Select a recovery point. Only objects for which the point is valid are recovered.
- Obtain a list of objects for which the point is valid (hits).
Obtain a list of objects for which the point is not valid (misses). Important If you are generating JCL in batch mode, the ARMBGEN program considers only common recovery points that have no misses. (A miss indicates that one or more objects in the object set do not have a share level reference image copy, a quiesce, or are within a quiet range at a given point.) In contrast, online JCL generation gives you the opportunity to select a common point that has one or more misses.
|
| | - Specific LOGPOINT—recovers all recoverable objects in the object set to a specified RBA or LRSN. You must supply the appropriate 12-digit hexadecimal value in the To LOGPOINT field.
- Restart RBA— recovers to the RBA of the last disaster recovery point.
- Timestamp—recovers to a user-specified timestamp and resolves inflight units of work. (Recovery Management for Db2 solution only)
- Logmark—recovers to a user-specified log mark and requires the use or BMC AMI Recover version 9.1.00 or later as the recovery utility. (Recovery Management for Db2 solution only)
|
| | Specifies whether to use only full copies for recovery If you select this option, BMC AMI Recovery Manager ignores all incremental copies and recovers to the full copy that you specify in the Copy or quiesce field. |
| | Specifies the copy, quiesce point, common point, or log mark to which to recover Provide a value from 0 to 99, where 0 represents the most recent copy, quiesce, common point, or log mark. Used in conjunction with Current, Image Copy, Quiesce, or Logmark. |
| | Specifies the timestamp for the recover |
To Timestamp Current minus hours n (SPE2110) | | Specifies the number of hours to subtract from the current TIMESTAMP. The valid values are from 1 to 960. This option is mutually exclusive with CURRENT_MINUS_DAYS n. |
To Timestamp Current minus days n (SPE2110) | | Specifies the number of days to subtract from the current TIMESTAMP. The valid values are from 1 to 40. This option is mutually exclusive with CURRENT_MINUS_HOURS n. |
| | Specifies the RBA or LRSN to which to recover Provide a 12-digit hexadecimal value of an RBA or LRSN. Used in conjunction with Specific LOGPOINT. |
| | Specifies the name of the log mark for recover |
| | Specifies whether to resolve inflight units of work when recovering to a log point or a log mark. |
| | Specifies a return code that ARMBGEN should issue if it encounters an object that cannot or will not be recovered. Valid values are 0 through 254, and the default value is 4. |
| | This option specifies the email entry name. he entry name must pass the same validation as a validation as a PDS member name. In this option, n must be a number from 0 through 254. If the ARMBGPV return code is greater than or equal to the EOJ_RC value, an End of Job email is sent. |
| | Use the EMAIL TIME EXCEEDED option to request email notification if email
time exceeded is specified, ARMBGEN completes, and the time estimate
exceeds the time objective. |
| | Applies log records to a data set that has already been restored to a prior point in time You can apply the records to one of the following points: - Backout Auto and Backout Yes overrides Rebuild all indexes and changes it to Rebuild No.
- The current time
- A specified RBA
- A specified LRSN
Important You cannot use the Log Only option when you perform a recovery to a specified copy. |
| | Specifies whether to use local or recovery-site resources for the recovery |
| | Specifies whether the JCL is to be used for local recovery or disaster recovery Important This option is used for mirroring support only. To invoke mirroring for a object set, the JCL type must be DR. |
| | Analyzes SYSLGRNX to determine which objects in the selected object sets have not changed since the last backup and then exclude those objects from the recovery Excluding unchanged objects can significantly reduce the amount of time required for recovery. This option is ignored for recover to current and for sitetype recovery. Important Organizations with heavy update activity may experience contention on SYSLGRNX when this option is used. |
| | Enables you to print a recovery plan before executing the recovery, as follows: - Yes— prints a recovery plan and generates JCL for recovery. Information includes
- Names of any required image copy data sets
- Names of any required log data sets
- Log ranges, if any
- Phases that will occur during execution
- Number of log pages to be read
- Record sizes for index sort work data sets
- Steps to occur within each phase
- No—prints only the information in the first four bullets and generates JCL for recovery.
- Only—execution terminates after the information is printed.
|
| | Simulates recovery for the objects in the object set or object sets (requires the Recovery Management for Db2 solution password) The recovery simulation feature simulates all aspects of recovery up to, but not including, the actual I/O. For more information about recovery simulation, see the Recovery Management for Db2 documentation. |
| BMC AMI Recovery Manager only: No Recovery Management: Auto | Invokes the BACKOUT strategy for BMC AMI Recover or IBM Db2 RECOVER (DSNUTILB) (depending on which recovery utility you selected) for point-in-time recovery Specify one of the following choices: - Yes—backout recovery for all objects in the object set
- No—do not perform backout recovery
- Auto— backout-to-forward recovery strategy (requires the Recovery Management for Db2 solution password. For point-in-time recoveries when you use Recovery Management, see BACKOUT-recovery.) BACKOUT AUTO is the default value. Backout Auto is not valid with DSNUTILB.
Be aware of the following issues: - To use Backout Auto or Backout Yes, you must specify Quiesce, Common recovery point, or Specific LOGPOINT, or Timestamp as the recovery point. If you specify Current (the default), BMC AMI Recovery Manager overrides Backout Auto and converts the option to Backout No.
- Backout Auto overrides the Outcopy by Recover option and uses the copy utility that you specified in the general backup options panel. (If you selected BMC AMI Recover - OUTCOPY as the copy utility on the general backup options panel, the product uses DSNUTILB.)
- Backout Auto overrides Unloadkeys and proceeds with the backout. If you specify Backout Yes with Unloadkeys, an error message is issued and you must change one option or the other to continue.
|
| | - Backout Auto and Backout Yes overrides Rebuild all indexes and changes it to Rebuild No.
- Logscan Yes overrides Backout Auto and changes it to Backout No. BMC AMI Recovery Manager issues a warning message.
Backout recoveries cannot be performed on the following objects: - LOB spaces
- NOT LOGGED spaces
If you specify Backout Auto, these spaces will be recovered by the forward recovery method. If you specify Backout Yes, BMC AMI Recovery Manager issues an error message.
|
| | Generates the CLONES ONLY option in the recovery JCL syntax The CLONES ONLY option causes clone objects to be included in the recovery and non-cloned objects and clone bases to be excluded. This option is displayed only when running on Db2 Version 10 or later and is not valid with compatibility mode. |
| | Specifies whether to recover to an independent outspace and not the table
spaces. To use this option, you must have BMC AMI Recover. - Model—BMC AMI Recover uses a default model if you do not enter a value.
(SPE2104 ) To SSID—BMC AMI Recover fills in the local objects DBID, PSID, and OBID. If the target Db2 is on the same LPAR and active, then DBID, PSID, and OBID are also filled in.
|