I disagree (never good to disagree with Ed ... he's always right ...
here goes anyway)...
IMHO, Calendar schedules are superior to Frequency based schedules in
this case.
First, NetBackup can do last Friday of the month, but not quarter. If
you use NetBackup scheduling, you need to decide whether you want NO
BACKUPS *or* MONTHLY backups if/when you forget to extend your
schedule. If you choose to NO BACKUPS is OK, specify the dates of your
quarterly backups. If time goes past the dates you specify, NetBackup
will quietly do NO BACKUPS. The alternative is to schedule last Friday
of the month backups and exclude all but the last Friday of the month.
this is more work, but fails by doing too many backups.
Second, you must account for missed/failed backups. You have some
choices here. If you can only rerun on a Friday, only create a Friday
window for the schedule and select "retry after run day"). The backup
will be retried next Friday. This will work perfectly for a calendar
based schedule, but frequency-based schedules will precess (is that the
word I'm looking for?) ... the end of next quarter backup will be first
tried a week late. If you can retry failures on other days of the week
and use calendar based schedules, simply create a schedule window for
each day you wish to allow a retry. Again, Frequency based schedules
cannot do this (and maintain 1st backup on a Friday.
It is surprising that the scheduler was recently rewritten (or I
understand it was), and concepts such as quarterly and yearly are still
missing.
Hope this helps!
cheers, wayne
Ed Wilts wrote:
> Frankly, I would rethink your requirements - it's likely going to
> cause you problems in the future. What are your recovery options if
> the backup fails? If the backup only runs on the last Friday of the
> quarter, is it okay to skip this quarter completely and reschedule the
> job for the next quarter? If not, then your application has to be
> capable of being backed up at other times anyway.
>
> In general, I've found that the more you try and force NetBackup to do
> things your way, the worse off you are. Just use frequency based
> scheduling and let it figure it out for itself. Yes, it may mean that
> it runs on a Monday instead of a Friday, but it *will* recover if a
> job fails for whatever reason. And I'll bet your business users
> probably say that the application must have a 24x7 uptime anyway so it
> should not really matter when the backups run...
>
> Pick a frequency of how often you want the jobs to run and pick a
> window that makes sense and then let NetBackup take it from there.
>
> .../Ed
>
> On Fri, Mar 28, 2008 at 9:00 AM, Randy Samora
> <Randy.Samora AT stewart DOT com <mailto:Randy.Samora AT stewart DOT com>>
> wrote:
>
> Does anyone know of an easier way to configure a Quarterly backup
> schedule to run on the last Friday of the Quarter other than going in
> and manually selecting those 4 dates in the year for each policy?
> I can
> do last Friday of the month but not last Friday of the Quarter. Just
> wondering if there was an easier way.
>
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
