Veritas-bu

[Veritas-bu] disk storage units

2005-07-29 13:52:43
Subject: [Veritas-bu] disk storage units
From: rich.dellaripa AT cingular DOT com (Dellaripa, Rich)
Date: Fri, 29 Jul 2005 13:52:43 -0400
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_01C59466.5249F200
Content-Type: text/plain

We do duplication using scripted bpduplicates. I'm curious, then, where
these ".ds" files come from and what creates them. 

-----Original Message-----
From: Geyer, Gregory [mailto:Gregory.Geyer AT Avnet DOT com] 
Sent: Thursday, July 28, 2005 5:55 PM
To: Jack L. Forester, Jr.; Veritas List
Subject: RE: [Veritas-bu] disk storage units

It depends on what type of duplication.  A DSSU job will leave the *.ds
file there and thus the image is then eligible to be removed if space is
needed.

A vault duplication however actually impedes the process.  Vault will
create a copy 2 of the image, but will not leave the *.ds (as your vault
job may expire in a much shorter time).  Then when the DSSU job kicks
off it will fail to stage the image to tape saying that "copy 2 already
exists".

This is something I want changed....if it hasn't been staged with a DSSU
job but vault has done its job first, stage it and make it copy 3.
 

-----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 Jack L.
Forester, Jr.
Sent: Thursday, July 28, 2005 7:58 AM
To: Veritas List
Subject: Re: [Veritas-bu] disk storage units

If I'm not mistaken, images are candidates for removal from the DSSU
after they have been duplicated to tape.  NBU will remove these images
if it needs to make room.

 From the NBU 5.1 Sysadmin guide, volume 1:

"When a Stage I process detects a full disk staging storage unit, it
pauses the backup, finds the oldest image that has been successfully
copied to the destination storage unit, and expires this image copy."

Paul Keating wrote:

>But even frequent duplication won't ensure the DSSU won't fill....
>The image remains on DSSU after duplication.
>
>From what I understand, it only gets flushed from the DSSU when a new 
>backup job determines there is insufficient room on the DSSU, at which 
>time, the two old images on the DSSU, that have already been duped to 
>tape, will be flushed from the DSSU.
>
>Also, if I still understand correctly, if that New job going to DSSU is

>bigger than the two oldest jobs that were flushed, then the job will 
>still fill the DSSU and fail.
>
>My DSSUs usually sit at 99%.
>
>Paul
>
>  
>
>>-----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 Ed Wilts
>>Sent: July 28, 2005 9:59 AM
>>To: Arne Kloecker
>>Cc: veritas-bu AT mailman.eng.auburn DOT edu
>>Subject: Re: [Veritas-bu] disk storage units
>>
>>
>>
>>Currently, you need to schedule your duplication jobs more frequently 
>>to ensure that your DSSU won't fill.
>>
>>    
>>
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>  
>


--
Jack L. Forester, Jr.
UNIX Systems Administrator, Stf
Lockheed Martin Information Technology
(304) 625-3946

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


------_=_NextPart_001_01C59466.5249F200
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] disk storage units</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>We do duplication using scripted bpduplicates. I'm =
curious, then, where these &quot;.ds&quot; files come from and what =
creates them. </FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Geyer, Gregory [<A =
HREF=3D"mailto:Gregory.Geyer AT Avnet DOT com">mailto:Gregory.Geyer AT Avnet 
DOT com</=
A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, July 28, 2005 5:55 PM</FONT>
<BR><FONT SIZE=3D2>To: Jack L. Forester, Jr.; Veritas List</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] disk storage units</FONT>
</P>

<P><FONT SIZE=3D2>It depends on what type of duplication.&nbsp; A DSSU =
job will leave the *.ds</FONT>
<BR><FONT SIZE=3D2>file there and thus the image is then eligible to be =
removed if space is</FONT>
<BR><FONT SIZE=3D2>needed.</FONT>
</P>

<P><FONT SIZE=3D2>A vault duplication however actually impedes the =
process.&nbsp; Vault will</FONT>
<BR><FONT SIZE=3D2>create a copy 2 of the image, but will not leave the =
*.ds (as your vault</FONT>
<BR><FONT SIZE=3D2>job may expire in a much shorter time).&nbsp; Then =
when the DSSU job kicks</FONT>
<BR><FONT SIZE=3D2>off it will fail to stage the image to tape saying =
that &quot;copy 2 already</FONT>
<BR><FONT SIZE=3D2>exists&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>This is something I want changed....if it hasn't been =
staged with a DSSU</FONT>
<BR><FONT SIZE=3D2>job but vault has done its job first, stage it and =
make it copy 3.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu">mailto:veritas-b=
u-admin AT mailman.eng.auburn DOT edu</A>] On Behalf Of Jack L.</FONT>
<BR><FONT SIZE=3D2>Forester, Jr.</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, July 28, 2005 7:58 AM</FONT>
<BR><FONT SIZE=3D2>To: Veritas List</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] disk storage units</FONT>
</P>

<P><FONT SIZE=3D2>If I'm not mistaken, images are candidates for =
removal from the DSSU</FONT>
<BR><FONT SIZE=3D2>after they have been duplicated to tape.&nbsp; NBU =
will remove these images</FONT>
<BR><FONT SIZE=3D2>if it needs to make room.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;From the NBU 5.1 Sysadmin guide, volume =
1:</FONT>
</P>

<P><FONT SIZE=3D2>&quot;When a Stage I process detects a full disk =
staging storage unit, it</FONT>
<BR><FONT SIZE=3D2>pauses the backup, finds the oldest image that has =
been successfully</FONT>
<BR><FONT SIZE=3D2>copied to the destination storage unit, and expires =
this image copy.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>Paul Keating wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt;But even frequent duplication won't ensure the =
DSSU won't fill....</FONT>
<BR><FONT SIZE=3D2>&gt;The image remains on DSSU after =
duplication.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;From what I understand, it only gets flushed =
from the DSSU when a new </FONT>
<BR><FONT SIZE=3D2>&gt;backup job determines there is insufficient room =
on the DSSU, at which </FONT>
<BR><FONT SIZE=3D2>&gt;time, the two old images on the DSSU, that have =
already been duped to </FONT>
<BR><FONT SIZE=3D2>&gt;tape, will be flushed from the DSSU.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Also, if I still understand correctly, if that =
New job going to DSSU is</FONT>
</P>

<P><FONT SIZE=3D2>&gt;bigger than the two oldest jobs that were =
flushed, then the job will </FONT>
<BR><FONT SIZE=3D2>&gt;still fill the DSSU and fail.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;My DSSUs usually sit at 99%.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Paul</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;From: =
veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;[<A =
HREF=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu">mailto:veritas-b=
u-admin AT mailman.eng.auburn DOT edu</A>] On Behalf Of Ed Wilts</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;Sent: July 28, 2005 9:59 AM</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;To: Arne Kloecker</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;Cc: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;Subject: Re: [Veritas-bu] disk storage =
units</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;Currently, you need to schedule your =
duplication jobs more frequently </FONT>
<BR><FONT SIZE=3D2>&gt;&gt;to ensure that your DSSU won't fill.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT =
SIZE=3D2>&gt;_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt;Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu </FONT>
<BR><FONT SIZE=3D2>&gt;<A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>--</FONT>
<BR><FONT SIZE=3D2>Jack L. Forester, Jr.</FONT>
<BR><FONT SIZE=3D2>UNIX Systems Administrator, Stf</FONT>
<BR><FONT SIZE=3D2>Lockheed Martin Information Technology</FONT>
<BR><FONT SIZE=3D2>(304) 625-3946</FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C59466.5249F200--

<Prev in Thread] Current Thread [Next in Thread>