How BMC AMI Recover works

To accomplish recovery tasks, BMC AMI Recover offers the following resources:
  • Uses the same Db2 resources that are used by the IBM Db2 RECOVER utility

  • Uses any available change accumulation files as input to forward recovery

  • Uses index image copies that are made by BMC AMI Copy for Db2  (BMC AMI Copy), the IBM Db2 COPY utility, BMC AMI Recover, or DSN1COPY

  • Uses Instant Snapshot copies that are made by BMC AMI Copy

  • Uses encrypted copies that are made by BMC AMI Copy

  • Uses cabinet copies that are created by BMC AMI Copy as part of the Recovery Management for Db2 solution

  • Uses Online Consistent Copies , which you can create if you have the Recovery Management for Db2 solution

  • Supports a wide range of recovery strategies by using a variety of commands and options

During a recovery, BMC AMI Recover automatically optimizes recovery processing by performing the following tasks:

  • Optimizing block sizes

  • Extracting index keys, when possible and requested, during table space recovery

  • Detecting and ordering activities for the proper positioning of stacked tape data sets, change accumulation files, and input and output copies containing all partitions of a partitioned space

  • Using a subtask to preallocate and open VSAM data sets required during recovery

  • Automatically falling back, without restarting, to a previous copy or Instant Snapshot, if an invalid or unavailable image copy or Instant Snapshot is encountered during recovery

Log data sets and table space data sets are dynamically allocated to the job. BMC AMI Recover also dynamically allocates the input image copy data sets and required change accumulation files. The target table and index spaces are identified through IBM compatible syntax, and the target Db2 subsystem is identified in the EXEC statement utility parameters. As an option, BMC AMI Recover provides support for dynamic allocation of output image copies.

BMC AMI Recover parses all BMC AMI Recover command statements before initiating recovery. BMC AMI Recover constructs a recovery plan and produces a report on this plan. Other options allow control over other aspects of the recovery. For example, you can specify the device type (SORTDEVT) and number of temporary data sets (SORTNUM) for sorting, or you can specify the MAXKSORT option for multitasking index key sorts and index rebuilds. You can further refine your index recovery using the KSORTSHARE option. You use the MAXLSORT option to specify concurrent log sorts and parallel MERGE phases. BMC AMI Recover provides the ANALYZE ONLY option to view recovery resources and preview recovery plans without actually executing a recovery job. BMC AMI Recover also provides a LOGSCAN command to gather information about the recovery and provide information that you can use to choose sort parameters.

BMC AMI Recover uses the BMC BMCSORT technology for sorts. BMCSORT provides BMC AMI Recover with more control of the sort process than external sort routines provide. This added control helps prevent memory-related problems during the sort process. BMC AMI Recover allocates the amount of resources to each sort process based on the amount of work that BMC AMI Recover determines that the sort process will perform. BMC AMI Recover also dynamically detects excess available memory and allocates a percentage of it to the sort processes.

The recovery simulation feature, which requires a Recovery Management for Db2 solution password, provides a non-destructive mechanism to exercise all recovery resources, including image copies, log records, and change accumulation files. This feature allows customers to ensure that all recovery resources are available to recover a table space or index without actually recovering it.

BMC AMI Recover controls spaces by altering the Db2 status of the objects as necessary. Synchronization with BMC utility operations is provided through Db2 tables that are delivered and installed as part of BMC AMI Recover.

BMC AMI Recover does not use the Db2 subsystem buffers; however, it uses the Db2 subsystem to find information for the recovery process.

Related topic



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

Comments