Rollback Rx horror show

[7leagueboot]

Please excuse the title of this post however, RB's task is to get you out of trouble when it strikes, not to add to your misery by telling you it has gone on strike. Here's what happened...

Yesterday, I spent the entire day working on building new graphics for one of my web sites. Whenever I do anything I always backup my work to 2 external drives immediately but last night my wife called me to help her with something and I did not return to my PC for about 2.5 hours.

This is a new laptop with very few programs installed. So far I have not had any trouble with it but when I returned last night it was frozen. Nothing would respond at all and I had not had time to backup my day's work.

Eventually, I gave up waiting for it to respond and attempted shut down. No movement there either so I just went to bed. At about 4am I awoke and checked to see if it had shut down. Negative, still completely frozen so I powered-off.

This morning I ran a manual snapshot of current system state from the sub console and then asked it to rollback to yesterday morning's snapshot. At least that way I would be able to recover the work I had done. But RB decided to play up once booted into Windows giving the error message "Not enough free disk space to synchronize snapshots." Yeah right, there's over 700 Gb of free space available!

I still managed to mount last night's crashed snapshot as a virtual drive and recover all my work but would like to get to the bottom of this.

Checking Windows reliability report tells me the reason for the crash was due to my screensaver failing. In fact, it appears it has failed every day even though I see it running perfectly and no crashes have occurred previously. Nonetheless, I will reinstall it and if that doesn't solve the problem I can change it for another.

So, why with 746 Gb of free space available, did RB decide there wasn't enough space to sync snapshots?

[Owl]

But it DID get you out of trouble, maybe not in the way you would have liked!

[7leagueboot]

Yes, absolutely! It is indispensable IMHO.

It's just that in the advanced settings I have specified plenty of folders and files to recover when synchronizing snapshots so I expect it to do that. I'm not panicking because no data has been lost butI would like to understand why RB claimed there was not enough disk space available to do its job when that clearly wasn't the case? My goal is to either fix whatever caused that or to take preventative measures against it happening again.