Best Practices for Surviving OutagesDesigning and implementing a High Availability and Disaster Recovery strategy

Sal Cardello, Director of Pro Services

Matt Dolian, System Engineer

Avroham Katz, System Engineer

2

Disaster Recovery

Photo credit: naturaldisasterss.com/wp-content/uploads/2011/12/Natural-Disaster-Images.jpg

3

0 - No off-site data

1 - Data backup with no hot site

2 - Data backup with hot site

3 - Electronic vaulting

4 - Point-in-time copies

5 - Transaction integrity

6 - Zero or near-Zero data loss

7 - Highly automated, business integrated solution

Tiers of Disaster Recovery

Citation: http://en.wikipedia.org/wiki/Seven_tiers_of_disaster_recovery

4

Definition: High Availability

“Design approach & associated service implementation that ensures a pre-arranged level of operational performance will be met during a contractual measurement period”

Citation: ttp://en.wikipedia.org/wiki/High_availability

5

High Availability Architecture

6

Why implement HA?

Best Practices for High Availability

7Photo Credit: http://bit.ly/z9OEwG

Environment Analysis

Geographic Mirroring

Database Replication

Store Assets Replication

Validate Synchronization

Escalation Plan

Test

Launch

8

• Environment Specific Configurations

• Asset Hosting

• Page Caching

• Other Data Stores

• Background Processing

• Cron Jobs

Application Considerations

Photo credit: http://www.flickr.com/photos/dseneste/5912382808/

9

1. Client contacted per terms of SLA

2. Engine Yard syncs database and performs manual failover

3. Redundant database promoted to master

4. DNS is updated

5. Replication to former master is re-established

Failover Process at Engine Yard

Manual, customer owned decision

10

Questions?

11

Get in touch

Contact us: Sal Cardello, Director of Pro Servicesproservices@engineyard.com

Learn more:http://www.engineyard.com/services