Veritas-bu

[Veritas-bu] Yet another bpstart/bpend script question

2007-01-19 13:27:05
Subject: [Veritas-bu] Yet another bpstart/bpend script question
From: pkeating at bank-banque-canada.ca (Paul Keating)
Date: Fri, 19 Jan 2007 13:27:05 -0500
Correct.....and should a stream fail and restart,  it creates a new lock
file so everything's cool, as long as the end script doesn't run and
somepoint before that stream restarts.....and the chances of that are
low.

Paul

-- 


> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu 
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf 
> Of Ellis, Jason
> Sent: January 19, 2007 11:49 AM
> To: Ed Wilts
> Cc: veritas-bu at mailman.eng.auburn.edu
> Subject: Re: [Veritas-bu] Yet another bpstart/bpend script question
> 
> 
> Actually I plan to create .lock files for each stream as they call the
> bpstart_notify script. For example:
> 
> Stream 1 starts and creates the stream_1.lock file.
> 
> Stream 2 starts and creates the stream_2.lock file.
> 
> Stream 3 starts and creates the stream_3.lock file.
> 
> Later:
> 
> Stream 2 completes and deletes its .lock file, but the bpend_notify
> script still finds the .lock file for stream 1 and 3.
> 
> Stream 1 completes and deletes its .lock file, but the bpend_notify
> script still finds the .lock file for stream 3.
> 
> Finally stream 3 completes and deletes its .lock file. The 
> bpend_notify
> script, not finding any more .lock files, runs the final tasks and
> completes.
> 
> In theory this should work.
> 
> Jason Ellis
> Technical Consultant, Data Protection Team
> IndyMac Bank, La Mirada Datacenter
> Phone: (714) 520-3414
> Mobile: (714) 889-8734
> 
> -----Original Message-----
> From: Ed Wilts [mailto:ewilts at ewilts.org] 
> Sent: Thursday, January 18, 2007 7:42 PM
> To: Ellis, Jason
> Cc: veritas-bu at mailman.eng.auburn.edu
> Subject: Re: [Veritas-bu] Yet another bpstart/bpend script question
> 
> On 1/18/2007 6:25 PM, Ellis, Jason wrote:
> > I really need to capture the STREAM_NUMBER if possible to help
> mitigate 
> > a job with multiple data streams. My idea is to use lock files to 
> > prevent the bpstart_notify from running once one stream has already 
> > started, and the bpend_notify script from kicking off until 
> the last 
> > stream has completed.
> 
> This is a lost cause so save yourself some work.  There is no 
> guarantee 
> that the last stream won't complete before an earlier stream 
> and unless 
> you disallow retries completely, the task gets harder and harders.
> 
> What are you going to do if stream 1 starts, gets partially 
> done, has a 
> tape error, and retries?  What are you going to do if the last stream 
> finishes early?  What are you going to do if the last stream dies 
> completely and can't finish?
> 
> The problem is much harder than it looks...
> 
>       .../Ed
> 
> -- 
> Ed Wilts, Mounds View, MN, USA
> mailto:ewilts at ewilts.org
> 
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
====================================================================================

La version fran?aise suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le pr?sent courriel peut contenir de l'information privil?gi?e ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires d?sign?s est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer imm?diatement et envoyer sans 
d?lai ?
l'exp?diteur un message ?lectronique pour l'aviser que vous avez ?limin? de 
votre
ordinateur toute copie du courriel re?u.