Statuscode 41 after a long time of backup !

[Holger_Luebbers]

Hi !

A scheduled backup needs more than 12 hours to go, and near the end ...

------------------------------------------------------------------------------------------------------------

07.11.2006 22:40:46 - connecting
07.11.2006 22:40:46 - mounting BIG118
07.11.2006 22:40:46 - positioning BIG118 to file 32
07.11.2006 22:40:46 - positioned BIG118; position time: 00:00:00
07.11.2006 22:40:46 - begin writing
07.11.2006 22:40:46 - connected; connect time: 00:00:00
07.11.2006 22:43:10 - Warning bpbrm(pid=922) from client SERVER123: WRN - Removable Storage Management: unable to export database (WIN32 21: Das Ger�t ist nicht bereit. )
08.11.2006 02:58:44 - mounting BIG117
08.11.2006 02:59:32 - mounted; mount time: 00:00:48
08.11.2006 02:59:38 - positioning BIG117 to file 1
08.11.2006 02:59:52 - positioned BIG117; position time: 00:00:14
08.11.2006 08:27:49 - mounting BIG068
08.11.2006 08:28:37 - mounted; mount time: 00:00:48
08.11.2006 08:28:43 - positioning BIG068 to file 1
08.11.2006 08:28:56 - positioned BIG068; position time: 00:00:13
08.11.2006 11:16:51 - end writing; write time: 12:36:05
network connection timed out(41)
08.11.2006 11:16:51 - Error bpsched(pid=24598) backup of client SERVER123 exited with status 41 (network connection timed out)
network connection timed out(41)
08.11.2006 11:16:51 - Error bpsched(pid=24598) backup of client SERVER123 exited with status 41 (network connection timed out)

Current kilobytes written : 54948480
Current files written : 275000

Percent 100% complete 0 miniutes remaining

------------------------------------------------------------------------------------------------------------------------

WHY ???

and

What does this mean -->
Warning bpbrm(pid=922) from client SERVER123: WRN - Removable Storage Management: unable to export database (WIN32 21: Das Ger�t ist nicht bereit. )

Hope anyone can help !

Greets and thanks

Holger

[zippy]

Holger,

What kind of backup is this?

Check the LAN on each server.
Check the switches and routers that touch each server
make sure the NIC cards and Switches are all set the same 10/100/1000 full duplex and not set to auto.
Put a Sniffer between the two servers.

JD

[Dennis_Strom]

can you communicate between the licnt and the server?
Verify the Client is communicating properly:

* bpclncmd -ip --> from both client and server
* bpclntcmd -hn --> from both client and server
* bpclntcmd -pn --> from client only

you can also run bpcoverage -c clientnameto verify connectivity.

run nslookup clientname and nslookup IP adress to verify dns is working.

Make sure the media servers name is in the client bp.conf SERVER = mediaservername

telnet to client to verify netbackup client telnet clientname bpcd

You can also ftp a large file from the client to the media server to verify connectivity and speed.

[Dennis_Strom]

http://support.veritas.com/docs/277695

In-depth Troubleshooting Guide for Exit Status Code 41 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 5.0 / 5.1

http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/277695.pdf
status 41 flow chart

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

also check network speed and whether or not the ports are running full or half duplex. On Solaris
determin nic speed and duplex ( you may hae to use ge or what ever if you are using an interface other than hme)
# ndd -get /dev/hme link_mode
Interpretation:
0 -- half-duplex
1 -- full-duplex

# ndd -get /dev/hme link_speed
Interpretation:
0 -- 10 Mbit
1 -- 100 Mbit
1000 -- 1 GbiMessage was edited by:
Dennis Strom

[Hugo_Almeida_2]

What is the version of Netbackup both on server and client?

[Holger_Luebbers]

Hi !

Thanks for your answers .

Any completions :

BackupServer =

Sun Solaris 8 , NetBackup 5.1 MP3

Client =
Windows Server 2003 Standard Edition with SP1

The backup job is a "normal" shedulded job from backupserver, with two clients in this policy, the other client work fine, the system is nearly the same.

The Clients are in a windowsdomain.

I have made all the troubleshooting procedures, except for the logging on client and server.

Must I ??

Greets
Holger

[Stumpr2]

> Client = Windows Server 2003

Defrag........