Veritas-bu

[Veritas-bu] Homemade HSM

2002-04-22 17:12:50
Subject: [Veritas-bu] Homemade HSM
From: Mark.Donaldson AT experianems DOT com (Donaldson, Mark)
Date: Mon, 22 Apr 2002 15:12:50 -0600
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_01C1EA42.75AEDDE0
Content-Type: text/plain;
        charset="iso-8859-1"

We had a library failure over the weekend and it underscored the degree to
which our library is a single point of failure for production processes.
(Oracle redo logs are archived to tape via netbackup: when the library
fails, the archive fails, the DB filesystems fill up and the DB crashes.
Nice, huh?)

Anyway, to compensate, I want to build a disk-based storage unit to be used
for critical files.  It'll only be a couple hundred of gig for our most
important stuff (like archived redo logs).  

I have this idea that I can backup to the disk, then periodically do a
bpduplicate to tape, rename the duplicate copy to be the primary, then
delete the disk image.  When the library is out of service, I'll let the
images accumulate on disk until it's available again.

Has anybody tried this?  Any caveats or experiences you'd like to share?

-Mark

-----------------------------------------------------------------------
   Mark Donaldson - Sr. Systems Engineer
   Experian EMS - Denver Colorado
-----------------------------------------------------------------------  
   Linux?  Wasn't he the kid with the blanket?
-----------------------------------------------------------------------



------_=_NextPart_001_01C1EA42.75AEDDE0
Content-Type: text/html;
        charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Homemade HSM</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>We had a library failure over the weekend and it =
underscored the degree to which our library is a single point of =
failure for production processes.&nbsp; (Oracle redo logs are archived =
to tape via netbackup: when the library fails, the archive fails, the =
DB filesystems fill up and the DB crashes.&nbsp; Nice, huh?)</FONT></P>

<P><FONT SIZE=3D2>Anyway, to compensate, I want to build a disk-based =
storage unit to be used for critical files.&nbsp; It'll only be a =
couple hundred of gig for our most important stuff (like archived redo =
logs).&nbsp; </FONT></P>

<P><FONT SIZE=3D2>I have this idea that I can backup to the disk, then =
periodically do a bpduplicate to tape, rename the duplicate copy to be =
the primary, then delete the disk image.&nbsp; When the library is out =
of service, I'll let the images accumulate on disk until it's available =
again.</FONT></P>

<P><FONT SIZE=3D2>Has anybody tried this?&nbsp; Any caveats or =
experiences you'd like to share?</FONT>
</P>

<P><FONT SIZE=3D2>-Mark</FONT>
</P>

<P><FONT =
SIZE=3D2>---------------------------------------------------------------=
--------</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Mark Donaldson - Sr. Systems =
Engineer</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Experian EMS - Denver Colorado</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
--------&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Linux?&nbsp; Wasn't he the kid with the =
blanket?</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
--------</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1EA42.75AEDDE0--

<Prev in Thread] Current Thread [Next in Thread>