This has been mentioned a few times, like in https://social.technet.microsoft.com/Forums/en-US/f8de03b6-b97b-4c7b-940f-7a8c72303427/critical-alert-backup-failure-this-operation-cannot-be-performed-now-because-a-backup-or-restore?forum=windowsazureonlinebackup
On some VM's (spread across different companies, OS and internet connections) we get "This operation cannot be performed now because a backup or restore operation is currently in progress.", this is either an intermittent error or on some VMs it happens on every MARS Agent scheduled backup job. We're only backing up files and folders.
When this happens, it looks like the MARS Agent is spawning two jobs instead of just one at the scheduled time. There are no other backups running at this time.
I've tried re-creating the schedule (i.e following the wizard again) but that doesn't help. I've re-installed the MARS Agent and ensured it's on the latest version at the time of writing this 2.0.9167.0
What does seem to help, is changing the schedule altogether, i.e the one common thing I noticed is a lot of the jobs run at 0100, if we change this to 0130 we don't seem to encounter further errors. The event logs don't really show anything else running/happening at 0100 that would account for this tho.
I'm unclear on if this will change our retention as the schedule wizard then says to keep the restore points at the new time slot rather than the old - I cannot afford to lose all of the previous restore points on some of these VM's.
Can anyone advise on the best way to resolve this? If I change the scheduled time to 0130 (which automatically changes the retention policy to that time also) will I lose all my previous retention/restore points? If I change it to 0130 and then immediately
back to 0100 again will I lose the previous retention/restore point? Or is anyone aware of a different fix altogether?
Any help is very much appreciated.