#Azure Backup workload protection as I understood it

The new #Azure Backup has been announced Azure Backup GA and it introduces the long awaited support for application workloads (SQL, Active Directory, …).

Prior to this release application level workloads on Azure could only be protected in two ways (often combined):

  • An host based VM backup using Azure Backup
  • A combination of System Center Data Protection Manager (DPM) implemented on a IaaS VM and Azure Backup. This was required every time you needed to have a short RPO and data level granularity at restore time without having to restore the entire VM and figure out a way to extract the data you needed.

With this release, well basically, you get a stripped down version of System Center DPM that integrates with Azure Backup.

This post is base on my understanding of what we gain, what we lose and what’s missing.
So what you get with Azure Backup for application workloads:

  • A stripped down DPM server
  • no tape support (not event virtual tapes)
  • no Operations Manager integration (central console has gone)
  • SQL server instance used by DPM must be local
  • You still have to deploy agents
  • You still have to pay for the IaaS VM you’re installing Azure Backup onto
  • The VM must still have data disks (vhd the Azure way) attached for disk based backup
  • but you don’t have to pay for a System center license, the pricing is based on instance/data model currently used by Azure Backup
    What’s surely missing:
  • Automated agent deployment at VM provisioning time and / or from the Azure Backup portal
  • Direct access to Azure storage accounts and/or backup vaults so to avoid the data disks configuration and lower the cost of the VM hosting Azure Backup (aka DPM).

In the end what you loose is secondary or actually not needed on an Azure based deployment, so basically you get DPM without the licensing costs of System Center. I think the vast majority of customer of mine will go that way, saving on System center licensing and moving their licensing toward OMS even for monitoring purposes.


This posting is provided “AS IS” with no warranties, and confers no rights

  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: