Ok, I had a reasonable job run last night. Looks like the copy jobs from one site took about 4:15hrs & the opposite direction took about 3:45. One thing I did note was that the primary-to-secondary site job seemed to have been interrupted after the first 5 (of 22) VMs or so and was 23% into a "merge" process when I checked on it last night.
I initially thought that perhaps the opposite direction job starting at the secondary-to-primary site, which is configured to use the exact same WAN accelerators, but the opposite way around, might have caused the copy job to stop (perhaps due to only a single WAN-x job being able to run at a time) but from what I was reading this morning at veeam-backup-replication-f2/wan-accelerator-concurrent-jobs-t18962.html
I could be reading incorrectly but is it the case that WAN-x's going in opposite directions can potentially process a simultanous job (i.e. a single job in each direction at the same time) or not?
In any case as it seems I have around a 4hr window for each site, I'm simply going to stagger the copy jobs so they don't run at the same time (even though neither is saturating the bandwidth). if it becomes an issue I can potentially create further WAN-x's on each side, but they would be VMs rather than physical so I'm not sure if the performance would be sufficient to make it worth while.
However, a *BIG* discovery I made this morning was that when i manually started my replica job, (from primary-to-secondary site) because the backup copy job completed about 06:30 this morning & replica-from-backup-copy was scheduled for 14:00 this afternoon, it replicated a couple of VMs but said that there were no new restore points for the remainder. I knew that there should have been so looked deeper and found that a bunch of replicas were effectively running 2 days behind, as far as restore points were concerned.
Again, I immediately suspected locked backup files so I disabled the copy job (which was sitting "idle") & retried the replica job again and suddenly a bunch of replications started kicking in, i.e. all the ones that were behind in the restore points.
So, I'm still struggling to understand what I'm doing wrong, or what incorrect expectation I have when all I want to achieve is to get a backup copy to the destination site (now working well) and THEN a "latest restore point" replica to be generated from that backup copy restore point.
What am I missing please?