03-04-2014 03:17 AM
Hi Friends
Receiving Status Code 24 is now becaming very common in our Infrastructure, where we are backing up alomost 7000 boxes using 10 different master servers. I agree there is a Technote Available from Symantec : http://www.symantec.com/business/support/index?page=content&id=HOWTO50801 for troubleshooting Status Code 24 Failures, but most of the time we are getting the situation where this is not enough to fix the issues.
Can someone please help me to understand that what are the parameters need to be checked in Client / Media / Master server and the tuning can be made to fix the issue. Also is there any tool is avaiable to determine the root cause of the Status 24 Failure.
Help would be highly appriciated
Solved! Go to Solution.
03-04-2014 05:39 AM
NIcolai and Marianne are right - timeouts can work around issues sometimes, but the root cause is almost always outside NBU for status 24.
Generally, if you try and solve status 24 inside NBU, you are likely to never fix it, it is rare that NBU is the cause of a 24 (not impossible, but very very unlikely).
These are the notes i sent out a while back for a status 24. As you will see, all the TNs and case examples I gave are outside NBU. I personally have never seen 24 caused by NBU, but have heard about the odd issue, hence my comment, it's possible but unlikely.
***************
03-04-2014 03:34 AM
There can be a ton of reason for this error code. And I don't think one setting will fix them all.
One setting I however want you to check is CLIENT_READ_TIMEOUT. If not configured - set it to 1800 (½ hour) on master/media and clients. Try it out on frequent failures and see if it makes any difference.
http://www.symantec.com/docs/HOWTO86358
03-04-2014 04:44 AM
Status 24 is normally caused by issues outside of NBU.
So, to try and solve from NBU is basically impossible.
Best you can do is to understand the process flow and to understand where the failure is occuring:
On the client side
On the media server
On the master server
Then start working with that server owner to determine if this is OS/NIC/network issue...
03-04-2014 05:39 AM
NIcolai and Marianne are right - timeouts can work around issues sometimes, but the root cause is almost always outside NBU for status 24.
Generally, if you try and solve status 24 inside NBU, you are likely to never fix it, it is rare that NBU is the cause of a 24 (not impossible, but very very unlikely).
These are the notes i sent out a while back for a status 24. As you will see, all the TNs and case examples I gave are outside NBU. I personally have never seen 24 caused by NBU, but have heard about the odd issue, hence my comment, it's possible but unlikely.
***************
03-04-2014 06:11 AM
Deb, log a call with Symantec and ask them to the send you the appcritical tool. This will check the network between a destination host and target and tell you if any network issues are seen on your network.
03-04-2014 08:49 AM
@revaroo: Will do that surely. Thanks for the Information
03-04-2014 08:50 AM
03-04-2014 12:50 PM
You are welcome - apologies, the post is cop/ paste from my 'personal' notes so some may not apply to you. It really was meant as a demonstartion from Mariannes post that 24 can be more or less anything.
NetBackup has very little control over the network, it sits above the network and pretty much uses what is avalable, it there are issues, you start to see network related error codes.
Revaroo makes a good point (as always) - AppCritical will evaluate the network and will highlight anything it finds - on average, I would say it's results are very accurate, I've never persoanally seen it be 'wrong' in about 6 years of using it.
I believe ther eis a free version of a tool similar to AppCritical that has good reviews, if I can find out what it is I'll let you know. Saw it mentioned somewhere ages ago, but foolishly didn't make a note of what it was.