Azure Backup protects data by creating recovery points for virtual machines, databases, and file shares. The backup policy defines how often a backup runs (frequency) and how long each recovery point is kept (retention). Recovery points are stored in a Recovery Services vault, which is a container that also holds backup configuration and encryption keys. When a failure occurs, you restore from the most recent valid recovery point, and the time needed to return to normal is defined by your recovery time objective (RTO); the amount of data you can afford to lose is your recovery point objective (RPO). Choosing the right backup policy means balancing cost (more frequent backups cost more) against your RPO requirement.
Azure Site Recovery (ASR) handles disaster recovery by replicating workloads from a primary region to a secondary region. The replication engine continuously copies changes to the target region, so the RPO can be as low as a few seconds. During a declared disaster you run a failover, which brings up the workloads in the secondary region using the replicated data. After the primary region recovers you can fail back to return to normal operation. The relationship between backup and disaster recovery is complementary: backup protects against data corruption or accidental deletion with long-term retention, while disaster recovery protects against a full-region outage with fast failover. You plan for both by deciding which workloads need only backup, which need full replication, and which need a combination of the two.
High availability keeps an application running even when individual components fail. Availability zones protect against a datacenter failure by placing resources in physically separate zones within the same region. For example, you deploy virtual machines across two or three zones, and a Standard Load Balancer distributes traffic to healthy instances in any zone. If one zone fails, the other zones continue to serve traffic. The design tradeoff is that cross-zone traffic adds a small amount of latency, and zonal resources cost more than single‑zone ones.
Availability sets protect against hardware failure within a single datacenter. An availability set places virtual machines into different update domains (so Azure reboots only one domain at a time during planned maintenance) and different fault domains (so VMs run on separate racks with independent power and network). Availability sets do not protect against a zone or region failure, so they are used when you cannot use zones or when lower cost is the priority. For stateful workloads, you must also decouple the application layer from the storage layer: use Azure Storage with geo‑redundancy to keep data accessible if the compute tier fails, or use a database with built‑in high availability like Azure SQL Database’s zone‑redundant configuration. The overall design decision depends on the workload’s criticality: mission‑critical applications use zones plus disaster recovery, while less critical ones may rely only on availability sets and backup.
A system architecture diagram comparing Availability Zones, which protect against datacenter failures using separate zones and a load balancer, with Availability Sets, which protect against rack failures within a single datacenter using fault and update domains.
Venture into the world of Azure Infrastructure, where design meets functionality. Harness your skills and gain mastery over complex cloud structures to ace the AZ-305 Designing Microsoft Azure Infrastructure Solutions exam!
Prepare and test your skills
Prepare and test your skills
Azure Backup protects against data corruption or accidental deletion through long-term retention of recovery points, whereas Azure Site Recovery (ASR) protects against full-region outages by continuously replicating workloads to a secondary region for fast failover. While Azure Backup creates scheduled restore points for virtual machines, databases, and file shares, Azure Site Recovery enables continuous replication with a recovery point objective (RPO) as low as a few seconds.
Availability zones protect against datacenter failures by placing resources in physically separate zones within the same region, whereas availability sets protect against hardware failures within a single datacenter. Availability sets distribute virtual machines across update domains and fault domains on separate racks, but they do not protect against zone or region outages.
Recovery time objective (RTO) is the time needed to return workloads to normal operation after a failure occurs, whereas recovery point objective (RPO) is the amount of data loss that can be afforded. In backup design, backup frequency is balanced against RPO requirements and cost, while continuous disaster recovery replication can reduce RPO to a few seconds.
StudyCerts
StudyCerts