Ultimately this isn't a big deal. I wouldn't consider this a code defect, but this might benefit from a Veeam KB if one doesn't already exist and if Veeam R&D is able to easily repro the issue.
Updates to my previous comment. Importantly - replication job runs have completed without issues since the couple _replica VM snapshot create/deletes (and SvMotions I did). A bit more background on my environment/circumstances:
Updates to my previous comment. Importantly - replication job runs have completed without issues since the couple _replica VM snapshot create/deletes (and SvMotions I did). A bit more background on my environment/circumstances:
- I inherited this environment, so don't know the full history.
- I recently rebuilt the vCenter server for a number of reasons (and ran the Veeam migrator utility, but I don't think that really matters for replica VMs)
- Just one replication job from "source" production site to the replica/DR site.
- Job has replica seeding advanced control enabled.
- Replica seeding comes from mapping on existing VMs (not from backup repo)
- CBT is enabled
- The reason I was doing SvMotions at all was due to the (iSCSI/VMFS) datastore looking a little ugly - I think David is on the right track with older/broken/duplicate replicas being related here, as that's exactly what I see/did see.
Statistics: Posted by FCU_JE — Jul 02, 2025 1:38 pm
