I'm facing the same issue, think I understand it by now, but one question remains:
I'm running a continous copy job, which is set to keep 100 Restore Points.
I also configured that job to keep 28 weekly backup, which - in my expectation - should lead to the following
Restore Points (Overall):
- About 3 months of DAILY data.
- About 1 Year of WEEKLY data.
The Copy Job is now running since 84 days and therefore created 1 vbk-File and 83 vib-files.
So, currently I have no weekly restore-Point, cause every weekly point would still be covered by the simple retention policy? right?
Then, the final question would be:
Once the Backup-Job reaches the point where 100 points are exceeded and a weekly (full) backup should be performed:
What is the datasource?
- Will it take the 100-days-old full backup file from the Copy-Location
- Will it take the closest restore-point from the actual BACKUP-Location? (Which only holds 14 restore-points)
Also i'm not quite sure about the disk-usage of that. If the weekly backups are FULL-Backups - wouldn't
a simple-retention-policy with 365 days (forever incremental) use LESS Disk-Space than - let's say - 180 daily + 28 weekly restore points?
(while also having daily version for the first half of the year?)
Or are the weekly restore points deduped / incremental their selfes?