Delete version chains older then XX days

Scott, this is similar to the answer to your other topic about 'Store no more than xx recent version chains".

The difference here is how the automatic cleanup action is applied.

The aging of a version chain only starts being counted once the version chain is complete, which in turn only happens when a new version chain is successfully started (by creating a new full backup file).

So if you set "Delete version chains older than 90 days" - the 90 days count is started when the next version chain has been created.  Using your example.  Version chain 1 = 1 x Full & 5 x Incremental files.  Version chain 2 will be the same when created.  The 90 days start counting when version chain 2 initial Full backup is created successfully.

Another factor here is the timing of when your Full and Incremental backups are created, so if you run this backup task weekly, then the Version chain 2 Full backup will be created on week 7, which is when the 90 days count will also start.  So in effect, nothing will be deleted until Version chain 3 is also being filled - 13 weeks after the full for version chain 2 was created.  I find this method gives less control over the space requirements for my backups.

Thanks.

so, which is better - and why?.....

David, for me, personally, I always use 'Store no more....' as I find it much easier to both understand and manage.

With 'Store no more...' I know that my oldest version chains will be deleted automatically as soon as a new Full backup has been created to start a new version chain when the criteria is met.  i.e. If I had set 'Store no more than 2 recent version chains', then when chain 3 is created successfully, chain 1 is removed, keeping just chains 2 and 3.

See my earlier update above for the difference with how 'Delete version chains older...' works.