In fact,
I don't think that my user is the issue. I'm using the same user as the vmware administrator uses while managing vmware vsphere. This users is not from any domain but a local admin user. Vcenter uses the local "suporte" user as the super admin. This users is listed in admin role.
Cheking carefully the logs I can see this:
[110] [VddkUtil::diskLibLog] DISKLIB-LINK : "san://snapshot-1406[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@esmirna.redecorp.br:443?suporte/XXX" : failed to open (You do not have access rights to this file).
[110] [VddkUtil::diskLibLog] DISKLIB-CHAIN : "san://snapshot-1406[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@esmirna.redecorp.br:443?suporte/XXX" : failed to open (You do not have access rights to this file).
[110] [VddkUtil::diskLibLog] DISKLIB-LIB : Failed to open 'san://snapshot-1406[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@esmirna.redecorp.br:443?suporte/XXX' with flags 0xe You do not have access rights to this file (3390).
Since i didn't presented the data stores to my backup host yet, I changed my backup transportation mode to NBD according to these logs:
[110] [VddkUtil::diskLibLog] 2014-05-14T14:32:37.336-03:00 [05588 info 'ThreadPool'] Thread enlisted
[110] [VddkUtil::diskLibLog] 2014-05-14T14:32:37.383-03:00 [05588 info 'ThreadPool'] Thread delisted
[110] [VddkUtil::diskLibLog] VixDiskLib: Trying to open disk [EVA6400_Datastore3] qvsrv/qvsrv.vmdk using mode nbdssl.
[110] [VddkUtil::diskLibLog] NBD_ClientOpen: attempting to create connection to vpxa-nfcssl://[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@bl-esx-lam10:902
[110] [VddkUtil::diskLibLog] Started up WSA
[110] [VddkUtil::diskLibLog] CnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed
[110] [VddkUtil::diskLibLog] CnxConnectAuthd: Returning false because CnxAuthdConnect failed
[110] [VddkUtil::diskLibLog] Cnx_Connect: Returning false because CnxConnectAuthd failed
[110] [VddkUtil::diskLibLog] Cnx_Connect: Error message: Host address lookup for server bl-esx-lam10 failed: The requested name is valid, but no data of the requested type was found
[ 20] [VddkUtil::diskLibWarning] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server bl-esx-lam10 failed: The requested name is valid, but no data of the requested type was found
[110] [VddkUtil::diskLibLog] NBD_ClientOpen: Couldn't connect to bl-esx-lam10:902 Host address lookup for server bl-esx-lam10 failed: The requested name is valid, but no data of the requested type was found
[110] [VddkUtil::diskLibLog] DISKLIB-DSCPTR: : "vpxa-nfcssl://[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@bl-esx-lam10:902" : Failed to open NBD extent.
[110] [VddkUtil::diskLibLog] DISKLIB-LINK : "vpxa-nfcssl://[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@bl-esx-lam10:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
[110] [VddkUtil::diskLibLog] DISKLIB-CHAIN : "vpxa-nfcssl://[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@bl-esx-lam10:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
[110] [VddkUtil::diskLibLog] DISKLIB-LIB : Failed to open 'vpxa-nfcssl://[EVA6400_Datastore3] qvsrv/qvsrv.vmdk@bl-esx-lam10:902' with flags 0xe NBD_ERR_NETWORK_CONNECT (2338).
[110] [VddkUtil::diskLibLog] 2014-05-14T14:32:44.247-03:00 [05588 info 'ThreadPool'] Thread enlisted
My question is: Using NBD transportation mode shouldn't DP VEPA Integration try to connect using the credentials previously placed at configuration's tab? I mean, DP will never be able to resolve the ESX server straightly, since this hostname is not listed at dns service. Moreover, port 902 probably is dropping packages once we have never changed the default settings of ESX Server. Do I need to create new entries for my ESX servers in DNS configuration? DP server must to resolve my ESX machines or everything is done from VCENTER server?
Thanks in advance