Before you begin disaster recovery

To prepare for disaster recovery, you must perform the following steps:

  • Determine the time of day that copies are sent offsite.
  • Determine the process that causes copies to be sent offsite.
  • Decide how many hours (or days) of data loss you are willing to accept in the case of a disaster. (This value is important in scheduling the BMC AMI Recovery Manager disaster recovery preparation programs in that it establishes the maximum time between their executions. You should also consider the time that is required to transport the assets to your recovery site.)

Related topic

Using-BMC-AMI-Recovery-Manager-at-the-local-site

  • Determine the method you will use to create offsite copies of archive logs.
  • Perform the following basic BMC AMI Recovery Manager setup procedures:
    • Verify that the option set is accurate. (See BMC-AMI-Recovery-Manager-option-sets-and-configuration-options for more information.)
    • Set up a data set that contains the job card to use with ARMBSRR (the systems resource recovery batch program). The job name must include the variable &##. The user ID on the job card must have installation SYSADM or installation SYSOPR authority when Db2 is brought up at the remote site
    • Set up a GDG base to hold JCL that is generated by ARMBSRR. If you are using SIMULATE YES, set up a GDG base that has a final node ending in SIM or .SIM to ensure that the JCL is not mistaken for actual disaster recovery JCL. ARMBSRR issues an error message if you specify a data set without the final node ending in SIM or .SIM. For example, ARMGDG.BASE.SIM or ARMGDG.BASESIM. If you are using ESTIMATE YES, set up a GDG base that has a final node ending in EST or .EST to ensure that the JCL is not mistaken for actual disaster recovery JCL.
    • Set up a GDG base to hold JCL that is generated by ARMBGEN

 

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