6.0
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 and Powered On Virtual 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
Supported Destination Disk Types
Several destination disk types might be available for the selected destination.
Table 2‑6. Destination Disk Types
Destination Available Disk Types
VMware vSphere virtual machine
Thick
Copies the entire source disk size to the
destination, regardless of its used and
free space.
Thin
For managed destinations that support
thin provisioning through GUI, creates
an expanding disk on the destination.
For example, if the source disk size is
10GB, but only 3GB is used, the created
destination disk is 3GB but can expand
to 10GB.
Managed destinations of virtual machine version 10 and
later support disks up to 62TB in size. Earlier virtual
machine versions support up to 2TB disks.
VMware Workstation or other VMware virtual machine
Pre-
allocated
Copies the entire source disk size to the
destination, regardless of its used and
free space.
Not pre-
allocated
Creates an expanding disk on the
destination. For example, if the source
disk size is 20GB, but only 5GB is used,
the created destination disk is 5GB but
can expand to 20GB. Take this
expansion into account when you
calculate the free disk space on the
destination datastore.
Split pre-
allocated
For disks smaller than 2TB, splits the
source disk into 2GB sections on the
destination.
For disks larger than 2TB, splits the
source disk into 2TB sections on the
destination.
Split not pre-
allocated
For disks smaller than 2TB, creates 2GB
sections on the destination that include
only the real used space on the source
disk. As the destination disk grows,
new 2GB sections are created to
accommodate the new data until the
size reaches that of the original source
disk.
For disks larger than 2TB, creates 2TB
sections on the destination that include
only the real used space on the source
disk. As the destination disk grows,
new 2TB sections are created to
accommodate the new data until the
size reaches that of the original source
disk.
VMware vCenter Converter Standalone User's Guide
24 VMware, Inc.