This is a multi-part message in MIME format.
------=_NextPart_000_0020_01C2C6A3.B7AF19B0
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
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]
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_000_0020_01C2C6A3.B7AF19B0
Content-Type: text/html;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D426155712-28012003>Mark, what type of drives are you =
using,=20
like Mark we are about to implement 4.5. We have a project this =
year to=20
get a portion of our daily backups (say about 4-6 tb) on to disk. =
We are=20
struggling with a methodology to do this. Fulls done every x days =
and held=20
for x weeks, then incrementals (cum or dif), and a host of other=20
questions. Anyone out there hold data on disk for a period of time =
longer=20
than what it takes to vault it? Any suggestions on how to NOT =
create a=20
brand new disk farm of backed up data (do I then have to back this up? =
:{) =20
) Thanks, Bill</SPAN></DIV>
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of =
</B>Donaldson,=20
Mark<BR><B>Sent:</B> Monday, January 27, 2003 12:25 PM<BR><B>To:</B>=20
'markjessup AT northwesternmutual DOT com';=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
Questions=20
on Staging to Disk and MS Exchange Age nt<BR><BR></FONT></DIV>
<P><FONT size=3D2>I do this. I stage backups to drives attached to =
my media=20
server, then use scripts built around bpduplicate, bpimagelist, & =
bpexpdate=20
to duplicate these backups to tape, then expire the disk =
image.</FONT></P>
<P><FONT size=3D2>The logic looks a little like this</FONT> <BR><FONT =
size=3D2>1.=20
use bpimagelist to query disk storage unit for image names</FONT> =
<BR><FONT=20
size=3D2>2. use bpduplicate to duplicate images to tape</FONT> <BR><FONT =
size=3D2>3.=20
use bpimagelist to verify there's a copy on tape</FONT> <BR><FONT =
size=3D2>4. if=20
tape image is recorded, then use bpexpdate to expire the disk =
copy</FONT> </P>
<P><FONT size=3D2>I've got other logic that uses a configuration file to =
associate=20
a tape pool name with class & schedule names to sort the images but =
this is=20
the basic core of it.</FONT></P>
<P><FONT size=3D2>It works nicely, it consolidates backups so I'm not =
always=20
mounting & unmouting tapes, it makes the backups from the clients =
faster,=20
and the disk storage unit has higher availability than my tape =
libraries. =20
The only problem that I have is that the disk storage units do not =
inherently=20
compress like a tape drive does (there is some new exceptions so this on =
some=20
arrays). The client compression saves some space but it is a =
pretty lousy=20
algorithm and doesn't squish the data much - plus there's client CPU =
load to use=20
it.</FONT></P>
<P><FONT size=3D2>HTH -M</FONT> </P>
<P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
markjessup AT northwesternmutual DOT com</FONT> <BR><FONT size=3D2>[<A=20
href=3D"mailto:markjessup AT northwesternmutual DOT
com">mailto:markjessup@north=
westernmutual.com</A>]</FONT>=20
<BR><FONT size=3D2>Sent: Sunday, January 26, 2003 3:09 PM</FONT> =
<BR><FONT=20
size=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT =
size=3D2>Cc:=20
markjessup AT northwesternmutual DOT com</FONT> <BR><FONT size=3D2>Subject: =
[Veritas-bu]=20
Questions on Staging to Disk and MS Exchange Agent</FONT> </P><BR>
<P><FONT size=3D2>We are implementing Netbackup 4.5 and was wondering if =
any=20
people are</FONT> <BR><FONT size=3D2>staging backups to a disk pool such =
as some=20
of new ATA disk systems from</FONT> <BR><FONT size=3D2>NetApps, NexSAN, =
and=20
StorageTek and then migrating to tape after using</FONT> <BR><FONT =
size=3D2>Vault=20
or some other process. If you are using such a device, can =
you</FONT>=20
<BR><FONT size=3D2>describe your environment, what performance you are =
getting,=20
what the</FONT> <BR><FONT size=3D2>benefits you are seeing, how it works =
with NB,=20
etc.</FONT> </P>
<P><FONT size=3D2>Secondly, we are moving to MS Exchange and I am =
wondering how=20
many</FONT> <BR><FONT size=3D2>people are using the NB Exchange agent =
for database=20
backups of Exchange.</FONT> <BR><FONT size=3D2>How does the agent work, =
what is=20
your performance numbers, how big are</FONT> <BR><FONT size=3D2>your =
Exchange=20
databases, do you compliment the tape backups with</FONT> <BR><FONT=20
size=3D2>snapshots to disk. Do you do mailbox backups or just full =
DB=20
backups.</FONT> <BR><FONT size=3D2>Any experience the Exchange Edition =
from=20
Veritas? </FONT></P><BR>
<P><FONT size=3D2>If anyone has any experience with either one of these =
topics, it=20
would</FONT> <BR><FONT size=3D2>be greatly appreciated. =
Thanks!</FONT>=20
</P><BR><BR>
<P><FONT size=3D2>Mark Jessup </FONT><BR><FONT size=3D2>IS Manager, =
Enterprise=20
Storage and Output Management</FONT> <BR><FONT size=3D2>Northwestern =
Mutual</FONT>=20
<BR><FONT size=3D2>(414) 665-3968</FONT> <BR><FONT=20
size=3D2>markjessup AT northwesternmutual DOT com</FONT> =
</P><BR><BR></BODY></HTML>
------=_NextPart_000_0020_01C2C6A3.B7AF19B0--
|
