Disaster Recovery

Question 1

Recovery time objective(RTO)

Answer 1

Time it takes after a disruption to restore operations back to its regular service level, as defined by the companies operational level agreement. (i.e. if the RTO is 4 hours, you have 4 hours to restore service bak to an acceptable level).

Question 2

Recovery point objective(RPO)

Answer 2

acceptable amount of data loss measured in time. ( i.e. if the system goes down at 10 PM, RPO is 2 hours, then you should recover all data as part of the application as it was before 8:00PM.

Question 3

Pilot light

Answer 3

minimal version of your production environment that is running on AWS. it is important to keep up todate AMI and instance configurations if following pilot light protocol.

Question 4

Warm standby

Answer 4

has a larger foot print than a pilot light setup, and would most likely be running business critical applications in “standby”. This type of configuration could also be used as a test area for application,

Question 5

Multi-Site Solution

Answer 5

Essentially clones your “production” environment, which can either be in the cloud or on premise. Has an active -active configuration which means instances size and capacity are all running in full standby and can easily convert at the flip of a switch.

Question 6

Services Examples

Answer 6

Elastic Load Balancer and Auto Scaling
Amazon EC2 VM import Connector
AMI’s with up to date configurations
Replication from on-premise database servers to RDS
Automate the increasing of resources in the event of a disaster
Use AWS import/Export to copy large amounts of data to speed up replication times(also used for off site archiving).
Route 53 DNS Failover/Latency Based Routing solutions
Storage Gateway.