White Papers on DRP recommends to assess the crisis before invoking the DRP, But none give the detailed list of elements to be assessed,
My approach to close that gap is to create the DRP plan as set of books, each covering DRP elements: procedures, steps, etc... thus providing DRP metrics
Book #1: Scope and principles: To describe the list of services include in the DRP with their associated RTO and RPO, for each service, the capacity rate: we provide 100% of the service feature or 75%... and the principles of the DRP: Data copy, Wan copy, etc.. This section provides RTE: Recovery time Expected and RPE: Recovery Point Expected
Book #2 : Run the DRP : The steps to be followed to activate the DRP. I recall that as the plan needs to be tested, this book will provide the following results: RTA: Recovery Time Actual and RPA: Recovery Point Actual. These metrics are the time taken from the "ground" used to activate the DRP.
Book #3: DRP resumption: The steps to be followed to resume operation as nominal. We calculate the Recovery Elapsed Time: The time used to restart on the nominal state and the Recovery Data Gap: The amount of data that could have been lost when the service has been
Book #4: DRP Crisis assesment: That's the book that deals with the decision to invoke or not the DRP: The purpose is to get answers to these questions:
Is the service to the customer affected by the outage?
Is the service from the current location unlikely to be restored within the contractual RTO
Can the service be restored at a Disaster Recovery location more quickly than in the problem location?
Will the total down for invocation: invoke the DRP+restore back to normal be less than the downtime to restore at the original location?
In it we evaulate the RTO/RTE/RTA/RET and RPO/RPE/RPA/RDP values to detemine if we got to trigger or not the DRP.
Your take dear community?