OPERATIONAL DEFECT DATABASE
...
...
The replication job completes with the warning: Cannot find a restore point newer than the seed
This warning occurs when the replication job has been: configured to seed from a repository that contains seed backup files that are as current as the backup job that generated them. or configured to seed from the same repository as where the backup job that processes the VM writes its files. Generally speaking, seeding is intended for the initial generation of the replica using restore points that have been moved to a distant remote site that is reached by a low-speed connection. The intent is for the replication job to create the initial replica VM based on the restore points on the remote site, then, through further running of the replication job, update that replica using incremental data from the primary site. Using both Replication from Backup and Seeding from the same repository is redundant.
Troubleshooting Advice If you have not run the backup job since you generated the seed backup data, run it once so that the backup job files are newer than the seed. Confirm that replica seeding is set to pull from the repository where the seed data is stored; this location should be different than the repository where the replica job is set to source from.
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
