This is a multi-part message in MIME format.
------=_NextPart_000_02AA_01C260A6.3C4ECCB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by dsihost-srv01.com id
NAA06349
Will not work on an expired tapes. However, if you freeze a tape and it
expires, it remains frozen and will show 0 images when you do a
bpmedialist -ev $ID -h $host
At that point you may bpimport that expired tape, all of the data is stil=
l
intact and you retain the ability to re-create the entries in the db with
the contents.
David
<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
Backup Storage Consultant
DataStaff, Inc.
http://www.datastaff.com
312 683 1144
---------------------------------------
-----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 W. Curtis
Preston
Sent: Friday, September 20, 2002 12:17 PM
To: 'Chris Madden'; Veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] How to handle "infinite" retention while
maintaining a reasonable catalog size?
No, there is nothing like this in NetBackup, and I wish there was. Onc=
e a
piece of media has been expired, you lose everything about it, and it wil=
l
be overwritten. You could build your own database by doing a bpmedialist
before expiring the tape, then expiring it. You have to make sure it=92s=
out
of the library, though, or it will be overwritten. (You may be able to u=
se
bpmedia =96freeze to prevent this as well, but I=92m not sure how that wi=
ll work
on an expired tape.)
-----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 Chris
Madde=
n
Sent: Wednesday, September 18, 2002 8:29 AM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] How to handle "infinite" retention while maintain=
ing
a reasonable catalog size?
All,
We have a business requirement to keep our full monthly backups for an
"infinite" period. While I can't minimize the additional media purchases=
to
support this business requirement I am looking for a way to minimize the
catalog growth that will accompany it. I have more experience with Legat=
o
NetWorker and in that environment there is an ability to purge the "clien=
t
file index" for a backup image while retaining the media database entry.
This allows the bulk of the data (the list of files) to be blown away but
still leaves the backup image entry itself so we still know what saveset =
is
on what tape(s).
Is there a similar functionality in NetBackup? I think not but perhaps
there are some other tricks or techniques that can allow me to accomplish
the same thing? I had thought about archiving the older client indexes
(perhaps after 1 yr) and then come client restore time I would first need=
to
restore that client's indexes for that point in time on the backup server
itself before trying to restore anything for the client (and of course I'=
d
keep the indexes for the backup server itself online for an infinite
period). Don't quite know how this strategy would play out though come t=
ime
to upgrade to 4.5 with the binary DB structure....
Any comments from those who have solved this problem or would solve thi=
s
problem are appreciated.
Regards,
-Chris
P.S. As an aside, today we're running at about 900 GB compressed (after=
2
weeks) on our catalogs and are soon going to pass the 1TB mark also
requiring a 2nd filesystem due to Veritas LVM limitations at 1TB on a sin=
gle
volume and will then have to symmlink some beefy client indexes onto a 2n=
d
filesystem. Yuck!
------=_NextPart_000_02AA_01C260A6.3C4ECCB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue bgColor=3Dwhite>
<DIV><SPAN class=3D741434917-20092002><FONT face=3DArial color=3D#0000ff =
size=3D2>Will=20
not work on an expired tapes. However, if you freeze a tape and it =
expires, it remains frozen and will show 0 images when you do a =
bpmedialist -ev=20
$ID -h $host</FONT></SPAN></DIV>
<DIV><SPAN class=3D741434917-20092002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D741434917-20092002><FONT face=3DArial color=3D#0000ff =
size=3D2>At=20
that point you may bpimport that expired tape, all of the data is still =
intact=20
and you retain the ability to re-create the entries in the db with the=20
contents.</FONT></SPAN></DIV>
<DIV><SPAN class=3D741434917-20092002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D741434917-20092002><FONT face=3DArial color=3D#0000ff =
size=3D2>David</FONT></SPAN></DIV>
<DIV> </DIV>
<P><FONT=20
size=3D2><><><><><><><><>=
<><><><><><><><><>&=
lt;><><><BR>David=20
A. Chapa<BR>Backup Storage Consultant<BR>DataStaff, Inc.<BR><A=20
href=3D"http://www.datastaff.com/"=20
target=3D_blank>http://www.datastaff.com</A><BR>312 683=20
1144<BR>---------------------------------------</FONT> </P>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader 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>W.
=
Curtis=20
Preston<BR><B>Sent:</B> Friday, September 20, 2002 12:17 =
PM<BR><B>To:</B>=20
'Chris Madden'; Veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> =
RE:=20
[Veritas-bu] How to handle "infinite" retention while maintaining a =
reasonable=20
catalog size?<BR><BR></FONT></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">No, there =
is nothing=20
like this in NetBackup, and I wish there was. Once a piece of =
media has=20
been expired, you lose everything about it, and it will be =
overwritten. You=20
could build your own database by doing a bpmedialist before expiring =
the tape,=20
then expiring it. You have to make sure it’s out of the =
library, though,=20
or it will be overwritten. (You may be able to use bpmedia =
–freeze to=20
prevent this as well, but I’m not sure how that will work on an =
expired=20
tape.)</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT> </P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DTahoma =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B>=20
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B><SPAN=20
style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Chris =
Madden<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, September 18, =
2002 8:29=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
Veritas-bu AT mailman.eng.auburn DOT edu<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [Veritas-bu] How to =
handle=20
"infinite" retention while maintaining a reasonable catalog=20
size?</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT> </P>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">All,</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We have a=20
business requirement to keep our full monthly backups for an =
"infinite" period. While I can't minimize the additional =
media=20
purchases to support this business requirement I am looking for a way =
to=20
minimize the catalog growth that will accompany it. I have more=20
experience with Legato NetWorker and in that environment there is an =
ability=20
to purge the "client file index" for a backup image while retaining =
the=20
media database entry. This allows the bulk of the data (the =
list of=20
files) to be blown away but still leaves the backup image entry itself =
so we=20
still know what saveset is on what tape(s). =
</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there a similar =
functionality=20
in NetBackup? I think not but perhaps there are some other =
tricks or=20
techniques that can allow me to accomplish the same thing? I had =
thought=20
about archiving the older client indexes (perhaps after 1 yr) and then =
come=20
client restore time I would first need to restore that client's =
indexes for=20
that point in time on the backup server itself before trying =
to=20
restore anything for the client (and of course I'd keep =
the indexes for=20
the backup server itself online for an infinite period). Don't =
quite=20
know how this strategy would play out though come time to upgrade to =
4.5 with=20
the binary DB structure....</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Any comments from those =
who have=20
solved this problem or would solve this problem are appreciated. =
</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Chris</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">P.S. As an aside, today =
we're=20
running at about 900 GB compressed (after 2 weeks) on our =
catalogs and=20
are soon going to pass the 1TB mark also requiring a 2nd filesystem =
due to=20
Veritas LVM limitations at 1TB on a single volume and will then =
have to=20
symmlink some beefy client indexes onto a 2nd filesystem. =20
Yuck!</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_02AA_01C260A6.3C4ECCB0--
|
