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_01C2F856.04866E30
Content-Type: text/plain
We do backups do disk here. The array is just 220G that I threw together
from my spare parts (it's nicknamed "Franken-array"). We backup our Oracle
archived redo logs to it on an hourly basis using a incremental schedule.
Doing this nearly guarentees availablity of the disk storage unit & keeps
the very frequent backups from making my library frequently shuffle tapes
around.
Because the disk array is very small compared to retention, we have a
process that duplicates the images to tape then expires the disk copy.
The only problem is that a disk array doesn't compress like a tape drive
does. If you want compressed backups, you have to turn on client-side
compression which loads your client's CPUs.
We're nearly an all solaris environment.
HTH - Mark
-----Original Message-----
From: Charlene Osborn [mailto:cpo AT helix.nih DOT gov]
Sent: Friday, March 28, 2003 10:57 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] backing up to disk
I'm fairly new to this list and so I apologize in advance if this
has been discussed (or beaten to death!) in the past. In the
last couple of months it has become clear to us that
as we increase storage capacity at our site, we're not
going to be able to easily keep up on tape capacity for backups.
We are considering using ATT technology for doing some of our
backups to disk, while continuing to use tape for at least
disaster recovery.
We are currently using NetBackup 3.4 to backup several large SGI
and Sun machines as well as a linux cluster and several NetApp
filers (using NDMP). It's mainly the filers that were going to
have trouble keeping up with. The demand for storage capacity at
our site has grown in leaps and bounds and for the most part we
are using NetApp filers to keep up with it. Not even considering the
problems with long backup and recovery time - the number of tapes
alone is enough that we're looking at alternative backup strategies.
So having said all that, I'm wondering just how common backups to disk
are and what sort of platforms people are using, and of course, just how
well it's working.
Thanks in advance,
Charlene Osborn
Helix Systems Staff
CIT, NIH
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C2F856.04866E30
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] backing up to disk</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>We do backups do disk here. The array is just =
220G that I threw together from my spare parts (it's nicknamed =
"Franken-array"). We backup our Oracle archived redo =
logs to it on an hourly basis using a incremental schedule. Doing =
this nearly guarentees availablity of the disk storage unit & keeps =
the very frequent backups from making my library frequently shuffle =
tapes around.</FONT></P>
<P><FONT SIZE=3D2>Because the disk array is very small compared to =
retention, we have a process that duplicates the images to tape then =
expires the disk copy.</FONT></P>
<P><FONT SIZE=3D2>The only problem is that a disk array doesn't =
compress like a tape drive does. If you want compressed backups, =
you have to turn on client-side compression which loads your client's =
CPUs.</FONT></P>
<P><FONT SIZE=3D2>We're nearly an all solaris environment.</FONT>
</P>
<P><FONT SIZE=3D2>HTH - Mark</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Charlene Osborn [<A =
HREF=3D"mailto:cpo AT helix.nih DOT gov">mailto:cpo AT helix.nih DOT
gov</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, March 28, 2003 10:57 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] backing up to disk</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>I'm fairly new to this list and so I apologize in =
advance if this</FONT>
<BR><FONT SIZE=3D2>has been discussed (or beaten to death!) in the =
past. In the</FONT>
<BR><FONT SIZE=3D2>last couple of months it has become clear to us =
that</FONT>
<BR><FONT SIZE=3D2>as we increase storage capacity at our site, we're =
not</FONT>
<BR><FONT SIZE=3D2>going to be able to easily keep up on tape capacity =
for backups.</FONT>
<BR><FONT SIZE=3D2>We are considering using ATT technology for doing =
some of our</FONT>
<BR><FONT SIZE=3D2>backups to disk, while continuing to use tape for at =
least</FONT>
<BR><FONT SIZE=3D2>disaster recovery.</FONT>
</P>
<P><FONT SIZE=3D2>We are currently using NetBackup 3.4 to backup =
several large SGI</FONT>
<BR><FONT SIZE=3D2>and Sun machines as well as a linux cluster and =
several NetApp</FONT>
<BR><FONT SIZE=3D2>filers (using NDMP). It's mainly the filers that =
were going to</FONT>
<BR><FONT SIZE=3D2>have trouble keeping up with. The demand for storage =
capacity at</FONT>
<BR><FONT SIZE=3D2>our site has grown in leaps and bounds and for the =
most part we</FONT>
<BR><FONT SIZE=3D2>are using NetApp filers to keep up with it. Not even =
considering the</FONT>
<BR><FONT SIZE=3D2>problems with long backup and recovery time - the =
number of tapes</FONT>
<BR><FONT SIZE=3D2>alone is enough that we're looking at alternative =
backup strategies.</FONT>
</P>
<P><FONT SIZE=3D2>So having said all that, I'm wondering just how =
common backups to disk</FONT>
<BR><FONT SIZE=3D2>are and what sort of platforms people are using, and =
of course, just how</FONT>
<BR><FONT SIZE=3D2>well it's working.</FONT>
</P>
<P><FONT SIZE=3D2>Thanks in advance,</FONT>
</P>
<P><FONT SIZE=3D2>Charlene Osborn</FONT>
<BR><FONT SIZE=3D2>Helix Systems Staff</FONT>
<BR><FONT SIZE=3D2>CIT, NIH</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2F856.04866E30--
|
