Skip to main content

Prework Before Updating ITDR

The following are questions to consider and data to gather in advance of making your updates in CardinalShield ITDR. Having this data in advance will streamline your data entry into CardinalShield ITDR.

Key questions and data

By following these steps, you can efficiently use CardinalShield ITDR to create and maintain comprehensive disaster recovery plans, ensuring preparedness and resilience for your IT infrastructure.

WORKFLOW STEPSSUMMARY OF DATA BEING GATHERED
Administrative
  1. Who is responsible for filling out the DR Plan as the owner?
  2. What school/unit, department/organization, and group/team/division are you part of?
  3. What is the name of the service/application?
  4. Which deployment model are you using?
  5. Did you read through Part A?
ScopeWhat are the name(s) of the services and/or applications in scope of this DR Plan?
Vendor InformationWhat is the name of the vendor you are using?
Service Infrastructure
  1. Is there a non-production environment available for this service?
  2. Are there any general assumptions or dependencies for this service?
  3. What are the production hardware/VM details for this service?
  4. What are the DR hardware/VM details for this service?
Recovery Team Resources
  1. Who from your team is responsible for the recovery of a service when it goes down?
  2. What role(s) will the team responsible for this service play?
  3. What skill set does the team need to have?
  4. Who are the primary and secondary contacts for this service?
  5. Do you have the primary contact's email and phone numbers?
  6. Does your team have a link to an on-call schedule?
  7. Do you have your vendors/suppliers' contact information name, email, phone number, website, and contract number?
Outage Notifications, Escalations, Monitoring & Communications
  1. What monitoring tools are being used?
  2. What team is responsible for monitoring alerts?
  3. Are alerts being monitored 24/7, or on another cadence?
  4. How are alerts being communicated to the team responsible for monitoring?
  5. Are there any special communications and service level considerations?
Recovery
  1. What is this service's RTO?
  2. What is this service's RPO?
  3. Does this service have data backup implemented?
  4. What are the recovery steps for this service, such as process name, process details, process owner, estimated time for recovery?
Scenarios
  1. What scenarios from the list are applicable to your service?
  2. What are the steps/instructions for each applicable scenario?
Testing, Drills, and Maintenance
  1. How often are testing or DR exercises done?
  2. How often are regular maintenance, patching, and server reboots done?
Closing Steps and Approval Setup
  1. Are there any additional comments related to the recovery of this service that you would like to reference that were not captured in other sections?
  2. Is there any other supporting documentation that would help with the recovery process that you would like to add?
Local ApprovalHave you completed the DR plan to the best of your knowledge and with the most current updates and are you ready to sign off for completion?
Closing ApprovalThis section will be completed by the IT Resilience team.
Last modified