Start by identifying the server whose VMkernel may be locking the file.
# vmkfstools -D /vmfs/volumes/UUID/VMDIR/LOCKEDFILE.xxx
 > Hostname vmkernel: gen 532, mode 1, owner xxxxxxxx-xxxxxxxx-xxxx- zzzzzzzzzzzz mtime xxxxxxxxxx]
zzzzzzzzzzzz gives the MAC adres of the server locking the file.
# lsof | grep -i LOCKEDFILE.xxx
OR
# vmkvsitools lsof | grep LOCKEDFILE.xxx
You see output similar to:
11773 vmx 12 46 /vmfs/volumes/Datastore_Name/VirtualMachineName/ VirtualMachineName-flat.vmdk
kill -9 PID (in the above case 11773)
Sometimes, and in my case after a failes “Migrate to production” of a server (as the ESX host died on me while migrating). After a Full VM Recovery the server won’t logon to the domain.
What to do:
Open a Command Prompt as Administrator (logged on localy)
And enter following command:
netdom.exe resetpwd /s:<server> /ud:<user> /pd:*
Where:
<server>
is the domain controller of the domain. <user> is the domain\user administrator user for the domain. the pd:* will ask you for the password. You should recieve a success. REBOOT and logon to the domain.
You will need to make changes to the registry to change the VBRCatalog folder location. To do so:
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Catalog
Find the string called CatalogPath, right-click it and choose modify