How SQL Server backup and recovery to the cloud are simplified

Apart from hard disks and tapes, you can now use the local backup function of SQL Server to back up your SQL Server Database to the Windows AzureBlob storage service. In this version, you can back up your T-SQL and SMO to Windows AzureBlob storage. SQLServer Databases on an SQL Server instance or in a host environment, such as an SQL Server instance running on Windows Azure VMs, can use this function.

Benefits:

· Flexible, reliable, and unlimited offline storage for disaster recovery: storing your backups on the Windows AzureBlob service is a convenient, flexible, and easy-to-access offline choice. Creating offline storage for your SQL Server backup is as easy as modifying your existing scripts/jobs. Offline storage is usually far away from the location of the formal database to prevent a single disaster from affecting the location of both the offline database and the formal database. You can also restore the backup to the SQL Server Instance running on Windows Azure Virtual Machine for disaster recovery of in-house databases. In case of a disaster, selecting geo replicate Blob storage will generate an additional protective layer that can affect the entire region. In addition, you can easily read backups for restoration anytime, anywhere.

· Backup archiving: The Windows AzureBlob Storage Service provides a better way for users who often use tape for archiving and backup. Tape storage may need to be physically uploaded to an external facility and protected against damages. Storing backups on Windows Azure Blob Storage provides you with an instant, highly available, and persistent archiving method.

· No hardware management overhead: The Windows Azure Storage Service does not have any hardware management overhead. Windows Azure manages hardware, ensures redundancy for geo-replication, and protects against hardware faults.

· At present, you can back up the SQL Server instance running on WindowsAzure Virtual Machine to Windows Azure Blob storage service by creating the attached disk. However, the number of disks that can be attached to Windows Azure virtual machines is limited. The maximum number of instances is 16. If you back up data directly to WindowsAzure Blob Storage, the maximum number of 16 disks is not limited.

· In addition, backup files stored in the Windows AzureBlob storage service can be directly provided to the indoor SQL Server or other SQL Server running on Windows Azure Virtual Machine, you do not need to connect to, detach, or download the database, and then attach VHD.

· Cost-effectiveness: only pay for the services used. It is a way to save costs for offline backup archiving. Windows Azure pricing calculator helps you estimate costs.

Storage: fees are charged based on the space you use, the number of servers, and the redundancy level. For more details and the latest information, see the Data Management section of PricingDetails.

Data transmission: it is free to transfer inbound data to Windows Azure. Outbound transmission is charged based on the bandwidth usage and the amount of traffic in a specific area. For more information, see the prransfers chapter of PricingDetails.

How it works:

Backup to Windows Azure Storage is designed as a backup device (DISK/tape ). Using Microsoft Virtual Backup Device Interface (VDI), Windows Azure Blob storage is encoded as a "virtual Backup Device". The URL format used to access Blob storage is considered as a Device. The main reason for supporting Azure storage as the target device is that it provides consistent and seamless backup and restoration processes, similar to our current disk and tape.

When the backup or restoration process is called and the URL "device type" is specified for Windows AzureBlob storage, the engine calls the VDI client process, which is part of this feature. The backup data is sent to the VDI client process and then to Windows AzureBlob storage.

As mentioned above, the URL is the same as the backup device we are currently using, but it is not a physical device, so there are some restrictions. For a list of all the methods supported by this tool, see SQLServer Backup and Restore with Windows Azure Blob Storage Service.

How to use it

To create a Windows AzureBlob Storage backup, you must first create a Windows Azure Storage account, and then create an SQL Server Credential to save the identity authentication information of the Storage account. Use the TRANSACT-SQL or SMO to issue Backup and Restore commands.

The following TRANSACT-SQL example describes how to create creden, complete database backup, and restore a database from a full database backup. For a complete instance of creating a storage account and performing simple restoration operations, see Tutorial: Getting Started with SQL Server Backup and Restore to Windows Azure BlobStorage Service.

Create creden

The following example shows how to create a credential to store Windows Azure Storage authentication information.

Back up the complete database

The following example shows how to back up the AdventureWorks2012 database to the Windows Azure Blob storage service.

Restore database

To restore the complete database backup, follow these steps.