Share via

Azure VM backup not triggering

David 40 Reputation points
2026-03-18T14:26:05.8766667+00:00

Azure VM backup is not triggering, it means the scheduled backup job is not starting at all.

Azure Backup
Azure Backup

An Azure backup service that provides built-in management at scale.

0 comments
Answer accepted by question author
  1. Naveena Patlolla 9,310 Reputation points Microsoft External Staff Moderator
    2026-03-18T14:34:57.6566667+00:00

    Hi David,
    Based on your description, the scheduled backup job is not initiating. This behavior is typically related to configuration, agent, or scheduling issues. Please follow the steps below to resolve the problem: 

    1.Verify Backup Policy Assignment Ensure the VM is correctly associated with a backup policy: Navigate to Recovery Services Vault ->Backup Items-> Azure Virtual Machine -> [Your VM] Confirm that a valid backup policy is assigned.

    2.Check Backup Schedule & Time Zone Review the backup policy schedule:

    • Ensure the scheduled time is correct
    • Validate time zone alignment (Azure uses UTC by default)
    • Confirm the schedule has not been recently modified

    3.Confirm VM Protection Status Verify that the VM is in a “Protected” state and not in a stopped or soft-deleted state.

    4.Validate Azure VM Agent Health Backup jobs rely on the Azure VM Agent:

    • Go to VM → Extensions + Applications
    • Ensure the VM Agent status is Ready
    • Restart the VM if the agent is unresponsive

    5.Check for Stale or Pending Jobs Navigate to Backup Jobs and ensure there are no stuck or in-progress jobs preventing new backups from triggering.

    6.Review Resource Locks Ensure there are no ReadOnly locks on the VM or Resource Group that could block backup operations.

    7.Trigger a Manual Backup Attempt a manual backup from the portal:

    • If manual backup works → issue is likely with scheduling
    • If it fails → review error details for further troubleshooting

    8.Validate Network Connectivity Ensure the VM can reach Azure Backup services and that no NSG/Firewall rules are blocking required endpoints

    Please let me know if you face any challenge here, I can help you to resolve this issue further

    Provide your valuable Comments.

    Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-18T14:26:30.81+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Use the following checks and steps to diagnose why the scheduled Azure VM backup job is not starting:

    1. Verify the VM is in a valid state for backup
      • Ensure the VM is not in Failed or provisioning Failed/Updating state.
      • The VM must be Running, Stopped, or Stopped (deallocated). If it is in a transient state between Running and Shut down, wait until it stabilizes, then let the next schedule run or trigger a manual backup.
      • If the VM provisioning state is failed due to an extension issue, go to VM → Settings → Extensions and make sure all extensions show provisioning succeeded. Fix any failed extensions and then retry.
    2. Confirm the VM is actively protected by Azure Backup
      • In the Recovery Services vault, check Backup items → Azure virtual machine and confirm the VM appears and is not in a paused or inactive state.
      • If you see errors like UserErrorBcmDatasourceNotPresent (“This virtual machine is not (actively) protected by Azure Backup”), re‑enable protection or ensure the VM is correctly associated with a backup policy, then retry.
    3. Check if another backup operation is blocking new jobs
      • In the Recovery Services vault, go to Backup Jobs and filter for the VM.
      • If any job is In progress, a new scheduled job will not start. For UserErrorBackupOperationInProgress, wait for the running job to complete or cancel it from Backup Jobs (or via Stop-AzRecoveryServicesBackupJob if using PowerShell), then let the next schedule run or trigger a manual backup.
    4. Inspect backup job failures and underlying error codes
      • In the vault, under Monitoring → Backup jobs, filter by Failures for the VM.
      • If you see UserErrorCrpReportedUserError (“Backup failed due to an error. For details, see Job Error Message Details”), open the failed job and follow the specific recommendations shown there. A recurring failure can prevent successful scheduled runs from completing even if they start.
    5. Validate VM Agent and backup extension health
      • Ensure the Windows Azure Guest Agent (for Windows) or Azure Linux Agent is installed, up to date, and running.
      • In the VM’s Extensions blade, check the backup extension (VMSnapshot / VMSnapshotLinux):
        • If in a failed or stuck state (for example ExtensionStuckInDeletionState), uninstall the backup extension from VM → Settings → Extensions, then retry backup; the next backup will reinstall it in a healthy state.
      • If errors like GuestAgentSnapshotTaskStatusError or UserErrorVmProvisioningStateFailed appear in failed jobs, resolve agent/extension issues first, then confirm that subsequent scheduled jobs start and complete.
    6. Ensure no conflicting backup/snapshot processes
      • Confirm that no other backup product or snapshot process is running at the same time as the Azure Backup schedule, as this can interfere with snapshot creation and cause jobs to hang or fail instead of completing.
    7. Review VM resource and network conditions
      • If you see errors such as ExtensionFailedTimeoutVMNetworkUnresponsive in failed jobs, the VM may be under heavy load or have network delays that affect the backup extension.
      • Mitigations include:
        • Configure snapshot to be taken through host (for Windows) using the registry keys described for SnapshotMethod and CalculateSnapshotTimeFromHost.
        • Move the backup schedule to a time when CPU/IOPS load is lower.
        • Increase the VM size and then observe whether scheduled backups start and complete successfully.

    After performing these checks, trigger a manual backup from the vault to validate that the configuration and extensions are healthy. Once a manual backup succeeds, the next scheduled backup should also trigger and run as expected.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.