Could be. Informix was on the Media Server. And like I said its a while ago. I just remember doing a lot of things to ~/bp.conf
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Thursday, July 31, 2008 11:14 AM To: Jim Horalek; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Informix Backup failing with Error 13 Um... CLIENT_READ_TIMEOUT is a media-server-specific setting, so it can't live in ~/bp.conf, even for user-directed backups. (The media server's bptm will still give up waiting for data from the client's bpcd before bpbkar has even spooled up to send anything.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery [EMAIL PROTECTED], 215 231 1556 _____ From: Jim Horalek [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 12:33 PM To: Rosenkoetter, Gabriel; 'Neeraj Puri (DHL MY)'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Informix Backup failing with Error 13 Been a long time since I've done Informix but CLIENT_READ_TIMEOUT? needs to be large 1/2 hour to 1hour. Same issues with Oracle. The time to get the database ready to start sending data can be significant. I believe the timeout values can be assocated with the User Account the backup is driven from. Look for a ~/bp.conf on the client. All user jobs (Database) look at ~/bp.conf before the netbackup/bp.conf Jim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Thursday, July 31, 2008 9:09 AM To: Neeraj Puri (DHL MY); veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Informix Backup failing with Error 13 Hrm... Come to think of it, even if you don't have a big honking bpstart_notify script in place, I distantly recall something about Informix and BPSTART_TIMEOUT. You might want to do a bpgetconfig | grep TIMEOUT and google all of those settings for relevancy: I always have to go dig around on which is the appropriate setting for a given timeout issue anew. It's odd that the behavior would be different between the media server running local to the client and remote: you may want to check that your SysV IPC values are tuned sufficiently (because the issue may be timing out waiting for message queue or shared memory slots to become available). My old standard, http://seer.support.veritas.com/docs/243461.htm, says that the 6.x "Backup Planning and Performance Tuning Guide for [blah blah blah]" includes updated version of everything that's there, so dig through your PDFs for that. -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery [EMAIL PROTECTED], 215 231 1556 _____ From: Neeraj Puri (DHL MY) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 10:13 AM To: Rosenkoetter, Gabriel; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Informix Backup failing with Error 13 Dear Gabriel, Thanks for your quick reply. The funny thing is that the other media server through which it is going fine is also installed today and doesn't have any CLIENT_READ_TIMEOUT. The values are all default. Another funny thing is that the media server through which the Informix backup is going fine is giving the same error 13 for its own Informix backup. This server's Informix backup is going fine through first media server's storage-unit. So, basically I installed 3 NBU6.5.1 media servers. All of them are not able to take their own Informix backups but are able to take each other's backup. All these media servers have default CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT. I think I will follow your advise and try to change the CLIENT_READ_TIMEOUT and try a backup. Previously, all these had NBU 4.5 media server software installed and had increased TIMEOUT values. Secondly, thanks for your observation about barcodes. Actually the bar code is 8 characters but media ID is generated using last 6 characters. I don't have a MEDIA_ID_BARCODE_CHARS setting in vm.conf. I will read the technote to understand its benefits. Regards, Neeraj _____ From: Rosenkoetter, Gabriel [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 9:49 PM To: Neeraj Puri (DHL MY); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Informix Backup failing with Error 13 Looks like you need to raise CLIENT_READ_TIMEOUT (and maybe, but probably not, CLIENT_CONNECT_TIMEOUT; don't try that unless only READ isn't enough) on the media server trying to write its own Informix backups. (I presume you had, long ago, raised this value on the other media server for a similar problem.) The circumstance in which you'd need to bump CONNECT_TIMEOUT too is f you've got a lengthy backup_start_notify in place (to, say, put Informix in backup mode or something like that). As an aside, that's a pretty kooky volser. It looks like you're using LTO-2 media and your robotic device is passing all 8 characters through to NetBackup (not all can be configured not to) and you don't have a MEDIA_ID_BARCODE_CHARS setting in vm.conf, but you probably want one, although addding one now may be a bit touchy, since you've already inventoried a bunch of tapes with the traily L2, and you'll need to blow the media and vol DB entries for those away and recreat them, which will definitely be a mess. (Cf, http://seer.support.veritas.com/docs/236271.htm.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery [EMAIL PROTECTED], 215 231 1556 _____ From: Neeraj Puri (DHL MY) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 9:04 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Informix Backup failing with Error 13 Dear All, I installed a NBU 6.5.1 media server on a HP-UX box. The File System backup of this box on its own storage-unit works fine whereas the Informix backup fails with Error 13. Here is the screen of shot of the exact error. 07/31/2008 19:54:21 - started process bpbrm (pid=1068) 07/31/2008 19:54:29 - connecting 07/31/2008 19:54:36 - connected; connect time: 0:00:00 07/31/2008 19:54:43 - mounting 0148L2 07/31/2008 19:55:38 - mounted 0148L2; mount time: 0:00:55 07/31/2008 19:55:38 - positioning 0148L2 to file 1 07/31/2008 19:55:45 - positioned 0148L2; position time: 0:00:07 07/31/2008 19:55:45 - begin writing 07/31/2008 19:58:35 - Error bpbrm (pid=1762) socket read failed: errno = 52 - Stream ioctl timeout 07/31/2008 20:00:58 - end writing; write time: 0:05:13 file read failed (13) If the same Informix backup is sent through another media server, it works fine. Please advise if you faced similar problem or know the reason for this failure. Regards, Neeraj
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
