For what it's worth, I have exactly the same issue running build 6584.

It's enough to drive you crazy!

It gets worse - I decided to give up and just do local backups and have them sync to the NAS but now I'm getting THIS error:


I should've just stuck with the free version and not upgraded. I'm willing to bet if I go back to it though, I'll still have these issues. I still can't be sure if this is more a Macrium issue or a Windows issue.

Open Reflect, menu item "Other Tasks" > Fix VSS problems
See if it helps.

Tried that a few times and it didn't fix the issue.

Just ran a Dism /online /scannow and Dism /online /restorehealth
Backup ran without error........for now

The error message shows that  some other process has a snapshot in progress; Windows is not letting Reflect create the needed snapshot.  What other backup solution are you using? 

@DanDanz It doesn't have to be another backup program, Windows Update likes to create snapshots & runs itself at random times, could simply be that type of collision.

+x

 

Beardy - 1 March 2022 7:05 PM

@DanDanz It doesn't have to be another backup program, Windows Update likes to create snapshots & runs itself at random times, could simply be that type of collision.

Thanks for that addition to MY knowledge base.  Whatever it is it's not another instance of Reflect, which uses a system semaphore so that only one instance of Reflect runs at a time.

@zr0 Can you determine what was running alongside the failed backup?   I doubt very much that SFC and DISM did anything to fix the problem.  But they did shift the execution of the backup out of the window that it originally failed in.  

Nothing else backup related is running at the same time (that I'm aware of).

I use Tweaking.com registry backup but that isn't scheduled to run until late evening whereas the Macrium backups are scheduled early morning.

I do have the backups going to a folder that is synced to my NAS using Synology Drive - I'm not sure if that does anything with VSS though.

I know I keep reiterating this, but everything was working as it should before I upgraded. No changes were made aside from that (at the time).
Now with all the troubleshooting I've been doing, I couldn't say what's all changed since then but I'm pretty confident in my technical abilities. Not a boast, just that all the obvious things to check have been checked.

Well if you open Resource Monitor (resmon in the run box), go to the Disk tab, sort Disk Activity by file, then if things are using or accessing shadow copies they'll show at the top of the list as accessing

the image column will tell you what process is doing it..

The trick is to be watching when the problem occurs.

We hear you on the correlation between the events of upgrading & tis issue arising, but correlation isn't causation, & the cause needs investigating with an open mind.. it may or may not be related.

Completely understandable. The only reason I keep bringing that up is because, before posting here, I was noticing people posting the same issues with previous upgrades and from what I remember they were never solved. So not sure if there's some bug that ended up in Macrium that hasn't been caught yet.

I'll try and keep an eye on the resource monitor next time the backup runs and see if I can catch anything there.
No problems trying new suggestions

Thank you