Study guide
8.3 Compute Backup & Recovery Design
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
8.3 Compute Backup & Recovery Design
Key Takeaways Explain This Topic AI
Azure Backup answers point-in-time data recovery for compute; Azure Site Recovery answers whole-environment failover -- the exam tests whether you pick the right one for a stated requirement.
Only the Enhanced backup policy supports sub-daily (every 4/6/8/12-hour) backups and zone-redundant/zone-pinned VM configurations; Standard policy is limited to one backup per day.
Cross Region Restore requires the vault to use geo-redundant storage (GRS) -- LRS or ZRS vaults cannot restore into the paired region.
Default retention tiers are 180 days (daily), 12 weeks (weekly), 60 months (monthly), and 10 years (yearly), all configurable per policy to match compliance requirements.
Soft delete protects against accidental or malicious backup deletion for a recoverable window (commonly around 14 days) and is a ransomware-resilience control, not a retention strategy by itself.
Last updated: July 2026
Why This Topic Matters
This section answers the official skill "Recommend a backup and recovery solution for compute." Where Azure Site Recovery (previous section) answers "how do we fail over a whole running workload to another location," Azure Backup answers a different question: "how do we recover a virtual machine's data to a specific point in time after deletion, corruption, or a ransomware event?" AZ-305 scenarios test whether you can pick the right vault type and policy to hit stated retention, restore-speed, and cross-region requirements at a reasonable cost.
Vault Types: Recovery Services Vault vs. Backup Vault
Recovery Services vault Backup vault
Workloads Azure VMs, SQL/SAP HANA in Azure VMs, Azure Files, on-premises servers, and Azure Site Recovery Newer workloads: Azure Disks, Blob Storage (operational and vaulted backup), PostgreSQL Flexible Server
Primary use The original, broad-workload vault; still required for ASR Streamlined vault focused purely on Backup, built for management at scale with Backup Center/Azure Policy
Restore features Instant restore, Cross Region Restore Backup (Instant Restore) short-term retention and Cross-Region Restore
For AZ-305 purposes, when a scenario says "back up Azure VMs," the Recovery Services vault is almost always the right answer; when it names disk-level or blob-level backup as a standalone need, the Backup vault is increasingly the modern answer.
Backup Policies: Standard vs. Enhanced
Standard policy : one backup per day; instant-restore snapshots retained locally for 2 days by default (configurable 1-5 days) before the vault copy takes over.
Enhanced policy : supports multiple backups per day (every 4, 6, 8, or 12 hours), required for zone-redundant/zone-pinned VMs, and retains instant-restore snapshots locally for 7 days by default (configurable 1-30 days).
Instant restore serves recovery requests directly from the local disk snapshot -- much faster than pulling data back from the vault -- so a scenario emphasizing fast restore of recent data should point you toward a shorter-interval Enhanced policy with a longer instant-restore snapshot window, not just "more retention."
Retention Hierarchy
Azure Backup retention is layered so you are not forced to keep every daily point forever:
- Retention tier Default retention
- Daily backup points 180 days
- Weekly backup points 12 weeks
- Monthly backup points 60 months
- Yearly backup points 10 years
All of these are configurable per policy. A scenario requiring "7 years of quarterly recovery points for compliance" is describing the yearly/monthly retention tiers , not a separate product.
Redundancy, Cross Region Restore, and Soft Delete
Storage redundancy for the vault itself (LRS, ZRS, GRS) determines whether backup data survives a regional outage. Cross Region Restore (CRR) -- restoring a VM directly into the paired region -- requires the vault to use geo-redundant storage (GRS) ; it is unavailable with LRS or ZRS.
Soft delete protects against accidental or malicious deletion of backup data (a key ransomware-resilience control): deleted backup items are retained in a soft-deleted state for a default recoverable window (commonly around 14 days) before permanent purge, and during that window an administrator can undelete the backup data.
Worked Scenario
A retail company runs order-processing VMs and states: "We need at least two backups per day, must be able to restore a VM into our secondary region if the primary region is unavailable, and we must be protected against an admin accidentally deleting the backup data." The design: use a Recovery Services vault configured with GRS , apply the Enhanced backup policy with a sub-daily schedule (e.g., every 12 hours), enable Cross Region Restore , and rely on the vault's default soft-delete protection. Each stated requirement maps to one specific configuration choice -- there is no single "enable everything" toggle, so the exam expects you to connect each requirement to its matching feature.
Common Decision Traps
Choosing the Standard policy when the scenario requires more than one backup per day or zone-pinned VM support -- only Enhanced policy supports sub-daily schedules and zone-redundant configurations.
Forgetting that Cross Region Restore requires GRS specifically -- picking LRS "to save cost" silently breaks a stated cross-region restore requirement.
Confusing Azure Backup's point-in-time VM recovery with Azure Site Recovery's whole-environment failover -- a requirement to "keep the app running in another region during an outage" is ASR, not Backup, even though both use a vault.
Treating soft delete as a backup strategy on its own -- it is a safety net against deletion, not a substitute for retention policy design.
Quick Recall Table
- Requirement in the scenario Feature to recommend
- More than one backup per day Enhanced backup policy
- Fast restore of very recent data Instant restore with an extended snapshot retention window
- Restore into the paired region after an outage Cross Region Restore (requires GRS)
- Protection against accidental/malicious backup deletion Soft delete (default vault behavior)
- Multi-year compliance retention Yearly retention tier, up to 10 years