Policy to automatically reset backup chains and mixed retention policies

[rsmontero]

Description This issue is to easily program automatic reset of incremental chains.

Ideally this issue will also include retention sets for all backup types

Use case User wants to do daily incremental backups and once a month do a reset

Interface Changes New parameters to schedule the RESET and retention of all backups.

This should be supported for BackupJobs and Single Backups

Progress Status

• [ ] Code committed
• [ ] Testing - QA
• [ ] Documentation (Release notes - resolved issues, compatibility, known issues)

[Franco-Sparrow]

@rsmontero Sir Montero, I have been waiting for this since the begining of new backups solutions.

Also please, take in count that right now the number of increments inside of an incremental chain is equal to the number of active chains you can have for a given VM. In other words:

KEEP_LAST = NUMBER_OF_INCREMENTS_PER_CHAIN = NUMBER_OF_CHAINS

I think that separating those vars would be better, because if I were to schedule a reset backup every 15 days, for a VM that is being backup three days per week (6 backups every 14 days, is below the recommended limit by VMWare, which is 7 per chain), i dont want to have 7 actives chains with 6-7 increments inside consuming space. I would like to have two different limits for that:

KEEP_LAST = NUMBER_OF_INCREMENTS_PER_CHAIN
KEEP_CHAIN = NUMBER_OF_CHAINS

KEEP_CHAIN should rotate when arrives to the limit, deleting the oldest chain and create the new one, which will store up to KEEP_LAST increments.

What do you think about the idea?