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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

By
The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...
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