Veritas-bu

[Veritas-bu] Tape Reclaimation

2006-01-30 09:13:36
Subject: [Veritas-bu] Tape Reclaimation
From: shekhar.dhotre AT lendlease DOT com (Dhotre, Shekhar)
Date: Mon, 30 Jan 2006 09:13:36 -0500
This is a multi-part message in MIME format.


------_=_NextPart_001_01C625A7.5C8B2C9F
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There is no reclamation in netbackup like TSM as far as I know =2E=0D=0A =
=0D=0A=0D=0AShekhar Dhotre=0D=0A=0D=0AICT Storage Engineering=2E =0D=0A=0D=
=0Av 404=2E846=2E7483 | f 404=2E848=2E1077 =0D=0A=0D=0AShekhar=2Edhotre@bov=
islendlease=2Ecom=0D=0A48 Perimeter Center East | Atlanta, GA  30346=0D=0A=
=0D=0A"Mistakes are a fact of life=2E It is the response to error that coun=
ts!" =0D=0A=0D=0A =0D=0A=0D=0A________________________________=0D=0A=0D=0AF=
rom: veritas-bu-admin@mailman=2Eeng=2Eauburn=2Eedu=0D=0A[mailto:veritas-bu-=
admin@mailman=2Eeng=2Eauburn=2Eedu] On Behalf Of Dean=0D=0ASent: Monday, Ja=
nuary 30, 2006 5:49 AM=0D=0ATo: David Rock; veritas-bu@mailman=2Eeng=2Eaubu=
rn=2Eedu=0D=0ASubject: Re: [Veritas-bu] Tape Reclaimation=0D=0A=0D=0A=0D=0A=
Coming from a mainframe background, I'd have to say that TSM-style=0D=0A"re=
clamation", or DFHSM-style "recycle", is something that would be very=0D=0A=
helpful in NetBackup=2E Compared to TSM and DFHSM, NBU is very inefficient=
=0D=0Ain it's tape usage, as David points out below=2E Of course, this=0D=
=0Areclamation does incur a fair processing overhead=2E =0D=0A=0D=0AI know =
of shops that try to tape reclamation via scriptiing, but it's=0D=0Afar fro=
m reliable=2E It would be nice to have the option built into NBU=2E=0D=0A=
=0D=0A/rant=0D=0A=0D=0A=0D=0A=0D=0AOn 1/27/06, David Rock <dave-bu@granitew=
eb=2Ecom> wrote: =0D=0A=0D=0A   * Mark=2EDonaldson@cexp=2Ecom <Mark=2EDonalds=
on@cexp=2Ecom> [2006-01-26=0D=0A09:05]:=0D=0A   > Your only way to do this is=
 to duplicate the images from=0D=0Apartially filled =0D=0A      > tapes to a 
con=
solidated pool, then delete the original images=2E=0D=0A        >=0D=0A > I 
suppos=
e you could automate this so that it's TSM-like=2E=0D=0A        >=0D=0A > 
However,=
 since Netbackup, by default, only groups like=0D=0Aretentions on a tape, =
=0D=0A  > all images on a tape should expire at roughly the same,=0D=0Aelimi=
nating the need=0D=0A   > to consolidate=2E=0D=0A       =0D=0A  That doesn't 
really =
hold up, though=2E if you have a tape with a 1=0D=0Ayear=0D=0A  retention on=
 it, and write a backup to it every week, the only=0D=0Away you =0D=0A  will=
 get it back is if it fills up completely so that nothing=0D=0Aelse can=0D=
=0A     write to it=2E  You have to remember that NetBackup does not use=0D=0As=
pace on=0D=0A   the tape that been vacated by earlier images until ALL images=
=0D=0Ahave=0D=0A        expired=2E  Plus, just because the default is to group 
sam=
e=0D=0Aretention=0D=0A  doesn't mean that you _can't_ mix retentions=2E  If =
you change the=0D=0A    retention of ONE of the images to a longer retention, =
the tape=0D=0Awon't be=0D=0A    reclaimed until that one image expires=2E =0D=
=0A     =0D=0A  --=0D=0A        David Rock=0D=0A        
david@graniteweb=2Ecom=0D=0A    _________=
______________________________________=0D=0A    Veritas-bu maillist  -  Verita=
s-bu@mailman=2Eeng=2Eauburn=2Eedu =0D=0A        
http://mailman=2Eeng=2Eauburn=2Eed=
u/mailman/listinfo/veritas-bu=0D=0A     =0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A---=
--------------------------------------=0D=0A"This email (including any atta=
chments) is confidential=2E  If you=0D=0Aare not the intended recipient you=
 must not copy, use, disclose,=0D=0Adistribute or rely on the information c=
ontained in it=2E  If you have=0D=0Areceived this email in error, please no=
tify the sender immediately=0D=0Aby reply email and delete the email from y=
our system=2E=0D=0AConfidentiality and legal privilege attached to this com=
munication=0D=0Aare not waived or lost by reason of mistaken delivery to yo=
u=2E  Lend=0D=0ALease does not guarantee that this email or the attachment(=
s) are=0D=0Aunaffected by computer virus, corruption or other defects=2E Le=
nd=0D=0ALease may monitor incoming and outgoing emails for compliance with=
=0D=0Aits Email Policy=2E  Please note that our servers may not be located=
=0D=0Ain your country=2E"=0D=0A
------_=_NextPart_001_01C625A7.5C8B2C9F
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<HTML>=0D=0A<BODY>=0D=0A<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4=2E0 Trans=
itional//EN">=0D=0A<HTML><HEAD>=0D=0A<META http-equiv=3DContent-Type conten=
t=3D"text/html; charset=3Dus-ascii">=0D=0A<META content=3D"MSHTML 6=2E00=2E=
2900=2E2802" name=3DGENERATOR></HEAD>=0D=0A<BODY>=0D=0A<DIV dir=3Dltr align=
=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =0D=0Aclass=3D093=
091214-30012006>There is no reclamation in netbackup like TSM as far as =0D=
=0AI know =2E</SPAN></FONT></DIV>=0D=0A<DIV>&nbsp;</DIV>=0D=0A<DIV align=3D=
left>=0D=0A<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt" align=3Dleft>=
<A =0D=0Aname=3DOLE_LINK2></A><A name=3DOLE_LINK1><SPAN =0D=0Astyle=3D"mso-=
bookmark: OLE_LINK2"><STRONG><SPAN =0D=0Astyle=3D"COLOR: gray; FONT-FAMILY:=
 'Arial Narrow'; mso-bidi-font-family: Arial">Shekhar =0D=0ADhotre</SPAN></=
STRONG><SPAN style=3D"COLOR: blue"><?xml:namespace prefix =3D o ns =3D =0D=
=0A"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></SPAN></A=
></P>=0D=0A<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN =0D=0As=
tyle=3D"mso-bookmark: OLE_LINK1"><SPAN style=3D"mso-bookmark: OLE_LINK2"><S=
PAN =0D=0Astyle=3D"FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: 'Arial Narrow=
'">ICT&nbsp;Storage =0D=0AEngineering=2E&nbsp;</SPAN></SPAN></SPAN></P>=0D=
=0A<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN =0D=0Astyle=3D"=
mso-bookmark: OLE_LINK1"><SPAN style=3D"mso-bookmark: OLE_LINK2"><SPAN =0D=
=0Astyle=3D"FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: 'Arial Narrow'">v 40=
4=2E846=2E7483 =0D=0A| f 404=2E848=2E1077 </SPAN></SPAN></SPAN></P>=0D=0A<P=
 class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN =0D=0Astyle=3D"mso-b=
ookmark: OLE_LINK1"><SPAN style=3D"mso-bookmark: OLE_LINK2"><U><SPAN =0D=0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial Narrow'">Shekhar=
=2Edhotre@bovislendlease=2Ecom</SPAN></U></SPAN></SPAN><SPAN =0D=0Astyle=3D=
"mso-bookmark: OLE_LINK1"><SPAN style=3D"mso-bookmark: OLE_LINK2"><SPAN =0D=
=0Astyle=3D"FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: 'Arial Narrow'"><BR>=
48 =0D=0APerimeter Center East | <?xml:namespace prefix =3D st1 ns =3D =0D=
=0A"urn:schemas-microsoft-com:office:smarttags" /><st1:place w:st=3D"on"><s=
t1:City =0D=0Aw:st=3D"on">Atlanta</st1:City>, <st1:State w:st=3D"on">GA</st=
1:State>&nbsp; =0D=0A<st1:PostalCode =0D=0Aw:st=3D"on">30346</st1:PostalCod=
e></st1:place></SPAN></SPAN></SPAN></P>=0D=0A<P class=3DMsoNormal style=3D"=
MARGIN: 0in 0in 0pt"><FONT face=3DVerdana size=3D2>"<FONT =0D=0Asize=3D1><F=
ONT color=3D#008000>Mistakes are a fact of life=2E It is the response to =
=0D=0Aerror that counts</FONT>!"</FONT> </FONT></P></DIV>=0D=0A<DIV>&nbsp;<=
/DIV><BR>=0D=0A<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr ali=
gn=3Dleft>=0D=0A<HR tabIndex=3D-1>=0D=0A<FONT face=3DTahoma size=3D2><B>Fro=
m:</B> veritas-bu-admin@mailman=2Eeng=2Eauburn=2Eedu =0D=0A[mailto:veritas-=
bu-admin@mailman=2Eeng=2Eauburn=2Eedu] <B>On Behalf Of =0D=0A</B>Dean<BR><B=
>Sent:</B> Monday, January 30, 2006 5:49 AM<BR><B>To:</B> David =0D=0ARock;=
 veritas-bu@mailman=2Eeng=2Eauburn=2Eedu<BR><B>Subject:</B> Re: [Veritas-bu=
] Tape =0D=0AReclaimation<BR></FONT><BR></DIV>=0D=0A<DIV></DIV>Coming from =
a mainframe background, I'd have to say that TSM-style =0D=0A"reclamation",=
 or DFHSM-style "recycle", is something that would be very helpful =0D=0Ain=
 NetBackup=2E Compared to TSM and DFHSM, NBU is very inefficient in it's ta=
pe =0D=0Ausage, as David points out below=2E Of course, this reclamation do=
es incur a fair =0D=0Aprocessing overhead=2E <BR><BR>I know of shops that t=
ry to tape reclamation via =0D=0Ascriptiing, but it's far from reliable=2E =
It would be nice to have the option =0D=0Abuilt into NBU=2E<BR><BR>/rant<BR=
><BR><BR>=0D=0A<DIV><SPAN class=3Dgmail_quote>On 1/27/06, <B class=3Dgmail_=
sendername>David =0D=0ARock</B> &lt;<A =0D=0Ahref=3D"mailto:dave-bu@granite=
web=2Ecom">dave-bu@graniteweb=2Ecom</A>&gt; =0D=0Awrote:</SPAN>=0D=0A<BLOCK=
QUOTE class=3Dgmail_quote =0D=0Astyle=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt=
 0pt 0=2E8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">* =0D=0A  <A href=3D=
"mailto:Mark=2EDonaldson@cexp=2Ecom";>Mark=2EDonaldson@cexp=2Ecom</A> &lt;<A=
 =0D=0A  href=3D"mailto:Mark=2EDonaldson@cexp=2Ecom";>Mark=2EDonaldson@cexp=
=2Ecom</A>&gt; =0D=0A  [2006-01-26 09:05]:<BR>&gt; Your only way to do this=
 is to duplicate the =0D=0A  images from partially filled <BR>&gt; tapes to=
 a consolidated pool, then =0D=0A  delete the original images=2E<BR>&gt;<BR=
>&gt; I suppose you could automate this =0D=0A  so that it's TSM-like=2E<BR=
>&gt;<BR>&gt; However, since Netbackup, by default, =0D=0A  only groups lik=
e retentions on a tape, <BR>&gt; all images on a tape should =0D=0A  expire=
 at roughly the same, eliminating the need<BR>&gt; to =0D=0A  consolidate=
=2E<BR><BR>That doesn't really hold up, though=2E if you have a tape =0D=0A=
  with a 1 year<BR>retention on it, and write a backup to it every week, th=
e =0D=0A  only way you <BR>will get it back is if it fills up completely so=
 that nothing =0D=0A  else can<BR>write to it=2E&nbsp;&nbsp;You have to rem=
ember that NetBackup does =0D=0A  not use space on<BR>the tape that been va=
cated by earlier images until ALL =0D=0A  images have<BR>expired=2E&nbsp;&n=
bsp;Plus, just because the default is to group =0D=0A  same retention<BR>do=
esn't mean that you _can't_ mix retentions=2E&nbsp;&nbsp;If =0D=0A  you cha=
nge the<BR>retention of ONE of the images to a longer retention, the =0D=0A=
  tape won't be<BR>reclaimed until that one image expires=2E <BR><BR>--<BR>=
David =0D=0A  Rock<BR><A =0D=0A  href=3D"mailto:david@graniteweb=2Ecom";>dav=
id@graniteweb=2Ecom</A><BR>_______________________________________________<=
BR>Veritas-bu =0D=0A  maillist&nbsp;&nbsp;-&nbsp;&nbsp;<A =0D=0A  href=3D"m=
ailto:Veritas-bu@mailman=2Eeng=2Eauburn=2Eedu">Veritas-bu@mailman=2Eeng=2Ea=
uburn=2Eedu =0D=0A  </A><BR><A =0D=0A  href=3D"http://mailman=2Eeng=2Eaubur=
n=2Eedu/mailman/listinfo/veritas-bu">http://mailman=2Eeng=2Eauburn=2Eedu/ma=
ilman/listinfo/veritas-bu</A><BR></BLOCKQUOTE></DIV><BR></BODY></HTML>=0D=
=0A=0D=0A=0D=0A<P><hr size=3D1></P>=0D=0A<P><STRONG>=0D=0A"This email (incl=
uding any attachments) is confidential=2E  If you<br>=0D=0Aare not the inte=
nded recipient you must not copy, use, disclose,<br>=0D=0Adistribute or rel=
y on the information contained in it=2E  If you have<br>=0D=0Areceived this=
 email in error, please notify the sender immediately<br>=0D=0Aby reply ema=
il and delete the email from your system=2E<br>=0D=0AConfidentiality and le=
gal privilege attached to this communication<br>=0D=0Aare not waived or los=
t by reason of mistaken delivery to you=2E  Lend<br>=0D=0ALease does not gu=
arantee that this email or the attachment(s) are<br>=0D=0Aunaffected by com=
puter virus, corruption or other defects=2E Lend<br>=0D=0ALease may monitor=
 incoming and outgoing emails for compliance with<br>=0D=0Aits Email Policy=
=2E  Please note that our servers may not be located<br>=0D=0Ain your count=
ry=2E"=0D=0A</STRONG></P>=0D=0A</BODY>=0D=0A</HTML>=0D=0A
------_=_NextPart_001_01C625A7.5C8B2C9F--


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