DR-strategy-analysis

pptx

School

University of Arkansas, Little Rock *

*We aren’t endorsed by this school

Course

7303

Subject

Information Systems

Date

Dec 6, 2023

Type

pptx

Pages

Uploaded by JusticeGalaxy2907

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

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

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

EVALUATION CRITERIA • Effectiveness : does the options provided will be effective and meets the company objective • Acceptability : the solutions provided to the company will it be acceptable by the business team • Equity : are we winners/losers to use DR strategy in AWS cloud. • Impact : what the impact of moving DR strategy to cloud env & the stakeholders

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

STATUS QUO ASSESSMENT Criteria Pros Cons Final Assessment Effectiveness No changes on the company side Manual efforts will be high Negative Acceptability On-prem DR servers Resources will not be happy negative Equity Onshore resources will have the work to do & job safety Leadership will have to put money for servers & resources Neutral Impact Fully manage on- prem data No major impact neutral

Criteria Pros Cons Final Assessment Effectiveness Moving to cloud env, low maintenance Team needs to be alert & do testing Positive Acceptability total functional copy of production env Recovery time objective will be in minutes Neutral Equity Can implement continuous testing easily, can be implemented and tested for initial DR migration, cost is low compared to Option 2 No cons other then RTO/RPO Neutral Impact Migrated to cloud env, will have a full copy of data backup Recovery point objective is in minutes Positive OPTION 1- Warm Standby - RTO/RPO will be in minutes

OPTION 2- Multi-site active-active – RTO/ RPO will be Real Time Criteria Pros Cons Final Assessment Effectiveness Moving to cloud env,very low maintenance Setup is difficult, need devOps resources initially Positive Acceptability Multisite active active real time data Complex approach & costly approach Positive Equity A win to leadership, It costs little high for the DR setup, but resources can be cutdown Positive Impact Migrated to cloud env, will have real time data backup upto date Removal on On-Prem DR servers will take time Positive

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

TRADE OFF’s Criteria STATUS QUO OPTION 1 OPTION2 Effectiveness Negative Positive Positive Acceptability negative Neutral Positive Equity Neutral Neutral Positive Impact neutral Positive Positive

RECOMMENDATION • Using the status quo, we cannot move forward, without changes as it’s a painfully manual efforts • Providing both option 1 & Option2 will be effective to that achieves the teams objective. • To use Option 1: it will be a warm standby instance but during a disaster recovery process it takes minutes for the environment to become active • To use Option 2: it will be a multi-site active-active instance which will be real time copy of the on-prem server

TELL YOUR STORY • Considering the RTO & RPO scenario option 2- Multi-site realtime will be the most effective, but it’s a little costly compared to option 1- warm standby . • If the company doesn’t consider the costs but need the real time copy of the onprem data then company must consider the Option 2. I would present them the costs incurred if option 2 is used. • Will present Option 1 wtih RTO/RPO time is in minutes if the team is fine going warm standby DR strategy. Also with Warm standby you can easily perform continuous testing to increase confidence in your ability to recover from a disaster. • Team can proceed the initial step of starting with Option 1 DR strategy and then move to Option 2 DR strategy when confident with using cloud environment

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

DR-strategy-analysis

Related Documents