Azure backup - OperationNotAllowed : Changes were made to the Virtual Machine

Fred Fulford 36

Hiya, I have failed backup jobs on one of our VMs a few days in a row, the error is as follows:

Error Code: UserErrorCrpReportedUserError
Error Message: Backup failed due to an error. For details, see Job Error Message Details
Error Message: "OperationNotAllowed : Changes were made to the Virtual Machine 'Example-Server-Name' while the operation 'Create Restore Point' was in progress. Operation Create Restore Point cannot be completed at this time. Please try again later."

I can't find much on this specific error online. I've tried to do general troubleshooting as per (https://learn.microsoft.com/en-us/azure/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout and have found the following which according to the guide seems out of place:

WindowsAgent.AzureSecurityCentre Extension on server is in transitioning state
No Azure Backup VM Extension visible in virtual machines - server - extensions
No outbound connectivity to 168.63.129.16 on port 443

Can anyone help me to troubleshoot this issue? Many thanks

SadiqhAhmed-MSFT 38,401 Reputation points Microsoft Employee

2021-02-18T16:28:08.497+00:00

@Fred Fulford Sorry for the inconvenience this must have caused.

There must have been some change done to the VM in question per error message. Would you be able to redeploy/recreate the VM?
Before doing so, you can retain the backed up data in vault and then the operation. Reference link - https://learn.microsoft.com/en-us/azure/backup/backup-azure-manage-vms#stop-protection-and-retain-backup-data if this option isn't feasible, you can reach out to Azure technical support team by raising a support request. Here is the link - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Suresh Udhayakumar 1 Reputation point

2021-03-08T13:01:08.687+00:00

I too getting similar error for two of my VM's - performed most of the checks seems ok