This is what I have been hearing as well. As customers continue to migrate physical servers to VMware virtual machines many data centers are looking to re-utilize those physical machines as either physical or virtualized disaster recovery targets. Because Double-Take can reside in the VM host or guest, when a VM is moved Double-Take can maintain the replication process. Should the movement of the VM take longer than the configured Double-Take UDP heartbeat parameter then at most Double-Take would reconnect to the target and initialize a file difference verify to maintain data integrity. Although this session is about  the Double-Take Virtual Recovery Assistant to assist with the P2V process, the Double-Take Livewire product which is specifically designed for use with VMware can be a cheaper solution for those Tier 2 and 3 servers that don't need to be highly available and where tape is not longer an acceptable recovery solution. Livewire doesn't include a failover feature like the Double-Take core product but instead recovers a disk image of the entire machine (Physical or virtual) and that recovery time can depend on the size of server image. Once the server image is applied it is essentially that same server from the IP address to the server name which is a option if you are looking to migrate to a more efficient virtualized blade server on different hardware. There is also the option to change the IP address before the last step of the image restoration should you be restoring on a different subnet.