User guide

Windows P2V Conversions 80
Conversion Overview
For procedures specific to RCC, see Additional Task Procedures at the end of this
chapter.
• Hardware Adaption Wizard utility will help install the drivers externally if you
cannot boot your Windows operating system due to missing drivers.
Note The VistaPE will assign the volume letter “X” to it’s own RAM drive volume. If the VistaPE is
used to convert a physical volume with the same volume label, the PE environment will
become unavailable to vConverter. Please ensure that source systems do not use the
volume letter “X” when converting with the VistaPE environment.
Converting with Synchronized Cutover
To minimize the cutover window, Synchronized Cutover completes a full conversion as
the source continues to run. Synchronization takes place continuously until the final
commit occurs during the cutover window. In other words, vConverter completes an
initial conversion. Then, at intervals that you schedule, vConverter determines which
files have changed and synchronizes only those files. During the final synchronization,
vConverter captures the remaining changes and places them on the target. This allows a
narrow cutover window and fast transition from physical to virtual.
Note For Windows 2000, all Intermediate and Cutover steps will be performed in cold mode. If
you have DHCP, make certain the VM is added to the task using its name, not it’s UIP
address (the IP address could be changed by DHCP after VM reboot, leading to a failed
task).
The sequence of activities during Synchronized Cutover is displayed below:
How Synchronized Cutover Works
The initial conversion can be done in block mode if there is no resizing required.
Otherwise file mode is used. It is important to note that during the initial conversion and
subsequent synchronizations, neither VSS nor the Consistency Driver are used.
Intermediate synchronizations are done only in file mode, again without consistency
compliance. The target VM image, after the initial conversion and any subsequent