Retention Policy Forever Incremental with Active Full

[deduplicat3d]

Hi,

I wanted to know if the following is by design or a flaw. Setup: forever incremental with retention of 3. If I run the job it will maintain that retention and merge old points. If I create an active full however, and then run incrementals, it will create up to 5 points and then finally remove all 3 backups from the initial chain after the 6th point is created. Wouldn't it make sense to merge the previous backup chain (as it would if it was the current chain), so that the retention is always maintained. This is an issue for me having a longer retention.

If my retention is 36 then I perform an active full, I have to wait 36 days until all of the previous chain is delete.

Corey

[foggy]

Corey, this is actually by design. Active full backup always starts the backup chain anew and requires additional space, regardless of the backup mode. All previous restore points are subject to the specified retention settings.