HowTo DR
- 2. Disaster Recovery
“The process, policies and
procedures that are related to
preparing for recovery or
continuation of technology
infrastructure which are vital to an
organization after a natural or
human-induced disaster.”
Wikipedia, February 2014
- 8. Dilbert is a copyright of Scott Adams. Used here as parody. All rights reserved to Scott Adams.
- 15. The Nines
●
Treats all downtime causes as
identical
–
●
●
●
except the ones it ignores
Doesn't address data loss
Really “Business Continuity”
also unrealistic
- 17. Disaster
Downtime Data Loss
Server Failure
0
0
Network Failure
0
0
Admin Error
0
0
Bad Update
0
0
Storage Failure
0
0
Getting Hacked
0
0
Natural Disaster
0
0
Detect
10 yrs
10 yrs
- 19. Disaster
Downtime Data Loss
Server Failure
5min
1min
Network Failure
3hrs
10min
Admin Error
1hr
1hr
Bad Update
1hr
1hr
Storage Failure
5min
30min
Getting Hacked
1hr
1hr
Natural Disaster
6hrs
1hr
Detect
3 mo
3 mo
- 21. Elements of a Plan
1. Backups/Replicas
2. Replacements
3. Procedures
4. People
- 38. Database Server
Does Not Respond
1. Determine if physical server is
down
a. if network is down, use plan N1.
2. If not, try to restart database
using command …
3. Still down? Fail over to replica
using command …
4. Check replica.
5. Not working? Restore backup to
test server 1 using command ...
- 43. Know who to call
●
●
●
●
●
on call staff
experts in each service
consultants/contractors
vendors
required authorizations
- 44. Contact Book
●
●
Include as much contact
information as possible
Put copies in more than one
place
–
●
including paper!
Keep it up to date
- 45. Test Your DR
Good: when you create the
procedure
Better: quarterly
Best: as part of daily/weekly
provisioning
- 54. Use your rapid deploy!
●
●
Continuous backup to S3
Deploy scripts + server images
–
●
Chef/Salt/Puppet/etc. helps here
= fast recovery
–
with low running costs
- 55. DR Tips
●
Have multiple copies of your plan
–
●
●
in multiple locations
A SAN is not a DR solution
One form of backup is seldom
enough