Step 1: from within the vSphere client, while connected to vCenter1, select the VM and then from "File" menu select "Export"->"Export OVF Template" (Note: make sure the VM is Powered Off otherwise this feature is not available - it will be gray). This action will allow you to save on your machine/laptop the VM (as an .vmdk, .ovf and a .mf file).
Step 2: Connect to the vCenter2 with your vSphere client and from "File" menu select "Deploy OVF Template..." and then select the location where the VM was saved in the previous step.
Copy all of the cloned VM's files from its directory, and place it on its destination datastore.
In the VI client connected to the destination vCenter, go to the Inventory->Datastores view.
Open the datastore browser for the datastore where you placed the VM's files.
Find the .vmx file that you copied over and right-click it.
Choose 'Register Virtual Machine', and follow whatever prompts ensue. (Depending on your version of vCenter, this may be 'Add to Inventory' or some other variant)
The VM registration process should finish with the cloned VM usable in the new vCenter!
For moving a virtual machine you need not clone the VM, just copy the VM files (after powering the VM off) to external HDD and register the same on destination host.
A much simpler way to do this is to use vCenter Converter Standalone Client and do a P2V but in this case a V2V. It is much faster than copying the entire VM files onto some storage somewhere and copy it onto your new vCenter. It takes a long time to copy or exporting it to an OVF template and then import it. You can set your vCenter Converter Standalone Client to V2V in one step and synchronize and then have it power up the VM on the new Vcenter and shut off on the old vCenter. Simple.
For me using this method I was able to move a VM from one vCenter to another vCenter in about 30 minutes as compared to copying or exporting which took over 2hrs. Your results may vary.
This process below, from another responder, would work even better if you can present that datastore to ESXi servers on the vCenter and then follow step 2. Eliminating having to copy all the VMs then follow rest of the process.
Copy all of the cloned VM's files from its directory, and place it on its destination datastore.
In the VI client connected to the destination vCenter, go to the Inventory->Datastores view.
Open the datastore browser for the datastore where you placed the VM's files.
Find the .vmx file that you copied over and right-click it.
Choose 'Register Virtual Machine', and follow whatever prompts ensue. (Depending on your version of vCenter, this may be 'Add to Inventory' or some other variant)
Copying the VM files onto an external HDD and then bringing it in to the destination will take a lot longer and requires multiple steps. Using vCenter Converter Standalone Client will do everything for you and is much faster. No external HDD required. Not sure where you got the cloning part from. vCenter Converter Standalone Client is simply copying the VM files by importing and exporting from source to destination, shutdown the source VM, then register the VM at destination and power on. All in one step. Takes about 1 min to set that up vCenter Converter Standalone Client.
You don't have to export your VMs at all. You can move the VM and clone to a TAXI host in vCenter 1. Then add the host to vCenter 2, and vMotion away whatever VMs to other hosts previously managed by vCenter 2. When done, you can add the TAXI host back to vCenter 1.
If you'd like to do this using the command line, you can do this if you have ESXi 6.0 (or possibly even ESXi 5.5) running, by using govc, which is a very helpful utility for interacting with both your vCenter and its associated resources.
That'll import it into your other vCenter. You might have to specify -ds NEW_DATASTORE too, if you have more than one datastore available, but govc will tell you so if you need to.
发布评论
评论（7）
我已经找到了问题的解决方案：
仅此而已！
谢谢！
I've figure it out the solution to my problem:
That was all!
Thanks!
是的，你可以这样做。
虚拟机注册过程应该完成，克隆的虚拟机可在新的 vCenter 中使用！
祝你好运！
Yes, you can do this.
The VM registration process should finish with the cloned VM usable in the new vCenter!
Good luck!
要移动虚拟机，您无需克隆虚拟机，只需将虚拟机文件（关闭虚拟机电源后）复制到外部硬盘并在目标主机上注册相同的文件即可。
For moving a virtual machine you need not clone the VM, just copy the VM files (after powering the VM off) to external HDD and register the same on destination host.
一种更简单的方法是使用 vCenter Converter Standalone Client 并执行 P2V，但在本例中是 V2V。它比将整个虚拟机文件复制到某个存储上并将其复制到新的 vCenter 上要快得多。将其复制或导出到 OVF 模板然后导入需要很长时间。您可以一步将 vCenter Converter Standalone 客户端设置为 V2V 并同步，然后让它在新 Vcenter 上启动虚拟机并在旧 vCenter 上关闭。简单的。
对于我来说，使用这种方法，我能够在大约 30 分钟内将虚拟机从一个 vCenter 移动到另一个 vCenter，而复制或导出则需要 2 个小时以上。您的结果可能会有所不同。
下面这个过程来自另一位响应者，如果您可以将该数据存储提供给 vCenter 上的 ESXi 服务器，然后按照步骤 2 进行操作，效果会更好。无需复制所有虚拟机，然后按照其余过程进行操作。
A much simpler way to do this is to use vCenter Converter Standalone Client and do a P2V but in this case a V2V. It is much faster than copying the entire VM files onto some storage somewhere and copy it onto your new vCenter. It takes a long time to copy or exporting it to an OVF template and then import it. You can set your vCenter Converter Standalone Client to V2V in one step and synchronize and then have it power up the VM on the new Vcenter and shut off on the old vCenter. Simple.
For me using this method I was able to move a VM from one vCenter to another vCenter in about 30 minutes as compared to copying or exporting which took over 2hrs. Your results may vary.
This process below, from another responder, would work even better if you can present that datastore to ESXi servers on the vCenter and then follow step 2. Eliminating having to copy all the VMs then follow rest of the process.
将虚拟机文件复制到外部硬盘上，然后将其带入目标位置将花费更长的时间，并且需要多个步骤。使用 vCenter Converter Standalone Client 将为您完成所有操作，而且速度更快。无需外部硬盘。不确定你从哪里得到克隆部分。 vCenter Converter Standalone Client 只是通过从源导入和导出到目标来复制虚拟机文件，关闭源虚拟机，然后在目标处注册虚拟机并打开电源。一步到位。设置 vCenter Converter Standalone Client 大约需要 1 分钟。
Copying the VM files onto an external HDD and then bringing it in to the destination will take a lot longer and requires multiple steps. Using vCenter Converter Standalone Client will do everything for you and is much faster. No external HDD required. Not sure where you got the cloning part from. vCenter Converter Standalone Client is simply copying the VM files by importing and exporting from source to destination, shutdown the source VM, then register the VM at destination and power on. All in one step. Takes about 1 min to set that up vCenter Converter Standalone Client.
您根本不必导出虚拟机。您可以将虚拟机移动并克隆到 vCenter 1 中的 TAXI 主机。然后将该主机添加到 vCenter 2，并将任何虚拟机通过 vMotion 移动到之前由 vCenter 2 管理的其他主机。完成后，您可以将 TAXI 主机添加回 vCenter 1 。
You don't have to export your VMs at all. You can move the VM and clone to a TAXI host in vCenter 1. Then add the host to vCenter 2, and vMotion away whatever VMs to other hosts previously managed by vCenter 2. When done, you can add the TAXI host back to vCenter 1.
如果您想使用命令行执行此操作，则可以如果您有 ESXi 6.0（或甚至可能是 ESXi 5.5)，通过使用
govc运行，这是一个非常有用的实用程序，可用于与 vCenter 及其关联资源进行交互。根据您的设置，您可以
然后将 VM
VM_NAME导出到文件夹export-folder中。从那里，您可以将其导入到您的其他 vCenter 中。如果您有多个可用数据存储，您可能还必须指定
-ds NEW_DATASTORE，但如果需要，govc会告诉您这一点。上述命令要求安装
govc，您应该这样做，因为无论哪种方式它都比 ovftool 好得多。If you'd like to do this using the command line, you can do this if you have ESXi 6.0 (or possibly even ESXi 5.5) running, by using
govc, which is a very helpful utility for interacting with both your vCenter and its associated resources.Depending on your setup, you can
Then, you'll have your VM
VM_NAMEexported in the folderexport-folder. From there, you can thenThat'll import it into your other vCenter. You might have to specify
-ds NEW_DATASTOREtoo, if you have more than one datastore available, butgovcwill tell you so if you need to.The commands above require that
govcis installed, which you should, because it's far better thanovftooleither way.