Backup and Restore for SQL Server in Azure Virtual Machines
This article provides guidance on the backup and restore options available for SQL Server running in a Windows virtual machine in Azure. Azure Storage maintains three copies of every Azure VM disk to guarantee protection against data loss or physical data corruption. Thus, unlike on-premises, you don't need to focus on hardware failures. However, you should still backup your SQL Server databases to protect against application or user errors, such as inadvertent data insertions or deletions. In this situation, it is important to be able to restore to a specific point in time.
The first part of this article provides an overview of the available backup and restore options. This is followed by sections that provide more information on each strategy.
Backup and restore options
The following table provides information on various backup and restore options for SQL Server running on Azure VMs:
|Automated Backup allows you to schedule regular backups for all databases on a SQL Server VM. Backups are stored in Azure storage for up to 30 days. Beginning with SQL Server 2016, Automated Backup v2 offers additional options such as configuring manual scheduling and the frequency of full and log backups.|
|Azure Backup for SQL VMs||2012
|Azure Backup provides an Enterprise class backup capability for SQL Server running in Azure VMs. With this service, you can centrally manage backups for multiple servers and thousands of databases. Databases can be restored to a specific point in time in the portal. It offers a customizable retention policy that can maintain backups for years. This feature is currently in public preview.|
|Manual backup||All||Depending on your version of SQL Server, there are various techniques to manually backup and restore SQL Server running on an Azure VM. In this scenario, you are responsible for how your databases are backed up and the storage location and management of these backups.|
The following sections describe each option in more detail. The final section of this article provides a summary in the form of a feature matrix.
Automated Backup provides an automatic backup service for SQL Server Standard and Enterprise editions running in a Windows VM in Azure. This service is provided by the SQL Server IaaS Agent Extension, which is automatically installed on SQL Server Windows virtual machine images in the Azure portal.
All databases are backed up to an Azure storage account that you configure. Backups can be encrypted and retained for up to 30 days.
SQL Server 2016 and higher VMs offer more customization options with Automated Backup v2. These improvements include:
- System database backups
- Manual backup schedule and time window
- Full and log file backup frequency
To restore a database, you must locate the required backup file(s) in the storage account and perform a restore on your SQL VM using SQL Server Management Studio (SSMS) or Transact-SQL commands.
For more information on how to configure Automated Backup for SQL VMs, see one of the following articles:
- SQL Server 2016/2017: Automated Backup v2 for Azure Virtual Machines
- SQL Server 2014: Automated Backup for SQL Server 2014 Virtual Machines
Azure Backup for SQL VMs (Public Preview)
Azure Backup provides an Enterprise class backup capability for SQL Server running in Azure VMs. All backups are stored and managed in a Recovery Services vault. There are several advantages that this solution provides, especially for Enterprises:
- Zero-infrastructure backup: You do not have to manage backup servers or storage locations.
- Scale: Protect many SQL VMs and thousands of databases.
- Pay-As-You-Go: This capability is a separate service provided by Azure Backup, but as with all Azure services, you only pay for what you use.
- Central management and monitoring: Centrally manage all of your backups, including other workloads that Azure Backup supports, from a single dashboard in Azure.
- Policy driven backup and retention: Create standard backup policies for regular backups. Establish retention policies to maintain backups for years.
- Support for SQL Always On: Detect and protect a SQL Server Always On configuration and honor the backup Availability Group backup preference.
- 15-minute Recovery Point Objective (RPO): Configure SQL transaction log backups up to every 15 minutes.
- Point in time restore: Use the portal to recover databases to a specific point in time without having to manually restore multiple full, differential, and log backups.
- Consolidated email alerts for failures: Configure consolidated email notifications for any failures.
- Role-based access control: Determine who can manage backup and restore operations through the portal.
For a quick overview of how it works along with a demo, watch the following video:
This Azure Backup solution for SQL VMs is currently in public preview. For more information, see Back up SQL Server database to Azure.
If you want to manually manage backup and restore operations on your SQL VMs, there are several options depending on the version of SQL Server you are using. For an overview of backup and restore, see one of the following articles based on your version of SQL Server:
- Backup and Restore for SQL Server 2016 and later
- Backup and Restore for SQL Server 2014
- Backup and Restore for SQL Server 2012
- Backup and Restore for SQL Server SQL Server 2008 R2
- Backup and Restore for SQL Server 2008
The following sections describe several manual backup and restore options in more detail.
Backup to attached disks
For SQL Server running in Azure VMs, you can use native backup and restore techniques using attached disks on the VM for the destination of the backup files. However, there is a limit to the number of disks you can attach to an Azure virtual machine, based on the size of the virtual machine. There is also the overhead of disk management to consider.
For an example of how to manually create a full database backup using SQL Server Management Studio (SSMS) or Transact-SQL, see Create a Full Database Backup.
Backup to URL
Beginning with SQL Server 2012 SP1 CU2, you can back up and restore directly to Microsoft Azure Blob storage, which is also known as backup to URL. SQL Server 2016 also introduced the following enhancements for this feature:
|Striping||When backing up to Microsoft Azure blob storage, SQL Server 2016 supports backing up to multiple blobs to enable backing up large databases, up to a maximum of 12.8 TB.|
|Snapshot Backup||Through the use of Azure snapshots, SQL Server File-Snapshot Backup provides nearly instantaneous backups and rapid restores for database files stored using the Azure Blob storage service. This capability enables you to simplify your backup and restore policies. File-snapshot backup also supports point in time restore. For more information, see Snapshot Backups for Database Files in Azure.|
For more information, see the one of the following articles based on your version of SQL Server:
- SQL Server 2016/2017: SQL Server Backup to URL
- SQL Server 2014: SQL Server 2014 Backup to URL
- SQL Server 2012: SQL Server 2012 Backup to URL
Beginning with SQL Server 2014, Managed Backup automates the creation of backups to Azure storage. Behind the scenes, Managed Backup makes use of the Backup to URL feature described in the previous section of this article. Managed Backup is also the underlying feature that supports the SQL Server VM Automated Backup service.
Beginning in SQL Server 2016, Managed backup got additional options for scheduling, system database backup, and full and log backup frequency.
For more information, see one of the following articles based on your version of SQL Server:
- Managed Backup to Microsoft Azure for SQL Server 2016 and later
- Managed Backup to Microsoft Azure for SQL Server 2014
The following table summarizes the capabilities of each backup and restore option for SQL Server virtual machines in Azure.
|Automated Backup||Azure Backup for SQL||Manual backup|
|Requires additional Azure service|
|Configure backup policy in Azure portal|
|Restore databases in Azure portal|
|Manage multiple servers in one dashboard|
|15-minute Recovery Point Objective (RPO)|
|Short-term backup retention policy (days)|
|Long-term backup retention policy (months, years)|
|Built-in support for SQL Server Always On|
|Backup to Azure Storage account(s)||(automatic)||(automatic)||(customer managed)|
|Management of storage and backup files|
|Backup to attached disks on the VM|
|Central customizable backup reports|
|Consolidated email alerts for failures|
|Customize monitoring based on Log Analytics|
|Monitor backup jobs with SSMS or Transact-SQL scripts|
|Restore databases with SSMS or Transact-SQL scripts|
If you are planning your deployment of SQL Server in an Azure VM, you can find provisioning guidance in the following guide: How to provision a Windows SQL Server virtual machine in the Azure portal.
Although backup and restore can be used to migrate your data, there are potentially easier data migration paths to SQL Server on an Azure VM. For a full discussion of migration options and recommendations, see Migrating a Database to SQL Server on an Azure VM.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.