Skip to main content

[2] Azure Tips and Tricks: Recovery Service vaults across regions

By

 Context:

You are managing multiple Azure VMs in 3 regions across the EU. Let's assume that you are using West Europe, North Europe, and UK West.

Problem:

Initially, the critical systems were running in UK West, a Recovery Service Vault was created in North Europe and configured. 

In the next 3 months, the critical application will need to run across all 3 regions. One of the requests is to ensure that the same backup and configuration policy is enforced across all regions.



Solution:

Most of the people would try to use the same instance of Recovery Vault from UK West regions across all regions. Unfortunately, this is not possible, a vault can be used only for resources from the same region. 

When you use a Recovery Vault all data and configuration information for each VM is copied and stored inside the vault. A vault is created for specific Regions for which you want to protect and ensure that you have a DR plan.

Behind the scene, when you enable a DR for a VM, the Site Recovery Mobility extension is deployed to the VM and the VM is added to Azure Site Recovery. From there, the data is automatically copied in cache storage in the source region. From there the data is pushed to the target region where multiple recovery points are created and ready to be used in the case of a DR. The target region will use the last recovery point available for each VM. 

In our case, you need to configure a new instance of Recovery Vault in each region. Even if this might sound like a lot of extra work, things are much simpler. If you already using Resource Manager (ARM) and automation, you would be able to reuse the UK West configuration for other regions, with just small changes in the parameters. Don't forget to activate Site Recovery and enable replication for the given VMs. 

Additional to it, for critical application it is important to so resource reservation to ensure that in a case of a disaster you have computation and storage resources that can be used to host and run your Azure VMs.

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more