It’s true that updating Rescue Media isn’t technically required every time you update the installed version, and that V6 Rescue Media can work with backups captured by V7. However, new Reflect updates sometimes have bug fixes or enhancements that pertain to the Rescue environment, and especially in the case of ReDeploy, you might not realize that you even need that fix or enhancement until you’re migrating to a new PC, which won’t always be a planned event, so the fact that your old Rescue Media might work now is no guarantee that it will work in an unforeseen scenario where you might need it. And of course some bugs only arise in specific circumstances that you may or may not encounter at any given time in testing, so here again in general it's good to stay current. Yes, there have been cases where a Reflect update introduced a bug that hampered or even completely broke the Rescue Media environment, but Macrium has typically fixed those very quickly. In one case I remember an update to address an issue like this being released within hours of a problem report.
The only image format change I remember Macrium discussing is that V6.1 added support for Delta Incremental Indexing, so if you need to work with Delta Incrementals, you’d need at least 6.1 Rescue Media. But again, the release notes for V6 and V7 are sprinkled with red text items indicating changes that pertain to Rescue, so it’s worth updating at least to the latest V6 release.
As for moving to V7, the "headline" features are CBT (link
), Macrium Image Guardian (link
), and viBoot (link
), and then there were some enhancements called out for the recent 7.2 update (link
). I especially like the new "completed with warnings" possible job outcome in 7.2 rather than just pure success or failure, because there are times where the backup technically completed but there's something you should be aware of, and having that notification can be crucial. And then there are a variety of smaller enhancements that I personally really like having:
- Better display DPI scaling support for high-DPI displays (especially handy when trying to run Rescue on a laptop with a high-resolution display)
- Warnings about a job that would restore formerly encrypted partitions onto unencrypted targets
- The ability to view the progress of a backup job that started while you weren't logged in
- Popup notifications that show the name of the job that's about to run for at-a-glance convenience so the user can decide whether they may want to postpone it
- The ability to have scheduled jobs run as the SYSTEM account so you no longer have to store admin credentials with Reflect to run scheduled backups. The latter could cause scheduled backups to break if that account's password was ever changed and the user forgot to update the credentials stored with Reflect.
- The ability to store credentials for network targets so the user running the backup doesn't have to have write access. This is necessary if you run backups as the SYSTEM account of course, but even if you want to use your own user account for scheduled backups, this allows you to grant your own account just read-only access to your backup share as a ransomware protection measure during your everyday use, while still granting Reflect write access.