Forum Discussion
I am battling with the OS and NBU versions that you have selected.
W2012 with 7.1.x and earlier?
Not possible as support for W2012 started much later.
Status 24 is never an NBU issue, therefore a good understanding of the environment is crucial, especially the problematic clients.
There are technotes for W2003 clients, but best if you give us correct info.
Herewith extract from excellent post :
I describe the 23/24/25 status codes as follows:
RC=23: Server A sent a IP packet to valid server B, and is waiting for a response packet. It fails to get the response packet within the TIMEOUT window and raises the rc=23.
RC=25: Server A tried to sent IP packet to invalid server B. No connection made so Server A sets rc=25.
RC=24: Server A sends packet to server B and get a response within the TIMEOUT window. But something happens that drops connection between them.
I make an analogy of this communication environment using phone calls:
Person on Phone A calls to phone number B, which connects and they leave a voice mail to call them back. They wait for a call back that does not come and after a specified time, they quit. RC=23.
Person A calls phone number for what he thinks is a valid Phone B. The call does not go through and they hear the message "The number you have dialed is not a working number". RC=25.
Person A calls Person B, they call is picked up but the line connection somehow gets dropped unexpectedly.while communications is in progress. RC=24.
All of these are communication errors of some kind.
For RC=25, the sourtce server may have the wrong target server name in its environment or an invalid/wrong IP address for the target server.
For RC=23, A can talk to B but B cannot talk to A. Could be a source server it does not recognize or it is using the wrong IP address t respond to. Possible bad host name to IP resolution.
RC 24: The toughest of the bunch. A and B know each other correctly. They just can't keep the call going.
You may also want to go through this post by mph999 :
https://vox.veritas.com/t5/NetBackup/Backup-job-fails-with-different-status-codes-13-24-and-42/m-p/460060#M102743
Unfortunately most of the Symantec URLs are no longer working...
- AdamChangepoint6 years agoLevel 3
Thanks for that info, but sorry for sending you down the wrong path :/
I made a mistake and have now updated my original message, my client and master server version is actually 7.7.3 and not 7.1.x
My Bad :(
- Marianne6 years agoLevel 6
What about OS and NBU version(s) on problematic clients?
How many clients are affected? The same or different clients each time?
Does this happen only during peak backup times?
If so, have you tried to stagger backup schedule times?The 2nd post that I have referred to lists quite a lot of possible reasons for network issues during backup window.
- AdamChangepoint6 years agoLevel 3
So OS is all Windows 2012 R2
Basically the turn of events is the problem occurs on a machine, I reboot the machine, the problem goes away for a few days and then the problem returns again. Not on every client but I am getting to the point now where every night a new client is having the problem. I'd say this is affecting about 10 - 15 different machines.
No it happens off peak times as well, once the (24) and (42) errors start occuring the clients will not complete a sucesseful backup at any time unitl I reboot them.
As an example I have 2 clients having the issue right now and I haven't rebooted them. I just tried the suggestions in this article:
https://vox.veritas.com/t5/NetBackup/network-read-failed-42/td-p/839890
Once I added the clients to the Resilient Network they haven't failed but they haven't completed either. Normally these clients can complete a backup in 20 mins to an hour and right now they are both entering hour 5 and still have not completed their backup, this is off peak times with no other backups running beside these two clients.
The only error I see from the details status on each is:
Error bpbrm (pid=7904) from client : ERR - Send bpfis state to CPASP-NBMSTR2 failed. status = 25
Sorry for not responding sooner.
Related Content
- 11 months ago
- 3 months ago
- 12 years ago
- 2 months ago