none
MARS Agent - Backup failure: This operation cannot be performed now because a backup or restore operation is currently in progress. RRS feed

  • Question

  • 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.

    Sunday, July 28, 2019 10:23 AM

All replies

  • @TrulyVexed I have moved your thread to Azure Backup Forum for better assistance on your query.
    Monday, July 29, 2019 11:35 AM
    Moderator
  • @TrulyVexed Checked and verified internally on this issue and we haven't heard anything from other customers and it is not recorded as known issue yet. If you're interested why the backup is failing then that would require some investigation and you can reach out to Azure technical support team by creating a support request.

    To answer your question about changing the backup schedule would affect retention policy?
    Changing the backup schedule wouldn't affect retention policy might get changed to default policy which could impact the retention.

    Recommendation: Take a screenshot of the retention policy before changing the backup schedule. After changing the backup schedule time set the retention policy to previous one. By doing this, you would still be on the same retention policy and changing the backup schedule wouldn't impact (you will not loose previous) backups. 

    Hope that clarifies!

    Wednesday, July 31, 2019 7:40 AM
    Moderator