VMware vCenter Converter Standalone 5.1用户指南：最新版本与技术支持

需积分: 9 108 浏览量更新于2024-07-25 收藏 1.31MB PDF 举报

VMware vCenter Converter Standalone 用户手册是针对VMware公司产品的一项重要文档，版本为5.1。这份用户指南适用于当时列出的每个产品版本，并且在新版本发布前一直有效，直到被替换。用户可以通过访问VMware官方网站 <http://www.vmware.com/support/> 查找最新版本的文档更新，获取最新的技术细节和产品信息。该手册提供了详细的安装、配置和操作指南，帮助用户将现有基础设施中的物理或虚拟服务器迁移到VMware vCenter环境。vCenter Converter Standalone 是一个关键工具，它支持数据迁移，包括操作系统转换、数据同步和性能优化，以确保平稳的迁移过程并最小化停机时间。在使用过程中，用户需要了解如何设置源和目标环境，配置迁移策略，以及处理可能遇到的问题和错误。手册还包含了安全注意事项，如备份和加密，以保护敏感数据在迁移过程中的安全性。版权方面，所有内容受1998年至2013年VMware, Inc. 的版权保护，并受到美国和国际版权及知识产权法的约束。VMware的商标包括vCenter、vSphere等，在美国和其他司法管辖区均为注册商标。手册中提到的其他商标和名称属于其各自公司所有。如果用户对这份文档有任何意见或反馈，可以直接通过电子邮件 docfeedback@vmware.com 提交。这本用户手册不仅是技术人员的参考指南，也适合管理员和IT专业人士使用，以提升他们的运维效率和数据中心的现代化转型能力。

Because the target and the source virtual machines or system images have the same identities (name, SID, and

so on), running them on the same network might result in conflicts. To redeploy the source virtual machine or

system image, make sure that you do not run the source and target images or virtual machines on the same

network at the same time.

For example, if you use Converter Standalone to test whether you can run a Virtual PC virtual machine as a

VMware virtual machine without first decommissioning the original Virtual PC machine, you must first resolve

the duplicate ID problem. You can resolve this problem by customizing the virtual machines in the

Conversion or the Configuration wizard.

Changes to Virtual Hardware

After conversion, most applications function correctly on the VMware virtual machine because their

configuration and data files have the same location as on the source virtual machine. However, applications

might not work if they depend on specific characteristics of the underlying hardware, such as the serial number

or the device manufacturer.

Table 1-2 contains hardware changes that might occur after virtual machine migration.

Table 1-2. Hardware Changes After Virtual Machine Migration

Hardware Behavior

CPU model and serial numbers Might change after migration if they are activated. They correspond to the physical

computer hosting the VMware virtual machine.

Ethernet adapters Might change (AMD PCNet or VMXnet) and have a different MAC address. The

IP address of each interface must be individually reconfigured.

Graphics cards Might change after migration (VMware SVGA card).

Disks and partitions The number of disks and partitions might change if you rearrange volumes during

the cloning process. Each disk device might have a different model and different

manufacturer strings.

Primary disk controllers Might differ from the source machine.

Applications might not work if they depend on devices that are not available within a virtual machine.

VMware vCenter Converter Standalone User's Guide

16 VMware, Inc.

Table 2-3. Supported Sources (Continued)

Source Type Sources

VMware virtual machines Powered off hosted virtual machines running on the following VMware products:

VMware Workstation 7.x, 8.x, and 9.0

VMware Fusion 3.x, 4.x, and 5.0

VMware Player 3.x, 4.x, and 5.0

Hyper-V Server virtual

machines

For Hyper-V Server versions distributed with Windows Server 2008 R2, powered off

virtual machines with the following guest operating systems:

Windows Server 2003 (x86 and x64), SP1, SP2, and R2

Windows Server 2008 (x86 and x64) SP2 and R2 SP2

Windows 7 (except Home editions)

Windows Vista SP1 and SP2 (except Home editions)

Windows XP Professional SP2, SP3, and x64 SP2

SUSE Linux Enterprise Server 10 SP1 and SP2

SUSE Linux Enterprise Server 11

Red Hat Enterprise Linux 5.2, 5.3, and 5.4 (x86 and x64)

For other Hyper-V Server sources, perform the procedure for powered on physical

machines.

Third-party virtual machines or

system images

Acronis True Image Echo 9.1 and 9.5, and Acronis True Image Home 10 and 11

(.tib).

Symantec Backup Exec System Recovery (formerly LiveState Recovery) 6.5, 7.0, 8.0,

and 8.5, and LiveState Recovery 3.0 and 6.0 (.sv2i format only).

Norton Ghost version 10.0, 12.0, and 14.0 (.sv2i format only).

Parallels Desktop 2.5, 3.0, and 4.0 (.pvs and .hdd). Compressed disks are not

supported.

Parallels Workstation 2.x (.pvs). Compressed disks are not supported. Parallels

Virtuozzo Containers are not supported.

StorageCraft ShadowProtect Desktop, ShadowProtect Server, ShadowProtect Small

Business Server (SBS), ShadowProtect IT Edition, versions 2.0, 2.5, 3.0, 3.1, and 3.2

(.spf).

The Microsoft VHD format for the following sources:

Microsoft Virtual PC 2004 and Microsoft Virtual PC 2007 (.vmc)

Microsoft Virtual Server 2005 and 2005 R2 (.vmc)

Sources that run Windows 7 and Windows Server 2008 R2 can be converted to ESX 4.0 or later destinations.

Supported Destination Types

With Converter Standalone, you can create virtual machines compatible with VMware hosted and managed

products.

Table 2-4. Supported Destinations

Destination Type Supported Versions

VMware vCenter virtual machines Managed destinations

ESX 4.0 and 4.1

ESXi 4.0, 4.1, 5.0, and 5.1

vCenter Server 4.0, 4.1, 5.0, and 5.1

VMware hosted virtual machines Hosted destinations

VMware Workstation 7.x, 8.x, and 9.0

VMware Fusion 3.x, 4.x, and 5.0

VMware Player 3.x, 4x, and 5.0

For UEFI sources, the supported destination types are Workstation 8.0 and later, ESXi 5.0 and later, and

vCenter Server 5.0 and later.

VMware vCenter Converter Standalone User's Guide

20 VMware, Inc.

剩余99页未读，继续阅读

fangzhong2010

粉丝: 0
资源: 2

VMware vCenter Converter Standalone 5.1用户指南：最新版本与技术支持

VMware Converter Standalone软件手册及排障.pdf

VMware vSphere P2V操作文档 图文版（VMware vCenter Converter 6.0）

VMware vCenter Converter 指导手册

Vmware-Converter-操作手册.pdf

VMware_vCenter_Converter5.0_中文手册.pdf

VMware_vSphere_4.1学习手册Converter工具V2V、P2V导入虚拟机

VMware-vSphere日常操作手册

VMware vSphere5安装实施手册完整版

VMWARE Converter6.2.0实现实体机向虚拟化的转换

VMware vCenter Converter 5.0 中文使用手册：物理到虚拟（P2V）迁移指南

最新资源

VMware vSphere P2V操作文档图文版（VMware vCenter Converter 6.0）