This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01BFE1FF.178EDF14
Content-Type: text/plain;
charset="iso-8859-1"
The regular disclaimers apply.
Use this in good health.
Bob
-----Original Message-----
From: [ISS] Veritas-Users [mailto:Veritas-Users AT wnt.sas DOT com]
Sent: Tuesday, June 27, 2000 1:11 PM
To: 'David A. Chapa'; Terese Pelletier
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Monthly backups for offsite storage
But...
Every 28 days does not fall on a weekend. If you have a window for Sat-Sun
F28 backups, and Monday is the 28th day, then it waits a week. You may, or
may not care about this.
The problem we found with adding a monthly schedule to a weekend that has a
full schedule is that the next incremental is take off the last full... if
you do the monthly after the full and then offsite the monthly tapes, then
if you need to restore, you should start with the last full. And doing the
monthly first might mean that you then have too little time to do a full
after that. Also, two schedules means double the image database entries for
that weekend.
If you have a schedule every 7 days for the full and the full fails on
Friday and you manually rerun it on Saturday, then it won't be attempted the
next Friday because 7 days have not passed. We have our fulls set up to run
every 5 days, but the window is Fri 18:30 for 24 hours and again Sat 18:30
for 24 hours. That way if a backup fails each time it is tried (three tries
in 12 hours) Friday night, it is reattempt Sat night. And, because we have
the schedule set for every 5 days, it is scheduled as usual for fulls the
next Friday night.
Our method is to recalculate the expiration date of all full backups that
run over the first weekend of the month. We may add duplication in there,
but we'll see...
Kelly
--
Kelly Wyatt, Kelly.Wyatt AT SAS DOT com
Senior Systems Programmer
Strategic Recovery
SAS Institute Inc. / SAS Campus Drive / Cary, NC 27513
http://www.sas.com
SAS... The Power to Know
-----Original Message-----
From: David A. Chapa [mailto:david AT datastaff DOT com]
Sent: Tuesday, June 27, 2000 10:23 AM
To: Terese Pelletier
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Monthly backups for offsite storage
Quoting Terese Pelletier <terese.pelletier AT kodak DOT com>:
> All,
>
> We are trying to develop a schedule for monthly
(full) backups to send
> to offsite storage. We would like to maintain our
current schedule
> scheme of Mon-Thur incrementals and Fri fulls and add
a monthly
> schedule. Since there doesn't seem to be the monthly
selection under
> frequency this is not as straight forward as we had
hoped.
>
> We are concerned that the weekly Fri full backup will
not allow a 4 week
> rotation to run. We would really like something
close to the first/last
> weekend of the month so that they can be labeled by
month similar to our
> other backup schemes that are offsite.
>
> Any suggestions?
> Thanks,
> Terese
> --
> Terese Pelletier |Internet:
terese.pelletier AT kodak DOT com
> Eastman Kodak Company |Phone: 716-477-1316
> Room 6235, Bldg 69, KRL |Pager: 716-253-7239
> Rochester, NY 14650-1925 |Fax: 716-477-0127
> _______________________________________________
> Veritas-bu maillist - Veritas-
bu AT mailman.eng.auburn DOT edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-
bu
>
The schedules work based on a heirarchy...let me try to
illustrate.
M T W Th F
I1 I1 I1 I1 F7
I1 I1 I1 I1 F7
I1 I1 I1 I1 F7
I1 I1 I1 I1 F28
I1 I1 I1 I1 F7
What I am trying to display here are your incrementals
running daily M-Th, with your Weekly Fulls on Friday
(every seven days). Each time the NetBackup
scheduler 'wakes up' to see what there is to do, it
looks at the schedules, the frequencies and the length
of time between the last backup of that particular
schedule. So if you have a Full Schedule that has a
frequency of 28 days (F28-monthly), NetBackup will give
that a higher priority than the F7 (full every seven
days) when they happen to fall on the same backup day.
NetBackup determines that it has seen this F7 schedule
seven days ago, but it hasn't seen this F28 in over 28
days, it will launch the backup with the F28 schedule.
make sense?
-David Chapa
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
David A. Chapa 847 413 1144 p
Director of Technology 847 413 1168 f
DataStaff, Inc. http://www.datastaff.com
nbu-lserv AT datastaff DOT com majordomo AT datastaff DOT com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_000_01BFE1FF.178EDF14
Content-Type: application/octet-stream;
name="cron.sh"
Content-Disposition: attachment;
filename="cron.sh"
#!/usr/bin/ksh
# Written by Bob Bakh
# Veritas Software
# Southwest Region Technical Account Manager
# email: bob.bakh AT veritas DOT com
# This Example deals with full weekly, monthly and yearly backups being done on
the second
# Sunday of the month. It can be changed as needed. It expects a yearly to be
completed
# in January as well.
# A daily is run everyday a weekly isn't, ulsess that weekly lands on the
second Sunday of
# the month in that case it runs a monthly, however if that weekly falls on the
second
# Sunday of January it will be run as a yearly.
# Create Server and Client and other constants in this script
SERVER=severname
CLIENT=clientname
CLASS=classname
# CLIENT_TYPE Parameters
# Specift the cient type as follows:
# 0 = Standard
# 3 = Apollo
# 4 = Oracle DB Backup
# 6 = Informix DB Backup
# 7 = Sybase DB Backup
# 10 = Netware
# 11 = SQL BackTrack DB Backup
# 12 = Auspex FastBackup
# 13 = Windows NT
# 14 = OS2
# 15 = SQL Server
# 16 = Exchange
# 17 = SAP
# 18 = DB2
# 19 = NDMP
# 20 = FlashBackup
# The default is 3 on Apollos and 0 (standard) on nonApollos.
CLIENT_TYPE=0
# Create Date Variables.
DAYNUM=`/usr/bin/date '+%d'`
DAYNAME=`/usr/bin/date '+%a'`
MONTH=`/usr/bin/date '+%b'`
# Start Logic for Backup Scheme and determine Schedule
if [ "$DAYNAME" = "Sun" ]
then
if [ $DAYNUM -ge 8 -a $DAYNUM -le 14 ]
then
if [ "$MONTH" = "Jan" ]
then
SCHEDULE=Yearly
else
SCHEDULE=Monthly
fi
else
SCHEDULE=Weekly
fi
else
SCHEDULE=Daily
fi
# Execute bpbackup
/usr/openv/netbackup/bin/bpbackup -c $CLASS \
-s $SCHEDULE \
-S $SERVER \
-h $CLIENT \
-t $CLIENT_TYPE \
-w -i
------_=_NextPart_000_01BFE1FF.178EDF14--
|
