07-18-2013 04:36 PM
So, i upgraded my 5200 to 2.5.3 today, and now all my backups can't connect with condition code 25. The upgrade APPEARED to go well.
my master is on windows 2008 R2, NetBackup 7.5.0.6
Support has been unable to find an issue, and while waiting for a call back, wondering if anyone had any ideas.
Here's a snippet of the errors I'm getting:
7/18/2013 7:33:26 PM - Error bptm(pid=28318) nbjm_media_request() failed: 25, cannot continue with copy 1
7/18/2013 7:33:26 PM - Error bptm(pid=28318) INF - cannot connect on socket (25), cannot continue with copy 1
7/18/2013 7:33:26 PM - Info bptm(pid=28318) EXITING with status 25 <----------
7/18/2013 7:33:27 PM - Info bpbkar(pid=2904) done. status: 25: cannot connect on socket
7/18/2013 7:33:27 PM - end writing
Solved! Go to Solution.
07-22-2013 10:13 AM
07-18-2013 04:58 PM
I should have added that these are all the same backups and the same setup that was working just fine before I upgraded.
07-18-2013 05:17 PM
07-18-2013 05:24 PM
Oh my WORD!! Thanks for the reply, but it's not encouraging. The 5200 is the only media server and storage we have!! That means no backups!!
07-18-2013 06:14 PM
Support helped me!! Maybe this is your answer too, schalk.
QUESTION: Do you have a couple interfaces bonded? I do.
My support guy put one line in my bp.conf file : (/usr/openv/netbackup)
REQUIRED_INTERFACE = nnn.nn.nn.nn
(where the nnn's are the IP number of the bond).
he caused the config to be re-read with
/usr/openv/netbackup/bin/admincmd/bprdreq -rereadconfig
and VOILA! Working
DNS and /etc/hosts must also resolve the IP number of the bond.
He's writing up a technote the number for which I will post when it's available.
07-22-2013 10:13 AM
07-23-2013 01:47 AM
Lynne - Thanks for sharing this with us - very useful