Surebackup VDDK error: 16064. Host is not licensed for this feature

Veeam Backup & Replication
5.x, 6.x, 7.x
Last Modified:


When SureBackup job is running against Domain Controller, Veeam B&R server is unable to access disk of the target machine. The following error can be seen in the log: VDDK error: 16064.Host is not licensed for this feature

[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: Failed to open VDDK disk [[VeeamBackup_server] name_a8a674bd6cca44fbb2be622c231e30a3/name.vmdk] ( is read-only mode - [false] )
[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: --tr:{
[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: --tr:VDDK error: 16064.Host is not licensed for this feature
[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: Failed to open VMDK.
[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: Logon attempt with parameters [VC/ESX: [hostname];Port: 443;Login: [domain\name];VMX Spec: [moref=vm-3216];Snapshot mor: [];Transports: [nbd]] failed because of the following errors:
[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: --tr:}
[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: --tr:Failed to mirror flat disk using VDDK. Disk path: [vddk://<vddkConnSpec><viConn name="hostname" authdPort="443" vicPort="443" /><vmxPath vmRef="vm-xxx" datacenterRef="datacenter" datacenterInventoryPath="VSD" snapshotRef="" datastoreName="VeeamBackup_server" path="name_a8a674bd6cca44fbb2be622c231e30a3/name.vmx" /><vmdkPath datastoreName="VeeamBackup_server" path="name_a8a674bd6cca44fbb2be622c231e30a3/name.vmdk" /><transports seq="nbd" hotAddRedirection="0" /><readBuffer size="0" /></vddkConnSpec>]. Flat file name: [name.vmdk]. Mount folder: [C:\Users\username\AppData\Local\Temp\f7823c16-fdf8-4631-b6da-e266bc735832].
[25.05.2011 07:53:34] <04> Info           [AP] (Client) error: --tr:Client failed to process the command. Command: [vddkMount].
[25.05.2011 07:53:34] <09> Info           [AP] (Client) state: closed


The account Veeam uses to connect to VC doesn't have sufficient permissions, even though backup jobs work with the same credentials.


Please make sure the account used to connect to VC has full administrative rights on this VC.

More Information

The following VMware KB indicates that this may occur on backup or restore when using VDDK 5.1 or 5.5: 

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
4.5 out of 5 based on 2 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: