Simplify SQL Server backup and restore to WindowsAzure

SQLServer2012SP1CumulativeUpdate2 has a new function that simplifies the backup and restoration capabilities of SQLServer databases from the Internal Platform SQLServer to WindowsAzure. Now, you can directly use SQLServerNativeBackup to create a backup to WindowsAzureStorage. See the following content to obtain the new

SQL Server 2012 SP1 Cumulative Update 2 has a new function that simplifies the SQL Server database backup and restoration capabilities from the in-house platform SQL Server to Windows Azure. Now, you can directly use SQL Server Native Backup to create a Backup to Windows Azure Storage. See the following content to obtain the new

SQL Server 2012 SP1 Cumulative Update 2 has a new feature that simplifies the SQL Server backup and restoration capabilities from the in-house platform SQL Server to Windows Azure. Now, you can directly use SQL Server Native Backup to create a Backup to Windows Azure Storage. For more information, see the following.

To update, go.

Overview:

Apart from hard disks and tapes, you can now use the local backup feature of SQL Server to back up your SQL Server Database to the Windows Azure Blob storage service. In this version, you can back up to Windows Azure Blob Storage Using T-SQL and SMO. SQL Server 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 Azure Blob 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 Azure Blob 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.
• There is no hardware management overhead: There is no hardware management overhead when you use the Windows Azure storage service. 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 Windows Azure 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 Windows Azure Blob Storage, you can ignore the limit of up to 16 disks.
• In addition, backup files stored in the Windows Azure Blob storage service can be directly provided to the indoor SQL Server or other SQL Server running on the 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, quantity, and redundancy levels.

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.

How it works:

Backup to Windows Azure Storage is designed as a backup device (DISK/tape ). With 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 Azure Blob 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 Azure Blob 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.

How to use it

To create a Windows Azure Blob 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.

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.