VMware Backups may fail with "Error 18000 (listener error GVmomiFaultInvalidResponse)"

VMware Backups may fail with "Error 18000 (listener error GVmomiFaultInvalidResponse)"

  • Article ID:100032262
  • Last Published:
  • Product(s):NetBackup
  • Ratings: 0 1

Problem

Due to known VMware issue in VDDK, vADP backups may fail with the following error in the VxMS Provider log "Error 18000 (listener error GVmomiFaultInvalidResponse)".

Error Message

We have seen this cause the backup to fail with:
EXIT STATUS 12: file open failed

Errors in VxMS Provider log:
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Callback for login.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Get error from listener.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Retrieve information from VIM fault.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: VixDiskLibVimGetFaultReason: fault (null) does not have reason.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Error 18000 (listener error GVmomiFaultInvalidResponse).
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1823 <DEBUG> : [VFM_ESWARN] VixDiskLibVim: Login failure. Callback error 18000 at 2434.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Failed to find the VM. Error 18000 at 2506.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Logout from server.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Clean up callback data.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Clean up after logging out from server.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Logout callback is done.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Logout from server is done.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Login callback is done.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Clean up callback data.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLibVim: Get NFC ticket completed.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLib: Error occurred when obtaining NFC ticket for: [SOMEDATASTORE] SOMEVM/SOMEVM-000003.vmdk. Error 18000 (Cannot connect to the host) (fault (null), type GVmomiFaultInvalidResponse, reason: (none given), translated to 18000) at 4515.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [SOMEDATASTORE] SOMEVM/SOMEVM-000003.vmdk. Error 18000 (Cannot connect to the host) (fault (null), type GVmomiFaultInvalidResponse, reason: (none given), translated to 18000) at 4669.
22:53:56.0238 : g_vixInterfaceLogger:../libvix.cpp:1819 <DEBUG> : [VFM_ESINFO] VixDiskLib: VixDiskLib_Open: Cannot open disk [SOMEDATASTORE] SOMEVM/SOMEVM-000003.vmdk. Error 18000 (Cannot connect to the host) at 4707.
22:53:56.0238 : vdOpen:../VixInterface.cpp:407 <DEBUG> : Done with Open(): 0
22:53:56.0238 : vdOpen:../VixInterface.cpp:428 <WARN> : Open() error: 18000
22:53:56.0238 : vdOpen:../VixInterface.cpp:381 <TRACE> : out
22:53:56.0238 : openVixDiskImage:../VixGuest.cpp:3621 <ERROR> : vdOpen() for [[SOMEDATASTORE] SOMEVM/SOMEVM-000003.vmdk] returned error code [18000] 22:53:56.0238 : openFileName:../VixGuest.cpp:3539 <ERROR> : Exception: VERIFY_VXMS
22:53:56.0238 : log:../Error.cpp:249 <WARN> : Error: 0x00000019 occured in file ../VixGuest.cpp, at line 3539
22:53:56.0238 : log:../Error.cpp:249 <WARN> : Error: 0x00000019 occured in file ../VixGuest.cpp, at line 3539
22:53:56.0238 : ~VixFile:VixFile.h:97 <TRACE> : in
22:53:56.0238 : ~VixFile:VixFile.h:97 <TRACE> : out
22:53:56.0238 : openFileName:../VixGuest.cpp:3581 <ERROR> : Returning: 25
22:53:56.0238 : openFileName:../VixGuest.cpp:3501 <TRACE> : out
22:53:56.0238 : vixMapOpenFileName:../VixCoordinator.cpp:1113 <TRACE> : rflags returned: 0x2aa970
22:53:56.0238 : vixMapOpenFileName:../VixCoordinator.cpp:1118 <ERROR> : Returning: 25
22:53:56.0238 : vixMapOpenFileName:../VixCoordinator.cpp:1081 <TRACE> : out
22:53:56.0238 : vix_map_open_file_name:../libvix.cpp:1428 <ERROR> : Returning: 25

Cause

When many VMs are backed up concurrently, VDDK can crash occasionally.
When many virtual machines are backed up in parallel, VixDiskLib might crash. The issue is not consistently reproducible, but was determined to be a problem with null entries in libgvmomi. This issue has been fixed in this VDDK version 6.0.2

See also: https://www.vmware.com/support/developer/vddk/vddk-602-releasenotes.html
 

Solution

VDDK version 6.0.2 is shipped with NetBackup version 8.0.  If you are experiencing this issue please ensure the Backup Host is running Netbackup version 8.0 or later.

For further details on VDDK versions and Netbackup compatbility please see the Virtual Systems Compatibilty section of the Software Compatibility List:

https://www.veritas.com/content/support/en_US/doc/NB_80_OSSCL

 

 

Was this content helpful?