I'm at something of a crossroads. The entire household of MOSTLY Win 7 systems* is auto-backed up nightly to a WHS-2011 server. I'm looking to replace the server in an orderly fashion, already have the essential hardware put together and tested with a Win 7 OS before installing 2012 R2 Essentials. But the existing [WHS but essentially 2008 R2] server may use hardware that is 8 year-old technology, yet that hardware has only 3 years of mileage on it.
So I've encountered some anomalies with the server on my Skylake (sig) system, and dual-boot complicates it. So far, I've been relieved to find that Macrium Reflect (free) will image a single drive containing both OSes and restore it without a hitch. But it needs the insurance that a regular backup can provide, and I'm not going to attempt making it work properly with the WHS box. So it has to be a LOCAL solution.
The Skylake, for being dual-boot, has been a mindful attempt to reduce the number of drives running 24/7. If the sig doesn't say so, the Macrium helped me put my dual-boot OS on a 960 Pro NVMe PCIEx4. I'm planning shortly to replace one HDD with a 1TB SATA SSD -- my Egg cookies and e-mails show Egg attention to my window-shopping.
So about that local backup. It should be incremental in addition to differential, so looking at Macrium, I'll need to purchase the software. I can't be sure I can trust Windows native backup to work in event of restoring dual-boot, even if it's run within Win 10. Macrium, however, is a known quantity with me at this point.
Pretty slick software, too. No criticism whatever for anyone using EaseUS ToDo or Acronis. But EaseUS tech support has been reticent about dual-boot systems, and Acronis tech support offered no assurances either.
UPDATE: Maybe I put it in another thread just hours ago. I have discovered that I can image my entire system with Macrium to a network drive -- which mean my server. So I can take local backups and manage or schedule a backup locally with a folder on my server as target. That's schweet. It's Schweet if you can't trust the WHS server to restore client backups even if they appear to be "successful" in creation.