Setting in an Azure Backup vault fixing when one type of workload is backed up and for how long. Policies don't extend beyond their vault, so VM and Azure Files policies must be created in each vault separately.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Backup policy in context, with comparison tables and the common traps.
Terms in this definition
- Azure Backup
Azure's backup service, which keeps recovery points, long-term retention included, in a Recovery Services vault. It restores data rather than failing workloads over, which is the job of Site Recovery.
- Workload
Also called an experience: a Fabric toolset aimed at one job role, e.g. Data Factory, Data Engineering, Data Warehouse, Real-Time Intelligence or Power BI. Each keeps its data in OneLake.
- Azure Files
Azure's managed file shares over SMB or NFS. There is no Archive tier, and a single encryption key applies across the whole storage account.
Related terms
- Enhanced policy
Backup policy for Azure VMs that supports several backups per day, scheduled every 4, 6, 8 or 12 hours.
- RPO
Recovery point objective: how much data, expressed as time, you can afford to lose. In a VM backup policy the smallest achievable RPO is the backup frequency.