Group: Forum Members
I've found that in a certain retention policy config, the state of the "Run purge before backup" checkbox results in a materially different outcome in terms of the backups that exist after the job completes, which I don't feel should be the case.
- Retention policy set to 1 Incremental
- Synthetic Fulls enabled
- Run purge before backup enabled
- Destination already contains 1 Full and 1 Incremental
- User then begins a job to capture Inc #2
Expected behavior: Reflect would first consolidate Inc #1 into the Full and capture a new Inc, resulting in 1 (Synthetic) Full and 1 new Inc.
Actual behavior: Reflect first deletes Inc #1 and then captures a new Inc.
If "Run purge before backup" is disabled, then Reflect captures a new Inc #2, then consolidates Inc #1 into the Full, leaving only 1 new Inc. Again, I feel that the timing of the purge should NOT affect the final outcome of the job, as is currently the case.