5.5
Table Of Contents
- VMware vCenter Converter Standalone User's Guide
- Contents
- About This Book
- Introduction to VMware vCenter Converter Standalone
- Migration with Converter Standalone
- Converter Standalone Components
- Cloning and System Configuration of Physical Machines
- Types of Data Cloning Operations
- Using Converter Standalone with Virtual Machine Sources and System Images
- System Settings Affected by Conversion
- Changes to Virtual Hardware After Virtual Machine Migration
- System Requirements
- Supported Operating Systems
- Supported Firmware Interfaces
- Supported Source Types
- Supported Destination Types
- Supported Source Disk Types
- Supported Destination Disk Types
- Support for IPv6 in Converter Standalone
- Installation Space Requirements
- Screen Resolution Requirements
- Configuring Permissions for vCenter Users
- TCP/IP and UDP Port Requirements for Conversion
- Requirements for Remote Hot Cloning of Windows Operating Systems
- Conversion Limitations
- 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 Be Copied 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
- Select 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 Be Copied 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
Types of Data Cloning Operations
Converter Standalone supports disk-based cloning, volume-based cloning, and linked-cloning modes.
Table 1‑1. Cloning Modes
Data Copy Types Application Description
Volume based Copy volumes from the source
machine to the destination machine.
Volume-based cloning is relatively
slow. File-level cloning is slower than
block-level cloning. Dynamic disks are
converted into basic volumes on the
target virtual machine.
Disk based Create copies of the source machines,
for all types of basic and dynamic
disks.
You cannot select which data to copy.
Disk-based cloning is faster than
volume-based cloning.
Linked clone Use to quickly check compatibility of
non-VMware images
For certain third-party sources, the
linked clone is corrupted if you power
on the source machine after the
conversion. Linked cloning is the
fastest (but incomplete) cloning mode
that Converter Standalone supports.
Volume-Based Cloning
During volume-based cloning, volumes from the source machine are copied to the destination machine.
Converter Standalone supports volume-based cloning during hot cloning, and during the import of existing
virtual machines .
During volume-based cloning, all volumes in the destination virtual machine, except LVM2 logical volumes,
are converted to basic volumes, regardless of their type in the corresponding source volume. LVM2 logical
volumes can be preserved as logical volumes during conversion.
Volume-based cloning is performed at the file level or block level, depending on the destination volume size
that you select.
Volume-based cloning
at the file level
Performed when you select a size smaller than the original volume for NTFS
volumes or you choose to resize a FAT volume.
For FAT, FAT32, NTFS, ext2, ext3, ext4, and ReiserFS file systems,
Converter Standalone preserves the file system type during a volume-based
cloning at the file level.
Dynamic source disks are read but not preserved during volume-based
conversions. Dynamic disks are converted into basic volumes on the target
virtual machine.
Volume-based cloning
at the block level
Performed when you choose to preserve the size of the source volume or
when you specify a larger volume size for NTFS source volumes . Volume-
based cloning at the block level is supported only for Windows.
Disk-Based Cloning
Converter Standalone supports disk-based cloning to import existing virtual machines.
Disk-based cloning transfers all sectors from all disks and preserves all volume metadata. The destination
virtual machine receives partitions of the same type, size, and structure, as the partitions of the source
virtual machine. All volumes on the source machine's partitions are copied as they are.
Disk-based cloning supports all types of basic and dynamic disks.
VMware vCenter Converter Standalone User's Guide
14 VMware, Inc.