Challenge
Replication job stops with warning:
“Cannot find restore point newer than seed”
Cause
The replication job has been (1) configured to seed from a repository that contains seed backup files that are as current as the backup job that generated them, or (2) has been configured to seed from the same repository as where the backup job that process the VM writes its files.
Solution
(1) If you have not ran the backup job since you generated the seed backup data, run it once so that the backup job files are newer than the seed.
(2) 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.