Azure Backup VMWware vCenter- Reverting VM to current snapshot always makes Azure backup fail.

asked 2020-09-11T03:32:27.703+00:00
T16 1 Reputation point

Is this expected behavior?

For instance, backup taken the day before with Azure backup, VM already has 2 snapshots on it, everything is fine. I revert the VM back to its snapshot taken the day before, and it seems this is enough to screw everything up with MABS, and requires a MANUAL consistency check in order to fix it.

Surely there must be an easier way than this for people to work on VMs and revert them back to a snap without completely breaking backups?

Sigh :(

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
774 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. answered 2020-09-14T10:06:25.273+00:00
    SadiqhAhmed-MSFT 25,366 Reputation points Microsoft Employee

    @T16 Sorry for the delay in response to your query.

    Was the user snapshots created before the first backup was taken using MABS? If yes, that’s not supported. There should not be any snapshots created before you take the backup of the VM using MABS.
    You cannot back up user snapshots before the first DPM backup. Once DPM completes the first backup, then you can back up user snapshots.

    It seems these limitation are not documented under MABS, I will get that added.


    If an Answer is helpful, please “Accept Answer” and Up-Vote for the same which might be beneficial to other community members reading this thread.

    No comments

  2. answered 2020-09-14T22:55:20.38+00:00
    T16 1 Reputation point


    No afterwards. So the scenario goes like this:-

    1) The VM gets added to protection without any snaps.
    2) The VM replica is created, and backed up online to the recovery services vault.
    3) Snaps are taken of the VM's before making a change say on Monday.
    4) Azure backup runs Monday night, backs up the VM with its snapshots.
    5) Tuesday, come in, and need to revert back to Mondays snapshot, this is fine.
    6) Azure backup runs Tuesday night and throws a fit with the error detailed above!