Direkt zum Inhalt

Understanding Incremental Backup Settings

Thread needs solution

I've got the setting "Create a full version after incremental versions" set to "31". So, I basically want a full backup and then a month's worth of incrementals.  

What I would expect to happen is that after a full backup and then 31 incrementals, a new .tibx file is created? True?

 

On "Old version cleanup rules", I've got "Delete version chains old than" set to 32 days.  So, assuming what I wrote above is true, on the day the new .tibx file is created, it deletes the old tibx file along with the 31 incrementals?  Is that how this works?

0 Users found this helpful

David, you are correct with regards to your first statement, i.e. after your Full backup and 31 incremental backups are created, a new Full backup will be created.

You are not correct regarding how cleanup rules work.

If you want the old .tibx file containing the Full + 31 incremental files to be deleted after the new Full .tibx for a new chain is created, then you need to use the option to "Store no more than 1 recent version chain".

When you use the Delete ... older than 32 days, the count of days does not start until the next new Full backup has been created, so wouldn't happen until that chain has been completed and another new Full backup is created!