This is a multi-part message in MIME format.
------=_NextPart_000_0015_01C67720.26B82920
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
You can clean up the "invalid" images the same way. I have sometimes seen
that the images are actually on tape, but the ".ds" file did not get
created.
bpimagelist will show you if it duped to tape.
You can also dupe the image yourself. If bpimagelist shows you that the
image is in the database, I would try to do a bplist of the image. If you
can see the files in the image, then it is a valid image.
Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee 37421
423-296-8200
_____
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Hillman,
Eric
Sent: Saturday, May 13, 2006 9:59 AM
To: bobbyrjw AT bellsouth DOT net; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] What command cleans out DSSU's?
Booby,
Thank you! It's actually not the valid images that automaticatlly get
removed that I am trying to clean. It's the invalid image files that get
left on disk when jobs fail that I need to find and clean. The only way I
know of is to wait until I get error code 190's when manually running
archival to tape and then finding all *.F1 files without a corresponding .ds
extention. Then I can remove all of those image files that belong to that
invalid image.
_____
From: Bobby Williams [mailto:bobbyrjw AT bellsouth DOT net]
Sent: Saturday, May 13, 2006 7:07 AM
To: Hillman, Eric; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] What command cleans out DSSU's?
First, look at your global setting of "maximum copies". If it is higher
than 2, this will give you more copies.
Also, go to the storage units area of the GUI and manually run the staging
to make sure that you are up to date.
On the dssu, there are files (all less than 2GB) named
{system_name}_{utime}_F$$ and there are files of "0" size named the same but
with "ds" at the end.
The file with the "ds" at the end are files that NB thinks it has put on
disk. The other files are the backup images named (in the above format) as
the backupid and the fragment number (dsu and dssu are limited to 2GB
fragments).
All NB is doing on the dssu is duplicating the images to tape. Copy 1 is on
disk, copy 2 (thru ...) is on tape. When the duplication process completes
successfully (the way it is designed anyway), the backupid_fragment.ds file
is created to let NB that it can be purged if necessary.
You can check each file that ends in F1 (fragment 1) and use bpimagelist to
see how many copies you have. If the ds file version of the file exists,
you should show copy 1 or primary to be on the DSSU and copy 2 to be on tape
(or wherever you stage to).
If you can verify that you have 2 copies, you can use "bpexpdate -d 0 -copy
1 -backid {backupid} -force" to expire the copy that is on disk.
That will clear up the DSSU.
Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee 37421
423-296-8200
_____
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Hillman,
Eric
Sent: Friday, May 12, 2006 2:55 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] What command cleans out DSSU's?
We use Disk Staging Storage Units in our Netbackup 5.0 MP5 environment.
When jobs fail for whatever reason, the image files created up to that point
still stay on disk. At some point, they get removed by Netbackup, but it's
not immediate. This used to be a huge problem pre mp5. In MP5, Veritas
added better cleanup processes, but they don't go into detail as to how it
works. Can someone tell me what process goes through DSSU's looking for
invalid images to remove and when that process runs? Also, is it possible
to run that process manually at will?
Thanks in advance for any help!
THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE
PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM
DISCLOSURE. If the reader of this message is not the intended recipient, you
are hereby notified that any dissemination, distribution, copying or use of
this message and any attachment is strictly prohibited. If you have received
this message in error, please notify us immediately by replying to the
message and permanently delete it from your computer and destroy any
printout thereof.
THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE
PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM
DISCLOSURE. If the reader of this message is not the intended recipient, you
are hereby notified that any dissemination, distribution, copying or use of
this message and any attachment is strictly prohibited. If you have received
this message in error, please notify us immediately by replying to the
message and permanently delete it from your computer and destroy any
printout thereof.
------=_NextPart_000_0015_01C67720.26B82920
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>What command cleans out DSSU's?</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D000162810-14052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>You can clean up the "invalid" images the same =
way. I=20
have sometimes seen that the images are actually on tape, but the ".ds" =
file did=20
not get created.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D000162810-14052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D000162810-14052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>bpimagelist will show you if it duped to=20
tape.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D000162810-14052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D000162810-14052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>You can also dupe the image yourself. If =
bpimagelist=20
shows you that the image is in the database, I would try to do a bplist =
of the=20
image. If you can see the files in the image, then it is a valid=20
image. </FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format --><BR><BR>
<P><SPAN lang=3Den-us><FONT face=3DArial color=3D#000080>Bobby =
Williams</FONT></SPAN>=20
<BR><SPAN lang=3Den-us><FONT face=3DArial color=3D#008080 size=3D2>2205 =
Peterson=20
Drive</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
color=3D#008080=20
size=3D2>Chattanooga, Tennessee 37421</FONT></SPAN> <BR><SPAN=20
lang=3Den-us><FONT face=3DArial color=3D#008080 =
size=3D2>423-296-8200</FONT></SPAN> </P>
<DIV> </DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
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>Hillman,=20
Eric<BR><B>Sent:</B> Saturday, May 13, 2006 9:59 AM<BR><B>To:</B>=20
bobbyrjw AT bellsouth DOT net; =
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE:=20
[Veritas-bu] What command cleans out DSSU's?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D088315213-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Booby,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D088315213-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2> Thank you! It's actually not the =
valid images=20
that automaticatlly get removed that I am trying to clean. It's =
the=20
invalid image files that get left on disk when jobs fail that I need to =
find and=20
clean. The only way I know of is to wait until I get error code =
190's when=20
manually running archival to tape and then finding all *.F1 files =
without a=20
corresponding .ds extention. Then I can remove all of those image =
files=20
that belong to that invalid image. </FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Bobby Williams=20
[mailto:bobbyrjw AT bellsouth DOT net] <BR><B>Sent:</B> Saturday, May 13, 2006 =
7:07=20
AM<BR><B>To:</B> Hillman, Eric;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
What=20
command cleans out DSSU's?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>First, look at your global setting of "maximum=20
copies". If it is higher than 2, this will give you more=20
copies.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Also, go to the storage units area of the GUI =
and manually=20
run the staging to make sure that you are up to =
date.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>On the dssu, there are files (all less than =
2GB) named=20
{system_name}_{utime}_F$$ and there are files of "0" size named the same =
but=20
with "ds" at the end.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The file with the "ds" at the end are files =
that NB thinks=20
it has put on disk. The other files are the backup images named =
(in the=20
above format) as the backupid and the fragment number (dsu and dssu are =
limited=20
to 2GB fragments).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>All NB is doing on the dssu is duplicating the =
images to=20
tape. Copy 1 is on disk, copy 2 (thru ...) is on tape. When =
the=20
duplication process completes successfully (the way it is designed =
anyway), the=20
backupid_fragment.ds file is created to let NB that it can be purged if=20
necessary.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>You can check each file that ends in F1 =
(fragment 1) and=20
use bpimagelist to see how many copies you have. If the ds file =
version of=20
the file exists, you should show copy 1 or primary to be on the DSSU and =
copy 2=20
to be on tape (or wherever you stage to).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If you can verify that you have 2 copies, you =
can use=20
"bpexpdate -d 0 -copy 1 -backid {backupid} -force" to expire the copy =
that is on=20
disk. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>That will clear up the =
DSSU.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D187445610-13052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV> </DIV><!-- Converted from text/rtf format --><BR><BR>
<P><SPAN lang=3Den-us><FONT face=3DArial color=3D#000080>Bobby =
Williams</FONT></SPAN>=20
<BR><SPAN lang=3Den-us><FONT face=3DArial color=3D#008080 size=3D2>2205 =
Peterson=20
Drive</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
color=3D#008080=20
size=3D2>Chattanooga, Tennessee 37421</FONT></SPAN> <BR><SPAN=20
lang=3Den-us><FONT face=3DArial color=3D#008080 =
size=3D2>423-296-8200</FONT></SPAN> </P>
<DIV> </DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
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>Hillman,=20
Eric<BR><B>Sent:</B> Friday, May 12, 2006 2:55 PM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] What =
command=20
cleans out DSSU's?<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>We use Disk Staging Storage Units in our =
Netbackup=20
5.0 MP5 environment. When jobs fail for whatever reason, the image =
files=20
created up to that point still stay on disk. At some point, they =
get=20
removed by Netbackup, but it's not immediate. This used to be a =
huge=20
problem pre mp5. In MP5, Veritas added better cleanup processes, =
but they=20
don't go into detail as to how it works. Can someone tell me what =
process=20
goes through DSSU's looking for invalid images to remove and when that =
process=20
runs? Also, is it possible to run that process manually at=20
will?</FONT></P>
<P><FONT face=3DArial size=3D2>Thanks in advance for any help!</FONT> =
</P><BR>THE=20
INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE =
PRIVILEGED,=20
CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the =
reader=20
of this message is not the intended recipient, you are hereby notified =
that any=20
dissemination, distribution, copying or use of this message and any =
attachment=20
is strictly prohibited. If you have received this message in error, =
please=20
notify us immediately by replying to the message and permanently delete =
it from=20
your computer and destroy any printout thereof. <BR>THE INFORMATION =
CONTAINED IN=20
THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, =
PROPRIETARY OR=20
OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is =
not the=20
intended recipient, you are hereby notified that any dissemination,=20
distribution, copying or use of this message and any attachment is =
strictly=20
prohibited. If you have received this message in error, please notify us =
immediately by replying to the message and permanently delete it from =
your=20
computer and destroy any printout thereof.</BODY></HTML>
------=_NextPart_000_0015_01C67720.26B82920--
|
