SQL backup failes with 41 error...

[Mindaugas_Lauci]

Hi,

I have few SQL backup jobs using NetBackup SQL Agent and once in a while some database's backups fail with 41 error:

1186285769 1 4 4 server 149294 0 0 server nbpem client server handling path /SERVER.MSSQL7.SERVER.db.DATABASE.~.7.001of004.20070804234730..C
1186285777 1 4 4 server 149294 149294 0 server nbjm starting backup job (jobid=149294)
1186285810 1 4 4 server 149294 149294 0 server bpdm begin writing backup id server_1186285777, copy 1, fragment 1, destination path e:\
1186286138 1 68 4 server 149294 0 0 server nbpem CLIENT server POLICY POLICY_NAME SCHED Default-Application-Backup EXIT STATUS 41 (network connection timed out)
1186286138 1 4 16 server 149294 0 0 server nbpem backup of client server exited with status 41 (network connection timed out)

Interesting thing that I have ~60 databases on this server and only some of them fail...

What could be wrong in my environment? Should I increase/decrease buffers or something?

Thanks

[Stumpr2]

try this

Use the registry editor to browse to this location. 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

2. Create the key KeepAliveTime

3. Then assign the key the type REG_DWORD

4. Then it assign it the Microsoft recommended value/data which is 300,000, but in hex; 0x000493E0 

After making the change, it is necessary to reboot the host to pick up the new value.

[sdo]

Is the client a SAN media server (i.e. save itself over the SAN), or is it a traditional client to a media server?

What is the CLIENT_READ_TIMEOUT value on your media server?

The default is 300 seconds (5 mins), but the Symantec/Veritas recommended value for clients using any database options is 900 seconds (i.e. 15 minutes).

[Stumpr2]

Interesting thing that I have ~60 databases on this server and only some of them fail...

Have you tried breaking out the databases that fail into their own batch file?

[N_4]

It works for me , with out reboot the host ..