Single VM showing up under 2 VSADs
Hi All,
My VMW infrastructure consists of only 2 hosts in a cluster.
They use shared storage.
I'm seeing a virtual machine showing up under VSADs-0 and VSADs-1 in vCenter. I'm not sure how that is possible. This is the only machine showing in both data-stores.
If I view the console for both of them, it takes me to the same machine... so it doesn't appear to be a clone.
My VMW infrastructure consists of only 2 hosts in a cluster.
They use shared storage.
I'm seeing a virtual machine showing up under VSADs-0 and VSADs-1 in vCenter. I'm not sure how that is possible. This is the only machine showing in both data-stores.
If I view the console for both of them, it takes me to the same machine... so it doesn't appear to be a clone.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When I re-add it to the inventory, again it shows up under VSADs-0 and VSADs-1...
Not sure why...
Not sure why...
Can you check it's definitely the same files and folder.
there's an easy way and a complicated, way
1. is digging around in vCenter SQL tables.
2. remove from inventory, create a new VM, and add the disks from the VM, something is clearly not correct with the VMX registration or SQL DB entries.
there's an easy way and a complicated, way
1. is digging around in vCenter SQL tables.
2. remove from inventory, create a new VM, and add the disks from the VM, something is clearly not correct with the VMX registration or SQL DB entries.
ASKER
I looked at the 'edit settings' for each VM showing up.
Both configuration files point to:
[VSADs-1] SERVER1/SERVER1.vmx
Both working locations point to:
[VSADs-1] SERVER1/
So it looks like they're using the same files.
Both configuration files point to:
[VSADs-1] SERVER1/SERVER1.vmx
Both working locations point to:
[VSADs-1] SERVER1/
So it looks like they're using the same files.
Clearly this is duplicated in the vCenter Db Tables, options apply as above.
ASKER
I have no idea how to view the SQL tables... Any advice?
I would recommend the remove from Inventory, create a new VM and then add the disks back.
otherwise you will need to use SQL Management Studio, to edit tables.
otherwise you will need to use SQL Management Studio, to edit tables.
ASKER
I actually got this figured out. I restarted the Vcenter server. Once it booted it still showed the same problem.
I removed the Windows 2003 SVR cd image and saved the VM. I guess by modifying the VM and saving it, VCenter updated the info.
I removed the Windows 2003 SVR cd image and saved the VM. I guess by modifying the VM and saving it, VCenter updated the info.
ASKER
[VSADs-1] SERVER1/SERVER1.vmx
Both working locations point to:
[VSADs-1] SERVER1/