This slide deck is used for my Azure Back to school video contribution about Azure Backup and how it can be used to backup and restore all your Azure IaaS workloads.
8. AZURE IAAS VM BACKUP SCENARIOS
Data Loss or Corruption
Create a VM copy
Accidental deletion of a VM
9. IMPLEMENTING IAAS VM BACKUPS
1) Create a Resource Group and setup a Recovery Services vault in the region where you want to store
the VM backup. Also determine how you want your storage replicated locally-redundant storage
(LRS) or geo-redundant storage (GRS), which is also the default. If you enable cross-region-restore,
backup storage is upgraded to read-access geo-redundant storage (RA-GRS).
2) Create a new or choose an existing Backup Policy to define the number of snapshots and retention
range intervals (day, week, month, year). Also specify the resource group to store the instant
recovery points if you want to use your own naming convention.
3) Backup the VM. Be aware that for the backup extension to work, the Azure VM Agent must be
installed on the Azure VM.
11. BACKUP AZURE IAAS LINUX VMS
▪ Backup takes a file-consistent backup
▪ During first backup, VMSnapshotLinux
extension is installed
▪ App-consistent backup -> customize
pre/post scripts
▪ Only supports ARM
https://github.com/MicrosoftAzureBackup/VMSnapshotPluginConfig
12. ▪ Application-consistent snapshot
When recovering a VM with an app-consistent
snapshot, the VM boots up and there is no data
corruption or loss. The apps start in a consistent state.
▪ File-system consistent snapshot
When recovering a VM with a file-system consistent
snapshot, the VM boots up and there is no data
corruption or loss. But apps need to implement their
own “fix-up” mechanism to make sure that restored
data is consistent.
▪ Crash-consistent snapshot
Although there are no guarantees, the VM usually
boots, and then it starts a disk check to fix
corruption errors. Any in-memory data or write
operations that weren't transferred to disk before the
crash are lost. Apps implement their own data
verification.
SNAPSHOT CONSISTENCY
13. AZURE IAAS VM BACKUP RESTORE OPTIONS
Also restore an encrypted VM and Cross region restore
14. BACKUP FOR SQL SERVER RUNNING IN AZURE VM
15min RPO
Auto-protection
PIT restores
Support for AG
Support for PowerShell
Database size up to 2TB
ARM and ASM
15. ! Things to keep in mind !
▪ You can create up to 500 Recovery Services vaults per subscription
▪ You can register 1000 Azure VMs per vault
▪ A Recovery Services vault can only change storage options before any backups
have been stored
▪ You can backup Azure VMs once a day
▪ There is no limit on the amount of data you can backup up in a Recovery
Services vault
18. WHAT IS A PROTECTED INSTANCE
Protected Instance
Windows
Client
Windows
Server
SQL, Exchange and Sharepoint
Server
Size of Files & Folders
being protected
Size of Instances, Databases and
Content Farms
Protected
Azure, Hyper-V and VMWare
VMs and on-premises servers
The size of the allocated disk
determines the data size
19. BACKUP PRICE FOR AZURE VMS
Cost per
Protected
Instance
Small Instance < or = 50GB
Medium Instance > 50 but < or = 500GB
Large Instance > 500 GB
€ 4.2165/mo
€ 8.433/mo
€ 8.433/mo/500GB
Cost of LRS,
GRS or RA-GRS
consumed
Storage
Cost of LRS Block Blob Storage
Cost of GRS Block Blob Storage
€ 0.0189 per GB/mo
€ 0.0378 per GB/mo
No
Charges for
Restores
Outbound
Bandwidth
Storage
Transactions
Cost of RA-GRS Block Blob Storage € 0.0480 per GB/mo
20. BACKUP PRICE FOR SQL SERVER ON AZURE VMS
Cost per
Protected
Instance
Instance < or = 500 GB
Instance > 500 GB
€ 27.4073/mo
€ 27.4073/mo/500GB
Cost of LRS or
GRS consumed
Storage
Cost of LRS Block Blob Storage
Or,
Cost of GRS Block Blob Storage
€ 0.0189 per GB/mo
€ 0.0378 per GB/mo
When backing-up SQL Server running on an Azure VM, the size of the databases
configured for backup determines the size of each instance.
When backing-up SQL Server availability groups, the size of the databases configured
for backup on an availability group determines the size of each instance.
21. OPTIMIZE YOUR BACKUP COSTS
▪ Estimate your costs with the advanced Azure Backup pricing
estimator: https://aka.ms/AzureBackupCostEstimates
▪ Before starting any backup determine your required storage
redundancy settings
▪ Optimize your backup policies and retention
▪ Clean up backup for your deleted resources
▪ Exclude or include certain data disk(s) from being protected