Initial replication of a large running VM over narrow WAN pipes can take a very long time and in some cases will fail due to TCP packet drops.
There are 2 options which can accomplish this:
1. Replicate the VMs locally and move the ESX host server to the DR site.
2. Run a backup of the VM using vRanger from Quest locally.
3.Create the replication job and run the replication until the VM's UUID is created [this UUID will be used for subsequent replications].
4.Go ahead and cancel the replication job after the VM appears in vCenter/ESX inventory. Now rename the VM's dispaly name to match the source VM's display name.
5.Now create the restore job. Select the correct DR host and datastore, make sure to also select -forceoverwrite option.
Once this job is completed the VM is preseeded so you can now rerun the replication job.
From that point vReplicator will sync only the changes since the last backup was captured (differential data).
