Solved

VM's not available in inventory of 2nd ESX

Posted on 2010-11-14
6
877 Views
Last Modified: 2012-05-10
We have 2 ESX machines running VMware 4.0 and 6 VM's.  There are supposed to be 3 VM's on each ESX but all six are showing up in the inventory of ESX1 and none are available in ESX2.  This is the case regardless of the VM's being powered on or off.  How can I get 3 moved to the inventory of ESX2?
0
Comment
Question by:stin27
  • 3
  • 3
6 Comments
 
LVL 40

Expert Comment

by:coolsport00
ID: 34133207
If you have appropriately licensing, you can 'live migrate' (Vmotion) them to the other host. If not, power them down, rt-click, select 'migrate' to cold migrate them to the other host.

~coolsport00
0
 

Author Comment

by:stin27
ID: 34133216
Don't seem to have the option to migrate when right clicking.  Any other way to do it?  Don't have Vmotion.
0
 

Author Comment

by:stin27
ID: 34133220
I have the option to remove from inventory.  Will that delete the VM?  If not, can I add it to the inventory of ESX2 once it is removed from the inventory of ESX1?
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 40

Expert Comment

by:coolsport00
ID: 34133224
Must be using standalone ESXi hosts. Well...there are a few ways to do this - pwr down the VMs you wanna move, download/install Veeam FastSCP & copy/paste the VM folders to the 2nd host; or you can download Converter Standalone to 'move' them. Both tools are free.
0
 
LVL 40

Accepted Solution

by:
coolsport00 earned 500 total points
ID: 34133240
Here is Converter Standalone:
https://www.vmware.com/tryvmware/?p=converter&ie=UTF-8&rlz=1T4GGLL_enUS371US371&q=vCenter%20Converter
and here's Veeam:
http://www.veeam.com/vmware-esxi-fastscp.html

BTW...no, removing from inventory won't delete the VM, just remove it from 'showing' while logged into the host. If you use Veeam (my recommendation), simply install Veeam, add both ESXi hosts under the 'Servers' heading (right-click -> Add Server/host), then browse the datastore of the host where the VMs are located. Right-click on the VM folder, then browse to the datastore of the 2nd ESXi host and then 'paste' the folder in the appropriate datastore. Once the VM is done copying, repeat for the remaining VMs. After all are copied over, log into that host with the vSphere Client, browse the datastore you placed them on, go into each VM folder, right-click the .vmx file and select 'Add to Inventory' for them to show up.

If you use vCenter Converter, you are basically creating a 2nd VM. During the Conversion Wizard, give the VM the same name, resources (RAM, etc.), and then select the appropriate host/datastore to place it in. Once it's done converting/moving, power it up and power down the source/orig VM. No need to 'Add to Inventory' as with Veeam...the Converter already does so for you.

A 3rd option is to use the Datastore Browser window to download the VM folder to your workstation (a copy of it), then upload it via the Datastore Browser on the 2nd host to the appropriate datastore (you'll have to 'add to inventory' as described above). This will only work if you have enough disk space on your workstation to house the VMs.

Regards,
~coolsport00
0
 

Author Comment

by:stin27
ID: 34133542
The datastores were identical on both hosts - strange.  I logged into vSphere and used the datastore browser and added the .vmx file to the inventory.  Starting up now -- fingers crossed.
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question