Reference Guide

vConverter v4.1 Chapter 1 Introduction 9
The installation of the ESX Host Agent adds these files to the host:
The installation of the ESX Server Daemon makes these changes to the host
configuration:
• Adds S79vzloader to the /etc/rc3.d startup script list.
• Adds S80vzboost to the /etc/rc3.d startup script list.
• Adds sftp-over-tcp to the /etc/xinetd.d script list.
• Opens the iptables firewall port 422 to allow incoming communication to the data
transfer component.
34BHot and Cold Cloning
vConverter offers two approaches for converting physical or virtual servers to VM
targets. Hot cloning allows the source OS to continue to run while cold cloning requires a
source reboot. Whether you use the block- or file-based methods, during cold cloning no
changes are made in the source’s file system.
Hot cloning is the process of taking a live source system and creating a complete copy of
it in the form of a VM. To yield a data-consistent image, Vizioncore Consistency Driver
(VCD) and MS VSS assist in the process. VCD captures write requests from the file
system and retains the former state of the updated disk sectors. VCD is unaware of
running applications on the source and therefore cannot save associated data for backup.
This is where MS VSS steps in—telling databases, application servers, and so forth to
flush uncached data to disk so that backup can proceed.
There are two types of cold conversion—manual and remote. During manual cold
conversion, the source is manually booted using a VistaPE ISO boot image burned to a
CD. You manually create and control the conversion.
There are three types of remote conversion. During RCC, you schedule a conversion.
When the job starts, a new boot loader and boot image are sent to the source. At a time
that you designate, the source reboots in Vizioncore’s boot environment. After the boot
image brings the source onto the network, the conversion monitor component connects to