Azure Backup Linux snapshot extension keeps retrying after backup was disabled

My last post was to say this was resolved.

What was wrong with the answer I provided??? It worked and you deleted it for some rule??? Trying to help others.

One more time, took a long time to type that last one so just a short note then in case you delete it again.

Title: VMSnapshotLinux 1.0.9225.0 fails on Debian 13 (Python 3.13.5): missing distutils/imp; extension stuck "Transitioning", Run Command blocked

Cause

Python 3.12 removed distutils and imp from the standard library, and 3.13 removed crypt. The 1.0.9225.0 handler imports them, so its enable step crashes before it can write a status file.

Fix

sudo apt install python3-setuptools python3-zombie-imp python3-crypt-r

python3 -c "import distutils, imp, crypt; print('ok')"

sudo systemctl restart walinuxagent

Versions:

Failed: 1.0.9225.0 on Python 3.13.5. Others report 1.0.9231.0 failing on the same imports on Ubuntu 26.04 with Python 3.14.

Newer build: on a fresh install, Azure Backup installed 1.0.9232.0. Its source wraps crypt, distutils and imp in try/except ImportError with fallbacks (a legacycrypt alternative, a built-in LooseVersion shim, and importlib for imp). It installed and enabled cleanly on Debian 13 / Python 3.13.5, and the Take Snapshot step completed.

Workaround for others: on Debian 13 or any Python 3.12+ system, install the three packages above before enabling Azure Backup.

Related: https://github.com/Azure/azure-linux-extensions/issues/2172

To help others here is exactly the problem how we resolved and what to look out for with the Azure VMSnaptop. There is also on GitHub Azure which reports this same problem. This would be used to get out of the stuck situation. As noted, this problem prevents the "run command" from working with PowerShell scripts.

OBSERVED

• VMSnapshotLinux 1.0.9225.0 fails on Debian 13 (Python 3.13.5): missing distutils/imp;
• Extension stuck "Transitioning", Run Command blocked

Environment

• Azure Linux VM, Debian 13 (trixie), Python 3.13.5, South Central US
• WALinuxAgent 2.12.0.2 (Debian package), self-updated to goal-state agent 2.16.0.2
• Extension: Microsoft.Azure.RecoveryServices.VMSnapshotLinux 1.0.9225.0 (config sequence 18)
• No Recovery Services vault protected the VM, and az vm extension list showed no extensions

Symptoms

Extension status stuck at Transitioning. The portal and CLI showed no ARM-visible extensions, and the Backup page only offered "Enable backup."

waagent logged every 30 minutes: no status file was reported by extension Microsoft.Azure.RecoveryServices.VMSnapshotLinux ... status/18.status does not exist.

The handler was re-run on each new goal state or agent restart and failed each time, exit code 1, with ModuleNotFoundError: No module named 'distutils', then No module named 'imp' (from WAAgentUtil.py, HandlerUtil.py, DiskUtil.py).

• Run Command (Invoke-AzVMRunCommand) failed while the extension state was pending.

Cause

• Python 3.12 removed distutils and imp from the standard library, and 3.13 removed crypt. The 1.0.9225.0 handler imports them, so its enable step crashes before it can write a status file.

Fix

• No backup enabled, nothing under /var/lib/waagent edited)

sudo apt install python3-setuptools python3-zombie-imp python3-crypt-r

python3 -c "import distutils, imp, crypt; print('ok')"

sudo systemctl restart walinuxagent

After the restart the agent logged Extension status: VMSnapshotLinux 'success' and All extensions in the goal state have reached a terminal state. Get-AzVM -Status showed the handler as Ready / Plugin enabled, and Run Command worked again.

Versions / Notes

Failed: 1.0.9225.0 on Python 3.13.5. Others report 1.0.9231.0 failing on the same imports on Ubuntu 26.04 with Python 3.14.

Newer build: on a fresh install, Azure Backup installed 1.0.9232.0. Its source wraps crypt, distutils and imp in try/except ImportError with fallbacks (a legacycrypt alternative, a built-in LooseVersion shim, and importlib for imp). It installed and enabled cleanly on Debian 13 / Python 3.13.5, and the Take Snapshot step completed.

Caveat: the shim packages were installed on that machine before the backup, so I could not confirm whether 1.0.9232.0 works without them. Result of the full backup job: [fill in: completed / failed].

Workaround for others: on Debian 13 or any Python 3.12+ system, install the three packages above before enabling Azure Backup.

• Related: https://github.com/Azure/azure-linux-extensions/issues/2172

Hello Bernie Luksich

I would recommend to verify the extension state with Azure CLI rather than relying only on the portal:

az vm extension list --resource-group <RG> --vm-name <VM> -o table

Microsoft documents this as the way to check the VMSnapshotLinux deployment state. VM Snapshot Linux extension for Azure Backup

If a VMSnapshotLinux extension resource is still returned, remove that extension through Azure rather than deleting files inside /var/lib/waagent. Microsoft specifically recommends uninstalling the backup extension when it is in an inconsistent/stuck state. Troubleshoot Azure VM backup errors

However, if:

• Backup protection has already been stopped/deleted,
• az vm extension list shows no backup extension, and
• waagent continues receiving/retrying Microsoft.Azure.RecoveryServices.VMSnapshotLinux,

then the issue is likely a stale platform/Backup desired state, not simply leftover files inside the guest.

There is no documented supported guest-side command to remove such a service-side assignment.
I would not manually delete the extension/waagent state as a permanent fix. In that situation, opening an Azure Support request is appropriate so Microsoft can check and clear the stale Backup/VM extension association or goal state.