Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

VMWare ESXi 4.0/4.1 'Add to Inventory' greyed out

Posted on 2010-11-18
5
Medium Priority
?
6,102 Views
Last Modified: 2012-05-10
I have a server that was running VMWare ESXi 4.1 (now 4.0) that is in pre production and I am unable to select add to inventory for VMs from a production server that have been backed up to a NAS with GhettoVCB.

I am able to see the add to inventory option on the original production server (ESXi 4.0). However the files appear slightly differently on the pre production server as below. The preproduction server is also reporting that the NAS has slightly more free space (659.78GB) than the production server (515.89GB)

   

I'm expect this is something simple, but its driving me up the wall!
0
Comment
Question by:excelsupport
  • 3
5 Comments
 
LVL 10

Assisted Solution

by:abhijitmdp
abhijitmdp earned 1000 total points
ID: 34163361
0
 

Author Comment

by:excelsupport
ID: 34163616
There is definitely something going on with the permissions, though I suspect it may be the result of VMA creating the backup folders on the NAS, rather than vCenter.

I guess I can either create the VMA user(s) on the new server or change the permissions on the NAS.

Will report back my findings - thanks for (hopefully) pointing me in the right direction.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34163673
VMware will only allow a vm to be added to inventory on a single server. Typically this is managed by vCenter Server rather than directly on the host. If you don't have vCenter Server available, then you should be able to shutdown the vm on the production server and remove it from inventory there - you should then be able to add it to inventory and bring it up on your new server.

Good Luck
0
 

Accepted Solution

by:
excelsupport earned 0 total points
ID: 34163903
Well don't I feel stupid.

It was indeed a permissions issue. But not related to VMWare at all.

I had setup IP based restrictions on the NAS for the VM Backups and as the preproduction server is getting an address from a DHCP server of a range that isn't allowed r/w access to the NAS VMs it was able to read the contents but without being able to write to it, it wasn't able to fire up the VM.

I said it was going to be something simple! Still - wood for the trees and all that.

abhijitmdp pointed me in the right direction so thats gotta be worth some points. Thanks!
0
 

Author Closing Comment

by:excelsupport
ID: 34194913
Good because the initial response pointed me in the right direction and was also a  quick response.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

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.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Suggested Courses

571 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