One of the many advantages of the advent of computers has been the ability to create perfect copies. Backups have been a cornerstone of the technology scene since the invention of electronic storage in 1953.
Microsoft has offered numerous backup utilities over the years. Some, like Windows Server Backup, have been great. Others not so much. Not so long ago, Microsoft decided to get into the enterprise backup market and launched Data Protection Management, aka DPM.
Per Microsoft’s marketing tradition, the product has been renamed to “something with Azure in it.” Don’t be fooled, Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS) are the same solution.
Naming challenges aside, the backup platform is top-notch in my opinion. MABS offers the modern backup features companies need. Features like snapshot mounting, Hyper-V and VMware protection, local disk to cloud replication, application-aware agents, and bare metal recovery of entire hosts are all part of the tool’s offerings.
Understanding the pricing model for Microsoft Azure Backup services can be challenging. Recent changes have attempted to simplify the options by moving from a storage space model to an object instance model.
In their documentation, Microsoft discusses backing up a 250GB SQL VM. When using standard retention and DR protection options, the backup of a server costs twenty dollars per month. Ten for the local (on-prem) copy and ten dollars for the cloud. Detailed pricing information is available on Microsoft’s site at: https://azure.microsoft.com/en-us/pricing/details/backup/
There are some key differences to be aware of in Microsoft’s backup tool. MABS must be installed on a domain member server. At first glance, this requirement would seem to prevent backup immutability. Microsoft Azure Backup Server utilizes a PIN code to ensure immutability. The PIN is generated and retrieved from the Azure Admin Portal.
Like other enterprise backup apps, MABS uses an agent to manage the backup process. That agent can be pushed to target systems from the MABS console, installed manually, or deployed via many package managers.
Both the MABS server software and its agents are automatically updated via Windows Update. Automation like this is where Microsoft’s advantage lies. MABS more or less takes care of itself. Automatic maintenance, the ability to backup and restore via PowerShell, and robust monitoring options help ensure it is running even when you forget to check on it.
I’ve used many of the major enterprise-grade backup tools over my career. Microsoft Azure Backup Server compares well to them. If you are considering which package to use in your environment, it’s worth taking a look at. I’ve been using it for more than a year in a medium-sized, multi-cloud, hybrid organization to great success.






