I have a THREE LOCAL ESX Server and would like to migration into a NEW Server reside in the SAN.
I used vmware STANDALONE CONVERTER to convert one of the test Machine ( 30 GB without any data). It takes about 18 minutes ( based on the standaone converter statistic which is about 10 MB/S).
The network switch is a GIGABIT SWITCH and the NIC is also GIGABIT. What is the throughput so slow ( between 9 to 11 MB/s) on average.
In addition to the above,
When i used the standalone vconverter, I select the VCenter and then select the host esx (targeted)
Will it be faster if I point directly to the ESX Server?
I dont think you can get significant result between both setup since the traffic should go directly between source and destination ESX and shouldn't go through vCenter except for browsing.
BTW, I can get max 30MB/s-50MB/s on vSphere during P2V using Converter Standalone 4.0.1(never did v2v yet). Have you try V2V via "scp" and do customize the VMs later. It's pretty straight forward though and mostly I can get better speed last time when did v2v via "scp" for ESX 3.5.
Are you trying to say when it Ask for the Target vmware infrastructure I select the ESX Server instead of pointing to the Vcenter and then select the host in the cluster?
How do you perform a V to V using SCP.
Assuming tempESX1 IP Address is 192.168.1.10 and the new server is esx1 - 192.168.1.20.
Do you use any special tools?
Thanks for your patience
You can use Veeam "FastSCP" tool or through command line interface CLI
Make sure both source(192.168.1.10) & destination(192.168.1.20) ESX permit SSH root login
Login to source ESX as root
then run command "scp -p -r /vmfs/volumes/datastoreName/VMA_folder firstname.lastname@example.org:/vmfs/volumes/datastoreName" or
Login to destination ESX as root
make virtual machine folder with command "mkdir /vmfs/volumes/datastoreName/VMA_folder"
then run command "scp email@example.com:/vmfs/volumes/VMA_folder/* /vmfs/volumes/datastoreName/VMA_folder/"