Backup Copy Job - behavior that will miss incrementals

[rahrenstorff]

Based on the documentation here: https://helpcenter.veeam.com/backup/vsp ... ssues.html and specifically this section:

The first synchronization interval always produces a full backup file — the starting point in the backup chain. If Veeam Backup & Replication fails to copy data for the full backup file during the first synchronization interval, it marks the job session as finished with the Warning status. During the next synchronization interval, Veeam Backup & Replication attempts to copy data for the full backup file in the following manner:

When a new synchronization interval begins, the restore point that was previously copied no longer corresponds to the restore point selection rules. That is, the time of the restore point creation falls out of the search scope. For this reason, Veeam Backup & Replication waits for a new restore point to appear on the source backup repository.

When a new restore point appears on the source backup repository, Veeam Backup & Replication detects what data blocks still need to be copied to make up a full backup file on the target backup repository, and copies these data blocks.

This process continues until there is a full backup file on the target backup repository.

At subsequent synchronization intervals, Veeam Backup & Replication copies incremental restore points. If Veeam Backup & Replication fails to transport an incremental restore point, it marks the synchronization task as failed. Veeam Backup & Replication waits for the expiration of the synchronization interval; after that, Veeam Backup & Replication marks the job session as finished with the Error status.

As, such any failed attempts to transport an incremental with a Backup Copy Job will subsequently ignore those missed incremental files because At every next synchronization interval, when a new restore point appears on the source backup repository, Veeam Backup & Replication copies incremental changes from this most recent restore point and transfers them to the target backup repository. and the most recent restore point will NOT include prior incremental restore points.

I'm hoping to get confirmation on this behavior and any possible resolutions or work-around to ensure all incremental files are transported to the offsite repository.

[Shestakov]

Hello Rodd and welcome to the community!
Description in the User Guide is correct.
Note that backup copy job retries a failed backup copy task 5 times within one backup copy job session by default.

and the most recent restore point will NOT include prior incremental restore points.

It will. In a case of failure you will have one incremental restore point after the next successful job run, which will include all the changes, so the chain will be consistent.
Thanks!

[rahrenstorff]

Shestakov,

So your saying: in the event a backup copy job missed one or more incremental files from a backup job, the subsequent backup copy job would locate the changed data necessary to build a consistent chain and then combine that data (by scanning multiple incremental files ?) into a single incremental file for the target repository?

If so, that process is not clearly described in the documentation, especially where it refers to Veeam Backup & Replication copies incremental changes from this most recent restore point and transfers them to the target backup repository. That underlined part, makes it sound like it will only copy the most recent restore point and not any earlier restore point missed due to failed transfers.

Please verify.

Rodd

[Shestakov]

So your saying: in the event a backup copy job missed one or more incremental files from a backup job, the subsequent backup copy job would locate the changed data necessary to build a consistent chain and then combine that data (by scanning multiple incremental files ?) into a single incremental file for the target repository?

That`s correct.
To make the explaination simple backup copy job takes the newest changed datablocks from available restore points of the source job and synthetically makes an increment. It does not just copy the last source restore point.
Thanks!