Disaster Recovery

Disaster Recovery

OPTION 1: Traditional Backup/Restore
Businesses can use their current backup software or i2mcloud supplied software to replicate data into AWS. Companies use Amazon S3 for short-term archiving and Amazon Glacier for long-term archiving. In the event of a disaster, data can be made available on AWS infrastructure or restored from the cloud back onto an on-premise server.

OPTION 2: The Pilot Light Plan
While backup and restore are focused on data, pilot light includes applications. Companies only provision core infrastructure needed for critical applications. When disaster strikes, using Amazon EC2 instances and other automation services, we can quickly provision the remaining environment for production.

pilot-light-plan

Stage 1: Users and systems access your local corporate office environment,
Data is replicated every 24 hours to the cloud environment

vpc

Stage 2: Disaster situation occurs, systems start and all users and systems are pointed
to access the cloud disaster recovery environment with minimal downtime.

Option 3: Warm Standby
Taking the Pilot Light model one step further, warm standby creates an active/passive cluster. The minimum amount of capacity is provisioned in AWS. When needed, the environment rapidly scales up to meet full production demands. Companies receive (near) 100% uptime and (near) no downtime.

warm-standby

Option 4: Hot Standby
Hot standby is an active/active cluster with both cloud and on-premise components to it. Using weighted DNS load-balancing, IT determines how much application traffic to process in-house and on AWS. If a disaster or spike in load occurs, more or all of it can be routed to AWS with auto-scaling.

hot-standby