4.3
Table Of Contents
- VMware vCenter Converter Standalone User's Guide
- Contents
- Updated Information
- About This Book
- Introduction to VMware vCenter Converter Standalone
- System Requirements
- Supported Operating Systems
- Installation Space Requirements
- Supported Source Types
- Supported Destination Types
- Configuring Permissions for VirtualCenter Users
- Support for IPv6 in Converter Standalone
- TCP/IP and UDP Port Requirements for Conversion
- Requirements for Remote Hot Cloning of Windows Operating Systems
- Installing and Uninstalling Converter Standalone
- Perform a Local Installation on Windows
- Perform a Client-Server Installation in Windows
- Perform a Command-Line Installation in Windows
- Command-Line Options for Windows Installation
- Modify Converter Standalone in Windows
- Repair Converter Standalone in Windows
- Uninstall Converter Standalone in Windows
- Connect to a Remote Converter Standalone Server
- Convert a Physical or Virtual Machine
- Start the Wizard for a Conversion
- Select a Source Machine to Convert
- Select a Powered-On Windows Machine to Convert
- Select a Powered-On Linux Machine to Convert
- Select an ESX/ESXi or vCenter Server Virtual Machine to Convert
- Select a VMware Hosted Virtual Machine to Convert
- Select a Backup Image or a Third-Party Virtual Machine to Convert
- Select a Hyper-V Server Virtual Machine to Convert
- Select a Destination for the New Virtual Machine
- Configure the Hardware of the Destination Virtual Machine
- Organize the Data to Copy on the Destination Machine
- Resize a Volume
- Exclude a Source Volume from the Conversion Process
- Move a Volume to a Different Virtual Disk
- Select the Destination Datastore for a Source Volume
- Add a Virtual Disk
- Move a Disk to a Different Datastore
- Create an Expandable Disk on a Managed Destination
- Create an Expandable Disk on a Hosted Destination
- Exclude a Source Disk from the Conversion Task
- Copy All Disks to the Destination
- Create a Linked Clone
- Edit the Number of Processors
- Allocate Memory for the Destination Virtual Machine
- Specify a Disk Controller for the Destination Virtual Machine
- Configure the Network Settings of the Destination Virtual Machine
- Configure the Network for the Helper Virtual Machine
- Organize the Data to Copy on the Destination Machine
- Configure the Software on the Destination Virtual Machine
- Configure the Conversion Task
- Set the Startup Mode for Destination Services
- Stop Services Running on the Source Machine
- Synchronize the Destination Machine with Changes Made to the Source Machine
- Power Off the Source Machine After Conversion
- Power On the Destination Virtual Machine After Conversion
- Limit the Amount of Resources Used by the Conversion Task
- Uninstall Converter Standalone Agent from the Source Machine
- Review the Summary and Submit the Conversion Task
- Configure Virtual Machines
- Save Sysprep Files
- Start the Configuration Wizard
- Select a Source Machine to Configure
- Select the Options to Configure
- Review and Submit the Configuration Task
- Managing Conversion and Configuration Tasks
- Index
Cold cloning, also called offline cloning, entails cloning the source machine when it is not running its operating
system. When you cold clone a machine, you reboot the source machine using a CD that has its own operating
system and the vCenter Converter application on it. Cold cloning allows you to create the most consistent copy
of the source machine because nothing changes on the source machine during the conversion. Cold cloning
leaves no footprint on the source machine, but requires you to have physical access to the source machine that
is being cloned.
When you cold clone a Linux source, the resulting virtual machine is an exact replica of the source machine
and you cannot configure the destination virtual machine. You must configure the destination virtual machine
after the cloning is complete.
Table 1-1 compares the hot and cold cloning modes.
Table 1-1. Hot and Cold Cloning Comparison
Comparison Criteria
Hot Cloning with Converter
Standalone 4.3
Cold Cloning with Converter
Enterprise 4.1.x
Licensing No license required with
VMware vCenter Converter
Standalone 4.3.
License file required for Enterprise
features of
VMware Converter Enterprise.
Required installation Full Converter Standalone installation
is required. As part of the cloning
process, Converter Standalone agent is
installed on the source machine
remotely.
No installation is required. All
components required for the conversion
are on the CD.
Supported sources Local and remote powered-on
physical or virtual machines.
Local powered-off physical or virtual
machines.
Advantages
n
Does not require direct access to
the source machine.
n
You can clone the source machine
while it is running.
n
Creates the most consistent copy of
the source machine.
n
Leaves no footprint on the source
machine.
Disadvantages
n
Applications that constantly
modify files need to be VSS aware
to allow Converter Standalone to
create a consistent snapshot for
cloning.
n
Dynamic source disks are read but
not preserved during volume-
based conversions. Dynamic disks
are converted into basic volumes
on the target virtual machine.
n
You must power off the source
machine to clone it.
n
Requires physical access to the
source machine.
n
Hardware detection and
configuration of Boot CD.
n
Converter Standalone 4.x features
are not supported.
Use
n
To clone running source machines
without shutting them down.
n
To clone unique hardware that the
Boot CD does not recognize.
n
To clone a system that Converter
Standalone does not support.
n
To preserve the exact disk layout in
the target.
n
To preserve logical volumes in
dynamic disks (Windows) or LVM
(Linux).
When to not use When you do not want anything to be
installed on the source system.
n
When you want Linux P2V with
automatic reconfiguration.
n
When you do not have physical
access to the source machine.
n
When you cannot afford a long
downtime of the source system.
n
To perform synchronization after
cloning.
VMware vCenter Converter Standalone User's Guide
12 VMware, Inc.