|    +91 44 43626468 / 78 /  88    

Setting up disaster recovery site on cloud using Azure Site Recovery

How we enabled a Disaster Recovery Site on the cloud for a large enterprise running Microsoft stack On-premise over the last 10+ years

Customer Challenges

  • The customer was running an on premise Dev, QA and Production setup with a basic tape based back up.
  • The customer did not want to high cost of maintaining secondary data center for disaster recovery purposes
  • They did not have any remote site for restoration in case of any disaster situation.
  • A proper environment for to test fail over/ fail back conditions was unavailable
  • Unable to commit on a firm plan given the stringent Recovery Time Objective (RTO) and Recover Point Objective (RPO) from the business team

Key Technologies

  • Windows server 2016 Data center
  • IIS
  • NSG
  • Backup and Site Recovery - OMS ( Azure )

Software Used

  • IIS Manager
  • Windows Firewall and advanced security

Our Solution

We, at Paripoorna, implemented Azure based BC/DR setup using Active – Passive model and enabled Azure site recovery at the App VM level and SQL replication using Always On model.

Implementation Steps

  • A Resource group was created on Azure to bundle all of the created resources
  • Windows 2016 Server Datacenter edition was added in the created resource group
  • With the required parameters, it was configured for replication such NIC, NSG, and PIP. Also with Unmanaged Disks in case of dynamic scaling.
  • Upon completion of that event, the internal VM was configured to be created in order to host a server which required IIS. Once this was created and a demo page was deployed in it.
  • Azure Portal NSG, was configured to allow TCP data to flow through port 80 to the VMs. This was also internally configured in control panel.
  • After this a Backup and Site Recovery resource was created in a separate resource group, which will essentially act as a recovery vault for our resources created.
  • On Creation of the resource target and source resource group were configured along with the recovery resource group location which should be different from the source target location.
  • After creation, resource health was monitored to reach 100% healthy. This provided us the guarantee that the data is being safely replicated.
  • Once it has been completed, we performed a test failover in order to verify the deployments.

Business Impact

  • Disaster Recovery site setup on the cloud in the same GeoPolitical region of the client
  • Azure Site Recovery replicating the App VM on a agreed frequency to the recovery vault
  • Ability to clearly commit on the RTO and RPO laid out by the Business team.
  • Complete App level replication including the configuration files and Database level replication to ensure data consistency
  • Provision to exercise the BC/DR drill to check for readiness bridge the gaps if any
  • Keep the DR App VM in passive mode to save cost during normal hours

Similar stories

Tell us a little about yourself, and we'll be in touch right away