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 Recovery Management for Db2 13.1.

Recovery estimation

The recovery estimation feature can provide an estimate of the hours, minutes, and seconds required to perform a complete disaster recovery, including application resources.

Important

You must have a BMC AMI Recovery for Db2 solution password to access recovery estimation in

Some content is unavailable due to permissions.

and

Some content is unavailable due to permissions.

.

The complexity and unique qualities of every disaster recovery situation make accurate estimates extraordinarily difficult.

When using estimation, consider the following points:

  • Consistency

    Estimates produced by the BMC AMI Recovery for Db2 solution are calculated based on information about your subsystem. The actual hours and minutes estimated may or may not be entirely accurate, but they are consistent and can be very useful from that standpoint. For example, you might find that an actual disaster recovery took 20 hours, even though the estimate was 24 hours. The next time that your estimate is 24 hours, you can safely assume that the actual recovery will take approximately 20 hours (assuming no major changes to the system).

    Important

    An estimate can only be as consistent as the data on which it is based. If you change variables at the remote site, the estimate might no longer have the same correlation to the actual time. For example, an estimate of 24 hours might ordinarily correlate to a recovery of 20 hours. If you add a new processor at the remote site but do not change the options used by the estimation, an estimate of 24 hours might now correlate to a recovery of 12 hours.

  • Scenarios

    You can use the estimate to perform what-if scenarios when you are trying to improve recovery time. Consider the following examples:

    • Your initial estimate indicates that a recovery will take 24 hours. You make changes to the objects in the list of the ten longest running recoveries to see if doing so reduces the recovery time. You run the estimate again, and the recovery estimate is 20 hours.
    • Your initial estimate indicates that recovery will take 20 hours. You increase the maximum concurrent jobs from 2 to 4 and run another estimate. Now the estimate indicates the recovery will take 12 hours.

These examples show how you can use estimation to improve recovery time even though you might not be certain how long the actual recovery will take.

This section contains the following topics:

Related topics

Key-concepts

Recovery-simulation-and-estimation


 

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