Bart, You aren't hitting a read timeout on the backup image, are you (long seek time to the data etc)?
Tar log on the client, and bpbrm log on the master server... That line: 9/14/2011 8:23:15 AM - Info bpbrm(pid=17433) media manager for backup id client_1315796976 exited with status 150 In your detailed log generally indicates that bpbrm chose to terminate the session - and a couple of lines above that entry in the bpbrm log should be a pointer as to why it was terminated... Cheers, Nic -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of WALLEBROEK Bart Sent: 14 September 2011 08:18 To: [email protected] Subject: [Veritas-bu] strange socket write failed error during restore Hi Guys, We have since a while status 25 (socket write failed errors). We have a P1 case open with Symantec but they are as clueless as we are. Environment: 1 Solaris Master, 2 Solaris Media Servers (10Gbit connected), Data is backed up to DSSU, restores are coming from both tape and disk (same issue). We noticed that if we restore some data, we get this status code from time to time. When resuming the job (a couple of times) it eventually succeeds. So we believed it would be a network issue. BUT... When we try a restore towards the Media Server itself (having the tape drive connected directly to it, so network involved in the restore) then we get the same error. It even gets worse. Sometimes we get the status 24 even before there was a tape mounted (see log below). Anyone seen this before and knows a resolution ? Activity log: 9/14/2011 8:18:56 AM - begin Restore 9/14/2011 8:19:31 AM - 6 images required 9/14/2011 8:19:31 AM - media 010174 required 9/14/2011 8:19:31 AM - media 200424 required 9/14/2011 8:20:08 AM - restoring image client_1315796717 9/14/2011 8:20:10 AM - Info bpbrm(pid=17661) telling media manager to start restore on client 9/14/2011 8:20:11 AM - Info bpbrm(pid=17661) spawning a brm child process 9/14/2011 8:20:11 AM - Info bpbrm(pid=17661) child pid: 17668 9/14/2011 8:20:11 AM - connecting 9/14/2011 8:20:12 AM - Info bpbrm(pid=17668) start tar on client 9/14/2011 8:20:12 AM - restoring image client_1315796976 9/14/2011 8:20:12 AM - Info tar(pid=17452) Restore started. 9/14/2011 8:20:12 AM - connected; connect time: 00:00:01 9/14/2011 8:20:12 AM - requesting resource 010174 9/14/2011 8:20:12 AM - awaiting resource 010174 Reason: Drives are in use, Media Server: media_server_1, Robot Number: 1, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A 9/14/2011 8:20:14 AM - Info bpbrm(pid=17433) telling media manager to start restore on client 9/14/2011 8:20:14 AM - Info bpbrm(pid=17433) spawning a brm child process 9/14/2011 8:20:14 AM - Info bpbrm(pid=17433) child pid: 17457 9/14/2011 8:20:14 AM - connecting 9/14/2011 8:20:15 AM - Info bpbrm(pid=17457) start tar on client 9/14/2011 8:20:15 AM - Info tar(pid=17470) Restore started. 9/14/2011 8:20:15 AM - connected; connect time: 00:00:01 9/14/2011 8:20:15 AM - requesting resource 200424 9/14/2011 8:20:15 AM - awaiting resource 200424 Reason: Drives are in use, Media Server: media_server_2, Robot Number: 1, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A 9/14/2011 8:23:11 AM - Info bpbrm(pid=17661) killing bpbrm child 17668. 9/14/2011 8:23:11 AM - Info bpbrm(pid=17661) sending media manager msg: STOP RESTORE client_1315796717 9/14/2011 8:23:11 AM - Info bpbrm(pid=17433) killing bpbrm child 17457. 9/14/2011 8:23:11 AM - Info bpbrm(pid=17433) sending media manager msg: STOP RESTORE beotcd02_1315796976 9/14/2011 8:23:11 AM - Warning bprd(pid=15388) Restore must be resumed prior to first image expiration on Wed Dec 14 03:04:14 2011 9/14/2011 8:23:12 AM - end Restore; elapsed time: 00:04:16 socket write failed(24) 9/14/2011 8:23:14 AM - Error bptm(pid=17667) The following files/folders were not restored: 9/14/2011 8:23:14 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:14 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:14 AM - Error bptm(pid=17667) UTF -[removed] / 9/14/2011 8:23:15 AM - Info bpbrm(pid=17433) media manager for backup id client_1315796976 exited with status 150: termination requested by administrator 9/14/2011 8:23:15 AM - Info bpbrm(pid=17433) sending media manager msg: TERMINATE 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:16 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:16 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:16 AM - Error bptm(pid=17667) more than 10 files were not restored, remaining ones are shown in the progress log. 9/14/2011 8:23:16 AM - Info bpbrm(pid=17661) media manager for backup id client_1315796717 exited with status 150: termination requested by administrator 9/14/2011 8:23:17 AM - Info bpbrm(pid=17661) sending media manager msg: TERMINATE Best Regards, Bart WALLEBROEK Backup Admin & Systems & Applications Management & Support Specialist Enterprise Applications Delivery - Infrastructure Management S.W.I.F.T. SCRL -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, September 13, 2011 7:00 PM To: [email protected] Subject: Veritas-bu Digest, Vol 65, Issue 12 Send Veritas-bu mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Veritas-bu digest..." Today's Topics: 1. LTO-5 Question (Justin Piszcz) 2. Re: LTO-5 Question (Patrick) ---------------------------------------------------------------------- Message: 1 Date: Tue, 13 Sep 2011 06:52:22 -0400 (EDT) From: Justin Piszcz <[email protected]> Subject: [Veritas-bu] LTO-5 Question To: veritas-bu <[email protected]> Message-ID: <[email protected]> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Hello all, LTO-1 = hcart LTO-2 = hcart2 LTO-3 = hcart3 LTO-4 = hcart What does LTO-5 show up as in NetBackup? Justin. ------------------------------ Message: 2 Date: Tue, 13 Sep 2011 13:33:22 +0200 From: "Patrick" <[email protected]> Subject: Re: [Veritas-bu] LTO-5 Question To: "'Justin Piszcz'" <[email protected]>, "'veritas-bu'" <[email protected]> Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAAuNdNEqAcBDlHAMs3V1J1KCgQAAEAAAAF3cYLCbW1pAlHW+q5lxUS4BAAAAAA==@whelan-consulting.co.uk> Content-Type: text/plain; charset="iso-8859-1" Whichever one you would like it to be, as long as you don't have one defined for other tape drives. HCART[x] is just a name. Regards, ? Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Justin Piszcz Sent: 13 September 2011 12:52 To: veritas-bu Subject: [Veritas-bu] LTO-5 Question Hello all, LTO-1 = hcart LTO-2 = hcart2 LTO-3 = hcart3 LTO-4 = hcart What does LTO-5 show up as in NetBackup? Justin. _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ------------------------------ _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu End of Veritas-bu Digest, Vol 65, Issue 12 ****************************************** _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu The information contained in this e-mail and its attachments is confidential. It is intended only for the named address(es) and may not be disclosed to anyone else without Attenda's consent. _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
