Hello Michael,
where can you see which backups the background retention would delete after a v12 installation/upgrade?
- GFS backups that are expired (same as in v11)
- Orphaned backups with time-based retention (new in v12), these backups displayed under the Orphaned node
- Retired backups attached to the jobs if for some reason they are not processed by job itself (say the job is disabled). This rule however would affect only the part of the chain if you have multiple full backups. For example:
Retention is set to 5 days
Backup chain is [ F1 + I1-1 + I1-2 ] [ F2 + I2-1 + I2-2 + I2-3 ]
Backup job is disabled
Incremental backup I1-1 is expired, so all the backup chain F1 + I1-1 + I1-2 can be removed
Incremental backup I2-3 is expired, but wont be removed because F2 + I2-1 + I2-2 + I2-3 is the last backup chain in the job
how can you manually overrule the system, so that a (orphaned) backup would not get deleted by the new functionality
You can remove backup from configuration, that will remove it from db and next import or repository rescan will place such backup under imported node which is not processed by system (or background) retention
what if you have set a wrong retention in the original backup job, say you would like to extent the retention now, how could that be achieved?
You can change retention in the job and that would affect the backup.