“Troublesome”’ is a bit of an understatement. Not only has CBT caused BSoDs, sometimes on its own and sometimes due to adverse interactions with other software on people’s systems, but for production Reflect releases that were current for about 3 weeks, it consistently created corrupt image backups, and of course even after Macrium fixed that, not everyone running a release with a bad version of CBT immediately updated. And even worse, someone on the Macrium forums had a system failure right after a Reflect release with a bad CBT version had created enough backups that all of his good backups had been purged, but before a patch became available. This problem was what drove Macrium to add options to check for Reflect updates in the background and also to send email notifications when an update is available, since servers typically don’t have users logged onto them to see conventional update notifications. https://knowledgebase.macrium.com/pages/viewpage.action?pageId=23397616
Now I remember! This is where I heard about 7.2.4398. I have it on all 5 computers without a problem.
The whole CBT thing has been a fail. I have had multiple issues with it. Version 6 was flawless for me and version 7 has not been as good. I wasn't even actively using it on a couple of PCs as they get shut down every day but experienced the BSODs all the same. I haven't had any issues too recently, I hope it stays that way.
wonder what the difference. I have a beta version of CBT I am using with v6. Wouldn't be with out it. It's flawless for me on Win 7
v7.2.4414 (d.s. aug. 8 2019) Free https://download.macrium.com/reflect/v7/v7.2.4414/reflect_setup_free_x86.exe https://download.macrium.com/reflect/v7/v7.2.4414/reflect_setup_free_x64.exe Home https://download.macrium.com/reflect/v7/v7.2.4414/reflect_home_setup_x86.exe https://download.macrium.com/reflect/v7/v7.2.4414/reflect_home_setup_x64.exe Workstation https://download.macrium.com/reflect/v7/v7.2.4414/reflect_wkstn_setup_x86.exe https://download.macrium.com/reflect/v7/v7.2.4414/reflect_wkstn_setup_x64.exe Server https://download.macrium.com/reflect/v7/v7.2.4414/reflect_server_setup_x86.exe https://download.macrium.com/reflect/v7/v7.2.4414/reflect_server_setup_x64.exe Server Plus https://download.macrium.com/reflect/v7/v7.2.4414/reflect_server_plus_setup_x86.exe https://download.macrium.com/reflect/v7/v7.2.4414/reflect_server_plus_setup_x64.exe
Where did you find that? When I go to the standard link to check current release notes — http://updates.macrium.com/reflect/v7/latest_release_notes.asp — I still see 7.2.4325 as of this writing. Are you on a different release track?
After the previous apparent 'pull', I would prefer to wait ... 'Check for updates' still shows 4325 as 'up to date'.
Yes I saw that URL in your browser. I’m asking what led you to it. As others are saying, that’s not the release that’s offered when you check for updates, and Macrium’s official link to get the release notes for the latest version doesn’t point to that either. Are you just plugging build numbers into your URLs to see what returns a page?
Might not be a production release. There are publicly posted release notes for builds that aren’t/weren’t meant for general production use, so this could be one of those. I remember those during some 7.1 builds that included an early version of the new Rescue Media Builder and then 7.2 beta builds.
+1 The internal updater still tells me that 4325 is the current build, which also corresponds to the latest official release notes.
Just to add to the stories of people's experiences with CBT, I also had issues with CBT for the longest time. I noticed that my computer frequently would run out of memory even though I have 32 GB of RAM and don't have that many programs left running. In particular, the non-paged memory would be completely consumed. However, I started noticing that the problem does not occur when CrashPlan was disabled. Eventually turns out the the CBT driver was doing some weird stuff that caused issues with VSS for people that are using CrashPlan or BackBlaze. Once CBT is disabled, everything is good and I can use CrashPlan as before. So yeah, ever since, I always had CBT disabled, lol.
Macrium Reflect 6 is still the most solid version. Version 7 has been a step back in regards to reliability. Argue all you like, but version 6 is still rock solid. Not so for version 7.
Agreed, v6 has been exceptionally reliable... especially if you don't need the new features offered in v7. As @Peter2150 has already mentioned, the BETA CBT effort under v6 has been rock solid and stable. V7's CBT improvement (along the way) has had a few wrinkles (some serious) and MIG (Macrium Image Guardian) has also offered some issues to its users. If those features aren't needed, v6 is rock solid. I have noticed, as @Stigg has mentioned, that development efforts since v6 have become hampered for some reason and the regression testing quality seems to have dropped significantly... a good reason for the many <Oooops!> since v7 has been released. Again, this is only an observation on my part. I use both v6 and v7 (without CBT most of the time) and v7 seems to have stabilized significantly as of late. In fact, I just turned CBT back on due to the lack of complaints in the more recent versions. BUT... when v4414 does (if ever) gets released, I will be turning off CBT due to the newly offered CBT protocols in that version... I'm scared of changes in that area. Based on recent stability, I will continue to use it without CBT being active. Bottom line... I LUV v6 with BETA CBT being active, and I'm beginning to trust the Macrium Devs a bit more in the v7 arena, although other than CBT I don't use any additional features (no MIG). And... I'm still MIFFED that over 2-1/2 years later, Macrium has never provided the "Continuous Incremental" feature promised "a few weeks after the v7 release." This was the main feature that interested me as CBT was being developed... a multi-incremental scheduling system that offered not only small time slots but periodic merging as defined by the user of those myriad incrementals. The idea was fantastic (actually "Shadow Protect" already offers a similar feature)... but if the intent was never really there, they should have never said "in a few weeks." It's tough for me to forgive...
I've used both, v.6 and v.7 with no problems so far. Maybe not using (and installing) CBT and MIG helped with stability and lack of problems.
+1 Excubits Pumpernickel, rather than MIG, has been my go-to portable USB backup drive protection mechanism, and has worked flawlessly. Never tried CBT, though the 'continuous incremental' feature mentioned by @TheRollbackFrog when developed, and reliable, would pique my interest in that.
V7 without CBT has been fine for me. MIG has also had some issues judging by the release notes, but they’ve never been an issue for me, and I like many of the improvements in V7. The ability to view the status of a backup that began while nobody was logged on is especially helpful for server installations, and the recent addition of a “completed with warnings” job outcome rather than just success/failure can be a huge benefit in certain scenarios. CBT just doesn’t make sense for my use cases because the normal “Looking for changes” step typically takes no more than 30 seconds, which just isn't enough time to worry about as a percentage of the overall backup job run time. V6 would have been useless for Windows 10 users by now if it weren’t for the fact that Macrium issued an update to maintain compatibility with Win10 1903 over a year after V6’s official end of support date.
It's NOT the latest version... it hasn't even been released (and may not be) by Macrium REFLECT. Be cautious...