Falha no backup de imagem da VM do Avamar com a mensagem de erro: "NBD_ERR_NETWORK_CONNECT"

Summary: Falha no backup da VM com a mensagem de erro: "Failed to open 'vpxa-nfcssl://[] /.Vmdk@:902' com bandeiras 0x1e NBD_ERR_NETWORK_CONNECT (2338)" ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms



  • Os backups de VM apresentam falha com o seguinte erro: 
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:DISKLIB-LIB   : Failed to open 'vpxa-nfcssl://[<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk@<esx_name>.com:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338). 
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:NBD_ClientOpen: attempting to create connection to vpxa-nfc://[<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk@<esx_name>:902
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:CnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed 2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:CnxConnectAuthd: Returning false because CnxAuthdConnect failed
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:Cnx_Connect: Returning false because CnxConnectAuthd failed
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:Cnx_Connect: Error message: Host address lookup for server esx-dc-ams003.avg.com failed: Name or service not known 2015-11-18 09:44:15 avvcbimage Warning <16041>: VDDK:[NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server esx-dc-ams003.avg.com failed: Name or service not known
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:NBD_ClientOpen: Couldn't connect to esx-dc-ams003.avg.com:902 Host address lookup for server esx-dc-ams003.avg.com failed: Name or service not known
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:DISKLIB-DSCPTR: : "vpxa-nfc://[<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk@<esx_name>:902" : Failed to open NBD extent.
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:DISKLIB-LINK  : "vpxa-nfc://[<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk@<esx_name>:902" : failed to open (NBD_ERR_NETWORK_CONNECT). 
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:DISKLIB-CHAIN : "vpxa-nfc://[<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk@<esx_name>:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:DISKLIB-LIB   : Failed to open 'vpxa-nfc://[<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk@<esx_name>:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).
2015-11-18 09:44:15 avvcbimage Error <0000>: [IMG0008] Failed to connect to virtual disk [<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk (13) (13) You do not have access rights to this file
2015-11-18 09:44:15 avvcbimage Info <19644>: Connecting virtual disk [san_storage_dc_ams_00_web] <VM_Name>/<VM_Name>.vmdk
2015-11-18 09:44:15 avvcbimage Error <0000>: [IMG0008] VixDiskLib_Open([<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk) returned (13) You do not have access rights to this file
2015-11-18 09:44:15 avvcbimage Info <9772>: Starting graceful (staged) termination, VixDiskLib_Open attempt to connect to virtual disk failed (wrap-up stage)
2015-11-18 09:44:15 avvcbimage Info <16052>: Terminating backup of all remaining virtual disks

 

Cause

  • O proxy está conectado ao ESX na porta 902, mas está tentando se conectar ao disco da VM mais de uma vez, mas ele falha devido a um problema de rede (ou seja, queda de pacote) com o seguinte erro:    
2015-11-18 09:44:15 avvcbimage Info <16041>: VDDK:DISKLIB-LIB   : Failed to open 'vpxa-nfc://[<Datastore_Name>] <VM_Name>/<VM_Name>.vmdk@<esx_Name>:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).

 

Resolution

Solução temporária:
  1. Host VMotion a máquina virtual cuja falha foi submetida a backup (conhecida acima como "VM_Name") para outro servidor ESX.
  2. Execute um backup sob demanda da máquina virtual migrada.
  3. Uma vez concluído com sucesso, o cliente deve envolver sua equipe de rede para verificar por que os pacotes estão sendo descartados entre o proxy (referido acima como "Proxy_Name") e o ESX (referido como "esx_name").

Solução temporária alternativa:

Verifique o registro do servidor ESX no DNS para ver se o proxy usado para esse backup de grupo pode resolver esse host ESX com o mesmo registro.  

Para isso:
  1. Abra um putty para o proxy usado para o backup (ou seja, Proxy_Name).
  2. Execute o comando nslookup <esx_FQN>.
  3. Se o resultado for negativo, peça ao cliente para modificar o registro ESX no DNS ou adicione cada arquivo /etc/hosts de proxy com o FQN e o IP corretos do esx.

 

Additional Information

Versão do Avamar: 7.1.1.145

Affected Products

Avamar

Products

Avamar, Avamar Client for VMware
Article Properties
Article Number: 000064048
Article Type: Solution
Last Modified: 07 Nov 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.