Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recovery Manager for Db2 13.1.

Overview of full subsystem recovery

This section discusses the use of the automation that the BMC AMI Recovery Manager product provides for the backup and local recovery of an entire Db2 subsystem. 

For information about disaster recovery, see Recovering-from-a-Db2-system-disaster.

Important

BMC AMI Recovery Manager and BMC AMI Recover treat DSNRLST spaces as application spaces, so there is no special processing to free these spaces outside of the STOP. For DSNRLST spaces, you can do a STOP RLIMIT.

BMC AMI Recovery Manager provides an automated process to create object sets and generate backup and recovery JCL for an entire Db2 subsystem or data sharing object set (hereafter simply referred to as a subsystem).

Important

As a component of the Recovery Management for Db2 solution, BMC AMI Recovery Manager supports:

  • Hardware mirroring in full subsystem recoveries
  • Conditional restart avoidance for faster more efficient recoveries

For more information, see Recovery Management for Db2 documentation.

BMC AMI Recovery Manager performs a log range analysis to identify objects that have not changed between the current time and the recovery point. This allows BMC AMI Recovery Manager to avoid the unnecessary recovery of unchanged objects and can dramatically improve processing time. BMC AMI Recovery Manager also uses log range analysis to avoid unnecessary backups, thus reducing backup time and resources when table spaces change infrequently.

Full local subsystem recovery is particularly useful for SAP applications. SAP comprises a large number of Db2 objects and generally is the only application in the subsystem. In addition, SAP performs a high degree of dynamic creation and deletion of Db2 objects, which impacts the contents of the Db2 catalog and directory. Its unique nature leads to the necessity of recovering the entire subsystem.

Important

BMC AMI Recovery Manager requires declared Db2 global temporary tables when generating JCL for unchanged analysis processing during local subsystem recovery. For more information, see Creating required temporary tables.

This topic discusses the backup and recovery of all table spaces in a Db2 subsystem. You can perform all procedures through the BMC AMI Recovery Manager online interface or by using the batch programs. BMC AMI Recovery Manager provides the following programs:

  • The ARMBGPS program divides all table spaces in the system into balanced object sets for backup and recovery purposes. ARMBGPS also creates a delta object set (00 object set), which will initially be empty, but because the definition of the object set is dynamic, will automatically pick up any newly-created objects. You decide how many object sets are necessary to process your backups (and recoveries) in a timely fashion given the resources available on your system. If you are using the BMC AMI Copy and BMC AMI Recover utilities, indexes meeting a specified size threshold can be included in the backup and recovery jobs. For more information about ARMBGPS, see ARMBGPS—Subsystem object set split.

    Important

    ARMBGPS automatically identifies LOB and XML-related spaces and keeps them together in the same object set regardless of size. LOB-related spaces must be recovered together and XML-related spaces must be recovered together so that they are not placed in pending status. See LOB-and-XML-object-recovery. ARMBGPS also identifies and keeps together all History-related objects, which must also be recovered together.

  • The ARMBGEN program can generate the following jobs:
    • Back up the entire subsystem
    • Back up only the new and changed objects
    • Recover the entire subsystem to a previous point in time
    • Simulate recovery of the entire subsystem to a previous point in time
    • Recover the new and changed objects to a previous point in time

For more information about ARMBGEN, see ARMBGEN—Backup and recovery JCL.

Related topic

Full-subsystem-recovery


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*