Windows 10: How Reliable is Macrium Reflect Backup Scheduling?

I've configured Reflect to automatically run full and differential backups to two drives as shown in the enclosed Reflect status report.



The report says the last " full system backup to usb hdd" was run on 14/11/16 and was successful. However when I look at the file backups there is no full backup file for 14/11/ 16 - see below.



There is no error report and there is ample space on the destination drive. The differential backup has worked as has the backups to the other drive "full ssd backup to drive X".

Has anyone else noticed missing backups from Reflect with no reported errors? I'll check more closely in future whether Reflect is scheduling backups correctly.

:)

 

Convert MBR to GPT without data loss?

Windows backup is depreciated in Windows 10 and is not reliable.

I Suggest backup using Macrium Reflect, a freeware that covers all the requirements.

Please see on how to backup:

Backup and Restore with Macrium Reflect

 

File History versus Dedicated Backup Software

I'll second JohnD's recommendation of Macrium Reflect. I'm very happy with it.

True Image and Reflect are image backup applications, although they can also make file and folder backups. File History only makes file backups.

For image backups I use the paid version of Macrium Reflect, but the free version works just as well and is equally reliable. It just has fewer features.

For file and folder backups I use 7zip, which is free. It's actually a compression program. I taught myself how to use command line and how to run it on a schedule. Not bad for a guy who didn't major in Computer Science.

 

According to the schedule view you posted your next scheduled Full backup will happen on 12/12/2016 at 0900 hours. In the meantime only differential backups will occur.

 

My point was that the Reflect status report says a full backup completed on 14/11/16 but there is no backup file. The last actual full backup was 16/10/16 and there should have been another one on 14/11/16.

 

Did you change the parameters of the backup from the first one in the screenshot to the second one? A modified schedule may not work correctly. Create a new schedule may fix the issue.