Disaster Recovery

Cloud Disaster Recovery Plan

ITS Disaster Recovery Plan (DRP-CLOUD)

[PLACEHOLDER TEXT - APPLICATION NAME]

 

Prepared By:

Revision:	Date:	Name:	Signature:	Revision Description
0
1

 

Approval

Revision:	Date:	Name:	Signature:	Comment(s)
0
1

 

 

Introduction 

Purpose

[PLACEHOLDER TEXT - State the purpose of the procedure. Mentioning the application name and perhaps business requirements.]

Objectives

[PLACEHOLDER TEXT - State the objectives of the DRP document such as providing information to direct teams in the failover to a DR site.]

Scope

[PLACEHOLDER TEXT - Describe whether the scope of the application is partial, tends beyond the application, or if it is always grouped or tested with another application.]

Assumptions

[PLACEHOLDER TEXT]

Resiliency Strategy

[PLACEHOLDER TEXT]

Application Runbook

[PLACEHOLDER TEXT - If an application runback exists or any operational support documents, provide links here.]

Procedures

Responsible Persons/Roles

[PLACEHOLDER TEXT - List the people/roles responsible for tasks related to the failover, testing or management of this application.]

Disaster Failover Steps

[PLACEHOLDER TEXT - List the sequential failover steps including any pre-requisites. Provide instructions for each DR scenario.]

Fail-back Steps from Disaster Alignment

[PLACEHOLDER TEXT - List the sequential fail-back steps.]

DR Test Failover

[PLACEHOLDER TEXT - List the sequential failover steps to perform a DR test of this application. Include a step requiring an approved change request to be processed. Provide an instruction per DR scenario.]

DR Test Fail Back

[PLACEHOLDER TEXT - List the fail-back steps from a DR test.]

DR Test Application Validation Procedure

[PLACEHOLDER TEXT - List the steps necessary to validate the application once failed over to DR. These steps are typically performed by the application manager or the business owner (if participating).]

Application Overview

Description

[PLACEHOLDER TEXT - Describe the features of the vendor’s deployment model that make the service highly available and resilient. Pull language from the service description, product architecture, contract, SLA, vendor DR plans, vendor SOC reports, etc.]

 

Cloud Deployment Model

Mark the cloud deployment model(s) implemented for this application with an "X", and complete the following sections based upon cloud deployment model(s) selected (see italicized text next to section and subsection headers):

___ SaaS - Software as a Solution

___ PaaS - Platform as a Solution 

___ IaaS - Infrastructure as a Solution

 

Summary List of Systems, Applications (SaaS, PaaS, IaaS) 

[PLACEHOLDER TEXT - A technical description of the architectural makeup of the application.]

Out-of-Scope (SaaS, PaaS, IaaS)

[PLACEHOLDER TEXT]

Hardware/VM Details (IaaS)

System/ Function	Region/ Availability Zone	Hostname	Model #	# Processors	Memory	O/S Name & Version	Other Characterist-ics (auto-scale, etc.)

 

Vendors/Suppliers (SaaS, PaaS, IaaS)

Vendor	Product/ Service Name	Contact	Phone #	Website	Contract #

 

Upstream and Downstream Dependencies

[PLACEHOLDER TEXT - Include any dependencies on U of C on-premises infrastructure or services from other cloud service providers.]

DNS Information 

[PLACEHOLDER TEXT]

Infrastructure Diagram

[PLACEHOLDER TEXT - Provide a diagram of the application, this is typically a Visio diagram.]

DR Scenarios

[PLACEHOLDER TEXT - List all DR scenarios the application is designed for.]

Recovery Time Objective

[PLACEHOLDER TEXT -Period of time within which minimum levels of services and/or products and the supporting systems, applications, or functions must be recovered after a disruption has occurred.]

Recovery Point Objective

[PLACEHOLDER TEXT - Point in time to which data must be recovered after a disruption has occurred.]

Backup/Restore Policy 

[PLACEHOLDER TEXT]

Attachments

[PLACEHOLDER TEXT - Add any necessary attachments.]