How to Run DR Solution on Azure Cloud?

Now, I would like to share how to optimize the usage of the DR Solution.
‍‍‍‍‍‍ 
When applications and data running on the Primary DC are damaged, this can be the big challenges of the organization to run continuously without any downtime with applications.
‍‍‍‍‍‍ 
So, DR solution (Disaster Recovery) is required. About DR solution has already been presented at former contents. In this content, I’ll discuss about DR solution related with how to process at minimum downtime and cost saving. 
‍‍‍‍‍‍ 
To start the DR solution, infrastructure, resources, configurations and all of the resources and services must be the same with DC infra. DR infra is usually located at one of the distances of DC infra. If there is a connection between DC and DR, we can define the best RPO and RTO time. For this solution, we can use the Cloud DR solution. So, I would like to discuss about how to use the cloud DR solution.
‍‍‍‍‍‍ 
On-Premise DR vs Cloud DR
‍‍‍‍‍‍ 
 There is no need to build the DR with the whole infrastructure like On-premise. So, we can save the initial cost investment.‍‍‍‍‍‍
‍‍‍‍‍‍ 
If DR is built On-premise, there may be within region or within country and if the whole region comes disaster, both DC and DR can be destroyed.‍‍‍‍‍‍
‍‍‍‍‍‍ 
 But, by using Cloud Solution, you can choose the region and country so that the region disaster can be recovered.‍‍‍‍‍‍
‍‍‍‍‍‍ 
 In Cloud Solution, the compute cost will count on charge only when failover start at the cloud.‍‍‍‍‍‍
‍‍‍‍‍‍ 
 Most of cloud providers can provide RPO and RTO for minimum downtime with zero RPO. So, the users can’t notice the downtime.‍‍‍‍‍‍
‍‍‍‍‍‍ 
How to Build DR with Azure Cloud
‍‍‍‍‍‍ 
So, how to build the DR with cloud solution.
‍‍‍‍‍‍ 
 As cloud solution, there have options to choose public cloud and private cloud. For example, AWS Cloud, Azure Cloud, Google Cloud and others Clouds are provided in Public cloud. 
‍‍‍‍‍‍ 
 At this content, I will explain about the Azure DR solution.
‍‍‍‍‍‍ 
 Whatever you make the choice for public clouds, there is a need to have the subscription. In Azure Cloud, we must also have the subscription.
‍‍‍‍‍‍ 
 And then, Configuration Server is needed to deploy at On-premise Datacenter (Primary Datacenter). Configuration Server is the main point in azure replication and connection between primary DC and Azure cloud. Data from primary DC will be replicated to the cloud by using configuration server and the service is used from Azure Site Recovery (ASR). So, ASR replication service works with the configuration server together.
‍‍‍‍‍‍ 
 From Azure side, Storage Account is required to keep the primary data which we replicated. 
‍‍‍‍‍‍ 
 The data from the storage account is located at the respective disk before the disaster occurs and failover is not started. When the failover is started at Azure, it changes to VM and starts running. VM compute cost will be only started at this time.
‍‍‍‍‍‍ 
 So, for the basic DR configuration, configuration server, storage account and ASR services will be needed. 
‍‍‍‍‍‍ 
 The time for the data replication between On-premise DC and Azure Cloud DR can provide real time synchronization which means that RPO will be zero so that the latest data before disaster can be received by using Azure ASR.
‍‍‍‍‍‍ 
 In other case, based on the organization requirements, other additional features such firewall, load balancer will be needed Other products can be available at Azure Market Place such Palo Alto, F5, SD-WAN, velo-cloud and many other products.
‍‍‍‍‍‍ 
 And also, Azure VPN can be used when it is connected with On-Premise.
‍‍‍‍‍‍ 
 In some cases, admins will have to open the device from azure cloud when the failover process started. These processes can be done by running auto-scripts. It’s only depended on the experiences and good skills of the cloud engineers and technicians.
‍‍‍‍‍‍ 
 RTO time is depending on the application admins and the running status of their application services.
‍‍‍‍‍‍ 
 Finally, when the DC comes stable again, failback can be processed from Azure Cloud to On-Premise or Primary DC. Data will be sent back to primary from Configuration server/ Process server there. 
‍‍‍‍‍‍ 
 After the Failback process is finished, VMs from Azure will be shut down and VMs will be run at Primary DC.
‍‍‍‍‍‍ 
So, I would summarize for DR solution. To start the best DR solution, there is no need to build another Datacenter to keep the best Datacenter facilities and to invest on the IT resources, connections and maintenance. By using the cloud services and applying the cloud architects, the DR solution can just build easily and cost effectively.
‍‍‍‍‍‍ 
How about current DC environment of customers?
Should DR solution be used on cloud and On-premise according to the organization nature? Which things are required to be done? And other suggestions can be advised by NEX4. In the next step, the best solutions and services can be also provided by NEX4.

Don’t forget to share this post!