What is Azure Backup?
The Azure Backup service backs up data to the Microsoft Azure cloud. You can back up on-premises machines and workloads, and Azure virtual machines (VMs).
Why use Azure Backup?
Azure Backup delivers these key benefits:
- Offload on-premises backup: Azure Backup offers a simple solution for backing up your on-premises resources to the cloud. Get short and long-term backup without the need to deploy complex on-premises backup solutions.
- Back up Azure IaaS VMs: Azure Backup provides independent and isolated backups to guard against accidental destruction of original data. Backups are stored in a Recovery Services vault with built-in managed of recovery points. Configuration and scalability are simple, backups are optimized, and you can easily restore as needed.
- Scale easily - Azure Backup uses the underlying power and unlimited scale of the Azure cloud to deliver high-availability with no maintenance or monitoring overhead.
- Get unlimited data transfer: Azure Backup does not limit the amount of inbound or outbound data you transfer, or charge for the data that is transferred.
- Outbound data refers to data transferred from a Recovery Services vault during a restore operation.
- If you perform an offline initial backup using the Azure Import/Export service to import large amounts of data, there is a cost associated with inbound data. Learn more.
- Keep data secure: Azure Backup provides solutions for securing data in transit and at rest.
- Get app-consistent backups: An application-consistent backup means a recovery point has all required data to restore the backup copy. Azure Backup provides application-consistent backups, which ensure additional fixes are not required to restore the data. Restoring application-consistent data reduces the restoration time, allowing you to quickly return to a running state.
- Retain short and long-term data: You can use Recovery Services vaults for short-term and long-term data retention. Azure doesn't limit the length of time data can remain in a Recovery Services vault. You can keep it for as long as you like. Azure Backup has a limit of 9999 recovery points per protected instance.
- Automatic storage management - Hybrid environments often require heterogeneous storage - some on-premises and some in the cloud. With Azure Backup, there is no cost for using on-premises storage devices. Azure Backup automatically allocates and manages backup storage, and it uses a pay-as-you-use model, so that you only pay for the storage you consume. Learn more about pricing.
- Multiple storage options - Azure Backup offers two types of replication to keep your storage/data highly available.
- Locally redundant storage (LRS) replicates your data three times (it creates three copies of your data) in a storage scale unit in a datacenter. All copies of the data exist within the same region. LRS is a low-cost option for protecting your data from local hardware failures.
- Geo-redundant storage (GRS) is the default and recommended replication option. GRS replicates your data to a secondary region (hundreds of miles away from the primary location of the source data). GRS costs more than LRS, but GRS provides a higher level of durability for your data, even if there is a regional outage.
What's the difference between Azure Backup and Azure Site Recovery?
Both the Azure Backup and Azure Site Recovery services contribute to a business continuity and disaster recovery (BCDR) strategy in your business. BCDR consists of two broad aims:
- Keep your business data safe and recoverable when outages occur.
- Keep your apps and workloads up and running during planned and unplanned downtimes.
Both services provide complementary but different functionality.
- Azure Site Recovery: Site Recovery provides a disaster recovery solution for on-premises machines, and for Azure VMs. You replicate machines from a primary location to a secondary. When disaster strikes, you fail machines over to the secondary location, and access them from there. When everything's up and running normally again, you fail machines back to recover them in the primary site.
- Azure Backup: The Azure Backup service backs up data from on-premises machines, and Azure VMs. Data can be backed up and recovered at a granular level, including backup of files, folders, machine system state, and app-aware data backup. Azure Backup handles data at a more granular level than Site Recovery. As an example, if a presentation on your laptop became corrupted, you could use Azure Backup to restore the presentation. If you want to keep a VM configuration and data safe and accessible, you could use Site Recovery.
Use the table points to help figure out your BCDR needs.
|Data backup/retention||Backup data can be retained and stored for days, months, or even years if required from a compliance perspective.||Backup solutions like Azure Backup allow you to finely pick data you want to back up, and finely tune backup and retention policies.
Site Recovery doesn't allow the same fine-tuning.
|Recovery point objective (RPO)||The amount of acceptable data loss if a recovery needs to be done.||Backups have more variable RPO.
VM backups usually have an RPO of a day, while database backups have RPOs as low as 15 minutes.
Site Recovery provides a low RPO since replication is continuous or frequent, so that the delta between the source and replica copy is small.
|Recovery time objective (RTO)||The amount of time that it takes to complete a recovery or restore.||Because of the larger RPO, the amount of data that a backup solution needs to process is typically much higher, which leads to longer RTOs. For example, it can take days to restore data from tapes, depending on the time it takes to transport the tape from an off-site location.|
What backup scenarios are supported?
Azure Backup can back up both on-premises machines, and Azure VMs.
|Machine||Back up scenario|
|On-premises backup||1) Run the Azure Backup Microsoft Azure Recovery Services (MARS) agent on on-premises Windows machines to back up individual files and system state.
2) Back up on-premises machines to a backup server (System Center Data Protection Manager (DPM) or Microsoft Azure Backup Server (MABS)), and then configure the backup server to back up to an Azure Backup Recovery Services vault in Azure.
|Azure VMs||1) Enable backup for individual Azure VMs. When you enable backup, Azure Backup installs an extension to the Azure VM agent that's running on the VM. The agent backs up the entire VM.
2) Run the MARS agent on an Azure VM. This is useful if you want to back up individual files and folders on the VM.
3) Back up an Azure VM to a DPM server or MABS running in Azure. Then back up the DPM server/MABS to a vault using Azure Backup.
Why use a backup server?
The advantages of backing up machines and apps to MABS/DPM storage, and then backing up DPM/MABS storage to a vault are as follows:
- Backing up to MABS/DPM provides app-aware backups optimized for common apps such as SQL Server, Exchange, and SharePoint, in additional to file/folder/volume backups, and machine state backups (bare-metal, system state).
- For on-premises machines, you don't need to install the MARS agent on each machine you want to back up. Each machine runs the DPM/MABS protection agent, and the MARS agent runs on the MABS/DPM only.
- You have more flexibility and granular scheduling options for running backups.
- You can manage backups for multiple machines that you gather into protection groups in a single console. This is particularly useful when apps are tiered over multiple machines and you want to back them up together.
What can I back up?
|Machine||Backup method||Back up|
|On-premises Windows VMs||Run MARS agent||Back up files, folders, system state.
Linux machines not supported.
|On-premises machines||Back up to DPM/MABS||Back up anything that's protected by DPM or MABS, including files/folders/shares/volumes, and app-specific data.|
|Azure VMs||Run Azure VM agent backup extension||Back up entire VM|
|Azure VMs||Run MARS agent||Back up files, folders, system state.
Linux machines not supported.
|Azure VMs||Back up to MABS/DPM running in Azure||Back up anything that's protected by MABS or DPM including files/folders/shares/volumes, and app-specific data.|
What backup agents do I need?
|Back up Azure VMs||No agent needed. Azure VM extension for backup is installed on the Azure VM when you run the first Azure VM backup.
Support for Windows and Linux support.
|Back up of on-premises Windows machines||Download, install, and run the MARS agent directly on the machine.|
|Back up Azure VMs with the MARS agent||Download, install, and run the MARS agent directly on the machine. The MARS agent can run alongside the backup extension.|
|Back up on-premises machines and Azure VMs to DPM/MABS||The DPM or MABS protection agent runs on the machines you want to protect. The MARS agent runs on the DPM server/MABS to back up to Azure.|
Which backup agent should I use?
|I want to back up an entire Azure VM||Enable backup for the VM. The backup extension will automatically be configured on the Windows or Linux Azure VM.||Entire VM is backed up
For Windows VMs the backup is app-consistent. for Linux the backup is file-consistent. If you need app-aware for Linux VMs, you have to configure this with custom scripts.
|I want to back up specific files/folders on Azure VM||Deploy the MARS agent on the VM.|
|I want to directly back on-premises Windows machines||Install the MARS agent on the machine.||You can back up files, folders, and system state to Azure. Backups aren't app-aware.|
|I want to directly back up on-premises Linux machines||You need to deploy DPM or MABS to back up to Azure.||Backup of Linux host is not supported, you can only back up Linux guest machine hosted on Hyper-V or VMWare.|
|I want to back up apps running on on-premises||For app-aware backups machines must be protected by DPM or MABS.|
|I want granular and flexible backup and recovery settings for Azure VMs||Protect Azure VMs with MABS/DPM running in Azure for additional flexibility in backup scheduling, and full flexibility for protecting and restoring files, folder, volumes, apps, and system state.|
Backup and retention
Azure Backup has a limit of 9999 recovery points, also known as backup copies or snapshots, per protected instance.
- A protected instance is a computer, server (physical or virtual), or workload configured to back up data to Azure. An instance is protected once a backup copy of data has been saved.
- The backup copy of data is the protection. If the source data was lost or became corrupt, the backup copy could restore the source data.
The following table shows the maximum backup frequency for each component.Your backup policy configuration determines how quickly you consume the recovery points. For example, if you create a recovery point each day, then you can retain recovery points for 27 years before you run out. If you take a monthly recovery point, you can retain recovery points for 833 years before you run out. The Backup service does not set an expiration time limit on a recovery point.
|Azure Backup agent||System Center DPM||Azure Backup Server||Azure IaaS VM Backup|
(to Recovery Services vault)
|Three backups per day||Two backups per day||Two backups per day||One backup per day|
|Not applicable||Every 15 minutes for SQL Server
Every hour for other workloads
|Every 15 minutes for SQL Server
Every hour for other workloads
|Retention options||Daily, weekly, monthly, yearly||Daily, weekly, monthly, yearly||Daily, weekly, monthly, yearly||Daily, weekly, monthly, yearly|
|Maximum recovery points per protected instance||9999||9999||9999||9999|
|Maximum retention period||Depends on backup frequency||Depends on backup frequency||Depends on backup frequency||Depends on backup frequency|
|Recovery points on local disk||Not applicable||64 for File Servers
448 for Application Servers
|64 for File Servers
448 for Application Servers
|Recovery points on tape||Not applicable||Unlimited||Not applicable||Not applicable|
How does Azure Backup work with encryption?
|Encryption||Back up on-premises||Back up Azure VMs||Back up SQL on Azure VMs|
|Encryption at rest
(Encryption of data where it's persisted/stored)
|Customer-specified passphrase is used to encrypt data||Azure Storage Service Encryption (SSE) is used to encrypt data stored in the vault.
Backup automatically encrypts data before storing it. Azure Storage decrypts data before retrieving it. Use of customer-managed keys for SSE is not currently supported.
You can back up VMs that use Azure disk encryption (ADE) to encrypt OS and data disks. Azure Backup supports VMs encrypted with BEK-only, and with both BEK and KEK. Review the limitations.
|Azure Backup supports backup of SQL Server databases or server with TDE enabled. Backup supports TDE with keys managed by Azure, or with customer-managed keys (BYOK).
Backup doesn't perform any SQL encryption as part of the backup process.
|Encryption in transit
(Encryption of data moving from one location to another)
|Data is encrypted using AES256 and sent to the vault in Azure over HTTPS||Within Azure, data between Azure storage and the vault is protected by HTTPS. This data remains on the Azure backbone network.
For file recovery, iSCSI secures the data transmitted between the vault and the Azure VM. Secure tunneling protects the iSCSI channel.
|Within Azure, data between Azure storage and the vault is protected by HTTPS.
File recovery not relevant for SQL.
Send feedback about: