5.0
Table Of Contents
- VMware vCenter Converter Standalone User's Guide
- Contents
- About This Book
- Introduction to VMware vCenter Converter Standalone
- System Requirements
- Supported Operating Systems
- Installation Space Requirements
- Screen Resolution Requirements
- Supported Source Types
- Supported Destination Types
- Restoring VCB Images in Converter Standalone
- Configuring Permissions for vCenter 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
- Change a Volume Cluster Size
- 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
- Set Up a Virtual Disk as a Logical-Volume Group Container
- 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 Process
- Copy All Disks to the Destination
- Create an Optimized Partition Layout
- Create a Linked Clone
- Edit the Number of Processor Sockets and Cores
- 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 Job
- 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 Job
- Uninstall Converter Standalone Agent from the Source Machine
- Review the Summary and Submit the Conversion Job
- 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 Job
- Manage Conversion and Configuration Jobs and Tasks
- Index
If you plan to run an imported virtual machine on the same network as the source physical machine, you must
modify the network name and IP address on one of the machines, so that the physical and virtual machines
can coexist. Besides, you must make sure that the Windows source machine and the destination virtual machine
have different computer names.
NOTE You cannot move original equipment manufacturer (OEM) licenses between physical machines. The
license is attached to the server when you purchase it from the OEM and cannot be reassigned. You can only
reassign retail and volume licenses to new physical servers. If you migrate an OEM Windows image, you must
have a Windows Server Enterprise or Datacenter Edition license to run multiple virtual machines.
Hot and Cold Cloning of Physical Machines
Although Converter Standalone 4.3 and later versions support only hot cloning, you can still perform cold
cloning by using the VMware Converter 4.1.x Boot CD. Depending on your virtual environment, you can
choose to use hot or cold cloning.
Hot cloning, also called live cloning or online cloning, requires converting the source machine while it is
running its operating system. Hot cloning lets you clone machines without shutting them down.
Because processes continue to run on the source machine during conversion, the resulting virtual machine is
not an exact copy of the source machine.
When converting Windows sources, you can set Converter Standalone to synchronize the destination virtual
machine with the source machine after hot cloning. Synchronization is performed by transferring from the
source to the destination the blocks that were changed during the initial cloning period. To avoid loss of data
on the destination virtual machine, Converter Standalone can shut down certain Windows services before the
synchronization. Based on your settings, Converter Standalone shuts down the selected Windows services so
that no critical changes occur on the source machine while destination is being synchronized.
Converter Standalone can shut down the source machine and power on the destination machine when the
conversion process is complete. When combined with synchronization, this action allows seamless migration
of a physical machine source to a virtual machine destination. The destination machine takes over the source
machine operations with the least possible downtime.
NOTE When you hot clone dual-boot systems, you can clone only the default operating system to which the
boot.ini file points. To clone the nondefault operating system, change the boot.ini file to point to the other
operating system and reboot. After the other operating system is booted, you can hot clone it. If your second
operating system is Linux, you can boot it and clone it using the standard procedure for cloning Linux physical
machine sources.
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 direct 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.
Chapter 1 Introduction to VMware vCenter Converter Standalone
VMware, Inc. 9