Group: Forum Members
Posting the log of the job where the backups were unexpectedly deleted would be helpful, but understand that the currently running backup is counted for retention policy purposes. So in your scenario where you have “Run purge before backup” enabled, if you already have 3 Fulls, then Reflect will delete an existing Full at the beginning of a job that would create a new Full.
If that doesn’t account for what you’re seeing, then once again please copy/paste the job log into a post here, taking care to omit your Reflect license key that appears at the bottom of the log.
Lastly, if you’re only making Full backups and your goal is to keep as many backups as possible, then you should simply disable the Full retention policy by unchecking the box. In that case Reflect will only purge older Fulls when needed to free up space per your setting there. And in fact even there, you can also drop that free space threshold purge far lower, because Reflect will perform purges for that purpose mid-job if that’s when you drop below the defined threshold. You don’t have to use that to make sure there’s enough free space at the beginning of a job.