Disaster Recovery: 3-Weeks Implementation

Why Disaster Recovery as a Service (DRaaS)?

• Traditional DR implementations are complex, costly with higher RPO & RTO and very difficult to test & validate
• Protect your environment by automating the replication of the virtual machines using Azure Site Recovery
• Use Azure or your secondary datacenter as your recovery site
• Easy Failback Capabilities & reduced RTO & RPO with low cost
• Protect Microsoft Hyper-V, VMware, and physical servers
• Easily create Disaster Recovery plans (No impact DR testing)
• Data encrypted while in replication and at rest

Steps for Implementation

Day 1-2: Discovery/Assessment

• Business Impact Analysis (BIA) for Application
• Requirements for RTO and RPO
• Application Assessment/Infrastructure Assessment
• Identify prerequisites and dependencies

Day 2-6: Design/Implementation

• DR Cost Estimate Creation and Approval (Protection Cost/Running Cost)
• DR Architecture Design
• Define DR Procedures and Processes
• Implementation and configuration of DR environment using ASR
• Replication of data and completion of protection

Day 7-10: Test/Pilot

• No impact test failover to cloud
• Validation of DR processes and procedures
• Validation of RTO & RPO
• Full DR Drill (failover & failback) of Production environment
• Finalize DR procedure documents

Note

• This service and commercials are defined for a single two-tier application consisting one instance of web & database each
• This is a standard offering, the price may change based on the complexity of the application & environment