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_01C44E34.AA9F1FBC
Content-Type: text/plain
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 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_01C44E34.AA9F1FBC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3DUS-ASCI=
I">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2657.7=
3">
<TITLE>Request for Comment...</TITLE>
</HEAD>
<BODY>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Okay gang=
,</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> I =
need an opinion on an idea I had. </FONT> </P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Backgroun=
d: 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 CO=
LOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">with a</FONT><FONT COLOR=3D"#0000=
80" SIZE=3D2 FACE=3D"Arial">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 CO=
LOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">system.</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Now there=
are 323 tapes in this</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Ar=
ial">'</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Archive_Exch=
ange</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">'</FONT><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> 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 ar=
chive database.</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">My curren=
t catalog backup is 11 gig. I realize this is miniscule compared to=
serious implementations of</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D=
"Arial">Netbackup</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">.=
My current Netbackup system is considered a point solution so I do=
n</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">'</FONT><FONT COL=
OR=3D"#000080" SIZE=3D2 FACE=3D"Arial">t backup that much.</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">The Plan:=
Here is what I was considering doing. Perform a catalog back=
up to tape, wrap that tape in bright red paper and store it with the arch=
ive tapes. Then I would expire all of the archive tapes from the sy=
stem and delete the tapes.</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D=
"Arial"> I will retain the most recent tapes in the database for a =
couple of months just in case.</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">My reason=
ing behind this is that I do not have the drive resources to perform the =
restores of these tape</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Ari=
al">s</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> in my produc=
ti</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">on environment a=
nd therefore the restore (if it ever happens) would need to be done on a =
separate system</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">.&n=
bsp; Therefore I see no reason to retain the catalogs on my production sy=
stem</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> and</FONT> <F=
ONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">can</FONT><FONT COLOR=3D"#0=
00080" SIZE=3D2 FACE=3D"Arial"> reduce my catalog size considerably.</FON=
T></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">The Reque=
st: Okay what flaws are there in my plan? Bugs, holes, weakne=
sses, stupidity, etc</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial=
">...</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">?</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Thanks</F=
ONT></P>
</BODY>
</HTML>
<BR>
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,=20
is for the sole use of the intended recipient(s) and may contain confiden=
tial
and privileged information or otherwise be protected by law. Any unautho=
rized
review, use, disclosure or distribution is prohibited. If you are not th=
e
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.
------_=_NextPart_001_01C44E34.AA9F1FBC--
|
