azureblog.co.uk
← AZ-305 study plan
AZ-305 · Design business continuity solutions

Design backup and disaster recovery

Meeting RPO and RTO for Azure and hybrid workloads, and backup and recovery for compute, databases and unstructured data.

  • 16 min
  • 4 concepts
  • Try it yourself
  • 4-question check

Learn

Every recovery design starts with two numbers from the business. RPO (recovery point objective): how much data can we lose? RTO (recovery time objective): how long can we be down? The answers decide the solution and the cost.

  1. 1

    Recommend a recovery solution for Azure and hybrid workloads that meets recovery objectives

    Azure Backup gives point-in-time copies (RPO of hours, RTO of hours) against deletion, corruption and ransomware. Azure Site Recovery replicates VMs continuously to another region or from on-premises to Azure (RPO of seconds to minutes, RTO of minutes) for disaster recovery, with recovery plans. Use both: they solve different problems. Test with test failovers.

    Remember: Backup = get data back. Site Recovery = keep running elsewhere.

  2. 2

    Recommend a backup and recovery solution for compute

    Back up Azure VMs with a Recovery Services vault and Enhanced policy (several backups a day). Use Cross Region Restore on GRS vaults. Protect on-premises servers with the MARS agent or MABS. Back up AKS with Azure Backup for AKS (Backup vault). Turn on immutable vaults and multi-user authorisation against ransomware.

    Remember: Ransomware protection: immutable vault + MUA + soft delete.

  3. 3

    Recommend a backup and recovery solution for databases

    Azure SQL Database and Managed Instance have automatic backups with point-in-time restore (1 to 35 days) and long-term retention up to 10 years. Use geo-restore or failover groups for regional DR. Back up SQL Server and SAP HANA in VMs with Azure Backup workload backup. Cosmos DB offers periodic or continuous backup with point-in-time restore.

    Remember: Keep SQL backups for years: long-term retention.

  4. 4

    Recommend a backup and recovery solution for unstructured data

    Blobs: operational backup (local, continuous, point-in-time restore) and vaulted backup (copied to a Backup vault) via Azure Backup, plus soft delete and versioning. Azure Files: share snapshots managed by Azure Backup, with vaulted backup for longer retention. Object replication copies blobs to another account.

    Remember: Blobs: operational or vaulted backup.

RPO and RTO

RPO
  • How much data can you lose?
  • Measured back from the failure
  • Smaller = more frequent copies
RTO
  • How long can you be down?
  • Measured forward from the failure
  • Smaller = faster failover, higher cost

Try it

Pick a recovery design from the business's objectives.

This interactive part needs JavaScript.

In the portal

  • Business Continuity CenterAzure portal: Business Continuity Center > Overview
  • Long-term retentionAzure portal: SQL servers > your server > Data management > Backups > Retention policies

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your AZ-305 study plan.

  1. Which objective describes acceptable data loss?

  2. Which gives an RTO of minutes for VMs if a region fails?

  3. How long can Azure SQL long-term retention keep backups?

  4. Which stops attackers deleting backups?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.