12-12-2013 06:27 AM
MasterServer 7.5.05 server does not communicate with the client netbackup 6.5.6.
log client:
0,51216,200,200,1,1386772765301,1767,3086427856,0:,69:exiting, not configured as a SAN CLIENT - bp.conf missing SANCLIENT=1,8:nbftclnt,1
Solved! Go to Solution.
12-27-2013 03:46 AM
looked and ran services iptables saved took a test and it worked the communication between the client and mediaserver MasterServer
12-12-2013 06:36 AM
not configured as a SAN CLIENT - bp.conf missing SANCLIENT=1,8:nbftclnt,1
so are you trying to configure as a SAN client?
does it ever worked...?
12-12-2013 07:36 AM
Please - the log snippet is not helping one bit. You need to tell us what exactly is wrong.
With your version mix, server will first attempt comms on port 1556, then fail back to 13724.
Please ensure that port 13724 is open in both directions and that forward and reverse hostname lookup is working in both directions.
Create bpcd log folder on client for further troubleshooting.
Any reason why client is on 6.5?
12-12-2013 08:28 AM
The reason is the compatibility of the client
12-12-2013 08:39 AM
Please reply to the rest of my post?
Have you created bpcd log folder on the client?
Have you confirmed forward and reverse lookup? And bi-directional comms on port 13724?
12-12-2013 08:47 AM
Normal Backing rather worked over the network but it appeared in the log
12-12-2013 08:57 AM
Probably that 7.5 has the new Master Server setting under Fibre Transport - defaults to Preferred
If you dont have any FT servers then set it to Never
This will help with any delays during restores too
12-12-2013 10:40 AM
yes, I created , but seemed nothing in the log , I conducted tests with telnet client to the master server is working ok
12-12-2013 11:14 AM
Are backups failing? With which status code?
Are you seeing any error messages when trying to connect via Host Properties?
What is the name of the log folder where you see the details in your opening post?
12-13-2013 04:47 AM
12-13-2013 05:13 AM
Please do the following and show us output:
1. confirm hostname lookup (If master server is also the only media server, please ignore reference to media server):
from master and media server(s) :
bpclntcmd -hn <client-hostname>
bpclntcmd -ip <client-IP>
from client:
bpclntcmd -hn <master-hostname>
bpclntcmd -ip <master-IP>
bpclntcmd -hn <media-hostname>
bpclntcmd -ip <media-IP>
bpclntcmd -self
bpclntcmd -pn
2. Test port connectivity from master and media server:
Create bpcd log folder on the client under /usr/openv/netbackup/logs.
Next, run bptestbpcd on master:
bptestbpcd -client <client-hostname> -verbose -debug
Check results.
Does it connect?
If not, check client's bpcd log for errors.
Check in bpcd log if client can resolve server's IP address to Server name that appears in Client's Server list.
Do the same test from media server if you have separate media server(s).
If nothing is created in bpcd log, check port connectivity between servers and client.
Port 13724 must be open in both directions.
On Linux client, check that iptables is disabled.
Hope this helps!
12-13-2013 08:24 AM
12-18-2013 10:02 PM
bptestbpcd shows us that connection is REFUSED on port 1556 (pbx), 13724 (vnetd) and bpcd (13782):
status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO serv-portal-03 10.8.215.31 bpcd VIA pbx status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO serv-portal-03 10.8.215.31 bpcd VIA vnetd status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO serv-portal-03 10.8.215.31 bpcd
Did you remember to do the following before running bptestbpcd as per my post above?
Create bpcd log folder on the client under /usr/openv/netbackup/logs.
Next, run bptestbpcd on master:
bptestbpcd -client <client-hostname> -verbose -debug
Check results.
Does it connect?
If not, check client's bpcd log for errors.Check in bpcd log if client can resolve server's IP address to Server name that appears in Client's Server list.
Do the same test from media server if you have separate media server(s).
If nothing is created in bpcd log, check port connectivity between servers and client.
Port 13724 must be open in both directions.
On Linux client, check that iptables is disabled.
Please post client's bpcd log.
12-19-2013 02:43 AM
Yes I realized the above procedure follows the log attached
10:36:21.653 [11776] <2> bpcd main: offset to GMT 10800
12-19-2013 02:55 AM
10:36:21.676 [11776] <4> bpcd valid_server: serv-portal-03 is not a master server10:36:21.676 [11776] <16> bpcd valid_server: serv-portal-03 is not a media server either
12-27-2013 03:46 AM
looked and ran services iptables saved took a test and it worked the communication between the client and mediaserver MasterServer