How To Get DPM/Azure Backup Server To Use USB Drive As Backup Storage

If you are running a demo or test lab, and you need some additional economical storage for backups, then you might think “I’ll use a USB drive”. However, DPM (and therefore Azure Backup Server) do not support adding a disk on a USB controller as a backup target. I struggled with this, and then it hit me this morning.

Storage Spaces will abstract that the disk is connected via USB Smile

I connected the disk, made sure it was unformatted and offline, launched Server Manger and created a pool from the primordial pool. I then create a simple virtual disk from the pool, and chose not to format it. Back into Azure Backup Server, and I was able to add the disk as a backup target.

Installing Azure Backup Server (DPM) Agent Leads To 0x80990a2b Error

This post explains how to solve an issue where installing the Azure Backup Server or DPM agent to a machine fails with a 0x80990a2b error.

I was asked to deploy Azure Backup to backup content on PCs in the office (organized admins –> that’s another story). I decided to test with my Windows 10 PC. I logged onto our Azure Backup server, and used the GUI to deploy the agent and it failed:

Install protection agent on <Machine Name> failed:

Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on <Machine Name>.

Error details: Unknown error (0x80990a2b)

Recommended action: Verify that the Agent Coordinator service on <Machine Name> is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.

I searched my services for something called DPM Agent Coordinator and found nothing. The DPM community is full of stories about Windows Firewall causing issues – I tried to disable it but it made no difference. And the 0x80990a2b error wasn’t appearing in my search results.

Next I decided to try a manual installation on my PC. That failed with the same error, but this time there was a clue:


There is a log file for the installation. I opened the log and started reading. There was the error about not being able to initialize something called an AC (Agent Coordinator). I was getting frustrated but kept reading.



WARNING    Failed: Hr: = [0x80990a2b] : MARS agent found. Cannot install Microsoft Azure Backup Agent

Now was exactly when I remembered that I had been backing up my OneDrive using the Azure Backup MARS agent. I remove the agent, cleaned up the backup, and re-ran the original agent deployment from the Azure Backup Server GUI. The agent installed perfectly and was added to the protection group.

Technorati Tags: ,,,

Understanding & Pricing Azure Virtual Machine Backup

In this article I want to explain how you can backup Azure virtual machines using Azure Backup. I’ll also describe how to price up this solution.

Backing up VMs

Believe it or not, up until a few weeks ago, there was no supported way to backup production virtual machines in Azure. That meant you had no way to protect data/services that were running in Azure. There were work-arounds, some that were unsupported and some that were ineffective (both solution and cost-wise). Azure Backup for IaaS VMs was launched in preview, and even if it was slow, it worked (I relied on it once to restore the VM that hosts this site).

The service is pretty simple:

  1. You create a backup vault in the same region as the virtual machines you want to protect.
  2. Set the storage vault to be LRS or GRS. Note that Azure Backup uses the Block Blob service in storage accounts.
  3. Create a backup policy (there is a default one there already)
  4. Discover VMs in the region
  5. Register VMs and associate them with the backup policy

Like with on-premises Azure Backup, you can retain up to 366 recovery points, and using an algorithm, retain X dailies, weeklies, monthlies and yearly backups up to 99 years. A policy will backup a VM to a selected storage account once per day.

This solution creates consistent backups of your VMs, supporting Linux and Windows, without interrupting their execution:

  • Application consistency if VSS is available: Windows, if VSS is functioning.
  • File system consistency: Linux, and Windows if VSS is not functioning.

The speed of the backup is approximately:


The above should give you an indication of how long a backup will take.


There are two charges, a front-end charge and a back-end charge. Here is the North Europe pricing of the front-end charge in Euros:


The front-end charge is based on the total disk size of the VM. If a VM has a 127 GB C:, a 40 GB D: and a 100 GB E: then there are 267 GB. If we look at the above table we find that this VM falls into the 50-500 GB rate, so the privilege of backing up this VM will cost me €8.44 per month. If I deployed and backed up 10 of these VMs then the price would be €84.33 per month.

Backup will consume storage. There’s three aspects to this, and quite honestly, it’s hard to price:

  • Initial backup: The files of the VM are compressed and stored in the backup vault.
  • Incremental backup: Each subsequent backup will retain differences.
  • Retention: How long will you keep data? This impacts pricing.

Your storage costs are based on:

  • How much spaces is consumed in the storage account.
  • Whether you use LRS or GRS.


If have 5 VMs in North Europe, each with 127 GB C:, 70 GB D:, and 200 GB E:. I  want to protect these VMs using Azure Backup, and I need to ensure that my backup has facility fault tolerance.

Let’s start with that last bit, the storage. Facility fault tolerance drives me to GRS. Each VM has 397 GB. There are 5 VMs so I will require at most €1985 for the initial backup. Let’s assume that I’ll require 5 TB including retention. If I search for storage pricing, and look up Block Blob GRS, I’ll see that I’ll pay:

  • €0.0405 per GB per month for 1 TB = 1024 * €0.0405 = €41.48
  • €0.0399 per GB per month for the next 49 TB = 4096 * €0.0399 = €163.44

For a total of €204.92 for 5 TB of geo-redundant backup storage.

The VMs are between 50-500 GB each, so they fall into the €8.433 per protected instance bracket. That means the front-end cost will be €8.433 * 5 = €42.17.

So my total cost, per month, to backup these VMs is estimated to be €42.17 + €204.92 = €247.09.


Microsoft Modifies The Azure Backup Announcement

Yesterday I posted an “Aidan Smash” article about the messed up Azure Backup Announcement. Microsoft had originally stated in their announcement of improvements that were coming to Azure Backup. Let’s remind ourselves what Microsoft said:

image_thumb[1] Why did I take a screenshot of the text instead of copying/pasting it? I’ve learned that when Microsoft makes a controversial announcement, or something that is just plain dumb, that text can change without any notice.

Controversy? Yes; Microsoft pretty much stated that the requests for feature improvements in Azure Backup that would make the product marketable to the breadth market (that will actually use Azure Backup) was going to be restricted to System Center customers that paid extra for OMS Add-On for Azure (not the breadth market).

That sounded pretty stupid. I reached out for a correction but did not get one within the 24 hours before I posted my rant. So it seemed that someone had made yet another dumb packing/pricing decision with a Microsoft online service.

24 hours later, the announcement was changed by Microsoft:


Note that the post does not say the following anymore:

… we are now announcing new Azure Backup services that are available today to OMS customers.

In fact, all mention of OMS in this section and the bullet points has been removed. Queue cautious celebration!

How do I read this (as a person that does not have access to OMS Add-On and cannot verify what OMS customers have access to)?

  • The new features will not be restricted to OMS Add-On customers
  • The new features are not available yet

This is much better. Now if only the author had bothered to communicate clearly in the first place – I’m guessing they were made walk the plank.


Microsoft confirmed that the improvements to Azure Backup will be coming to everyone. These features will be coming before the end of the calendar year. I look forward to trying them out, and hopefully selling them.

A Totally New Blog Design After Restoring From Azure Backup

Monday was one of those days you dread – this site’s server had a catastrophic failure and I had to restore the VM from an Azure Backup. Luckily, the process worked perfectly and I was back online. But I realised that I just wasn’t doing a very good job at running the VM, the software (MySQL and WordPress), and managing the site.

So after getting things back online, I spent a bit of time doing updates and re-engineering the site. And this is the result. The site has a whole new home page with featured posts, and recent posts in several key categories. The blog has much more imagery, and the design is brighter, more modern, and easier to read. Hopefully you agree.