Group: Forum Members
Adding these type of retention options to the interface would become very confusing, and I don't know how much desire there would be for any of them. Keeping the first Full seems fairly arbitrary -- why is the first Full necessarily better than any Full that comes after it? In terms of limiting the total storage that Reflect's backups are allowed to consume, there are already 2 indirect ways to do that: the retention policy and the disk space threshold purge option. In the former case, if your backups are taking up more space than you want, then set a more aggressive retention policy and/or manually delete some backups; in the former case, Reflect will delete multiple older backups next time that job runs if necessary to comply with your new settings, so storage consumption increases beyond your intended threshold can be corrected fairly easily. For the disk space threshold purge option, granted that option looks at total free space on disk rather than space consumed by backups AND it deletes older backup sets when enabled rather than simply halting new ones, but looking at free space rather than space consumed by backups and deleting older backup sets to allow new ones to continue are what most people would prefer to happen anyway. Still, the recommended practice is to set a retention policy that's feasible for your disk capacity and results in storage consumption that you consider acceptable for Reflect, and then if you use the disk space threshold purge, it should be as a last resort to allow backups to continue at the cost of older backups in case something else has consumed a significant amount of storage on your disk.
In terms of specifying that 12 Differentials should be kept, you can already do that with the current settings, although you can't specify that the Diffs always be created from the first Full. Diffs always append to the most recent matching Full, and Incs always append to the most recent matching Diff or Full. But if you WANT to create brand new Diffs against an older Full even if a newer one exists, see below for a way you might be able to force this.
In terms of keeping the first Full permanently and perhaps treating specific other backups in a special way, i.e. outside of your normal retention settings, there are two ways to handle this:
- After you generate a backup that you want to receive special treatment, move it into a subfolder of your destination (or anywhere else), and then Reflect's retention policy won't touch it anymore.
- Right-click your definition file, select "Duplicate", and change the destination of the new copy to a subfolder (or anywhere else). You may also wish to remove the scheduled executions of this, unless your do have a formal schedule in mind for these "special" backups. If not, then simply run that secondary definition file manually any time you wish to generate one. This mechanism would allow you to create Diffs from an older Full even if you have newer backups generated by your "main" definition file, because if the older Full is the newest backup that Reflect can see in that folder, that's what it will work with when creating a new Diff/Inc.