My migration team is doing a good job trying to push as many VM’s through Move to stage reboots after-hours. I’ve noticed that replication slows way down when we have about 15-20 VM’s waiting for cutover.
I have checked the load on the Move VM and increased the amount of CPUs. Replication goes well (25Gbit network), but now we only have 2 seed streams going with 19 waiting to cutover. I have 4 other VM’s that are in the “seeding data” phase, but haven’t started their copies. Is this a bottleneck within the Move postgres database?
Any ideas on how I can get more VM’s copying in parallel?
Best answer by David Teague
Move performs up to 16 disks migration in parallel. If it is from the single ESX host, then the limit is 8 disks in parallel.
Hope this helps.