3.1.4.1. Create and Configure a Recovery Services Vault
3.1.4.1. Create and Configure a Recovery Services Vault
💡 First Principle: A Recovery Services vault is the fundamental Azure resource for centralizing backup and disaster recovery management, providing a secure, scalable, and policy-driven control plane for protecting diverse workloads.
Scenario: Your organization needs a centralized solution to manage backups for all its Azure Virtual Machines, SQL Databases, and Azure File Shares. This solution must be scalable and protect backups from accidental deletion, with data replicated to a secondary region for disaster recovery.
What It Is: A Recovery Services vault is a logical container that stores the backup data for various Azure and on-premises workloads.
How to create a Recovery Services vault:
-
In the Azure Portal, search for "Recovery Services vaults" and select "Create."
-
Specify:
- Subscription: Choose the billing context.
- Resource Group: Select or create for logical organization.
- Vault Name: Enter a unique identifier.
- Region: Pick the closest Azure Region for compliance and performance.
-
Storage Replication Type: This choice can only be changed while the vault contains no backup items and dictates its disaster recovery capabilities.
- LRS (Locally Redundant Storage): Replicates data within a single datacenter; cost-effective, but less resilient to datacenter-level outages.
- GRS (Geo-Redundant Storage): Replicates data to a secondary Region hundreds of miles away; higher durability and disaster protection.
Key Considerations:
- Security: Enable soft delete to protect backups from accidental or malicious deletion. Consider immutability to prevent changes to backup data for a set period.
- Monitoring: Integrate with Azure Monitor for backup health, alerts, and job status.
⚠️ Common Pitfall: Choosing LRS replication for a vault that protects critical production workloads. This provides no protection against a regional disaster.
Key Trade-Offs:
- Durability (GRS) vs. Cost (LRS): GRS provides disaster recovery capability but is more expensive than LRS. The choice depends on the criticality of the data being protected.
Recovery Services Vault vs. Azure Backup Vault
💡 First Principle: Azure Backup has two vault types, and the datasource decides which one you need. Creating the right vault first saves a redesign later.
Scenario: Your Recovery Services vault already protects the production VMs. The storage team now wants backups for blob containers and for individual managed disks, and asks whether the existing vault can take them.
What It Is: A Backup vault is a storage entity that holds backup data for the newer workloads Azure Backup supports. It's a separate resource from the Recovery Services vault, not a replacement for it.
| Recovery Services vault protects | Backup vault protects |
|---|---|
| Azure Virtual Machines | Azure Disks |
| SQL Server in Azure VM | Azure Blobs |
| SAP HANA in Azure VM | Azure Database for PostgreSQL server |
| Azure Files | Kubernetes services (preview) |
| MARS agent, Azure Backup Server (MABS), DPM |
How to create a Backup vault:
- In the portal, search for Backup vaults and select Add.
- On Basics, pick the subscription, resource group, vault name, and region.
- Choose Storage redundancy. Geo-redundant is the recommended default when Azure is your primary backup store; locally redundant costs less. Storage redundancy can't be changed after you protect items in the vault.
- Select Review + create.
The vault's identity does the work: A Backup vault uses its managed identity to reach the resources it protects, so it needs role assignments before backup validates:
- Azure Disk Backup: Disk Backup Reader on the source disk, and Disk Snapshot Contributor on the snapshot resource group. The portal's Add missing roles action can grant both.
- Azure Blob backup: Storage Account Backup Contributor on the storage account.
Where disk backups actually live: Azure Disk Backup is operational-tier only. It takes incremental snapshots and keeps them in the snapshot resource group in your subscription; they aren't copied into vault storage, so the vault's LRS/GRS setting doesn't apply to them. The vault and the disk must be in the same region.
⚠️ Exam Trap: "One vault for everything" is the misconception. A VM goes in a Recovery Services vault, while blobs and standalone disks go in a Backup vault. Adding another Recovery Services vault never adds blob or disk support.
Reflection Question: How does creating and configuring a Recovery Services vault, particularly by choosing the appropriate storage replication type (e.g., GRS), fundamentally enable centralized backup management and ensure data durability for diverse workloads?