Simplify SQL Server backup and restore to cloud working principle and operation Method _mssql

In addition to hard drives and tapes, you can now use SQL Server's native backup feature to back up your SQL Server database to Windows azureblob storage service. In this release, you can use T-SQL and SMO backups to Windows Azureblob storage. This functionality can be exploited in SQL Server databases or in a hosting environment, such as an instance of SQL Servers running on Windows Azure VMS, in an instance on the server.

Benefits :

· Flexible, reliable, and unlimited offline storage to improve disaster recovery: storing your backups on Windows Azureblob Services is a convenient, flexible, and easy to access offline option. Offline storage to create your SQL Server backup is as easy as modifying your existing scripts/jobs. Offline storage is usually far enough away from the official database to prevent a single disaster from potentially affecting the location of offline and official databases. You can also restore backups to SQL Server Instance running on Windows Azure Virtual machine for disaster recovery in an indoor database. In the event of a disaster, selecting Geo Replicate BLOB storage will create an additional layer of protection that can affect the entire area. In addition, you can easily read backups for recovery anytime, anywhere.

· Backup archive: The Windows Azureblob Storage service provides a better way for users who frequently use tape to archive backups. Tape storage may require physical transmission to an external facility and will also protect these media from damage. Storing backups on Windows Azure Blob Storage provides an instant, highly available, and durable way to archive.

· No hardware management overhead: Using the Windows Azure Storage Service does not have the overhead of hardware management. Windows Azure Services manages hardware and guarantees redundancy for geo-replication and provides protection against hardware failure.

· Currently, you can back up the SQL Server instance running in Windowsazure Virtual machine to the Windows Azure Blob storage service by creating the accompanying disk. However, the number of disks that can be attached to the Windows Azure virtual machine is limited. The maximum instance is no more than 16. If you are backing up directly to Windowsazure Blob Storage, you can limit the maximum 16 disks.

· In addition, the backup files stored in the Windows Azureblob Storage Service can be provided directly to the SQL Server in the Windows or to others that are running on machine, which does not require a database connection/ Detach or download and then attach the VHD to the operation.

· Cost effectiveness: Just pay for the services you use. is a way to save cost for offline backup archives. Windows Azure Pricing Calculator can help you estimate costs.

Storage: Fees are priced according to the space you use, the number of servers, and the level of redundancy. For more detailed and up-to-date information, please refer to the Pricingdetails Data Management section.

Data transfer: Inbound data transfer to Windows Azure is free of charge. Outbound transmissions are based on bandwidth usage and are charged according to the amount of progressive specific areas. For more details, see the Datatransfers section of the Pricingdetails section.

How it works :

Backup to Windows Azure storage is designed to resemble a backup device (disk/tape). With Microsoftvirtual backup Device Interface (VDI), Windows Azure BLOB storage is encoded as a "virtual backup device," and the URL format used to access Blob storage is considered a device. The main reason for supporting Azure storage as a target device is that it provides a consistent and seamless backup and restore process, similar to our current disk and tape.

When the backup or restore process is invoked and the specified Windows Azureblob store uses the URL "device type", the engine invokes the VDI client process, which is also part of the feature. The backup data is sent to the VDI client process and is then sent to the Windows Azureblob store.

As mentioned above, the URL is the same as the backup device we are using now, but it is not a physical device, so there are some limitations. For a full list of the methods it supports, see SQL Server Backup and Restore with Windows Azure Blob Storage Service.

How to use it

To write a backup of a Windows Azureblob store, you must first create a Windows Azure storage account, and then create a SQL Server credential to save the authentication information for the stored account. You can use Transact-SQL or SMO to issue backup and restore commands.

The following Transact-SQL example describes the process of creating credentials, doing a full database backup, and restoring a database from a full database backup. For a complete instance of creating a storage account and performing a simple restore operation, see tutorial:getting started with SQL Server Backup and restore to Windows Azure blobstorage Servic E.

Create credentials

The following example shows how to create a credential that stores Windows Azure storage authentication information.

Back up the full database

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

Restore Database

To restore a full database backup, follow these steps.