Azure Backup
What it is
Azure Backup is Azure’s backup (data-protection) service. It takes secure, policy-driven backups (snapshots) of workloads — Azure VMs, on-premises servers (via MARS/MABS agents), SQL Server, Azure Files shares, and more — and stores them in a Recovery Services vault, from which you can restore.
Why it exists
Data loss protection for accidental deletion, corruption, or ransomware: you need reliable, retention-controlled, point-in-time copies you can restore on demand. Azure Backup provides managed, encrypted, off-server copies with a simple policy model — instead of scripting your own snapshot jobs.
Key ideas
- Workloads: Azure VMs (VM backup), on-prem → Azure (MARS agent or MABS), Azure Files shares, SQL Server / SAP HANA in VMs, blobs, and (managed) disks.
- Backup policy (Backup policy) defines what, when (schedule), and how long (retention) to back up — policy is applied via the vault.
- VM backup flow: uses snapshots (instant restores) stored in the vault + transfers data; backed up to the vault with vault-encrypted storage.
- Restore options: restore as a new VM, restore a disk, or restore to original/alternate location, from restore points.
- Security: vault-level encryption, soft delete, and checks against accidental deletion.
How it fits (diagram)
Diagrams courtesy of Microsoft Learn / Azure docs: backup/backup-overview
Exam notes
- Azure Backup = back up / restore (data protection); Site Recovery = disaster recovery replication (know the distinction).
- Backups are governed by a policy and land in a Recovery Services vault.
- VM backup supports instant restore via app-consistent snapshots.
- Vault must exist and a policy must be assigned before VM backups run.
Related
recovery-services-vault · azure-backup-policy · azure-site-recovery · azure-vm · Home
📘 Source: Microsoft Learn — Azure Backup