Installed and tested Server Edition v7 on Windows 10 Pro 64bit with two external hard drives, and rescue media on a CD with no problems. V7 seems to work smoothly. Here's hoping the worst is behind us.
IMHO... The switch to the WTS v2 API (new Windows Task Scheduler) in Reflect v7 to properly accommodate Win10 turned out to be a real challenge for Macrium with lots of problems initially (and some ongoing). That probably scared them a bit (and rightfully so, I feel). To consider doing the same using their own scheduling implementation (like Shadow Protect does) is probably a lot bigger job than they are willing to take on at the moment... probably would require a significant expansion of their existing service that runs all the time. I think at this point in time they're hesitant to trust the WTS v2 scheduler (I know I am... MicroSloth keeps changing it right under your nose).
Macrium boasted 3-major features with the introduction of v7... CBT and viBOOT to arrive at release time, and a feature called CONTINUOUS INCREMENTALS (CE) to arrive "a few weeks after release." CE never arrived with its promised easy to schedule (less than a day) and "merge" continuous Incremental operation. It was for anyone who wanted to set up Incrementals at quicker intervals other than 1-day (snapshot users and Servers admins) and also to "merge" those frequent Incrementals at selected intervals... like your Shadow Protect product does. ...and no, BG and I don't want to set up 96 DAILY Incrementals using v6 or current v7 just to get a 15-min snapshot interval over a 24-hour period. And no, we don't want to modify Reflect's existing WTS scheduling entry for something quicker than 1-day just to lose that entry as far as the Reflect UI is concerned. Even adding an HOULY Reflect UI schedule entry would have helped a lot of these types of users... how hard could that be. Alas, we wait... and wait
Interesting, Using V6 I do take hourly incrementals during business hours and have never had any problem with GUI or losing them. A merge function would be nice, but I've lived with out it. You mentioned SP's CI, and yes they use a completely separate program, and it does work well, but not at all without issues of there own. The decision to take earlier time frame incrementals is sort of questionable depending on what you are running. I start with some 30 minute increments and dropped them because the software I was running doesn't make it self VSS aware, so if I run all morning all the images have the latest copy of the file that was one disk. Also I've had occasion to go back and look at those intra day files, and the hourly spacing was fine. So far v6 as it stands has served my needs with excellence.
That's because you used the Reflect UI to create those hourly Incrementals... that works just fine. It's only when users actually go into the WTS and change the installed interval to something else. The change works fine but Reflect no longer sees the task in its scheduling interface... because it's no longer the one it set up to begin with.
But you don't need a recovery media for each computer. Make just one using the same USB drive from all of your computers. The drivers will just add up on the same thumbdrive (Macrium doesn't reformat). I have 4 computers at home with just 1 USB thumbdrive to boot any of them when needed. And when there's a Macrium update, just update the thumbdrive from one of the computers so that the software on is it updated. You don't have to go again to all computers and rebuild the rescue drive.
No fault of MR as far as I can tell. This machine has had problems booting from disks for quite some time. It almost never boots from v7 disks but usually boots from the latest v6 disk I burned. It will boot from a Windows 10 ISO if I try more than once but I have yet to see it ever boot from a flash drive. It's an old Acer (bought in 2010) and I have no idea what its problem is. It plays DVDs with VLC Media Player without problem.
Using v6 Home on latest stable Win10 x64 Pro ... since January Meltdown/Spectre CU, backups have slowed to a crawl here on second machine. Anyone else experiencing this?
