This is a multipart message in MIME format.
--=_alternative 005F9F4480257138_=
Content-Type: text/plain; charset="us-ascii"
Hi Phil,
you have over estimated the complexity of the NBU catalog, the image
catalog is not a real database, its a filesystem structure containing a
large number of monolithic binary files for each backup images stored - so
there is no way the catalog can become fragmented as it isnt composed of
real database files like Oracle etc. When an image is expired the
corresponding file from the catalog filesystem is removed thereby freeing
space.
As to why you see growth, couldn't tell you sorry......
thanks Andy.
"Stockton, Phil" <Phil.Stockton AT rs-components DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
21/03/2006 15:51
To: <veritas-bu AT mailman.eng.auburn DOT edu>
cc:
Subject: [Veritas-bu] Catalog Question
Hi Everybody,
Netbackup 5.0 MP3 on Solaris 8. Clients are a mixture of Windows, NT and
2000 and Unix Solaris.
I'm aware of the ability to compress/cleanup images etc via the bpimage
command but have a question regarding how this works.
When images are expired/deleted from the catalog, is there any way to
reorg. the catalog so that fragmentation within the catalog is minimised.
Our catalog is 50 gb and growing with no increase in the numbers of
clients. I accept that the number of files per client is increasing but
not materially. Is there something we've missed configuration wise here?
Regards
Phil
***************************************************************
The contents of this Email and any files transmitted with it
are confidential and intended solely for the use of the
individual or entity to whom it is addressed. The views stated
herein do not necessarily represent the view of the company.
If you are not the intended recipient of this Email you may not
copy, forward, disclose or otherwise use it or any part of it
in any form whatsoever. If you have received this mail in
error please Email the sender.
***************************************************************
RS Components Ltd.
--=_alternative 005F9F4480257138_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">Hi Phil,</font>
<br>
<br><font size=2 face="sans-serif"> you have over estimated the
complexity of the NBU catalog, the image catalog is not a real database, its a
filesystem structure containing a large number of monolithic binary files for
each backup images stored - so there is no way the catalog can become
fragmented as it isnt composed of real database files like Oracle etc. When an
image is expired the corresponding file from the catalog filesystem is removed
thereby freeing space.</font>
<br><font size=2 face="sans-serif">As to why you see growth, couldn't tell you
sorry......</font>
<br>
<br><font size=2 face="sans-serif">
thanks Andy.</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Stockton, Phil"
<Phil.Stockton AT rs-components DOT com></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">21/03/2006 15:51</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
<veritas-bu AT mailman.eng.auburn DOT edu></font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
[Veritas-bu] Catalog Question</font></table>
<br>
<br>
<br><font size=2 face="Arial">Hi Everybody,</font><font size=3 face="Times New
Roman"> </font>
<p><font size=2 face="Arial">Netbackup 5.0 MP3 on Solaris 8. Clients are
a mixture of Windows, NT and 2000 and Unix Solaris.</font><font size=3
face="Times New Roman"> </font>
<p><font size=2 face="Arial">I'm aware of the ability to compress/cleanup
images etc via the bpimage command but have a question regarding how this
works.</font>
<p><font size=2 face="Arial">When images are expired/deleted from the catalog,
is there any way to reorg. the catalog so that fragmentation within the catalog
is minimised. </font>
<p><font size=2 face="Arial">Our catalog is 50 gb and growing with no increase
in the numbers of clients. I accept that the number of files per
client is increasing but not materially. Is there something we've missed
configuration wise here?</font>
<p><font size=2 face="Arial">Regards</font><font size=3 face="Times New Roman">
</font>
<p><font size=2 face="Arial">Phil</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
</font><font size=3 face="Times New Roman"> </font>
<p><font size=3 face="Times New Roman"><br>
<br>
<br>
***************************************************************<br>
The contents of this Email and any files transmitted with it<br>
are confidential and intended solely for the use of the <br>
individual or entity to whom it is addressed. The views stated<br>
herein do not necessarily represent the view of the company.<br>
If you are not the intended recipient of this Email you may not<br>
copy, forward, disclose or otherwise use it or any part of it<br>
in any form whatsoever. If you have received this mail in <br>
error please Email the sender. <br>
***************************************************************<br>
<br>
RS Components Ltd.</font>
<p>
<p>
--=_alternative 005F9F4480257138_=--
|
