Veeam Backup & Replication always copies the most recent restore points, even if a backup copy job runs for the first time and source backup repositories already contain chains of restore points.
In the immediate copy mode, the most recent restore point is the latest complete restore point created by a source backup job.
In the periodic copy mode, Veeam Backup & Replication uses the backup copy interval to identify a restore point as the most recent one — the time of restore point creation must be greater or equal to the difference between the current time and the backup copy interval.
Time of restore point creation >= current time – backup copy interval
Consider the following example. You create a backup copy job and set the backup copy interval to 24 hours. The source backup job will create a restore point on 6/30/2020 at 1:00 PM. The backup copy job will start on 7/1/2020, 12:00 PM. According to the rule, Veeam Backup & Replication will copy the created restore point:
6/30/2020, 1:00 PM >= 7/1/2020, 12:00 PM – 24 hours
If there are no restore points considered as recent, Veeam Backup & Replication does not copy data from source backup repositories. Instead, it waits for new restore points to appear. Only after that, Veeam Backup & Replication copies the most recent data blocks to the target repository.
In the periodic copy mode, you can also specify the search scope for restore points. For more information, see Select Machines to Process.
Limitations for Restore Points Selection
The following limitations apply when Veeam Backup & Replication selects restore points that must be copied to the target repository:
- Veeam Backup & Replication does not copy restore points from imported backups.
- Veeam Backup & Replication does not copy restore points that have already been copied by the same backup copy job to the target backup repository.
- Veeam Backup & Replication does not copy incomplete restore points.
- Veeam Backup & Replication does not copy restore points that are locked by the backup transformation process (merge, transform).
- A backup copy job does not copy a restore point if its data block size differs from the data block size of restore points that the job has already copied to the target backup repository. To copy restore points with the changed block size, you need to create active full backups. For details, see Change Storage Optimization Settings for Backup Copy Job.
For example, if you have changed the block size for restore points in the source backup job (the Storage optimization option in the Storage Settings), Veeam Backup & Replication will not copy newly created restore points and will display the Restore point is located in backup file with different block size message.