VMware Snapshot are slower after upgrading to NetBackup and


The are three known issues that may cause VMware snapshots to slow down after upgrading to NetBackup
Issue #1:( Only)
VMware snapshots using display names are slower due to getaddrinfo calls on display names.  At NetBackup, NetBackup by default perform getaddrinfo calls against the display names of a virtual machine(VM).  This in turn causes the snapshots to slow down when the display name cannot be resolved.

Issue #2: ( Only)
VMware snapshots on pre-vSphere 5 environment are slower due to a new lock VM call for vSphere 5 that pre-vSphere 5 environments do not support.

Issue #3:(Both and
VMware snapshots on vSphere 5 environment are intermittently slow due to the new lock VM call.  VixDiskLib_PrepareForAccess functions is intermittently failing in vSphere 5 environment with "Not licensed to use this function."

Error Message

bpfis showing getaddrinfo calls on Display names:
13:44:51.402 [724.5388] <2> onlfi_vfms_logf: INF - find_virtual_server_vm: Comparing: VMCLIENT01 to VMCLIENT02
13:44:51.402 [724.5388] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6669: 0: fopen() failed: 2 0x00000002
13:44:51.402 [724.5388] <2> file_to_addrinfo: ../../libvlibs/vnet_addrinfo.c.6670: 0: fopen() failed: C:\Program Files\VERITAS\NetBackup\var\host_cache\0ea\e663dcea+0,1,2,0,1,0+vmclient02.txt
13:44:51.402 [724.5388] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1574: 0: found via getaddrinfo name: VMCLIENT02
13:44:51.402 [724.5388] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1576: 0: found via getaddrinfo service: NULL
13:44:51.402 [724.5388] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1505: 0: file cache has expired name: VMCLIENT01
13:44:51.402 [724.5388] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1506: 0: file cache has expired service: NULL
13:44:51.418 [724.5388] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1574: 0: found via getaddrinfo name: VMCLIENT01
13:44:51.418 [724.5388] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1576: 0: found via getaddrinfo service: NULL

bpfis showing the new lock call failing:
17:11:06.552 [6652.6788] <2> onlfi_vfms_logf: INF - vddkLog: VixDiskLibVimResolveHostName: Resolved to
17:11:06.552 [6652.6788] <2> onlfi_vfms_logf: INF - vddkLog: VixDiskLibVim: VixDiskLibVimLogin
17:11:07.301 [6652.6788] <2> onlfi_vfms_logf: INF - vddkWarnLog: VixDiskLibVim: Not licensed to use this function.
17:11:07.301 [6652.6788] <2> onlfi_vfms_logf: INF - vddkLog: VixDiskLibVim: VixDiskLibVimLogout 
17:11:07.488 [6652.6788] <2> onlfi_vfms_logf: INF - lockVM: VixDiskLib_PrepareForAccess returned 16064


Contact Support to obtain the binary from ET2670418 for or upgrading to  Please review issue #3 as it is necessary to upgrade to to obtain a fix for that issue.

Issue #1 will be addressed after adding binary to the VMware Backup Host.  If you wanted to enabled reverse lookup calls on your display names, the following registry could be added to the VMware Backup Host:


  1. Open the registry editor and drill down to "HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config" 
  2.  If needed, right click on "Config" and create a new key called "BACKUP"  (all upper case) 
  3.  Right click on the new key "BACKUP" and create a new string value called "displayNameEnableIP"  (case sensitive) 
  4.  You should now have the registry path indicated above.

Issue #2 will be addressed by just installing the binary.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec Corporation to be addressed in a forthcoming Maintenance Pack, Release Update, or version of the product.  Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.  Please refer to the maintenance pack readme or contact NetBackup Enterprise Support to confirm this issue (ET2670418) was included in the maintenance pack. 

This issue is addressed in the following version of NetBackup:

7.1 Maintenance Release 4 ( is available for download, please access the following link for download and readme information:


Issue #3, Symantec made a change in the code to not attempt the VixDiskLib_PrepareForAccess function 10 times.  Instead we will only attempt to make the call one time, and if it fails then we will move forward with the snapshot.  Symantec recommends reviewing your virtual environment to determine why the call is failing.  It is likely another process like vMotion already has a lock on your VM.  To obtain the change in code to make the call once, upgrading to NetBackup and contact Symantec to obtain the binary from ET2744563.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)