Disaster Recovery & Business Continuity Overview

Agenda

I. Overview

II. DR & BC Planning

III. Essentials For High Availability

IV. Hardware Solutions

V. Conclusion

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)

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.

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.

Business Continuity Cycle

Business Continuity

Disaster Recovery

Operational Recovery

High Availability

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.

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.

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.

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.

Disaster Recover Planning

Infrastructure Layer

Storage Layer

Server Layer

Application Layer


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


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


Server Layer • The file servers and the strategy for keeping them

active and running

• Three common architectural approaches: 1. Virtualizing the servers so the application sits on a virtual

container

2. Clustering the servers so that two or more servers are working in unison supporting an application or process

3. Load balancing the servers to create two separate processing domains that can work in conjunction with each other and yet are maintained separately

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

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

Essentials For Ensuring Recovery & Minimum Downtime

1. System Configurations

2. Hardware Failover

3. Data Storage

4. Backups and Replication


Recommended Configurations


Basic Disaster Recovery

2 Servers, Identically Configured


Warm Standby Disaster Recovery

3 Servers, Identically Configured

2 Local & 1 Remote Site

Automated Replication


High Availability With Disaster Recovery

2 Clustered Servers & 1 Remote DR Site

2 Shared Storage Network With Replication


High Availability With Disaster Recovery

4 Clustered Servers With 2 In Remote DR Site

2 Shared Storage Network With Live Replication


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

Questions?

Disaster Recovery & Business Continuity Overview

Technology

Transcript of Disaster Recovery & Business Continuity Overview