In today’s article, we will discuss the Recover service by utilizing the Azure Site Recovery service. The article talks about a quick overview of the service.
In order to make sure the operations within the Enterprise to work as it is supposed to it is vital for us to make sure all the infrastructure is running efficiently and don’t encounter any disasters and also doesn’t affect the business operations continuity, the organizations have to design and implement a Disaster Recovery team.
So with Site Recovery service is nothing but a plan B of execution whenever your systems go down. Instead of affecting your business operations and minimize the disaster, your business operations are completely diverted to Virtual machines and physical servers. Thus by doing this, the business can continually work as are were supposed to work and they couldn't find any change at all.
This is more sort of a backup plan. Let say if your primary site is up and running then your systems will be automatically shifted towards your primary site of execution.
If you have an active electricity connection to your apartment and also an inverter connection. If you have experienced a power cut then the power supply to all your appliance is diverted and the power supply will come from the inverter. Vice versa.
As the name suggests this service is all about making sure that your data is always backed up. Using Azure Backup services, all your data is in safe hands and there is always a roll-out version is available just in case if anything happens.
1. Azure Virtual machines replicating between different Azure regions
2. Replication of the site to a secondary site.
So let us understand what does Site recovery will provide in terms of service. The following features will explain us in detail
By using the Site Recovery service, one can set up and manage a replication failure in the Azure portal.
So while the Site recovery does it’s an activity, i.e. replicating the application and it’s data. The replicated application data is stored in Azure storage. During this process, the data is not at all affected.
1. RTO stands for Recovery Time Objectives
2. RPO stands for Recovery Point Objectives
Based on these points, the application is replicated and this can be managed by further integrating with Azure Traffic Manager.
Based on your recovery time objectives and recovery point objectives the application can be consistent and one can easily configure recovery points within the application-consistent snapshots.
You can easily test your failovers, again and again, to understand and analyze disaster recovery drills. All this can be happened without actually affecting your replication.
You can create custom-tailored recovery plans. Once the recovery plans are created they can be easily integrated with Azure automation tools.
All the automation libraries which are provided by Azure are production-ready and specific scripts according to the application can be easily downloaded and integrated to Site Recovery without any problem.
All the networking management settings, load balancers configuration, including reserving IP addresses and integration to Azure Traffic Manager can be easily done.
What is the operating system that the replicated machines would need?
For Hyper V VMs, any guest OS which is supported by Azure should be sufficient.
You can actually replicate any running workload that is supported on a replicated machine.
So we have talked about Azure Site recovery services and the features that are available with this service. If you feel that any of the vital information is worth mentioning then please do advise in the comments section.
Free Demo for Corporate & Online Trainings.