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_01C2C6EC.0A6221A0
Content-Type: text/plain
I've got a total of eight DLT7000 drives across two libraries (roughly 220
slots total). Deciding on which backups to go which storage units & for how
long is purely an operation decision with the limiting factor being disk
space. For that reason, I'd stick to a full/diff pattern and forget the
cummulative images. There's really only two reasons to do cummulatives,
IMO, and that's speed of restore (which'd be fast enough from disk) and
image protection from tape loss/damage (also negated by disk).
The quick skeleton method below would work fine for what you're talking
about, rather than set an expiration date of "0" with bpexpdate, you could
set it at a week or something & NB will automatically reclaim your disk
space as the images expire. The on-tape image automatically becomes your
primary restore image following the expiration of the on-disk image.
I immediately expire since my disk "buffer" region is a mere 200G and I just
don't have the space for any retained images once they're successsfully on
tape. The reason I do it in the first place is that I have 7 production
databases and I hourly do an incremental backup of the archived redo logs to
protect against data failure. This made the library constantly thrash
loading & unload tapes. Buffering to disk lets me collect a set of these,
then a cron-job starts every four hours to dup them to tape. If the tape
machine is busy or unavailable & continue to buffer until it becomes
available. 200M will hold about 2-3 days worth for me - less if it's been
busy.
Let me know if you need help.
-M
-----Original Message-----
From: William H Blandy [mailto:william_h_blandy AT fanniemae DOT com]
Sent: Tuesday, January 28, 2003 6:03 AM
To: 'Donaldson Mark'; markjessup AT northwesternmutual DOT com;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Questions on Staging to Disk and MS Exchange Age
nt
Mark, what type of drives are you using, like Mark we are about to implement
4.5. We have a project this year to get a portion of our daily backups (say
about 4-6 tb) on to disk. We are struggling with a methodology to do this.
Fulls done every x days and held for x weeks, then incrementals (cum or
dif), and a host of other questions. Anyone out there hold data on disk for
a period of time longer than what it takes to vault it? Any suggestions on
how to NOT create a brand new disk farm of backed up data (do I then have to
back this up? :{) ) Thanks, Bill
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Donaldson,
Mark
Sent: Monday, January 27, 2003 12:25 PM
To: 'markjessup AT northwesternmutual DOT com'; veritas-bu AT
mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Questions on Staging to Disk and MS Exchange Age
nt
I do this. I stage backups to drives attached to my media server, then use
scripts built around bpduplicate, bpimagelist, & bpexpdate to duplicate
these backups to tape, then expire the disk image.
The logic looks a little like this
1. use bpimagelist to query disk storage unit for image names
2. use bpduplicate to duplicate images to tape
3. use bpimagelist to verify there's a copy on tape
4. if tape image is recorded, then use bpexpdate to expire the disk copy
I've got other logic that uses a configuration file to associate a tape pool
name with class & schedule names to sort the images but this is the basic
core of it.
It works nicely, it consolidates backups so I'm not always mounting &
unmouting tapes, it makes the backups from the clients faster, and the disk
storage unit has higher availability than my tape libraries. The only
problem that I have is that the disk storage units do not inherently
compress like a tape drive does (there is some new exceptions so this on
some arrays). The client compression saves some space but it is a pretty
lousy algorithm and doesn't squish the data much - plus there's client CPU
load to use it.
HTH -M
-----Original Message-----
From: markjessup AT northwesternmutual DOT com
[ mailto:markjessup AT northwesternmutual DOT com
<mailto:markjessup AT northwesternmutual DOT com> ]
Sent: Sunday, January 26, 2003 3:09 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Cc: markjessup AT northwesternmutual DOT com
Subject: [Veritas-bu] Questions on Staging to Disk and MS Exchange Agent
We are implementing Netbackup 4.5 and was wondering if any people are
staging backups to a disk pool such as some of new ATA disk systems from
NetApps, NexSAN, and StorageTek and then migrating to tape after using
Vault or some other process. If you are using such a device, can you
describe your environment, what performance you are getting, what the
benefits you are seeing, how it works with NB, etc.
Secondly, we are moving to MS Exchange and I am wondering how many
people are using the NB Exchange agent for database backups of Exchange.
How does the agent work, what is your performance numbers, how big are
your Exchange databases, do you compliment the tape backups with
snapshots to disk. Do you do mailbox backups or just full DB backups.
Any experience the Exchange Edition from Veritas?
If anyone has any experience with either one of these topics, it would
be greatly appreciated. Thanks!
Mark Jessup
IS Manager, Enterprise Storage and Output Management
Northwestern Mutual
(414) 665-3968
markjessup AT northwesternmutual DOT com
------_=_NextPart_001_01C2C6EC.0A6221A0
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">
<TITLE>Message</TITLE>
<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff size=2>I've
got a total of eight DLT7000 drives across two libraries (roughly 220 slots
total). Deciding on which backups to go which storage units & for how
long is purely an operation decision with the limiting factor being disk
space. For that reason, I'd stick to a full/diff pattern and forget the
cummulative images. There's really only two reasons to do cummulatives,
IMO, and that's speed of restore (which'd be fast enough from disk) and image
protection from tape loss/damage (also negated by disk).</FONT></SPAN></DIV>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff size=2>The
quick skeleton method below would work fine for what you're talking about,
rather than set an expiration date of "0" with bpexpdate, you could set it at
a week or something & NB will automatically reclaim your disk space as
the images expire. The on-tape image automatically becomes your primary
restore image following the expiration of the on-disk image.
</FONT></SPAN></DIV>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff size=2>I
immediately expire since my disk "buffer" region is a mere 200G and I just
don't
have the space for any retained images once they're successsfully on
tape.
The reason I do it in the first place is that I have 7 production databases and
I hourly do an incremental backup of the archived redo logs to protect against
data failure. This made the library constantly thrash loading &
unload
tapes. Buffering to disk lets me collect a set of these, then a cron-job
starts every four hours to dup them to tape. If the tape machine is
busy or unavailable & continue to buffer until it becomes available.
200M will hold about 2-3 days worth for me - less if it's been
busy.</FONT></SPAN></DIV>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff size=2>Let
me
know if you need help.</FONT></SPAN></DIV>
<DIV><SPAN class=583241716-28012003><FONT face=Arial color=#0000ff
size=2>-M</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> William H Blandy
[mailto:william_h_blandy AT fanniemae DOT com]<BR><B>Sent:</B> Tuesday,
January 28,
2003 6:03 AM<BR><B>To:</B> 'Donaldson Mark';
markjessup AT northwesternmutual DOT com;
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
Questions on Staging to Disk and MS Exchange Age nt<BR><BR></FONT></DIV>
<DIV><SPAN class=426155712-28012003>Mark, what type of drives are you using,
like Mark we are about to implement 4.5. We have a project this year to
get a portion of our daily backups (say about 4-6 tb) on to disk. We
are
struggling with a methodology to do this. Fulls done every x days and
held for x weeks, then incrementals (cum or dif), and a host of other
questions. Anyone out there hold data on disk for a period of time
longer than what it takes to vault it? Any suggestions on how to NOT
create a brand new disk farm of backed up data (do I then have to back this
up? :{) ) Thanks, Bill</SPAN></DIV>
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of
</B>Donaldson, Mark<BR><B>Sent:</B> Monday, January 27, 2003 12:25
PM<BR><B>To:</B> 'markjessup AT northwesternmutual DOT com';
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
Questions on Staging to Disk and MS Exchange Age nt<BR><BR></FONT></DIV>
<P><FONT size=2>I do this. I stage backups to drives attached to my
media server, then use scripts built around bpduplicate, bpimagelist, &
bpexpdate to duplicate these backups to tape, then expire the disk
image.</FONT></P>
<P><FONT size=2>The logic looks a little like this</FONT> <BR><FONT size=2>1.
use bpimagelist to query disk storage unit for image names</FONT> <BR><FONT
size=2>2. use bpduplicate to duplicate images to tape</FONT> <BR><FONT
size=2>3. use bpimagelist to verify there's a copy on tape</FONT> <BR><FONT
size=2>4. if tape image is recorded, then use bpexpdate to expire the disk
copy</FONT> </P>
<P><FONT size=2>I've got other logic that uses a configuration file to
associate a tape pool name with class & schedule names to sort the images
but this is the basic core of it.</FONT></P>
<P><FONT size=2>It works nicely, it consolidates backups so I'm not always
mounting & unmouting tapes, it makes the backups from the clients faster,
and the disk storage unit has higher availability than my tape
libraries. The only problem that I have is that the disk storage units
do not inherently compress like a tape drive does (there is some new
exceptions so this on some arrays). The client compression saves some
space but it is a pretty lousy algorithm and doesn't squish the data much -
plus there's client CPU load to use it.</FONT></P>
<P><FONT size=2>HTH -M</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
markjessup AT northwesternmutual DOT com</FONT> <BR><FONT size=2>[<A
href="mailto:markjessup AT northwesternmutual DOT com">mailto:markjessup AT
northwesternmutual DOT com</A>]</FONT>
<BR><FONT size=2>Sent: Sunday, January 26, 2003 3:09 PM</FONT> <BR><FONT
size=2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT
size=2>Cc:
markjessup AT northwesternmutual DOT com</FONT> <BR><FONT size=2>Subject:
[Veritas-bu] Questions on Staging to Disk and MS Exchange Agent</FONT>
</P><BR>
<P><FONT size=2>We are implementing Netbackup 4.5 and was wondering if any
people are</FONT> <BR><FONT size=2>staging backups to a disk pool such as
some
of new ATA disk systems from</FONT> <BR><FONT size=2>NetApps, NexSAN, and
StorageTek and then migrating to tape after using</FONT> <BR><FONT
size=2>Vault or some other process. If you are using such a device, can
you</FONT> <BR><FONT size=2>describe your environment, what performance you
are getting, what the</FONT> <BR><FONT size=2>benefits you are seeing, how it
works with NB, etc.</FONT> </P>
<P><FONT size=2>Secondly, we are moving to MS Exchange and I am wondering how
many</FONT> <BR><FONT size=2>people are using the NB Exchange agent for
database backups of Exchange.</FONT> <BR><FONT size=2>How does the agent
work,
what is your performance numbers, how big are</FONT> <BR><FONT size=2>your
Exchange databases, do you compliment the tape backups with</FONT> <BR><FONT
size=2>snapshots to disk. Do you do mailbox backups or just full DB
backups.</FONT> <BR><FONT size=2>Any experience the Exchange Edition from
Veritas? </FONT></P><BR>
<P><FONT size=2>If anyone has any experience with either one of these topics,
it would</FONT> <BR><FONT size=2>be greatly appreciated. Thanks!</FONT>
</P><BR><BR>
<P><FONT size=2>Mark Jessup </FONT><BR><FONT size=2>IS Manager, Enterprise
Storage and Output Management</FONT> <BR><FONT size=2>Northwestern
Mutual</FONT> <BR><FONT size=2>(414) 665-3968</FONT> <BR><FONT
size=2>markjessup AT northwesternmutual DOT com</FONT>
</P><BR><BR></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C2C6EC.0A6221A0--
|
