03-02-2012 02:55 PM
Master Server: udin06 - (Solaris10 – NBU 7.1)
Client: sdib, or sdin (two interfaces, B at end is the backup interface) – Solaris10
Backup failing with Status 25, cannot connect or socket. Through GUI hostproperties too, it doesnt connect.
IP address and Names have been changed for security reasons.
I won’t be able to provide the logs, but let me know what specifically are you loking for? Or give me sometime, i’ll change few things and would post asap. Would appreciate if it could be done without the logs cause they’re too big to change IPs and hostnames. Although the problem doesn’t seem difficult to tackle but I’ve spent days just to get this error fixed, but all in waste. Seems like a firewall issue but not sure.
All the commands were run from Master server.
Me@udin06:/usr/openv/netbackup/bin> sudo ./bpclntcmd -hn sdib01
host sdib01: sdib01.my.company.com at 192.160.170.40
aliases: sdib01.my.company.com sdib01 192.160.170.40
Me@udin06:/usr/openv/netbackup/bin> sudo ./bpclntcmd -hn sdin01
host sdin01: sdin01.my.company.com at 155.60.210.100
aliases: sdin01.my.company.com sdin01 155.60.210.100
Me@udin06:/usr/openv/netbackup/bin> sudo ./bpclntcmd -ip 192.160.170.40
host 192.160.170.40: sdib01.my.company.com at 192.160.170.40
aliases: sdib01.my.company.com 192.160.170.40
Me@udin06:/usr/openv/netbackup/bin> sudo ./bpclntcmd -ip 155.60.210.100
host 155.60.210.100: sdin01.my.company.com at 155.60.210.100
aliases: sdin01.my.company.com 155.60.210.100
-
Me@udin06:/usr/openv/netbackup/bin/admincmd> sudo ./bptestbpcd -client sdin01
<16>bptestbpcd main: Function ConnectToBPCD(sdin01) failed: 25
cannot connect on socket
ping
Me@udin06:/usr/openv/netbackup/bin/admincmd> sudo ./bptestbpcd -client sdib01
^C
-
Me@udin06:/usr/openv/netbackup/bin/admincmd> telnet sdin01 bpcd
Trying 155.60.210.100...
telnet: Unable to connect to remote host: Connection refused
Me@udin06:/usr/openv/netbackup/bin/admincmd> telnet sdib01 bpcd
Trying 192.160.170.40...
telnet: Unable to connect to remote host: Connection timed out
Solved! Go to Solution.
03-05-2012 08:23 PM
Ok, i've got a similar looking bpcd log today, and this time i confirmed this twice to provide me the correct one. the log is from the time when i initiated the bptestbpcd command.
Although I think I should run this command on the backup interface but still i did for both. but i'm little surprised that the log file doesn't logs as i hit the command there on the server. I noted the time when i ran the commands so posting that too along with the log file which is 100% correct this time. :)
@19:38:08.015 - ./bpclntcmd -client sdib01 -verbose -debug (backup interface of client)
@19:43:20.194 - ended.
19:46:25:813 - ./bpclntcmd -client sdin01 -verbose -debug (network interface of client)
19:46:25.928 - ended
Additional question: Why do we see NBU 6.5.5 in the logs and the old master server? I posted the bp.conf file too in case you need that. It's posted above.
03-05-2012 09:35 PM
03-05-2012 11:20 PM
Reviewing this thread, I doubt that your master server does not have route to sdib01.
In addition to bpcd log and bptestbpcd output, please provide output of following commands
* "ping -s sdib01 56 5" on udin06
* "ifconfig -a" on both hosts
* "netstat -rn" on both hosts
* "cat /usr/openv/netbackup/bin/version" on both hosts
03-06-2012 12:44 AM
bpcd log contains no evidence of connection request from IP 155.60.200.10.
You have either used wrong command (bpclntcmd instead of bptestbpcd) or firewall ports are blocked between new master and client.
You see 6.5 in the log because the client is still on NBU 6.5.
Connection attempts from old master because there is still a policy on old master trying to backup this client?
03-06-2012 02:35 AM
Sorry, my bad. No, I ran bptestbpcd only, it was a typo here. :|
03-06-2012 02:38 AM
5 packets transmitted, 0 packets received, 100% packet loss
Will provide you the next few commands later cause I don't see any sys admin at this time of night. :)
Thanks..
03-06-2012 02:39 AM
I'll check with that tomorrow morning, thanks. :)
03-07-2012 05:11 AM
This means udin06 can not communicate with sdib01. There are no available route from udin06 to sdib01.
You should talk with network team, and OS team as well.
03-07-2012 07:15 AM
it's not that, the backup interface in non-routable. i can successfully ping the network interface sdin01 but not sdib01. :)
03-07-2012 07:30 AM
So, if that is the case, how is NBU on udin06 supposed to get to sdib01?
03-12-2012 04:15 PM
i will test this by taking baxckup via production network.. thanks..
03-12-2012 08:16 PM
Hi 16ris10,
have you tried editing the host file of the master server, defining the ip address of you target client? and let me know the outcome when you try to do bptestbpcd.
Thanks
04-10-2012 09:39 PM
the resoltion to the problem was pretty basic. :|. there wasn't any backup interface or network connectivity. :|