But what can I *do* with Windows Azure? Backups

If you want to know more about Windows Azure, how it works, the components, or more about the entire platform, I’ve written about that here: http://blogs.msdn.com/b/buckwoody/archive/2012/06/13/windows-azure-write-run-or-use-software.aspx


Maybe you just want to cut to the chase. Windows Azure. What do I *do* with it? Let’s talk about that. One of the quickest, easiest ways to use Azure is in the storage feature, as a backup target.  Can Windows Azure backup data, servers, workstations or databases? Yes. Yes it can.  Windows Azure storage is replicated three times in one datacenter (on different fault-domains) and then those three are replicated to another geographically separate (but still in the same country region) location, you get six copies of the data automatically. Your data stays in the datacenter you choose, and is replicated within a geo-politically same region. So it’s actually a great target for backups.

First, you need a storage account, a container underneath that, and a Blob object to put the backups on. Here’s how you do that (for free):

  1. Set up an account: https://www.windowsazure.com/en-us/pricing/free-trial/
  2. Create a Container: http://www.windowsazure.com/en-us/develop/net/how-to-guides/blob-storage/#create-account (Steps 1-7 are all you need)
  3. Get the Account String: Open the Portal (as above), click on Storage, select the account you want, and click Manage Keys at the bottom of the screen. Copy that string to a secure place.

OK, now that you have all that, you’re all set. In fact, you’re all set for things like Web Sites, VM’s, Code Deployment and lots of other things, but let’s focus on backups first. What are your options?

Mount a Drive, Use as Backup Target

The easiest way to send files to Windows Azure is to mount the storage as if it is a local drive.  You can use that as regular storage (I’ll talk more about this in my next post) but you can also use that as a drive letter where you can send backups. While that’s simple to implement, it isn’t always the most efficient – you’re going through a layer of storage abstraction. Still and all, it’s a good choice and quick and easy to implement.  Here are some options:

Backup Servers and Workstations using Third-Party Software

In addition to (and including) the providers mentioned above, some also skip the step of having to mount a drive to use as a backup target, and simply allow you to mount an agent or tool that just backs up straight to Azure.

 Backup Servers and Workstations using Hardware

Backup Servers and Workstations using Data Protection Manager

Data Protection Manager is a feature that is part of the System Center suite. We’ve updated that in the latest versions that will allow you to incrementally back up Servers and even Workstations and Laptops straight to Windows Azure. The beauty of this feature is that if the user is in a remote office or traveling the data will flow up to Windows Azure from wherever they are. 

Backup SQL Server Databases

SQL Server can use the mounted-drive approach described above, and you can back up your databases


Comments (3)

  1. tonyr says:

    if you are on w2k12 servers doesn't the native windows backup have an interface to azure storage?

  2. BuckWoody says:

    TonyR – yes, you could do that. But The scenario I'm talking about here is on-prem to Azure. Thanks for reading!

  3. Krasen Asenov says:

    I'd like to comment on Backup SQL Server Databases:

    Mount Drive will not work unless you mount the drive with the account which runs the SQL service.

    SQL Server 2012 backup to Windows Azure is great, but if you are using earlier version, you can use Microsoft® SQL Server® Backup to Microsoft Windows® Azure®Tool http://www.microsoft.com/…/details.aspx

    It can even compress/encrypt the backups.

Skip to main content