UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.

Data Protector - Support Tip - VMware fails to select SAN, using NBD instead

The backup did run over SAN and after a VEAgent problem some VM backup’s are now passing over NBD instead.


Typical message in the session report:

Virtual Machine 'VM': Backup disk scsiX:X using transport method NBD


The most probable reason is the SAN lock from VMware was not released.

Manual cleaning up the data is the only solution.


Note: If only a NBD transport mode exits, the backup will fail since no other transport mode is then available.

Virtual Machine 'VM': Could not backup disk scsi0:0 ...


When no backups are running have a look on the VEAgent backup host.

The place where VMware sets its lock files is C:\Windows\Temp\vmware-SYSTEM


This folder should be free of any uuid#-vm-XXXX folders, for example:


10/01/2012 07:56 PM <DIR> 420e8db6-5146-8aaf-5596-1dc7c738c1a1-vm-27

Directory of C:\Windows\Temp\vmware-SYSTEM\420e8db6-5146-8aaf-5596-1dc7c738c1a1-vm-27

10/01/2012 07:56 PM <DIR> .

10/01/2012 07:56 PM <DIR> ..

10/01/2012 07:56 PM <DIR> LOCK.lck

10/01/2012 07:56 PM <DIR> nbd

10/01/2012 07:56 PM <DIR> san

When the folder is deleted, the file LOCK.lck is removed


To release this VM, the folder 420e8db6-5146-8aaf-5596-1dc7c738c1a1-vm-27 should be removed.
Verify that no backups VEagent backups are active!
Note that this directory has special permissions and can only be removed if permissions are changed first.
Select folder, properties, security tab.
Select “Edit” and allow administrators “full control”, apply and answer “yes” to continue and now delete the directory.
When L6 Trivia debugs are enabled the following message will be logged:
2012-11-09T14:16:23.215+01:00 [02212 error 'Default'] Cannot use advanced transport modes for vcenter.hp.com:443/moref=vm-27/snapshot-27:
Cannot create directory C:\Windows\TEMP\vmware-SYSTEM\420e8db6-5146-8aaf-5596-1dc7c738c1a1-vm-27.
Tags (4)
2 Replies
Absent Member.
Absent Member.

Hey Bob, 


Quick question for you, you state that the locks are containted in the c:\windows\temp\vmware-system\ folder. In my structure, Data Protector 7.1 (various levels of updates applied), my locks seem to be in folders like c:\windows\temp\vmware-system-xxx\ and I have multiples of these folders. Is there a reason for this? Why are my SAN .lck files located differently than what you have listed as the lock directory?

Absent Member.
Absent Member.

I am pretty sure that these files are created by VMware, and are not a function of Data Protector.  When I am working a VMware problem, I am, like you, finding these files in different places, although always in



This is why I said 'for example', and the best way to find these files is probably be doing a search for '.lck'

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.