We have a remote location that is connected to our central infrastructure via a 2.4 Mbps TLS connection. There is a Windows Server 2003 SP1 domain controller at that location that we would like to virtualize on a Hyper-V virtual host running on Server 2008 R2 Core (also at the same remote location) Both the source computer (the domain controller) and the virtual host are located on the same LAN which is capable of 1Gbit speeds. SCVMM lives on a virtual machine back at main office (at the other end of the TLS link).
I would like to do an online P2V of the domain controller to the virtual host using the SCVMM installation we already have. This technet article seems to indicate that only the "meta-data" (such as machine.xml) required for the VMM host (the Hyper-V virtual host) is sent back and forth between the SCVMM machine (the VMM server). Our remote connection can obviously not sustain the traffic required for imaging the physical machine during the P2V process - I want all of the imaging traffic to stay on the remote location's LAN.
Can anyone confirm that when doing an online P2V using SCVMM located on another network segment than the source computer and the virtual host that no imaging traffic (or any bandwidth intensive) traffic is sent between the SCVMM server and either the source computer or the virtual host?
What happens to the physical host if I cancel the P2V process? Will it fail safe (i.e., will the source machine be effected)?