[Veritas-bu] Overnight scheduling quirk

[W. Curtis Preston]

I'll be curious to see how that changes things, since calendar-based
scheduling is really frequency based scheduling underneath.   It still
sets a frequency variable in the info file.

> -----Original Message-----
> From: Gardner, Jesse [mailto:Jesse.Gardner at storaenso.com] 
> Sent: Tuesday, September 24, 2002 10:48 AM
> To: 'larry.kingery at veritas.com'; W. Curtis Preston
> Cc: Gardner, Jesse; veritas-bu at mailman.eng.auburn.edu
> Subject: RE: [Veritas-bu] Overnight scheduling quirk
> 
> 
> I am using calendar-based scheduling.  One of the first 
> people to reply suggested to use frequency-based with a 
> 12-hour frequency.  I made the change, and we'll see how it 
> goes tonight.
> 
> My scheduler wake-up time is the default 8 minutes.
> 
> Jesse
> 
> -----Original Message-----
> From: Larry Kingery [mailto:larry.kingery at veritas.com] 
> Sent: Tuesday, September 24, 2002 12:39 PM
> To: W. Curtis Preston
> Cc: 'Gardner, Jesse'; veritas-bu at mailman.eng.auburn.edu
> Subject: RE: [Veritas-bu] Overnight scheduling quirk
> 
> W. Curtis Preston writes:
> > This is a very common FAQ, and we should put it in the FAQ.
> > 
> > NetBackup checks the interval against the amount of time since the 
> > COMPLETION time of the last backup.  Therefore, a backup (with a 24 
> > hour
> > frequency) that doesn't finish until 5 AM will not start 
> until 24 hours
> > after 5 AM, if the window is open.
> 
> This is not true for 4.5 (and I thought some version 
> beforehand, but the only note I have specifically says "4.5").
> 
>     If you have the frequency set to a multiple of 24
>     hours, the scheduler will check to see if the backup
>     is due during the current window and will start it
>     when the window opens.
> 
> 
> There's also something in the back of my mind about midnight, 
> but I can't get at it.  The fact that his jobs start just 
> after midnight (presumedly the first time the scheduler wakes 
> up after midnight) makes me curious.  What's the frequency set to?
> 
> 
> > 
> > This is why all of my "daily" incrementals have intervals 
> of 12 hours. 
> > It's because of what you're seeing.  When the next window rolls 
> > around, chance are it will have been at least 12 hours 
> since the last 
> > backup, since the window closed 12 hours ago.  
> Occasionally, a backup 
> > might go later than that, and result in it being run slightly later 
> > that night within the window, but I will never have what 
> you're having 
> > -- skipped backups.
> > 
> > I bet it's pretty common for people to set the interval to 
> 1 day or 24 
> > hours (either results in the same number of seconds being 
> put in the 
> > schedule's INFO file.)  Then they occasionally skip 
> backups, and don't 
> > even know it.
> > 
> > NOTE: If you're setting your backups to a 1 day interval, and they 
> > come anywhere near filling up your window with backups, you are 
> > missing backups and you don't know it.  (If your backups all finish 
> > within an hour or so, then you've got no problem.)  It's only when 
> > you've got what is described here, a relatively full window.
> > 
> > > -----Original Message-----
> > > From: veritas-bu-admin at mailman.eng.auburn.edu
> > > [mailto:veritas-bu-admin at mailman.eng.auburn.edu] On Behalf Of 
> > > Gardner, Jesse
> > > Sent: Tuesday, September 24, 2002 7:46 AM
> > > To: 'veritas-bu at mailman.eng.auburn.edu'
> > > Subject: [Veritas-bu] Overnight scheduling quirk
> > > 
> > > 
> > > (Netbackup 4.5)
> > > 
> > > I'm having a problem where I've got a policy whose backup
> > > window needs to be open between 7pm and 6am.  So it's set up 
> > > the common sense way- window starts at 7pm and runs for 11 
> > > hours.  Netbackup then automatically sets the end time to be 
> > > the next day at 6am, which is fine.
> > > 
> > > We run incrementals M-Tr and fulls on Friday.  On Monday, the
> > > Incremental starts at 7pm like it should.
> > > 
> > > On Tuesday->Thursday, it starts at 12:08am (5 hours late).  I
> > > figure that since Monday night's backups ran into Tuesday 
> > > morning, it confuses the backup window and thinks it's 
> > > already done Tuesday's backup.  So it waits until Wednesday 
> > > comes around (12:08 am).
> > > 
> > > Anyone seen this?  Any advice?
> > > 
> > > Thanks,
> > > Jesse
> > > _______________________________________________
> > > Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> > > http://mailman.eng.auburn.edu/mailman/listinfo> /veritas-bu
> > > 
> > 
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu 
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> -- 
> Larry Kingery 
> 	   Linux: Because rebooting is for adding hardware
>