So, let’s now go to vCenter Converter: Here I have the option to start an additional synchronization. One snapshot was created after the initial transfer, a second snapshot was created after the second synchronization run, although this was not the final synchronization. Let’s see how this looks in vSphere, where I have a VM available that didn’t had a final synchronization:Īs you can see, the VM (this is the P2V’ed virtual machine!) has two snapshots. You can start the final synchronization at a moment that is convenient for you. This means that your P2V’ed VM can stay in sync for a long time. The final synchronization option determines if a sync is the final (and last) sync, or maybe you want to schedule one or more additional synchronization tasks between the source server and the destination VM. The first option is pretty clear I think now it’s possible to schedule the second run at a selected date/time. You can choose to perform a final synchronizationīoth options are visible in the Converter interface:.In Converter Standalone 5 there are two new options available: Any additional changes in source server are not synced anymore, because the P2V process finished. After this second run completed, your new VM was ready to go. Before this second run started, you had the option to stop certain services so the consistency of the disk was guaranteed.
This meant that, after a initial full backup (or P2V) of the source system, a second run was initiated right away to save the last changes to the new virtual machine. In previous versions of vCenter Converter you had the option to synchronize a P2V conversion to complete a hot migration.