Backup Copy Job minimum of 2 restore points

[mikegodwin]

Is there a reason a copy job requires a minimum of 2 restore points? The 2 restore points, plus the third restore point that happens before transformation, is filling up the disk.

[tsightler]

Sounds to me like you don't have enough space. The way Backup Copy storage works (assuming no GFS) is that there is always at least one VBK file, which unlike regular backup jobs represents the "oldest" restore point and is a full backup, then there are VIB which are incremental files for each newer restore point. When the retention period is reached, the oldest VIB is rolled into the VBK file. Because of this, when you choose 2 restore points, there has to be enough space for one full restore point, and 2 incremental restore points. Once the second incremental point is written the 1 incremental point rolled into the full point.

Typically incremental points are only a small fraction of the space of the full backup, so if you don't have enough space to store a full backup, and two small incremental points, you are playing with fire. Even if there was a setting for only one point, your VBK would likely grow to fill the available space in a matter of weeks. I'd strongly suggest you consider planning for some additional space.

[foggy]

Is there a reason a copy job requires a minimum of 2 restore points?

This is due to how transform works while applying retention settings in backup copy job. Having additional restore point ensures at least one restore point remains valid in case of incremental backup failure.

Agree with Tom, you definitely should have some extra space in the repository. But weren't you notified about lack of space on the repository during the backup copy job run (there is a corresponding setting in Veeam B&R options dialog and there should be a warning in the job session log)?