Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.
Backup and Recovery Community Blog

Network Connection Timed Out(41)

Created: 04 Sep 2009 • Updated: 04 Sep 2009 • 1 comment
Zahid.Haseeb's picture
0 0 Votes
Login to vote

Today we discuss in this BLOG "Network Connection Timed Out(41)" in the Activity Monitor of Veritas Netbackup Server with the restore failed to recover the requested files(5)
In our case we have a environment of :

  • Windows2003 server
  • Veritas Netbackup 6.5.
  • MS SQL Server 2005

In this BLOG we will discuss:

  • Error which i have found
  • Resolution

Error which i have found

9/3/2009 2:09:05 PM - media 0010L4 required
9/3/2009 2:09:08 PM - restoring image dbserver-sec_1251836312
9/3/2009 2:09:16 PM - started process bptm (4200)
9/3/2009 2:09:16 PM - mounting 0010L4
9/3/2009 2:09:14 PM - requesting resource 0010L4
9/3/2009 2:09:14 PM - granted resource 0010L4
9/3/2009 2:09:14 PM - granted resource IBM.HHLTOGEN4.000
9/3/2009 2:09:20 PM - mounted; mount time: 00:00:04
9/3/2009 2:09:22 PM - positioning 0010L4 to file 82
9/3/2009 2:09:25 PM - connected
9/3/2009 2:10:14 PM - positioned 0010L4; position time: 00:00:52
9/3/2009 2:10:14 PM - begin reading
9/3/2009 2:17:56 PM - Error bptm(pid=5516) The following files/folders were not restored:      
9/3/2009 2:17:56 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:56 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:56 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:56 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:57 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:57 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:57 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:57 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:57 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:57 PM - Error bptm(pid=5516) UTF - /server.MSSQL7.APP-CLUSTER.db.App-Dotnet.~.7.001of001.20090902011720..C         
9/3/2009 2:17:57 PM - Error bptm(pid=5516) more than 10 files were not restored, remaining ones are shown in the progress log.
9/3/2009 2:17:58 PM - restored image server_1251836312 - (network connection timed out(41)); restore time 00:08:50
9/3/2009 2:18:06 PM - end Restore; elapsed time: 00:09:08
the restore failed to recover the requested files(5)

 

Resolution

Actually my database of MS SQL Server which i was trying to restore has a size of around 150GB and the default timout value of "Client read timeout" and "File browse timeout" value is 300 seconds thats why i had been face the above mentioned error so i just increase the value of timeout from Veritas Netbackup Server admin Console-->Host properties-->Master Server--> and then at the right pane double click on your Master Server --> Timeouts--> here you increase the value of "Client read timeout" and "File browse timeout" as shown in the below snapshot

imagebrowser image

 

Comments 1 CommentJump to latest comment

WY-Thinker's picture

Thanks for you post I used it to confirm what I'd read elsewhere and did similar to resolve my issue. I had already established the backup took time to restore. I had the luxury of a recent SQL backup to attempt a restore with too. When I did this SQL restore it progressed as normal and then sat for several minutes before finishing. As a result I too extended the timeouts but, as per the support document I had found, as this was a DB Agent restore I did this on the Client Hosts settings not the master. This worked fine the restore progressed to 93% restored and sat for a long time as before but on this occasion it finished and the restore showed as complete. where as before I had been having the long wait and then getting the error as above.   
N.B. I only set the tile out to 900 (15 Minutes) as I didn't fancy sitting for several hours for it to timeout if the problem was elsewhere.

Life; Don't talk to me about life

+3
Login to vote