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_001_01C20E37.BE5A8A30
Content-Type: text/plain
I use the rule for classes/policies that if it's the same set of files at
the same time of day then it's the same class. I used to divide them into a
class for devel servers, test servers, & production servers but that was
also so weekly full backups were distributed across the week - I've changed
this so all my fulls are on the same night and combined the classes. Now I
have just two for my servers, one which multiplexes the backups for backup
speed, the other which doesn't multiplex for duplication speed.
Because of the pre- & post-schedule processing each of my databases is its
own class. This way I call different bpend_notify & bpstart_notify scripts.
I pool my databases separate from my filesystem backups just for
administrative tracking. I like to know how many tapes are being taken up
by this different class of data. I also have a pair of pools for a specific
project-related set of servers because this client is paranoid about sharing
tapes with other client's data.
I use a specific pool for offsite tapes. This is because I duplicate the
pools above to other tapes for offsite storage, the offsite pool easily
identifies which tapes get ejected from the library after the duplication is
done. I have a script called "eject_pool" that I call that pushes all tapes
from the library that are part of the supplied poolname.
I think a scratchpool is a necessity - I return all deassigned tapes to the
scratchpool with a daily script.
One reason for separating full and incremental backups would be to protect
against media damage. If you smash a tape full of incremental images, then
you can be sure your full backups weren't damaged in the fall.
Be aware, that using lots of pools will cost slightly more tapes. For each
pool, there's a portion of tape "on the end" that wasn't filled fully by the
previous jobs - from an efficiency point of view, this is wasted space. I
have roughly a dozen pools, each one has at least one tape that isn't full.
This free space adds up. It's a balancing act - although a pretty easy one.
HTH - Mark
-----Original Message-----
From: rene_casalme AT baxter DOT com [mailto:rene_casalme AT baxter DOT com]
Sent: Thursday, June 06, 2002 8:33 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] good way to create classes, pools, and schedules
I will be using NetBackup to backup a variety of platforms (Windows 2000,
Novell NetWare, and Solaris). I was thinking of creating a class for the
Oracle databases, one class for each server, etc. How have some of you
folks determined how many classes you should have?
Also, I was thinking of creating pools for different OS, Oracle database,
offsite, scratch, etc. How did you folks determined the pools? Does it
make sense to put all backups of the OS, database, applications all into the
offiste pool so the operator can easily identify where they are and have
them archived?
I have a schedule planned out of the standard operating procedure. Does it
make sense to have separate incremental backups from full backups into their
own separate pool?
Any pointers will be appreciated.
Rene Casalme
------_=_NextPart_001_01C20E37.BE5A8A30
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2716.2200" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff size=2>I use
the rule for classes/policies that if it's the same set of files at the same
time of day then it's the same class. I used to divide them into a class
for devel servers, test servers, & production servers but that was also so
weekly full backups were distributed across the week - I've changed this so all
my fulls are on the same night and combined the classes. Now I have just
two for my servers, one which multiplexes the backups for backup speed, the
other which doesn't multiplex for duplication speed.</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2>Because of the pre- & post-schedule processing each of my databases
is its own class. This way I call different bpend_notify &
bpstart_notify scripts.</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff size=2>I
pool
my databases separate from my filesystem backups just for administrative
tracking. I like to know how many tapes are being taken up by this
different class of data. I also have a pair of pools for a specific
project-related set of servers because this client is paranoid about sharing
tapes with other client's data.</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff size=2>I use
a specific pool for offsite tapes. This is because I duplicate the pools
above to other tapes for offsite storage, the offsite pool easily identifies
which tapes get ejected from the library after the duplication is done. I
have a script called "eject_pool" that I call that pushes all tapes from the
library that are part of the supplied poolname.</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff size=2>I
think a scratchpool is a necessity - I return all deassigned tapes to the
scratchpool with a daily script.</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff size=2>One
reason for separating full and incremental backups would be to protect against
media damage. If you smash a tape full of incremental images, then you
can
be sure your full backups weren't damaged in the fall.
</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff size=2>Be
aware, that using lots of pools will cost slightly more tapes. For each
pool, there's a portion of tape "on the end" that wasn't filled fully by the
previous jobs - from an efficiency point of view, this is wasted space. I
have roughly a dozen pools, each one has at least one tape that isn't
full. This free space adds up. It's a balancing act - although a
pretty easy one.</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff size=2>HTH -
Mark</FONT></SPAN></DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=213551115-07062002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> rene_casalme AT baxter DOT
com
[mailto:rene_casalme AT baxter DOT com]<BR><B>Sent:</B> Thursday, June 06,
2002 8:33
PM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B>
[Veritas-bu] good way to create classes, pools, and
schedules<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>I will be
using
NetBackup to backup a variety of platforms (Windows 2000, Novell NetWare, and
Solaris). I was thinking of creating a class for the Oracle databases,
one class for each server, etc. How have some of you folks determined
how many classes you should have?</FONT> <BR><BR><FONT face=sans-serif
size=2>Also, I was thinking of creating pools for different OS, Oracle
database, offsite, scratch, etc. How did you folks determined the
pools?
Does it make sense to put all backups of the OS, database, applications
all into the offiste pool so the operator can easily identify where they are
and have them archived?</FONT> <BR><BR><FONT face=sans-serif size=2>I have a
schedule planned out of the standard operating procedure. Does it make
sense to have separate incremental backups from full backups into their own
separate pool?</FONT> <BR><BR><FONT face=sans-serif size=2>Any pointers will
be appreciated.</FONT> <BR><BR><FONT face=sans-serif size=2>Rene
Casalme</FONT> <BR><BR></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C20E37.BE5A8A30--
|
