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_01C44E37.36117CA0
Content-Type: text/plain;
charset="iso-8859-1"
Sounds solid to me.
I would also include a copy of the bp.conf file in the catalog backup
-----Original Message-----
From: Marx, Keath [mailto:Keath.Marx AT anthem DOT com]
Sent: Wednesday, June 09, 2004 11:16 AM
To: Veritas-Bu
Subject: [Veritas-bu] Request for Comment...
Okay gang,
I need an opinion on an idea I had.
Background: For the past couple of years I have had to make a third copy of
every full exchange backup (I included the system state for the Exchange
2000 servers and the AD Controllers) and ship it off-site with an infinite
retention period. I got the word last week that we will be stopping this
practice in the next week or so due to the implementation of an active mail
archiving system.
Now there are 323 tapes in this 'Archive_Exchange' tape pool. The original
instructions said that at some point a contractor would take these tapes,
restore the data, scrub the duplicate messages and upload them to the
archive database.
My current catalog backup is 11 gig. I realize this is miniscule compared
to serious implementations of Netbackup. My current Netbackup system is
considered a point solution so I don't backup that much.
The Plan: Here is what I was considering doing. Perform a catalog backup
to tape, wrap that tape in bright red paper and store it with the archive
tapes. Then I would expire all of the archive tapes from the system and
delete the tapes. I will retain the most recent tapes in the database for
a couple of months just in case.
My reasoning behind this is that I do not have the drive resources to
perform the restores of these tapes in my production environment and
therefore the restore (if it ever happens) would need to be done on a
separate system. Therefore I see no reason to retain the catalogs on my
production system and can reduce my catalog size considerably.
The Request: Okay what flaws are there in my plan? Bugs, holes,
weaknesses, stupidity, etc...?
Thanks
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise be protected by law. Any
unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply e-mail
and destroy all copies of the original message.
------_=_NextPart_001_01C44E37.36117CA0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Request for Comment...</TITLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=797393215-09062004><FONT face=Arial color=#0000ff
size=2>Sounds
solid to me.</FONT></SPAN></DIV>
<DIV><SPAN class=797393215-09062004><FONT face=Arial color=#0000ff size=2>I
would also include a copy of the bp.conf file in the catalog
backup</FONT></SPAN></DIV>
<DIV><SPAN class=797393215-09062004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Marx, Keath
[mailto:Keath.Marx AT anthem DOT com]<BR><B>Sent:</B> Wednesday, June 09, 2004
11:16
AM<BR><B>To:</B> Veritas-Bu<BR><B>Subject:</B> [Veritas-bu] Request for
Comment...<BR><BR></FONT></DIV>
<P align=left><FONT face=Arial color=#000080 size=2>Okay gang,</FONT></P>
<P align=left><FONT face=Arial color=#000080 size=2> I need an opinion on
an idea I had. </FONT> </P>
<P align=left><FONT face=Arial color=#000080 size=2>Background: For the
past couple of years I have had to make a third copy of every full exchange
backup (I included the system state for the Exchange 2000 servers and the AD
Controllers) and ship it off-site</FONT> <FONT face=Arial color=#000080
size=2>with a</FONT><FONT face=Arial color=#000080 size=2>n infinite retention
period. I got the word last week that we will be stopping this practice
in
the next week or so due to the implementation of an active mail
archiving</FONT>
<FONT face=Arial color=#000080 size=2>system.</FONT></P>
<P align=left><FONT face=Arial color=#000080 size=2>Now there are 323 tapes in
this</FONT> <FONT face=Arial color=#000080 size=2>'</FONT><FONT face=Arial
color=#000080 size=2>Archive_Exchange</FONT><FONT face=Arial color=#000080
size=2>'</FONT><FONT face=Arial color=#000080 size=2> tape pool. The
original instructions said that at some point a contractor would take these
tapes, restore the data, scrub the duplicate messages and upload them to the
archive database.</FONT></P>
<P align=left><FONT face=Arial color=#000080 size=2>My current catalog backup
is
11 gig. I realize this is miniscule compared to serious implementations
of</FONT> <FONT face=Arial color=#000080 size=2>Netbackup</FONT><FONT
face=Arial
color=#000080 size=2>. My current Netbackup system is considered a point
solution so I don</FONT><FONT face=Arial color=#000080 size=2>'</FONT><FONT
face=Arial color=#000080 size=2>t backup that much.</FONT></P>
<P align=left><FONT face=Arial color=#000080 size=2>The Plan: Here is
what
I was considering doing. Perform a catalog backup to tape, wrap that tape
in bright red paper and store it with the archive tapes. Then I would
expire all of the archive tapes from the system and delete the tapes.</FONT>
<FONT face=Arial color=#000080 size=2> I will retain the most recent
tapes
in the database for a couple of months just in case.</FONT></P>
<P align=left><FONT face=Arial color=#000080 size=2>My reasoning behind this is
that I do not have the drive resources to perform the restores of these
tape</FONT><FONT face=Arial color=#000080 size=2>s</FONT><FONT face=Arial
color=#000080 size=2> in my producti</FONT><FONT face=Arial color=#000080
size=2>on environment and therefore the restore (if it ever happens) would need
to be done on a separate system</FONT><FONT face=Arial color=#000080
size=2>. Therefore I see no reason to retain the catalogs on my
production
system</FONT><FONT face=Arial color=#000080 size=2> and</FONT> <FONT face=Arial
color=#000080 size=2>can</FONT><FONT face=Arial color=#000080 size=2> reduce my
catalog size considerably.</FONT></P>
<P align=left><FONT face=Arial color=#000080 size=2>The Request: Okay
what
flaws are there in my plan? Bugs, holes, weaknesses, stupidity,
etc</FONT><FONT face=Arial color=#000080 size=2>...</FONT><FONT face=Arial
color=#000080 size=2>?</FONT></P>
<P align=left><FONT face=Arial color=#000080
size=2>Thanks</FONT></P><BR>CONFIDENTIALITY NOTICE: This e-mail message,
including any attachments, is for the sole use of the intended recipient(s) and
may contain confidential and privileged information or otherwise be protected
by
law. Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please contact the sender by reply e-mail
and destroy all copies of the original message. </BODY></HTML>
------_=_NextPart_001_01C44E37.36117CA0--
|