7784 is the shareware version - 8.1.7784 7783 is the free version - 8.0.7783 https://updates.macrium.com/reflect/v8/v8.0.7783/details8.0.7783.htm https://updates.macrium.com/reflect/v8/v8.1.7784/details8.1.7784.htm
Because the free version of Macrium Relfect has been updated to v8.0.7783 and the non-free versions have been updated to v8.1.7784.
How to tell MR to remember its Windows size and position on desktop beyond exit+restart? Currently is starts always maximized How to tell MR to show always tab "Create Backups" at first after start (AND NOT "Existing Backups")?
I have all of this without any effort or customization on my part. There have been no complaints about this from other users, you may have a local problem with your operating system.
Thanks! I use the free version, but the auto update has never worked from the beginning. The only way I know there is a rare update is to see it mentioned here.
What's difference between Create Differential from Full vs Create Differential from last Differential or from any Differential in the string. The string looks the same....working off the Full.
To my knowledge, all DIFFs are created off the most recent FULL in the image chain. I know of no other imaging system that does it any other way.
A nice, detailed explanation from Macrium: Incremental vs differential backups Something I never knew before about incremental backups:
One of the things I don't like about them. If ANY of the incremental backups becomes corrupted you can't restore to that point or any time after that one.
As it has to process them all that part does not surprise me. Something I do wonder, and I'm not sure if someone else knows or if maybe if it even varies by product, when restoring incremental images, does it just restore the base image and then individually restore each incremental over the top of that, or does it somehow process them all and write the entire thing at once?
The options to create new backups from the Existing Backups interface don’t operate any differently based on what specific backup you select, beyond creating the new backup in the same set as the selected backup. Every Differential is appended to the Full, and every Incremental is appended to the most recent backup in the set, whatever type that is.
For the paid version with Rapid Delta Restore: The result is an 'Incremental' restore applying only file system changes detected between the image and the target. https://knowledgebase.macrium.com/display/KNOW80/Rapid Delta Restore - RDR So for my understanding they just restore what's changed not a base image and then the rest. Edit: Corrected typo
Imaging applications that don't have some sort of DELTA restore feature will, indeed, restore the base FULL, most recent DIFF (if one exists) then every incremental after that. Only those with delta restore options (not many, BTW) will write only the changes during restorations.
I’m not sure this is accurate. RDR just avoids the need to write out the full contents of the partition by analyzing the current (pre-restore) state of that partition. But even if not using RDR, the index that Reflect stores in each backup would allow it to examine all relevant backups in the set and determine what should be written to each sector of the partition — and which backup contains that data — so that it would only have to write to any given sector at most once. I don’t see why Reflect would have to write whatever the Full says was in each sector and then overwrite sectors potentially several more times as it worked through later backups in the chain. The design I’m describing would still entail writing out the entire partition rather than leveraging the data that was already there before the restore began as RDR can, but it achieves efficiencies from working with the backups holistically rather than in isolation. Due respect TRF, but absent a citation, I would bet rather heavily that you are incorrect here.
Due respect, JP , I don't have a citation but offer the following for your perusal... feel free to spin it in whatever way may meet your assumption here. I've done this in the distant past but have not done it recently until now. I have a NvME System disk with 6-partitions on it. I image 5-partitions on that disk hourly throughout the day with the final image used for this test being at 7:30pm EST. The current image chain contains a FULL, a DIFF and 63-INCs. I enter the Recovery media and do a RDR restore to the 7:30pm snapshot. I do this to make the disk image and the image chain exactly the same. Remaining in the Recovery Media I perform... Step#1: nothing more than another RDR restoration of the image chain which is exactly the same as the current disk image after the above preparation. Step#2: after unchecking the RDR option in the Recovery, repeat Step#1 without RDR being active. Step#3: Using an off-line Partition tool (Minitool Partition Wizard), I delete the 5-partitons on the System disk that are being imaged. Step#4: re-enter Macrium's Recovery media and do a full restore of the 5-partition image... process shows Full Copy being done. Step timings reported by the Recovery media... Step#1 = 42-sec. Step#2 = 8-min, 50-sec Step#3 = 8-min, 40-sec If I interpret those timings correctly, I'd say that a non-RDR and Full Copy restore are both restoring the entire image, or at least the very same DATA. Wha'd'ya think?
