Downgrade NBU (windows client) 7.1 to 6.5.6

[vilhena]

Hello.

I'm trying to downgrade NBU (windows client) 7.1 to 6.5.6 in order to solve a problem with the duplications of the backup of some domain controllers.

I've uninstalled the 7.1 version, and installed the 6.5 version (so that it could be upgraded to the 6.5.6 version). Untill here all seemed ok, but when I tried to browse the clients in the NBU Java Admin Console, when I select the downgraded machine I get a socket communication error, but this doesn't happen with the 7.1 version. So my question is, do you know if there is some different ports used by the 6.5.6 version that the 7.1 doesn't?

Thanks for the attention.

Regards,

Vilhena

[vilhena]

The master's version is 7.1.

[Marianne]

NBU 7.1 will first try to connect to client on port 1556 (PBX), then fail back to port 13724 (vnetd). If vnetd is LISTENING on the client, there should be no reason for connection failure.

Please do the following:

Create bpcd log dir on client (install-path\veritas\netbackup\logs)

Test connection from master from cmd:

bptestbpcd -client <client-name> -verbose -debug

Please post output as well as client bpcd log.

[vilhena]

Hi Marianne.

Well I did what you told and it failed, here's the output from bptestbpcd -client <client-name> -verbose -debug:

[root@backupserver ~]# bptestbpcd -client myclient.domain.pt -verbose -debug
10:48:16.828 [24093] <2> bptestbpcd: VERBOSE = 3
10:48:16.834 [24093] <2> vnet_pbxConnect: ../../libvlibs/vnet_pbx.c.666: pbxSetAddrEx/pbxConnectEx return error 104:Connection reset by peer
10:48:16.834 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1718: 0: vnet_pbxConnect() failed: 18 0x00000012
10:48:16.835 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1719: 0: save_errno: 104 0x00000068
10:48:16.835 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1720: 0: use_vnetd: 0 0x00000000
10:48:16.835 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1721: 0: cr->vcr_service: bpcd
10:48:16.835 [24093] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1353: 0: do_service failed: 18 0x00000012
10:48:16.892 [24093] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.1957: 0: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
10:48:16.892 [24093] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.1971: 0: service: bpcd
10:48:17.099 [24093] <2> logconnections: BPCD CONNECT FROM 10.101.241.60.52565 TO 10.101.251.11.13724 fd = 3
10:48:17.101 [24093] <2> vnet_pbxConnect: ../../libvlibs/vnet_pbx.c.666: pbxSetAddrEx/pbxConnectEx return error 104:Connection reset by peer
10:48:17.101 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1718: 0: vnet_pbxConnect() failed: 18 0x00000012
10:48:17.101 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1719: 0: save_errno: 104 0x00000068
10:48:17.101 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1720: 0: use_vnetd: 1 0x00000001
10:48:17.101 [24093] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1721: 0: cr->vcr_service: vnetd
10:48:17.101 [24093] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1353: 0: do_service failed: 18 0x00000012
10:48:17.243 [24093] <2> do_vnetd_service: ../../libvlibs/vnet_connect.c.1675: 0: connect: VNETD CONNECT FROM 10.101.241.60.60647 TO 10.101.251.11.13724 fd = 4
10:48:17.243 [24093] <2> vnet_vnetd_connect_forward_socket_begin: ../../libvlibs/vnet_vnetd.c.445: 0: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
10:48:17.441 [24093] <2> vnet_vnetd_connect_forward_socket_begin: ../../libvlibs/vnet_vnetd.c.462: 0: ipc_string: 62594
10:48:21.700 [24093] <2> get_short: (1) cannot read (byte 1) from network: Connection reset by peer (104)
10:48:21.700 [24093] <2> bpcr_put_vnetd_forward_socket: get_short failed: 104
10:48:21.700 [24093] <2> local_bpcr_connect: bpcr_put_vnetd_forward_socket failed: 23
10:48:21.700 [24093] <2> ConnectToBPCD: bpcd_connect_and_verify(myclient.domain.pt, myclient.domain.pt) failed: 23
<16>bptestbpcd main: Function ConnectToBPCD(myclient.domain.pt) failed: 23
10:48:21.701 [24093] <16> bptestbpcd main: Function ConnectToBPCD(myclient.domain.pt) failed: 23
<2>bptestbpcd: socket read failed
10:48:21.701 [24093] <2> bptestbpcd: socket read failed
<2>bptestbpcd: EXIT status = 23
10:48:21.701 [24093] <2> bptestbpcd: EXIT status = 23
socket read failed

This is the bpcd log:

10:48:17.168 [760.1684] <2> bpcd main: offset to GMT 0
10:48:17.168 [760.1684] <2> bpcd main: Got socket for input 280
10:48:17.183 [760.1684] <2> logconnections: BPCD ACCEPT FROM 10.101.241.60.52565 TO 10.101.251.11.13724
10:48:17.183 [760.1684] <2> bpcd main: setup_sockopts complete
10:48:21.699 [760.1684] <8> bpcd peer_hostname: gethostbyaddr failed : The requested name is valid, but no data of the requested type was found.

 (0)
10:48:21.699 [760.1684] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 0
10:48:21.699 [760.1684] <16> bpcd main: Couldn't get peer hostname

I can't understand why it isn't working:/

Regards,

Vilhena

[Marianne · Accepted solution]

Your client is unable to resolve the master server's IP address (10.101.241.60 ) to a hostname that appears in the Client's SERVER list.

"gethostbyaddr failed to return peer host"

"Couldn't get peer hostname"

Please double-check DNS or add hosts entry on the client for the master.

Next, check Client's SERVER entries - you can use the BAR GUI on the Client : File -> Specify NetBackup Machines.............

[vilhena]

The problem was related with the reverse DNS, in the client when I did nslookup master_hostname I got the ip address, but if I did nslookup master_ip_address I got an error.

So I added the 'hostname ipaddress' in the clients hosts file and it worked ;)

Thanks, for your attention.

Regards,

Vilhena