Can you please help me about how to view "vmware.log" file? I want to get the locked file name.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
did you look at the Backup Appliance ?
and check the disks attached to the Backup Appliance if any belong to this VM you cannot power on.
VMware.log is a text file, you can download and view using WinSCP.
cbinayak
ASKER
Backup Appliance is not showing anything any locked file for this VM. However, our Backup Admin wants the name of the file that is locked so that he can do an advanced search in the Backup Appliance itself.
I am able to view the vmware.log file using vi editor. Please let me know where from I will get the locked file name.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
The Backup Appliance WILL NOT show any locked file.
BUT does the appliance, have any disks attached to it, which do not belong to it!
the VMWARE.log file may not report on the locked file. search for the word "lock"
this could also be chasing a red hearing....and appliance may not be the device locking the file.
can you try the following:-
1. Take a new snapshot.
2. wait 1-2 minutes
3. select DELETE ALL....
does it create a new snapshot file, or remove the snapshots.
e.g. does it create a file -0006.vmdk
also is the name of the file currently -00005.vmdk in disk settings, I cannot see because you masked it out.
cbinayak
ASKER
I migrated the vm to different host, took snapshot, waited 1-2 minutes, deleted all successfully. After that I tried to run Disk Consolidation but it fails with the same error.
I can see Hard Disk 1 is using "vmname_C-000006.vmdk" and Hard Disk 2 is using "vmname_E-000006.vmdk" but these two files are not there in the datastore.
The last two files that are there in the datastore are "vmname_C-000005.vmdk" and "vmname_E-000005.vmdk".
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
okay Consolidating and the method I asked you to do are the same, Consolidation is just VMware's easy method!
can you repeat...
1. Take a new snapshot.
2. wait 1-2 minutes
3. select DELETE ALL
but no running the consolidation process.
and check the datastore, any snapshots left ?
and what disks are in use ?
there is another method we can also try and thats CLONE.
CLONING the VM, will merge all current snapshots, and create a new VM without snapshots, and then you can continue to use this new VM.
BUT, if there is a lock on the parent vmdk, this is what is causing the issue. and either you will need to find the process causing the lock, or reboot the host, hosting the VM,
Can you try to migrate this VM to other hosts one by one and try to consolidate them on all hosts and check if that works ?
Not sure if VMKFSTOOLS works with 5.0. If it does, can you try the command below on all the VMDK files and help me with the output please ?
Take a putty to the ESXi host where the VM runs and change directory (CD) to VM's working directory and run the command below.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
yes, this is often the problem, resulting in a restart of the Host.
and you are certain it's not locked by the Backup Appliance ?
cbinayak
ASKER
I've asked backup team to look into this matter more deeply. In the meantime will restarting the ESXi host resolve this issue? I am asking this because I heard that backup of VM happens through ESXi host.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
If the lock is by another process, and not the appliance, it should clear.