Macrium Reflect

Same here. Only one reboot was required.

 

By again I meant the same as the last update. To which multiple people replied last time that they had not been prompted to do so.

 

I believe that somewhere on the Macrium Reflect Forums, over a year ago, I read that reboots are required after every patch install if you have CBT installed and active. I do not, so I seldom need to reboot my computer after a patch.

Could that be the difference in who has to reboot and who doesn't?

Have a great day.

Regards,
Phil

 

A good thought but not the case here. I had enough trouble with it in version 7 to remove CBT with no intentions of wanting it back. I am sure it has improved in version 8 but with high speed SSDs I don't feel the need to enable it.

 

CBT will add the most value in two main use cases:

• Very frequent Diff/Inc backups, such as every 15 minutes. If you have frequent small backups, then conventional change detection will make up a greater percentage of your overall backup time, and CBT can eliminate that.
• Volumes that contain very large files, such as VHDX files or databases. In this case, conventional change detection can identify which files have changed since the last backup relatively rapidly. That occurs during the "Looking for changes" phase. However, as the backup runs, Reflect will still have to scan those changed files in their entirety to determine which specific blocks within them have changed and therefore need to be backed up. So if you have a 50 GB VHDX file that only contains minor changes since the last backup, you'll still incur the time overhead of reading the whole 50 GB. CBT eliminates this.

If your scenario doesn't fit either of the above use cases, CBT's benefit will likely be minimal.

 

I don't have CBT, Image Guardian or viBoot installed on my computers, but sometimes I have to reboot when upgrading a computer, but not on other computers. Even on computers that have just been recently booted.

 

I don't have CBT enabled because I do only weekly full system images of my OS drive. As @jphughan has pointed out, it is of no benefit to me, and it does mean rebooting after patching. I backup changed data files in the interim to another internal drive and to OneDrive, so I think that I am reasonably secure from a backup perspective.

Have a great day.

Regards,
Phil

 

I have CBT enabled on my system, and I have not had a single issue with it. So I am kind of surprised to read that so many people here have CBT disabled! What is so problematic about CBT that one needs to have it disabled?

 

I'm only guessing here... some don't "trust" driver level DATA mgmt, some don't like the added reSTART request when patches/updates arrive, and to be honest, for most users, CBT makes very little difference in imaging & restore times.

It's of great value for users taking lots of IntraDaily Incrementals that include lots of very large files with very small changes between images (large databases and any other large change indexed files, possibly used on Servers).

IMHO (I use it all the time and really don't have any of the above mentioned requirements as well)...

 

I see, so it is just personal preference and CBT does not actually do any harm to cause people to disable it.

You mentioned "some don't trust driver level data management" but isn't CBT just silently tracking sector level changes and not actually managing data on the drive?

Also, I remember a product called ShadowProtect, and I remember that a lot of people here on Wilder's used to rave about how quick its backups were (circa 2009). Wasn't it only able to do quick backups because it was doing exactly the same thing. It was tracking changes in real-time in the background, and when it was time to take a backup, all it had to do was to back the changed data. The other utilities at that time had to first scan the disk to look for changes, and that added to the backup time. So I am surprised that people now have issues with Macrium's CBT which is essentially doing the exact same thing.

I am not 100% sure that CBT is a benefit to me, but I know for a fact that it is at least not doing any harm, and my backup speeds have improved significantly with the newer versions of Macrium, on the same SSD that I have had since 2019. So I am guessing CBT is contributing something on my system at least.

 

@Raza0007 If you check the release notes from Reflect V7, there are MANY instances of changes to the CBT driver to resolve issues that caused BSoDs — sometimes due to conflicts with other applications, sometimes not. There was also a period of about 3 weeks where the current Reflect releases contained a CBT driver with a bug that resulted in images created with CBT to be corrupt.

So some users have made a cost/benefit or risk/reward analysis and decided that the benefits of CBT aren’t worth even the potential drawbacks. I personally favor keeping things simple because 15 years in IT has made it clear to me that there are all sorts of bugs that are difficult to diagnose and create unexpected behavior, so the fewer components involved in my system, the better.

One of my favorite examples of the above is the Samsung NVMe driver. Some users choose to run it for a bit of extra performance. But at one point it had a bug where simply creating a VHDX file caused a BSoD. If I saw that behavior, I would have lost a lot of time and hair before I suspected that my SSD driver might be the cause of that. I never used that driver because I decided that I didn’t need the additional performance enough to deviate from the standard MS driver.

 

@jphughan, so that is the reason. People had issues with it when CBT was originally released, and they decided to stop using it to avoid any unnecessary headaches.

I personally do not update Macrium with every update. I check the changelog to see if anything they changed or fixed is relevant to me. And when they release a complete new version, I usually wait for over a year before upgrading to it. So I guess I must have missed all the fun, and all these CBT bugs were ironed out before I migrated to the new release.

 

Yep, sure is.

Edit: I actually had to reboot twice. The first time Windows froze up immediately after reboot. Coincidence? Probably. But it is extremely rare for this laptop to freeze.

 

Update Macrium Reflect Free v8.0.7783.

https://updates.macrium.com/reflect/v8/v8.0.7783/details8.0.7783.htm

 

7783 ... 7784!

7784 here. No reboot required, Win 10 Home, in-app download.

Edit:: Win 10 Pro machine needed reboot.

 

Same error. Downloaded and (re)installed the full version x64 from Deskmodder.de. This works for me.

 

Download the installer and install it that way.

Code:

Macrium Reflect Free Edition (v8.0.7783)

64-bit:
https://download.macrium.com/reflect/v8/v8.0.7783/reflect_setup_free_x64.exe

32-bit:
https://download.macrium.com/reflect/v8/v8.0.7783/reflect_setup_free_x86.exe



Macrium Reflect Free Edition (Latest Version)

64-bit:
https://updates.macrium.com/Reflect/v8/getmsi.asp?edition=0&type=99&arch=1&redirect=Y

32-bit:
https://updates.macrium.com/Reflect/v8/getmsi.asp?edition=0&type=99&arch=0&redirect=Y

 

Manually updated worked fine here. Also, the rescue media was updated correctly too.

https://i.ibb.co/s6WQ7qp/Image-627.png

 

But why are some referring to build 7783 and others to 7784?

In my case, 7784 was downloaded which includes:
'We've resolved a problem where an auto restore could hide the main Reflect window in the rescue media.'