I have a Networker 9.2.1 with a vproxy on vmware6. I am trying to do a nbd backup on a different esx where the vproxy is installed. The backup of another VM on the esx where the vproxy is, works without issue.
I already check the port 902 (telnet) from the vproxyVM to the ESX host and it works. the nslookup too.
The actual problem was SSL protocol not supported (old versions tls.protocols=tls1.0,tls1.1,tls1.2 ). This happen because one of the esxi host was version 5.1 (not supported), The client is going to migrate those VMs to the esxi version 5.5 and above . I already did the test on those esx and all work fine.
Can you check the vbackupd-vddk.log at the location /opt/emc/vproxy/runtime/logs/vbackupd/ on the NvProxy and see what error you see there or which host is not being able to be communicated to.
2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: Failed to open disk vpxa-nfc://[datastore A] AVP01V/Template_WS2008R2x.vmdk@vmwarea.berlitz.com.co:902!52 24 3c b6 cb f9 f9 ad-f5 f2 19 07 70 dc df 41. Error 14009 (The server refused connection) (DiskLib error 2338: NBD_ERR_NETWORK_CONNECT) at 4799.
2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [datastore A] AVP01V/Template_WS2008R2x.vmdk. Error 14009 (The server refused connection) (DiskLib error 2338: NBD_ERR_NETWORK_CONNECT) at 5026.
2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: VixDiskLib_Open: Cannot open disk [datastore A] AVP01V/Template_WS2008R2x.vmdk. Error 14009 (The server refused connection) at 5064.
2018/03/07 11:22:11 NOTICE: VDDK INFO VixDiskLib: VixDiskLib_Disconnect: Disconnect.
It seem some kind of SSL error, but dont know how to solve it yet.
This error occur when i I tried to make a backup of a VM with NBD on a different ESX where the vproxy is.
Ok, let me explain better. The hotadd and the NBD works as long as the VMs are on the same ESXi host as the vproxy. When the VMs that I am trying to backup are not on the same ESXi host as the vproxy the NBD is not working.
I need to use the NBD protocol because not all the storage on the ESXi host are SAN base, some are local.
carlos_romero
4 Posts
23733
1
Posted March 9th, 2018 08:00
Ok, I resolved the issue.
The actual problem was SSL protocol not supported (old versions tls.protocols=tls1.0,tls1.1,tls1.2 ). This happen because one of the esxi host was version 5.1 (not supported), The client is going to migrate those VMs to the esxi version 5.5 and above . I already did the test on those esx and all work fine.