Hi all,
Wondering if someone can please possibly put me right.
Since upgrading to Vsphere 4.1, We in the process of serching all datastores for any Orphaned VMDK files.
I have got the script from the below page to complete, however it appears to list out Several Currently live servers.
Can anyone advise why this may be happening or is there a better more current script to check for Orphaned VMDKs....?
http://communities.vmware.com/docs/DOC-6960
It also seems to think that the .VMDKs for our all of our ESX hosts are also orphaned which im sure cannot be correct.
********13-local Orphaned VMDK Found: esxconsole.vmdk
********12-local Orphaned VMDK Found: esxconsole.vmdk
********11-local Orphaned VMDK Found: esxconsole.vmdk
********10-local Orphaned VMDK Found: esxconsole.vmdk
********09-local Orphaned VMDK Found: esxconsole.vmdk
********08-local Orphaned VMDK Found: esxconsole.vmdk
********06-local Orphaned VMDK Found: esxconsole.vmdk
********05-local Orphaned VMDK Found: esxconsole.vmdk
********04-local Orphaned VMDK Found: esxconsole.vmdk
********03-local Orphaned VMDK Found: esxconsole.vmdk
********02-local Orphaned VMDK Found: esxconsole.vmdk
********01-local Orphaned VMDK Found: esxconsole.vmdk
Cheers all
Paul
I used to use a script , but I've also had a lot of sucess with using Wastefinder , which is part of the Vkernel Capacity Management suite.
Hi there,
Thanks for the prompt response, However im not sure we are licenced for this product.
p
Try the powershell alternative...
http://communities.vmware.com/thread/266913
if that script is lookinf for .VMDK files that are not referenced in a VMX file then its bound to pick out your console VMDK.
my advice....update to ESXi while you can