I've just been through this, so it's still fresh in my mind.
What I have done and it works great is to use the frequency. If you look at
the documentation, you'll see that the scheduler uses the frequency to
prioritize between two schedules that occur at the same time. So what I did
was to create a monthly schedule by making a copy of the weekly schedule for
each class. I set the retention time, tape pool accordingly for the for
monthly schedule, and made sure the frequency on the weekly schedule is set
to one 1 week and the monthly is set to 4 weeks.
A couple of caveats to are. The first backup that will run will be the
monthly schedule, since it has the longer retention time. For any given
client, I get a monthly, followed by 3 weeks of weeklies. If you add a new
client into an existing class, it will run the monthly, even if the other
clients run the weekly.
Because I use a 4 week frequency, I get 13 monthly backups a year instead of
12. It took some doing, but I finally convinced our operations group to
treat all the full backups the same. They get pulled from the library to
get sent to our off-site storage for a week, then they all come back to our
on-site vault, where they are all hung on the shelves in numerical order
until their retention period has ended. I have scripts that I run each week
that mails a reports to the operators telling them what tapes to pull as
scratch tapes. They don't care if they are weekly or monthly, as NetBackup
takes care of that for us.
This may not do exactly what you need, but hopefully it will give you some
ideas.
======================
John Snodgrass
Siemens ICN
Lake Mary, FL
407-942-5583
======================
--__--__--
Message: 2
Date: Wed, 08 May 2002 08:16:53 -0500
From: "Ryan Anderson" <Ryan.Anderson AT udlp DOT com>
To: <veritas-bu-admin AT mailman.eng.auburn DOT edu>, <lfafard AT saskpower DOT
com>,
<geoffh AT us.ibm DOT com>
Cc: <veritas-bu AT mailman.eng.auburn DOT edu>
Subject: Re: [Veritas-bu] What is the BEST WAY to schedule a monthly
backup (without4.5)
You can also set the frequency to one day less than the shortest month,
which would be 27, then put a backup window for every day of the week.
Its less predictable _when_ the backup occurs, but its using the NBU
scheduler.
RCA
--
Ryan C. Anderson
Unix Administrator
United Defense L.P.
desk 763.572.6684
pager 952.235.9936
>>> "Lowell Fafard" <lfafard AT saskpower DOT com> 05/07/02 05:31PM >>>
What we do is setup monthly and yearly schedules, with the same time as
the regular full but longer retention periods, as user backups(not
recognized by the scheduler). At the first of the month have a script
run
via crontab change these schedules to full backups and then back to
user
backups on the 8th of the month. The scheduler will take the backup
with
the longer retention period.
Hope this helps.
Lowell
"Geoffrey Hazel" <geoffh AT us.ibm DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
2002-05-07 04:04 PM
To: <veritas-bu AT mailman.eng.auburn DOT edu>
cc:
Subject: [Veritas-bu] What is the BEST WAY to schedule a
monthly backup (without
4.5)
I have a requirement to run a month end backup in the first week of
the
month. The data isn't there prior to that week, and after that week
it
disappears. If I wanted to schedule the job with NetBackup and not
simply
run a manual job from "cron", what would be the best way to do that?
I'm toying with the idea of scheduling it every 730 hours (that's 365
days
x 24 hrs/day / 12 months) and just opening up the schedule 24/7 so when
it
gets to the 730'th hour, off it goes.
Anyone else come up with a better way? A more clever plan?
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
