Last Update: Sep 24, 2024 | Published: Apr 09, 2014
Data protection is an all-time priority for IT administrators. It doesn’t really matter if the server catches fire or the hard disk roasts, as long as the data is safe. Even the slightest hint of data loss can send even the most experienced administrators into a tizzy. That’s a reason why there are dozens of backup solutions available in the market designed to protect objects, applications, servers and even complete sites.
A lot of meticulous planning is needed when it comes to designing a backup strategy: deciding between the types of storage to be used, the frequency of backup, and deploying complex products that often have a learning curve. Another important aspect of choosing a reliable backup solution is ensuring that it protects the data against site-wide failure in case of a catastrophe.
Microsoft Azure Online Backup — former known as Windows Azure online backup — offers a very quick and easy-to-configure entry-level backup solution for Windows Server. Once set up, it backs up your mission critical data at regular intervals to the cloud. It uses the familiar Windows Server Backup-type interface for ease of use. This is a cost-effective solution that is especially helpful in cases in which you want to quickly set up a data protection mechanism without having to bear the pain of procuring storage or setting up an offsite at a distant location to protect against a site-wide failure.
This functionality of Microsoft Azure IaaS leverages Microsoft Azure blob storage to store the backups. In this blog post, let’s try to configure a lab environment and see how that works in a little more detail using a Windows Server 2012 R2 box. For better understanding, I’m going to break this process into four steps.
If you don’t already have an Azure subscription, you may want to sign up for one. There [this_link_has_been_removed] (you may need a credit card to register). Once done, login to the Azure Management Portal.
This part can be a bit tricky if you’re not too familiar with certificates. You will need the makecert.exe tool from the Windows SDK (already present if you have Visual Studio installed or you’ll need to install the Windows SDK) to create a certificate (if not using an external CA) to be uploaded to Azure and installed on the server to be backed up. Note that a self-signed certificate made using IIS Manager does not seem to work (due to difference in enhanced key usage attribute).
makecert.exe -r -pe -n CN=CertificateName -ss my -sr localmachine -eku 1.3.6.1.5.5.7.3.2 -len 2048 -e 01/01/2016 CertificateName.cer
To add the server for backup in Azure, you’ll first need to download and install the Microsoft Azure Backup Agent for Windows Server on it to connect it to the Backup Vault created in step 1.
Most of your work is done. A final part of the job is to schedule the backups itself. You can choose the frequency of backup, time, bandwidth throttling, and encryption settings from here.
You can now either wait for the backup process to be triggered at the scheduled time or manually force it. We’ll try to manually force it to see how this looks. Here’s how we go about that:
That’s it! You’re now ready to roll. The recovery process is quite simple as well. I’ll leave that up to the readers to figure out. If you’ve got any questions, jot them down in the comments section.