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
Procedure
u
In the Data to copy pane, select a copy mode from the Data copy type drop-down menu.
Option Description
Copy all disks and maintain layout
Results in disk-based cloning. You can preserve the source disk layout in
the destination virtual machine. This option is not available for physical
machine sources.
Select volumes to copy
Results in volume-based cloning. Volume-based cloning is performed at
file or block level. You can select the volumes to be copied to the
destination virtual machine. You can also resize and reorganize the
volume layout. This option is available for powered on source machines
that run Windows and Linux, and for all other supported sources that run
Windows.
Linked clone
Results in creating a VMware virtual machine that shares the virtual disk
of the source machine or system image. This option is available only for
hosted sources and hosted destinatons .
What to do next
The destination that you select determines the destination disk types that are available to you. To support
destination virtual disks on FAT file systems, divide the source data into 2GB files. For detailed information
about destination virtual disks types, see “Supported Destination Disk Types,” on page 22.
Resize a Volume
To manage disk space on the destination datastore, you can resize the disk volumes before you begin the
conversion.
Prerequisites
On the Options page of the Conversion wizard, click Data to copy in the options list.
Procedure
1 From the Data copy type drop-down menu, select Select volumes to copy.
2 In the Destination size column, select an option to specify the size of a destination volume.
Option Description
Maintain size
Maintains the original source volume size.
Min size
Copies only the used space of the source volume.
Type size in GB
Allows you to type a custom size in GB for the destination volume. The
value cannot be smaller than the used space on the source volume, but can
be larger than the total size of the source volume. The maximum allowed
volume size for the destination is 999999GB.
Type size in MB
Allows you to type a custom size in MB for the destination volume. The
value cannot be smaller than the used space on the source volume, but can
be larger than the total size of the source volume. The maximum allowed
volume size for the destination is 999999GB.
VMware vCenter Converter Standalone User's Guide
52 VMware, Inc.