Unsolved
This post is more than 5 years old
1 Rookie
•
4 Posts
0
8847
November 14th, 2013 23:00
Virtual machine backups were failing.
Hi friends ,
We are getting below error on virtual machine backups , can you please let me know the way to resolve this issue ,
Sorry I am very new to Networker.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:NBD_ClientOpen: attempting to create connection to vpxa-nfcssl://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:CnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:CnxConnectAuthd: Returning false because CnxAuthdConnect failed
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:Cnx_Connect: Returning false because CnxConnectAuthd failed
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:Cnx_Connect: Error message: Host address lookup for server mumlbmvadpesx01 failed: Name or service not known
2013-11-14 18:30:38 avvcbimage Warning <16041>: VDDK:[NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server mumlbmvadpesx01 failed: Name or service not known
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:NBD_ClientOpen: Couldn't connect to mumlbmvadpesx01:902 Host address lookup for server mumlbmvadpesx01 failed: Name or service not known
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-DSCPTR: : "vpxa-nfcssl://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902" : Failed to open NBD extent.
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-LINK : "vpxa-nfcssl://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-CHAIN : "vpxa-nfcssl://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-LIB : Failed to open 'vpxa-nfcssl://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:VixDiskLib: Trying to open disk [MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk using mode nbd.
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:NBD_ClientOpen: attempting to create connection to vpxa-nfc://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:CnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:CnxConnectAuthd: Returning false because CnxAuthdConnect failed
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:Cnx_Connect: Returning false because CnxConnectAuthd failed
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:Cnx_Connect: Error message: Host address lookup for server mumlbmvadpesx01 failed: Name or service not known
2013-11-14 18:30:38 avvcbimage Warning <16041>: VDDK:[NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server mumlbmvadpesx01 failed: Name or service not known
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:NBD_ClientOpen: Couldn't connect to mumlbmvadpesx01:902 Host address lookup for server mumlbmvadpesx01 failed: Name or service not known
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-DSCPTR: : "vpxa-nfc://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902" : Failed to open NBD extent.
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-LINK : "vpxa-nfc://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-CHAIN : "vpxa-nfc://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
2013-11-14 18:30:38 avvcbimage Info <16041>: VDDK:DISKLIB-LIB : Failed to open 'vpxa-nfc://[MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk@mumlbmvadpesx01:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).
2013-11-14 18:30:38 avvcbimage Error <0000>: [IMG0008] Failed to connect to virtual disk [MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk (13) (13) You do not have access rights to this file
2013-11-14 18:30:38 avvcbimage Error <0000>: [IMG0008] VixDiskLib_Open([MUMLBMVADPESX01] MUMLBMDNS01v/MUMLBMDNS01v.vmdk) returned (13) You do not have access rights to this file
2013-11-14 18:30:38 avvcbimage Info <9772>: Starting graceful (staged) termination, VixDiskLib_Open attempt to connect to virtual disk failed (wrap-up stage)
2013-11-14 18:30:38 avvcbimage Info <16052>: Terminating backup of all remaining virtual disks
2013-11-14 18:30:38 avvcbimage Info <9671>: VixDiskLib_Cleanup() cleaned up 1 VMs with 0 remaining
2013-11-14 18:30:38 avvcbimage Info <16055>: Sending cancel message to avtar so the backup is changed to a partial.


TimQuan
6 Operator
•
1.2K Posts
1
November 17th, 2013 18:00
Does NetWorker VADP proxy have access to the VMware ESX host via port 902?
If not, ensure that bi-directional TCP/IP connections can be established on port 902 between the NetWorker VADP proxy host and the VMware ESX hosts.
o17Uu33DCF12520
6 Operator
•
1.1K Posts
2
November 17th, 2013 20:00
This is a kind of common error we oftern see in VM image level backup. In my experience, I could give you some leads as follows.
1. make sure the proxy could see and is athoraized to access the datastore where the vmdk resides
2. make sure the proxy is functioning well, for example it's been well-configured and has no communication issue with vcenter.
3. make sure the storage has granted the access to the proxy server.
here also I have a few solutions you could check out and see if they can help.
Symptoms
The VADP backup fails with an error indicating are no access rights to the virtual clients vmdk file.
Cause
The NetWorker VADP proxy does not have access to the VMware ESX host via port 902.
Resolution
Ensure that bi-directional TCP/IP connections can be established on port 902 between the NetWorker VADP proxy host and the VMware ESX hosts.
For further details on NetWorker and port requirements, refer to the "Network and Firewall port requirements" section in the "EMC NetWorker and VMware Integration Guide".
madhu_bhairi
1 Rookie
•
4 Posts
0
November 17th, 2013 22:00
Thanks the issue restored with your suggession
Thanks & Regards,
Madhu Sudhan Rao Bhairi
L3 - Backup, Global Services Management Centre(GSMC)
Growth Venture
Tata Communications Limited
Tiruvalluvar Satellite Earth Station,
No.226, Red Hills Road,
Kallikuppam, Ambattur,
Chennai - 600053
India
Direct +91 66674392 | Mobile +91 9500144877 | IP 514392
madhu.bhairi@tatacommunications.com
o17Uu33DCF12520
6 Operator
•
1.1K Posts
1
November 17th, 2013 22:00
glad to help.
please mark my answer as correct/helpful answer if it helps.
TimQuan
6 Operator
•
1.2K Posts
0
November 17th, 2013 22:00
Well, I world also thank you if you could also mark mine