Aws for disaster recovery - DevOps Union
- 4. Save up to 85% in reduced infrastructure capital expenditure for servers, storage, networking, and physical data center costs Lower on-going reoccurring expenses such as co-location charges, power, and maintenance Increased efficiency for recovery time and recovery point objectives Only pay for what you use
- 5. Handling Large Databases Network Integration Rapid Spin-up of Standby Machine Images Set RTO/RPO
- 6. RTO is a measure of the maximum amount of time within which operations are expected to be resumed after a disaster RPO is a measure, in terms of time, of the maximum amount of data that can be lost as a result of a disaster.
- 10. Select an appropriate tool or method to back up your data into AWS. Ensure that you have an appropriate retention policy for this data. Ensure that appropriate security measures are in place for this date, including encryption and access policies Regularly test the recovery of this data and restoration of your system
- 13. Set up EC2 instances to replicate or mirror data. Ensure that you have all supporting custom software packages available in AWS. Create and Maintain Amazon Machine Images (AMI) of servers where fast recovery is required. Regularly run these servers, test them, and apply any software updates and configuration changes.
- 14. Start your application EC2 instances from your custom AMI’s. Resize and/or scale any database / data store instances, where necessary. Change DNS to point at the EC2 servers.
- 17. Set up EC2 instances to replicate or mirror data. Create and maintain Amazon Machine Images (AMIs). Run your application using a minimal footprint of EC2 instances or AWS infrastructure. Patch and update software and configuration files in line with your live environment.
- 18. Start applications on larger EC2 Instance types as needed (vertical scaling). Increase the size of the EC2 fleets in service with the Load Balancer (horizontal scaling). Change the DNS records so that all traffic is routed to the AWS environment. Consider using Auto scaling to right-size the fleet or accommodate the increased load.
- 21. Set up your AWS environment to duplicate your production environment. Set up DNS weighting or similar technology to distribute incoming requests to both sites.
- 22. Change the DNS weighting, so that all requests are sent to the AWS site. Have application logic for failover to use the local AWS database servers. Consider using Auto scaling to automatically right-size the AWS fleet.
- 23. As enterprise needs for disaster recovery progress toward a need for complete business continuity, and while IT budgets for DR remain stagnant, enterprises can no longer avoid considering cost-effective, multi-tenant, cloud-based disaster recovery solutions like AWS.