Group: Forum Members
Another issue that came up a while ago is that if you try to start a backup after an upgrade to a new version of Windows 10 has been "staged", but before the PC has been restarted, Reflect won't be able to make a backup. My guess there was that Windows wouldn't allow a VSS snapshot to be performed in that situation. It was unfortunate because the user specifically wanted to make a backup before restarting to allow the upgrade to proceed, but apparently that isn't an option. I'm not sure if the same applies to regular monthly updates, but if Windows allowed a VSS snapshot to be captured, I personally wouldn't worry about the integrity of the backup. Absolute worst case if that backup turns out not to be usable for system restore, you could restore the previous day's backup and then grab any required user data out of the latest backup. I realize that would be rather inconvenient, but again I doubt it would be necessary even if you needed to restore that backup -- although this incidentally is yet another reason it's nice to have a different partition for your user data separate from the OS, so that you can roll back your OS without also rolling back your personal data.
I'm surprised that the performance impact was that drastic, though. But in any case, as dbminter says, scheduling your backups to occur during your active hours wouldn't be a bad idea, especially if they tend to take only 15 minutes. Or one way to split the difference would be to start your active hours earlier than you actually start using your PC and/or later than you stop using it, then schedule your backups to occur at either the beginning or end of that window. At that point, your backups should occur either just before or shortly after updates have installed outside of your active hours. Your active hours range can be at most 18 hours long, fyi.