Enable low connection bandwidth on replication job to allow for replica seeding. Seed the job with a pre-existing replica and the job runs as expected.
However, if for whatever reason the replica VM is then deleted, and you simply untick the low connection bandwidth option, the job still tries to find the replica seed and fails. If you leave the low connection bandwidth option ticked, and then manually remove the seed this way, the job runs fine. I just would have expected the job to stop looking for a seed if the low connection bandwidth option was unticked.
Perhaps there is a reason for this behaviour, its just not what I was expecting. This is with Veeam B&R 6.1 patch 1a
Thanks,
Ian
