Re: [Veritas-bu] bpstart timeout not honoured
Hi dave, Hope you found the answer, but if not, my best guess would be the global setting 'backup start notify timeout' setting on the Admin Console > Netbackup Management > Host properties > master server properties > timeout. Is this overriding the other timeout setting in bp.conf? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Markham Sent: Thursday, August 28, 2008 4:01 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] bpstart timeout not honoured Guys i have a bpstart script on a client which initiates an RMAN backup (i just emailed about it 2 mins ago for a different reason). As the RMAN backup takes some time i have put the following into bp.conf on the client that initiates the bpstart CLIENT_READ_TIMEOUT = 24000 BPSTART_TIMEOUT = 2400 After some investigation it seems a job has exited with status 74 after 11000 seconds saying bpstart failed to complete. It then causes the script to run again as i have retries per 12 hours set to 2. Anyone any idea why the time out is not being honoured for the client? Cheers Dave ___ 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
Re: [Veritas-bu] bpstart timeout not honoured
Hi For netbackup RMAN backups we also set CLIENT_CONNECT_TIMEOUT Regards Michael 2008/8/28, Dave Markham <[EMAIL PROTECTED]>: > > Guys i have a bpstart script on a client which initiates an RMAN backup > (i just emailed about it 2 mins ago for a different reason). > > As the RMAN backup takes some time i have put the following into bp.conf > on the client that initiates the bpstart > > CLIENT_READ_TIMEOUT = 24000 > BPSTART_TIMEOUT = 2400 > > After some investigation it seems a job has exited with status 74 after > 11000 seconds saying bpstart failed to complete. It then causes the > script to run again as i have retries per 12 hours set to 2. > > Anyone any idea why the time out is not being honoured for the client? > > Cheers > Dave > ___ > 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
Re: [Veritas-bu] bpstart timeout not honoured
Dave, Looks like you have a typo below, but that's not important. What is is that regardless of what the bpstart timeout is set to on the client, it has to be set to the same or greater on the master server...if master server timeout is less than client, master will get honored before the client. You also need to have it set the same or greater on the media server. Ken Zufall Technical Analyst D660C The Goodyear Tire & Rubber Company Dave Markham <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 08/28/2008 07:00 AM Please respond to [EMAIL PROTECTED] To "veritas-bu@mailman.eng.auburn.edu" cc Subject [Veritas-bu] bpstart timeout not honoured Guys i have a bpstart script on a client which initiates an RMAN backup (i just emailed about it 2 mins ago for a different reason). As the RMAN backup takes some time i have put the following into bp.conf on the client that initiates the bpstart CLIENT_READ_TIMEOUT = 24000 BPSTART_TIMEOUT = 2400 After some investigation it seems a job has exited with status 74 after 11000 seconds saying bpstart failed to complete. It then causes the script to run again as i have retries per 12 hours set to 2. Anyone any idea why the time out is not being honoured for the client? Cheers Dave ___ 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