Disaster Recovery: the process related to preparing for recovery or planning critical technology infrastructure before a natural or human disaster occurs.

2. Agenda
I. Overview
II. DR & BC Planning
III. Essentials For High Availability
IV. Hardware Solutions
V. Conclusion

3. Did You Know?
• 60% of companies that lose their data will shut down within 6 months
of the disaster.
• 93% of companies that lost their data center for 10 days or more due
to a disaster filed for bankruptcy within one year of the disaster. 50%
of businesses that found themselves without data management for
this same time period filed for bankruptcy immediately. (Source:
National Archives & Records Administration in Washington)
• Companies that aren’t able to resume operations within ten days (of a
disaster hit) are not likely to survive. (Strategic Research Institute)

4. Did You Know?
• 30% of small businesses admit they have no formal storage
procedures, or do not implement their procedures consistently.
(Imation’s Small Business Survey Special Report)
• 55% of small businesses rated themselves as “fair” or “poor” in terms
of having a documented disaster recovery plan, or do not have one at
all.
• Hardware or system failure accounts for 78% of all data loss - Human
error accounts for 11% of all data loss - Software corruption accounts
for 7% of all data loss - Natural disasters account for only 1% of all data
loss.

5. Types of Disasters
• Natural Disasters
– Power Outages, Floods, Hurricanes, Tornadoes, or
Earthquakes
• Human Disasters
– Hazardous Material Spills, Bio-terrorism, Human
Errors
• Hardware Failures
– Hard Drive Meltdowns, Internet Outages, Etc.

6. Business Continuity Cycle
Business
Continuity
High
Availability
Disaster
Recovery
Operational
Recovery

7. What Is Disaster Recovery?
• Disaster Recovery:
– the process related to preparing for recovery or planning critical
technology infrastructure before a natural or human disaster
occurs.

8. What Is Operational Recovery?
• Operational Recovery:
– Like disaster recovery, this practice focuses on the recovery of
applications and technology; however, in this case, the recovery is
within the primary processing location.
– Operational recovery contemplates the need to recover from a
service disruption that does not require a disaster declaration.
– Operational recoveries may be daily occurrences responding to
something that is not operating to plan and needs to be fixed, for
example, failure of a file server.

9. What Is High Availability?
• High Availability:
– In contrast to planning for recovery is planning for resiliency or uptime.
– Application clustering, hardware clustering, virtualization, and local replication
technologies are all used to keep an application resilient.
– Basic idea is to build an architecture that can continue to operate without
disruption even when one of its components fails. Resiliency is focused on “uptime”
rather than recovery time.

10. What Is Business Continuity?
• Business Continuity:
– In contrast to planning for recovery is planning for resiliency or uptime.
– Application clustering, hardware clustering, virtualization, and local replication
technologies are all used to keep an application resilient.
– Basic idea is to build an architecture that can continue to operate without
disruption even when one of its components fails. Resiliency is focused on “uptime”
rather than recovery time.

11. Disaster Recover Planning




Infrastructure Layer
Storage Layer
Server Layer
Application Layer

12. Disaster Recover Planning
Infrastructure Layer
 Needs to be architected in the most resilient fashion possible
 Must be built to 24 x 7 uptime
 Redundant components, secondary routes, and
redundant power
 Develop a site that is an extension of your primary site,
not a mirror or isolated copy

13. Disaster Recover Planning
Storage Layer
 Contains the vital data of your business
 Copies of the data for local processing, copies for local
restoration and local outages, & copies for disaster
recovery

14. Disaster Recover Planning
Server Layer
• The file servers and the strategy for keeping them
active and running
• Three common architectural approaches:
1.
2.
3.
Virtualizing the servers so the application sits on a virtual
container
Clustering the servers so that two or more servers are
working in unison supporting an application or process
Load balancing the servers to create two separate processing
domains that can work in conjunction with each other and
yet are maintained separately

15. Disaster Recover Planning Best Practices
• Create a strategic plan
– Identify and analyze disaster risks/threats
– Classify your disaster risks
– Build a risk assessment
– Determine the effects of a disaster
– Evaluate the mechanisms for recovery
– Implement your recovery phases

16. Disaster Recover Phases
1. Activation Phase
– Disaster effects are assessed
2. Execution Phase
–
–
Recovery procedures executed
Business operations are restored
3. Reconstitution Phase
–
Original system restored

17. Essentials For Ensuring Recovery & Minimum Downtime
1.
2.
3.
4.
System Configurations
Hardware Failover
Data Storage
Backups and Replication

18. Essentials For Ensuring Recovery & Minimum Downtime
Recommended Configurations

19. Essentials For Ensuring Recovery & Minimum Downtime
Basic Disaster Recovery
2 Servers, Identically Configured

20. Essentials For Ensuring Recovery & Minimum Downtime
Warm Standby Disaster Recovery
3 Servers, Identically Configured
2 Local & 1 Remote Site
Automated Replication

21. Essentials For Ensuring Recovery & Minimum Downtime
High Availability With Disaster Recovery
2 Clustered Servers & 1 Remote DR Site
2 Shared Storage Network With Replication

22. Essentials For Ensuring Recovery & Minimum Downtime
High Availability With Disaster Recovery
4 Clustered Servers With 2 In Remote DR Site
2 Shared Storage Network With Live Replication

23. Essentials For Ensuring Recovery & Minimum Downtime
Extreme High Availability With Disaster Recovery
4+ Clustered Servers With 2 In Remote DR Site
2 Shared Storage Network With Live Replication
No Data Loss

24. Questions?