DR-strategy-analysis .pptx

STRATEGY ANALYSIS

BACKGROUND • Thomson-Reuters a global-news & information provider company wants to improve data protection, application recovery for one of its business units by moving its On-Prem disaster recovery (DR) site to the cloud. • Until 2020, the business unit has a time-consuming manual DR process in place which requires an engineering team fully to manage on-premises data centers, and it does not provide data protection & recovery times the way company wants • Company is planning to explore AWS Disaster Recovery options which will have minimal - downtime, reliable recovery, recovery time objective(RTO) & recovery point objective(RPO).

PROBLEM STATEMENT • Which AWS elastic disaster recovery service (DRS) should Thomson Reuters use in order to move their On-prem DR to cloud which has minimal - downtime, reliable recovery, recovery time objective(RTO) & recovery point objective(RPO). • AWS has four disaster recovery options • Backup/Restore - RTO/RPO will takes hours to bring the DR back up • Pilot Light - RTO/RPO will take 10s of minutes • Warm Standby - RTO/RPO will be in minutes • Multi-site active-active – RTO/ RPT will be Real Time • From the above four services Warm Stanby & Multi-site active-active will be the two options. Lets discuss with the team which one to pick

CLOUD DR TEAM MEETING TR IT team TR Business Team • AWS Solution architect – to design, Implement and validate the the options provided • SysOps admin – system administrators in cloud operations to validate the services • AWS developer – to review the network traffic & add restrictions to it on the Security groups and Access Control Lists(ACL) • AWS admin – resource who handles the AWS account on company side to purchase the services • DevOps Team - Developer Operational resources who provide inputs on the AWS DR usage • DR On-Prem team – Resources who works on the current onprem servers to provide inputs • Business team - Owners of the application to review the inputs and shar business outcomes • QA team – to provide the inputs of testing • Also groups that needs to be involved in the discussion

STRATEGIES UNDER CONSIDERATION • Status Quo 0 : No change, team will still use the On-Prem servers, time-consuming manual DR process in place which requires an engineering team fully to manage on-premises data • Option 1: Warm Standby - RTO/RPO will be in minutes This approach ensures a scale-down and have the total functional copy of production env. Warm Standby handles traffic (at reduced capacity levels) and reduces time of recovery because the workload is always-on in On-Prem so it takes backup on Cloud. It also allows you to more easily perform testing or implement continuous testing to increase confidence in your ability to recover from a disaster. • Option 2 : Multi-site active-active – RTO/ RPO will be Real Time With this approach we can run workload simultaneously in multiple Regions as part of a multi- site active/active or hot standby active/passive strategy. This is the most complex & costly approach to disaster recovery, but it can reduce your recovery time to near zero which meets the companies objective

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help