VMware VCENTER CONVERTER EN-000158-02 - Manual (Page 24)

Table 2-6. Supported Destinations
Destination Type Supported Versions
VMware Infrastructure virtual machine Managed destinations
n ESX 3.x and 4.0
n ESXi 3.x and 4.0 Installable and ESXi 3.x and 4.0
Embedded
n vCenter Server 2.x and 4.0
VMware virtual machines Hosted destinations
n VMware Workstation 5.x, 6.0.x, and 6.5.x
n VMware Fusion 1.x and 2.x
n VMware ACE 2.0.x and VMware ACE 2.5.x
n VMware Player 1.x, 2.0.x, and 2.5.x
n VMware Server 1.x and 2.x
OVF and OVA virtual appliances n OVF spec version 1.0
n Local .ovf or .ova file
N
OTE
For hosted destinations that reside on SMB or NFS shares, you must use volume-based cloning and
create 2GB disks that are not preallocated.
Restoring VCB Images in Converter Standalone
VMware Consolidated Backup enables you to back up all of the virtual machines of an entire ESX server. The
backup is stored by using Workstation disks, a .vmx file, and a catalog file. Converter Standalone can restore
VCB images to ESX server hosts and convert them to VMware standalone virtual machines.
When it runs on Windows hosts, Converter Standalone supports restoring VCB images of the source operating
systems described in Table 2-1 .
The virtual machine conversion limitations for Windows hosts described in Table 2-5 also apply when restoring
VCB images. Restoring VCB images from Linux host operating systems is not supported.
Converter Standalone does not maintain the
.nvram file, nor the VMware log files.
Converter Standalone does not read the original location settings from the catalog file. To restore to the same
location, find information such as datastore, host name, folder name, and resource pool in the catalog file and
enter it in the Conversion wizard. In addition, Converter Standalone does not read the original display name
from the catalog file. To use the same name and if you do not remember it, look it up in the catalog file. You
can read the catalog file as a plain text file.
Information Not Preserved When Using Converter Standalone for Managed
Product Destinations
When you restore VCB images for managed product destinations (ESX server hosts, for example), Converter
Standalone does not preserve certain hardware backing information from the original image, but rather
substitutes default settings.
Table 2-7 shows which areas are affected.
Table 2-7. Changes to Hardware Information Because of Conversion
Affected Area Behavior
CD-ROM Defaults to device type: client device.
Floppy Defaults to device type: client device.
Network adapters Defaults to the list of network adapters in the GUI. The MAC address is not preserved. The destination
host regenerates the MAC address.
User's Guide
24 VMware, Inc.