Macrium Reflect leaving multiple backups instead of overwriting

[steffeeh]

I use automated backups to my NAS with Macrium Reflect, where I do a weekly full backup on Mondays, and daily differential backups.

However, I've noticed that the backup image file doesn't get overwritten, instead Macrium just leave a new backup alongside the older ones, until my HDD on the NAS becomes full and I have to manually delete the old ones.

I realize that there's probably some settings I've set wrongly, but I can't figure out where and what.

I just want there to be 1 backup image file that gets overwritten with each new backup session.

 

I've attached a screenshot of my backup schedule inside Macrium Reflect, in case my error is there. I do also use my own backup filename, if that could be the culprit.

 

[userzero]

A base backup/image is exactly that and isn't incremental as you are hoping for. Why are you making a base/full backup every week exactly? 

 

The norm here at our HQ for endpoints is quarterly with incremental's once a week.

[steffeeh]

What I'm doing is running a full backup every monday when I'm away from home, and then I run differential backups each day so that the backup is up to date throughout the week, and then go back to a new full backup by the start of the week. Because of this, the differential backups gets larger everyday, so having the weekly full backup keeps the differential backup sessions short.

I can't do incremental backups as I don't have the paid version of Macrium Reflect, and I don't really need it since I can just run the differential ones instead with the weekly full backup, the full backup isn't really "in my way" as I'm not home at that time.

 

However, optimally this would mean that I always have an image-file of the full backup and one for the differential one (for some reason) stored, and then each new full/differential backup would overwrite the old one so that I always have 1 of each that is up to date - but instead I keep getting more and more backup files for each backup, until the HDD becomes full, so the overwriting doesn't work for some reason.

 

For now I've tried editing the retention rules, so I'll see how that goes tonight when the full backup fires up.