[Veritas-bu] **** Assistance Plz ;-) *****

About the only thing I can think of is setting your global settings in
terms of how many tries within a 12 window. Have a cronned script that
looks at the bpdbjobs table and uses bpdbjobs -kill <job_id> to take
care of your problem. I am thinking of a UNIX master.

Bill 

----------------------------------
   Bill Jorgensen
   CSG Systems, Inc.
   (w) 303.200.3282
   (p) 303.947.9733
----------------------------------

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Charles
Ballowe
Sent: Tuesday, September 20, 2005 10:57 AM
To: Ray.Hill AT ny.frb DOT org
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] **** Assistance Plz ;-) *****

What do you mean "against its time frame" - the windows in netbackup are
not the window where the backup must complete, but the window where the
backup must start. I would suggest that, If you have a certain set of
jobs that MUST finish by a time, that you make their window only extend
to that time minus the amount of time you expect the job to run. I.e. if
the job takes 3 hours to complete, and the service must be up by 6AM,
consider having the start window only extend until 2 or 3 AM to give
room for those days when it runs a little long.

If you must set up something to kill jobs, consider having a script run
from cron at each of the time frames when you have systems that need to
end and services start. Checking against the start window would be very
ugly.

-Charlie

On 9/20/05, Ray.Hill AT ny.frb DOT org <Ray.Hill AT ny.frb DOT org> wrote:
>  
> I tested your sultion thats good and I run it from the master, so its
central., but how do I check a specific job againist its time frame. 
> 
>  Ray H.
>  ext 8527
>   
>  
>  
>   
>  "Tschida, Tom (C)(STP)" <tom.tschida AT guidant DOT com>
> 
> 09/20/2005 10:31 AM   
>   
> To <Ray.Hill AT ny.frb DOT org>, <veritas-bu-admin AT mailman.eng.auburn DOT 
> edu>, 
> <veritas-bu AT mailman.eng.auburn DOT edu>
>   
> cc
> 
>   
> Subject RE: [Veritas-bu] **** Assistance Plz ;-)   ***** 
>   
>   
> 
>  
> 
>  
>  
>  
> I've used crons that basically run "bpdbjobs -report | grep -i active
| grep policyname" .  Then you can run "bpdbjobs -kill" and kill the
particular job.   
>   
> Tom Tschida
> Guidant Corp. 
>  
>  ________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
Ray.Hill AT ny.frb DOT org
>  Sent: Tuesday, September 20, 2005 9:03 AM
>  To: veritas-bu-admin AT mailman.eng.auburn DOT edu; 
> veritas-bu AT mailman.eng.auburn DOT edu
>  Subject: [Veritas-bu] **** Assistance Plz ;-) *****
>   
> 
>  __________________
>  
>  
>  
>  I have a master/media server; Solaris 2.8 64 bit running  NBU 5.1
MP2. 
>  
>  Does anyone have any script(s) or a place where I can obtain any
script(s) which will do the following: 
>  
>  (1) Monitor if a backup job has not completed its backup within its
scheduled amount of time (start window)  and...... 
>  (2) If it has not cancel it. 
>  
>  I've spoken to Veritas...oops... Symantec and this feature is not yet
there. 
>  
>  One of many reason you would want something like this is if at the
end of your backup process you will be executing a bpend_notify  which,
starts up a process that must be active by a specific time. 
>  
>  Thanks in advance for any and all suggestions and solutions. 
>  
>  
>  Ray H. 
>  ext 8527
>    
>

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu