Status 41: network connection timed out

[NavinB]

Hi All,

I am new to Veritas Netbackup.I am facing this unusual problem.I have a Win NT Client coming under two policies.Bkp in one policy(of SQL database) is successfully completing but in other policy(bkp of drives) it is giving me n/w error (this policy I had added few weeks ago only.)Veritas Server is ver 4.5 FP6 .
I have tried restarting netbkp service on the client but still prob remains.
Any help would be greatly appreciated.

Thanks,
Navin

 

[creakyjoe]

status 41 is one of the irritating ones, but there is a very good bit of info the troubleshooting manual for this one. See how you get on and report back. good luck.

Richard

 

[NavinB]

Hi There,

I have read the troubleshoot manual...and tried every option but I am not able to solve it.
So guys I need some help...

Cheers,
Navin

 

[24carat]

Error 41 is usually a network issue

Check the port speeds and duplex of the network card of the server. It must be set to 100/Full minimum not to auto negotiate. Also check the port and duplex speed of the switch It must also be set to 100/Full minimum not to auto negotiate.

Check the DNS/Host entries

Change cables if necessary.

 

[NavinB]

The port speeds are already set to 100/Full and switch is also the same.....so any more options ????

 

[creakyjoe]

without more to go on i can't think of anything else other than dns & host entries, but 24carat suggested that already. there should be sone clues in the logfiles, sorry can't think which ones, it's erm years since i hit status 41s

Rich

 

[Stumpr]

Navin,
Intermittent 41 errors is a very hard problem to troubleshoot and it will require reading log entries. This is both a blessing and a curse. The curse is obvious but the blessing is that you are about to embark on a journey that provides enlightenment and understanding of how NetBackup actually works.
This is because the 41 error is a timeout error YES, but it ia also very generic in nature. Its a timeout but, you will have to discover what is causing the timeout. Sometimes it is a busy system trying to backup an active file.I would start with disabling VSP and seeing if that will allow the backup to partially complete and see what disk and then what files may be the culprit.
Perhaps this explanation provides insight as to why the answers so far have been so vague. I wish you well.

Bob Stump
Just because the Veritas documentation states a certain thing does not make it a fact

 

[NavinB]

I don't think there is prob with DNS as the SQL backup is going on fine.....and hosts file also has the correct entry...but one thing I found out...we have 2 n/ws on the client....one for normal and other for bkp...however bkp n/w entry is not there on server's host file..and this is the case with other clients also which have SQL databse on them(is it becoz of SQL database bkp...???)....
Any help would be greatly appreciated...

 

[creakyjoe]

cheers Bob, as ever, better put than i could have explained, i'm afraid i' never get detailed enough due to my goldfish memory

Rich

 

[NavinB]

VSP has already been diaabled...and file browse timeout is set to 0 secs and client read timeout to 144000 secs...
Pls help.....

 

[NavinB]

Hi,
Regd the two n/w cards...The public n/w is used by master server and the bkup n/w is used by media server....and both r able to ping the client...Is there any other method to check for client connection...??

 

[creakyjoe]

pls see comments on

http://www.tek-tips.com/viewthread.cfm?qid=1029336&page=1

Rich

 

[1781]

PLEASE SEE MY COMMENTS:
1. Go to the Administrator console
2. Select a the host properties tab.
3. Select the Client properties.
4. Select the Universal Settings tab
4. Up the Client Read Timeout to 144000.

This should correct your problem