Last active
April 7, 2020 06:20
-
-
Save josephphyo/5cd679310250265e9e3af35fa8a5fcbd to your computer and use it in GitHub Desktop.
Key factors for Disaster Planning
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Backup & Restore (Data backed up and restored) | |
| Pilot Light (Only Minimal critical functionalities) | |
| Warm Standby (Fully Functional Scaled down version) | |
| Multi-Site (Active-Active) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| << Understanding RTO and RPO >> | |
| 1. Recovery Time Objective (RTO) | |
| - The time its takes after disruption to restore business process to service level. | |
| - Disaster occur at 12:00PM(NOON), RTO is Eight Hours , DR Process should restore and acceptable service level at 8:00PM(Night). | |
| 2. Recovery Point Objective (RPO) | |
| - Acceptable amount of time of data loss measured in time of Disaster. | |
| - If RPO is one hour for organization, If Diaster happened in 12:00PM(Noon) , Data can be recovery before 11:00AM. | |
| - Data can be loss between 11:00AM to 12:00PM. (One hour data can be loss according to RPO) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment