------_=_NextPart_001_01C67695.64372C17
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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_001_01C67695.64372C17
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>What command cleans out DSSU's?</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=088315213-13052006><FONT face=Arial
color=#0000ff size=2>Booby,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=088315213-13052006><FONT face=Arial
color=#0000ff size=2> 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. </FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Bobby Williams
[mailto:bobbyrjw AT bellsouth DOT net] <BR><B>Sent:</B> Saturday, May 13, 2006
7:07
AM<BR><B>To:</B> Hillman, Eric;
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
What
command cleans out DSSU's?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>First, look at your global setting of "maximum
copies". If it is higher than 2, this will give you more
copies.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>Also, go to the storage units area of the GUI and manually
run the staging to make sure that you are up to date.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>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).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>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).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>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. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2>That will clear up the DSSU.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=187445610-13052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV> </DIV><!-- Converted from text/rtf format --><BR><BR>
<P><SPAN lang=en-us><FONT face=Arial color=#000080>Bobby Williams</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#008080 size=2>2205 Peterson
Drive</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#008080
size=2>Chattanooga, Tennessee 37421</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#008080 size=2>423-296-8200</FONT></SPAN> </P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> veritas-bu-admin AT mailman.eng.auburn
DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of
</B>Hillman,
Eric<BR><B>Sent:</B> Friday, May 12, 2006 2:55 PM<BR><B>To:</B>
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] What
command
cleans out DSSU's?<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial size=2>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?</FONT></P>
<P><FONT face=Arial size=2>Thanks in advance for any help!</FONT> </P><BR>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. </BODY></HTML>
<br>
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_001_01C67695.64372C17--
|
