Imaging with free Macrium

I had 300 GB available, so (theoretically) there was never any danger of a backup image being purged. :)

My issue is that MR was saying, it would purge a backup, despite me telling it not to.

That is why I posted:

lehnerus2000 said:

I don't know if this is:

• A bug
• A glitch on my PC
• A display error
• Just poorly worded

It looks like a bug to me too.

DavidE said:

I was curious so did some testing.
For me, creating an image uses my default settings and ignores my "run-time override" choice for Retention Rules.

With default setting set to never delete old backups, it didn't delete old backups, and gave me a clear message about the problem of not enough space.
See screen print 1.

When I set default settings to delete old images, then did an override to not delete old images at "backup run-time", it ignored my override and did delete old images.
See screen print 2.

I see ignoring the retention rules override choice as a bug.
For me, with my default settings set to not delete old images, v6 works as i want.
Your mileage may vary.

Thanks for testing that.


Asking the user to make a choice and then ignoring that choice is unacceptable.

Now all we need is for someone with a non-free version of Macrium Reflect to report this issue about the free version.

Well, if the trim feature wasn't as part of V5 Pro, it might explain why my SSD is at 87% (although SSDLife projects it has nine more years of life).

Thanks for the info DavidE,
I think I still need to do a bit more reading on the TRIM issue. Three points for comment that may also be of interest to others:

1) Is Macrium V6 (free) still buggy?
2) Can you have both V5 and V6 installed?
3) Re the TRIM issue - with V5 and maybe other imaging software would it be useful to format the SSD using the bootable Partition Wizard before a reimage?

Kari said:

...A Windows system image is always bigger than 5 GB so that is simply just plain theoretical issue, you will never select a storage location with so little free space...

Unless you are my 83 year old father. I have his SSD Windows drive scheduled to be imaged every Wednesday morning. I put a reminder in his calendar to check the disk space on the storage drive but he does not always remember to do it. (Or remember "how" to do it; he suffers from some significant problems at this point.)

As for the concerns about wanting to preserve certain very old images, I create a subfolder named "Saved" and use it for things like the first image created after a clean install, etc. It leaves those images out of the mix when any automatic deletion might take place.

profdlp said:

...As for the concerns about wanting to preserve certain very old images, I create a subfolder named "Saved" and use it for things like the first image created after a clean install, etc. It leaves those images out of the mix when any automatic deletion might take place.

I did pretty much the same. I put the first image I made after first setting up my machine into a subfolder of my Boot Drive Image folder named "Boot Back Up 1 (Do Not Delete)(Disabled)". The image file itself I further protected by adding .disable to the end of the filename. If I ever need to use the image, all I have to do is delete the .disable.