Spreadsheet: 60bfd23a-d1e8-4743-9d05-02be7f9395e3
Sheet: Sheet1

Document: Return to Operation / Recovery Point Objective | Unnamed: 1 | Unnamed: 2 | Unnamed: 3 | Unnamed: 4 | Unnamed: 5 | Unnamed: 6 | Unnamed: 7 | Unnamed: 8 | Unnamed: 9 | Unnamed: 10 | Unnamed: 11 | Unnamed: 12 | Unnamed: 13 | Unnamed: 14 | Unnamed: 15 | Unnamed: 16 | Unnamed: 17 | Unnamed: 18 | Unnamed: 19
Customer: ABC Company
Last Updated: 10/03/2012
Last Updated By: [NAME]
 |  | Current Environment |  |  |  |  |  |  |  | With [NAME] |  |  |  |  |  |  | Fail Over
 | Critical | Return To Operation (RTO) in Hours |  |  | Recovery Point Objective (RPO) in Hours |  |  | On Site HA | Off Site DR | Return To Operation (RTO) in Hours |  |  | Recovery Point Objective (RPO) in Hours |  |  | Data Change and Rate | On Site Fail Over | Off Site Fail Over | Business Owner
Site | System/Application  Description | Goal | Current | Gap* | Goal | Current | Gap* | Y/N | Y/N | Goal | Proposed | Gap* | Goal | Proposed | Gap* |  | Y/N | Y/N
 | MS Exchange | 1 | 6 | -5 | 1 | 8 | -7 | Y | N | 1 | 1 | 0 | 0 | 0 | 0 |  | Y | N | Finance
 | Sharepoint Server | 4 | 8 | -4 | 4 | 24 | -20 | Y | N | 1 | 1 | 0 | 0 | 0 | 0 |  | Y | N | HR
 | File & Print | 4 | 12 | -8 | 4 | 24 | -20 | Y | N | 1 | 1 | 0 | 0 | 0 | 0 | 80MB/hr | Y | N | Operations
 | Payroll Server | 4 | 6 | -2 | 1 | 24 | -23 | Y |  | 1 | 1 | 0 | 1 | 1 | 0 |  | Y | N | IT Dept.
 | Web Server | 4 | 12 | -8 | 4 | 24 | -20 | N | N | 0 | 0 | 0 | 0 | 0 | 0 |  | N | N | Messaging
 | Sharepoint Server | 4 | 12 | -8 | 4 | 24 | -20 | N | N | 0 | 0 | 0 | 0 | 0 | 0 |  | N | N | Supply
 | File & Print | 2 | 12 | -10 | 2 | 24 | -22 | N | Y | 0 | 0 | 0 | 0 | 0 | 0 |  | N | Y | Management
 | File & Print | 2 | 12 | -10 | 2 | 24 | -22 | N | Y | 0 | 0 | 0 | 0 | 0 | 0 |  | N | Y | Distribution
 | File & Print | 2 | 24 | -22 | 2 | 24 | -22 | N | Y | 0 | 0 | 0 | 0 | 0 | 0 |  | N | Y | IT Dept.
 |  | 0 | 168 | -168 | 0 | 24 | -24 | N | N |  |  | 0 | 0 | 24 | -24 |  | N | N | [NAME]
 |  | 4 | 168 | -164 | 24 | 24 | 0 | N | N |  |  | 0 | 24 | 24 | 0 |  | N | N | [NAME]
 |  | 72 | 168 | -96 | 24 | 24 | 0 | N | N |  |  | 0 | 24 | 24 | 0 |  | N | N | Production Departments
 |  | 72 | 168 | -96 | 24 | 24 | 0 | N | N |  |  | 0 | 24 | 24 | 0 |  | N | N | Production Departments
 |  | 4 | 168 | -164 | 24 | 24 | 0 | N | N |  |  | 0 | 24 | 24 | 0 |  | N | N | IT Dept.
 |  | 24 | 168 | -144 | 48 | 24 | 24 | N | N |  |  | 0 | 120 | 24 | 96 |  | N | N | SRM Management Team
 |  | 3 | 168 | -165 | 25/75 | 24 |  | N | N |  |  | 0 | 25/75 | 24 |  |  | N | N | [NAME]
 |  | 0.5 | 168 | -167.5 | 192.5 | 24 | 168.5 | N | N |  |  | 0 | 192 | 24 | 168 |  | N | N | [NAME]
 |  | 8 | 168 | -160 | 168 | 24 | 144 | Y | N |  |  | 0 | 216 | 24 | 192 |  | Y | N | [NAME]
 |  | 8 | 168 | -160 | 168 | 24 | 144 | Y | N |  |  | 0 | 216 | 24 | 192 |  | Y | N | [NAME]
 |  | 0 | 168 | -168 | 24 | 24 | 0 | N | Y |  |  | 0 | 24 | 24 | 0 |  | N | Y | IT Dept.
 |  | 8 | 168 | -160 | 24 | 24 | 0 | N | N |  |  | 0 | 24 | 24 | 0 |  | N | N | IT Dept.
 |  | 168 | 168 | 0 | 192/216 | 24 |  | N | N |  |  | 0 | 192/216 | 24 |  |  | N | N | [NAME]
 | Criticality Rating: | A rating based on the business criticality of the system.
 | Return To Operation: | Represents the amount of elapsed time between when the outage occurs and the system is recovered.
 |  |  | Current Recovery Times should be based on a "worst case" outage
 | Recovery Point Objective: | Represents the amount of elapsed time between when the backup used to restore a system is taken and when system restoration is complete.
 |  |  | Times should be based on a "worst case" scenario.
 |  |  | (EX: Backups are taken at midnight and the system fails at 11:59 p.m.  Recovery Time would be 24 hours.)
Site |  | Facility where the system is located.
System Description |  | Server Name or Hardware Type.
Criticality Rating |  | Assign a rating based on the business criticality of the system.  Below is a sample rating system.
3=Low or Least Critical.  Last systems to be recovered.
[NAME] |  | The times entered in this section of the chart are based on a system outage scenario.  Facilities are intact but system has failed.  All other portions of the business continue to function.
Recovery Time Objective |  | Represents the amount of elapsed time between when the outage occurs and the system is recovered.  Current Recovery Times should be based on a "worst case" outage (EX: Replacement system needs to be brought in.)
 | Goal | This field is provided by the Business Owner and represents the maximum number of hours that business can continue to function without the system.
 | Current | The current number of hours that it would take to restore the system based on a "worst case" outage.
 | Gap | The difference between the Goal and Current Recovery Times.  A negative gap indicates that the length of an outage could exceed business tolerance.
Recovery Point Objective |  | Represents the amount of elapsed time between when the backup used to restore a system is taken and when system restoration is complete.  Times should be based on a "worst case" scenario. (EX: Backups are taken at midnight and the system fails at 11:59 p.m.  Recovery Time would be 24 hours.)
 | Goal | This field is provided by the Business Owner and represents the amount of data that the business can lose before they would not be able to recover from an outage.)
 | Current | The maximum amount of data that could be lost due to an outage based on current backup practices.   If backups are done daily, this would be 24 hours.
 | Gap | The difference between the Goal and Current Recovery Points. A negative gap indicates that the amount of data lost could exceed business tolerance.
Alternate Site Recovery |  | The times entered in this section of the chart are based on a scenario that involves loss of the current server room and a recovery done at the alternate recovery site.
Recovery Time Objective |  | Represents the amount of elapsed time between when the outage occurs and the system is recovered.
 | Goal | This field is provided by the Business Owner and represents the maximum number of hours that business can continue to function without the system.
 | Current | The current number of hours that it would take to restore the system at an alternate site.
 | Gap | The difference between the Goal and Current recovery times.  A negative gap indicates that the length of an outage could exceed business tolerance.
Recovery Point Objective |  | Represents the amount of elapsed time between when the last off-site backup was taken and the when the system is restored.  Times should be based on a "worst case" scenario. (EX: Backups are done daily at midnight and are taken off site at 6:00 a.m. each morning.  Disaster occurs at 5:00 a.m.)
 | Goal | This field is provided by the Business Owner and represents the amount of data that the business can lose before they would not be able to recover from an outage.
 | Current | The maximum amount of data that could be lost due to an outage based on current off-site storage practices.  (EX: Backups are done daily at midnight and are taken off site at 6:00 a.m. each morning.  Disaster occurs at 5:00 a.m.  The last backup stored off-site is 29 hours old.  It takes 24 hours to restore the system.  The recovery point is 53 hours)
 | Gap | The difference between the Goal and Current recovery points. A negative gap indicates that the amount of data lost could exceed business tolerance.
On-Site Failover |  | Indicates whether there is an on-site failover for the system.   A failover is a system that has data that is kept in sync with the primary system.  An on-site failover is used in the event of a system outage.
Off-Site Failover |  | Indicates whether there is an off-site failover for the system.   A failover is a system that has data that is kept in sync with the primary system.  An off-site failover is used in the event that the primary system is destroyed, or the facility is not accessible.
Business Owner |  | The primary Business Owner for the system.  This will be the person that provides the Recovery Time Goals and Recovery Point Goals.