01-30-2016 09:42 PM
Solved! Go to Solution.
02-14-2016 02:17 AM
Is your master really on CentOS ?
If so, you are unsupported, and no-one can help you.
As Reveroo said, see here:
01-31-2016 04:02 AM
01-31-2016 04:25 AM
You don't need to add any clients under the master server > server section so lets not get stuck on that poiint.
If comms failed, investigate why it failed.
Can you ping / telnet to the client (pbx port)?
Can you find the client name/ip by nslookup?
Can you successfully connect to the client using bptestbpcd -client "client name" / bptestbpcd -client "Client IP"
Does bpclntcmd -pn/-ip/-hn work from the client?
02-02-2016 01:20 AM
Hi,
Master is Centos 5.7 NBU 7.5
I checked 2 clients: both of em are Centos 6.7 and kernel updated on clients last week. NBU version is 7.5 and is running. no active firewall on master and clients.
I can ping and telnet to 1556 and 13782 from master to clients and reverse.
But for one client bptestbpcd -client returned "socket write failed" and for another returned "server not allowed access". (master exist in client's bp.conf!)
I will Checked bpclntcmd on clients and update this thread.
Thanks
02-02-2016 01:35 AM
For starters, CentOS is not supported as a Master server at all. It is only supported as a media server or a client.
Check the compatibility guide:
http://www.veritas.com/docs/000040842
02-02-2016 01:46 AM
Did you test telnet in both directions? master to client and client to master?
Did you test using hostnames or IP address?
NBU will first try port 1556 (pbx), then 13724 (vnetd), then 13782 (bpcd).
Please create bpcd log folder on the client and run bptestbpcd on master as follows:
bptesbpcd -client <client-NAME> -debug -verbose
Important that the client can resolve master's IP to SAME hostname that appears in bp.conf SERVER entry.
Please post output of bptestbpcd and list of NBU services/processes running on the client.
All of these must be running:
bpcd, vnetd and pbx_exchange
02-13-2016 11:49 PM
Hi all,
connections are ok both directions
./bptestbpcd -client xxxxx -debug -verbose
11:04:06.268 [27385] <2> bptestbpcd: VERBOSE = 0 11:04:06.268 [27385] <2> read_client: dname=CO_0, offline=0, online_at=0 offline_at=0 11:04:06.268 [27385] <2> read_client: dname=host_info, offline=0, online_at=0 offline_at=0 11:04:06.268 [27385] <2> read_client: dname=OA_0, offline=0, online_at=0 offline_at=0 11:04:06.268 [27385] <2> read_client: dname=., offline=0, online_at=0 offline_at=0 11:04:06.268 [27385] <2> read_client: dname=.., offline=0, online_at=0 offline_at=0 11:04:06.269 [27385] <2> db_freeEXDB_INFO: ? 11:04:06.283 [27385] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:04:06.284 [27385] <2> logconnections: BPCD CONNECT FROM 172.20.22.231.34730 TO 172.20.23.48.1556 fd = 3 11:04:06.298 [27385] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:04:06.298 [27385] <8> vnet_pop_byte: [vnet.c:1168] errno 0 0x0 11:04:06.298 [27385] <2> vnet_pop_byte: vnet.c.1170: 0: Function failed: 9 0x00000009 11:04:06.298 [27385] <2> vnet_pop_string: vnet.c.1250: 0: Function failed: 9 0x00000009 11:04:06.298 [27385] <2> vnet_pop_signed: vnet.c.1293: 0: Function failed: 9 0x00000009 11:04:06.298 [27385] <2> vnet_version_connect: vnet_vnetd.c.1664: 0: Function failed: 9 0x00000009 11:04:06.298 [27385] <8> do_pbx_service: [vnet_connect.c:2088] vnet_version_connect failed 9 0x9 11:04:06.299 [27385] <8> async_connect: [vnet_connect.c:1630] do_service failed 9 0x9 11:04:06.301 [27385] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3485] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 11:04:06.380 [27385] <8> do_vnetd_service: [vnet_connect.c:1955] remote host supports PBX, but PBX is not running 0 0x0 11:04:06.380 [27385] <8> do_vnetd_service: [vnet_connect.c:1991] connect VNETD CONNECT FROM 172.20.22.231.47569 TO 172.20.23.48.13724 fd = 4 11:04:06.381 [27385] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 11:04:06.382 [27385] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string /tmp/vnet-28143455434807697351000000000-KFoc3c 11:04:06.422 [27385] <2> put_string: cannot write data to network: Connection reset by peer (104) 11:04:06.422 [27385] <2> bpcr_put_vnetd_forward_socket: put_string /tmp/vnet-28143455434807697351000000000-KFoc3c failed: 104 11:04:06.422 [27385] <2> local_bpcr_connect: bpcr_put_vnetd_forward_socket failed: 24 11:04:06.422 [27385] <2> ConnectToBPCD: bpcd_connect_and_verify(xxxx, xxxx) failed: 24 <16>bptestbpcd main: Function ConnectToBPCD(xxxx) failed: 24 11:04:06.422 [27385] <16> bptestbpcd main: Function ConnectToBPCD(xxxx) failed: 24 <2>bptestbpcd: socket write failed 11:04:06.422 [27385] <2> bptestbpcd: socket write failed <2>bptestbpcd: EXIT status = 24 11:04:06.422 [27385] <2> bptestbpcd: EXIT status = 24 socket write failed
./bpps -x
NB Processes ------------ root 28114 1 0 10:56 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -standalone root 28119 1 0 10:56 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone Shared Symantec Processes ------------------------- root 2778 1 0 Jan23 ? 00:00:54 /opt/VRTSpbx/bin/pbx_exchange
Also bpcd log attached
02-14-2016 12:17 AM
I found this article and by it client connected successful. but transfer statuses between master and client is very slow now. and backups still failed with status 24
https://www.veritas.com/support/en_US/article.000025616
any idea?
02-14-2016 02:16 AM
The bptestbpcd failed. Why did did say it was ok?
02-14-2016 02:17 AM
Is your master really on CentOS ?
If so, you are unsupported, and no-one can help you.
As Reveroo said, see here:
02-14-2016 04:02 AM
Hi sdo, After I maked change that said in next reply client connected well, but I rolled back because of very slow actions,
02-14-2016 04:05 AM
Yes it is, whats your recommendation now, migrate?
02-14-2016 04:07 AM
Unfortunately, yes. Plan it carefully, and you should be ok.
02-14-2016 08:51 AM
02-14-2016 10:36 AM
does ur master have multiple interfaces ? can you do a nslookup on ip 172.20.22.231 and verify this entry exits on clients bp.conf file