Evaluate the disaster recovery

The final step of DR is evaluation: Did the DR work? If not, why?

Obviously, evaluation is most effective in the context of a test; if you find a problem, you can correct it before you run the next test. And you can continue to run tests until you get the exact results you want. Therefore, by carefully examining the results of your DR tests, along with making adjustments in the preparation and performance phases of DR, you can ensure successful recovery when a real disaster strikes.

Related topics

Disaster-recovery-with-RMGR

You may ask the following questions to evaluate the DR:

  • Were all necessary databases recovered, and were they recovered correctly (without losing too many in-flight transactions and without pointer errors)? If not, why did the error occur? The following problems may have caused the error:
    • Incorrect or incomplete preparation at the home site
    • Unexpected variations at the DR site
  • Was performance acceptable? Did you meet service level agreements for the length of the database outages? If not, why? The following problems may have caused the unacceptable performance:
    • Need for more frequent image copies
    • Need for more frequent change accumulations
    • Need to improve recovery profile options
    • Inadequate resources (such as tape drives, CPU cycles, and DASD)
    • Need for more recovery points
    • Inappropriate image copy stacking strategy
    • Recovery rather than rebuild of indexes

You can contact BMC Customer Support to discuss the results of your DR tests and to obtain advice for improving these results. BMC can help to analyze your preparation procedures and utility parameters and adjust them to ensure data integrity and maximum performance.

 

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