Hi Rusty, I have been trying a similar approach using the exclude lists. I haven't been able to gather enough data to say for certain that a specific group of files is causing the problem. There doesn't seem to be a specific file causing the issue.
-- Jim Canon Sr. Data Protection Analyst Global Technology Services - AHS Mylan 781 Chestnut Ridge Road Morgantown, WV 26505 jim.ca...@mylan.com Phone: 800.826.9526 ext. 6236 Direct: 304.554.6236 Fax: 304.285.6404 Mobile: 304.224.6815 From: rusty.ma...@sungard.com To: jim.ca...@mylan.com Cc: veritas-bu@mailman.eng.auburn.edu, veritas-bu-boun...@mailman.eng.auburn.edu Date: 05/06/2011 04:04 PM Subject: Re: [Veritas-bu] NetBackup 7.1 media server backup issue Sent by: veritas-bu-boun...@mailman.eng.auburn.edu When we've encountered these issues and the logs were no help, we had to narrow down the problem by creating multiple backups or streams. This approach allowed us to narrow down the culprit by eventually closing in on a bad file during the backup. Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693 Keeping People and Information Connected® ▪ http://availability.sungard.com/ P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. <jim.ca...@mylan.com> Sent by: <veritas-bu-boun...@mailman.eng.a uburn.edu> To Girish Jorapurkar <giris...@yahoo.com> 05/06/2011 10:41 AM cc <veritas...@mailman.eng.aubur n.edu> Subject Re: [Veritas-bu] NetBackup 7.1 media server backup issue Girish, A file read error is what it appears, however (bpbkar -nocont / > /dev/null) completes with status 0. Here is where it gets strange. I've also tried creating a storage unit that uses /dev/null as it's basic disk pool. I've then set the backup policy to use this storage unit. This backup fails with the same error as if I use a storage unit and disk pool pointing to our data domain. Thanks, -- Jim Canon Sr. Data Protection Analyst Global Technology Services - AHS Mylan 781 Chestnut Ridge Road Morgantown, WV 26505 jim.ca...@mylan.com Phone: 800.826.9526 ext. 6236 Direct: 304.554.6236 Fax: 304.285.6404 Mobile: 304.224.6815 From: "Girish Jorapurkar" <giris...@yahoo.com> To: veritas-bu@mailman.eng.auburn.edu, jim.ca...@mylan.com Date: 05/05/2011 10:01 PM Subject: Re: [Veritas-bu] NetBackup 7.1 media server backup issue Sent by: veritas-bu-boun...@mailman.eng.auburn.edu If I am understanding it correctly, an error occurred while reading a file. > 05/05/2011 09:52:27 - Info bpbkar (pid=9437276) done. > status: 13: file read failed That is strange. See if there is any storage (volume manager or disk I/O) related error/fault reported at the time of bpbkar failure. Also, you can try bpbkar null test - just to ensure that data can be read without any random read failures: bpbkar -nocont <failed_to_backup_path> > /dev/null Hope that helps, /Girish --- On Fri, 5/6/11, jim.ca...@mylan.com <jim.ca...@mylan.com> wrote: > From: jim.ca...@mylan.com <jim.ca...@mylan.com> > Subject: [Veritas-bu] NetBackup 7.1 media server backup issue > To: veritas-bu@mailman.eng.auburn.edu > Date: Friday, May 6, 2011, 6:45 AM > > Hi All, > > We're having a strange problem when the media server (AIX > 6.1) is backing > up itself. This problem only occurs when the media server > attempts to back > up itself. The media server can back up other clients just > fine. Other > media servers can back up this media server just fine. > > Here is the general output of the backup: > > 05/05/2011 09:37:01 - begin writing > 05/05/2011 09:52:16 - Error bpbrm (pid=7405600) socket read > failed: errno = > 119 - System call timed out > 05/05/2011 09:52:18 - Error bptm (pid=8912950) media > manager terminated by > parent process > 05/05/2011 09:52:27 - Info bpbkar (pid=9437276) done. > status: 13: file read > failed > > This isn't necessarily helpful, so I've enabled verbose > logging level 5 on > both bpbkar and bpbrm. I'm not seeing any red flags. > > I have tried disabling shared memory, reducing the buffers > to bare > minimums, excluding what I thought were problem files, but > it seems we are > chasing a ghost. It is as if bpbkar stops sending data. The > backup runs for > a while, stops on a random file, and sits there until the > job times out. > > Any ideas? > > -- > Jim Canon > Sr. Data Protection Analyst > Global Technology Services - AHS > Mylan > 781 Chestnut Ridge Road > Morgantown, WV 26505 > > jim.ca...@mylan.com > > Phone: 800.826.9526 ext. 6236 > Direct: 304.554.6236 > Fax: 304.285.6404 > Mobile: 304.224.6815 > > > ============================================================================== > CONFIDENTIALITY NOTICE: This e-mail message and all > attachments transmitted with it may contain legally > privileged, proprietary and/or confidential information > intended solely for the use of the addressee. If you > are not the intended recipient, you are hereby notified that > any review, dissemination, distribution, duplication or > other use of this message and/or its attachments is strictly > prohibited. If you are not the intended recipient, > please contact the sender by reply e-mail and destroy all > copies of the original message and its attachments. > Thank you. > ============================================================================== > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ============================================================================== CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you. ============================================================================== _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ============================================================================== CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you. ============================================================================== _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu