Veritas-bu

[Veritas-bu] restrict only one volume pool from returning expired media to Scratch.

2005-08-17 10:38:14
Subject: [Veritas-bu] restrict only one volume pool from returning expired media to Scratch.
From: Gregory.Geyer AT Avnet DOT com (Geyer, Gregory)
Date: Wed, 17 Aug 2005 07:38:14 -0700
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5A339.4CD6D9B2
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

IF you have a separate media server for this group and IF you have a
sophisticated robot you could possibly limit tape access to different
media servers.  In other words media server B can't see tapes that start
with 333, while media server A can't see tapes that start with 222.  So
tapes would return to scratch but wouldn't be picked up by competing
media servers.
=20
I am just theorizing as I don't know for sure if this would work for
you.  I'm looking at a similar issue, but with two masters sharing the
same ACS robotics.  But in that case there are two separate volume
databases, not one.

________________________________

From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Paul
Keating
Sent: Tuesday, August 16, 2005 9:36 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] restrict only one volume pool from returning
expired media to Scratch.


in general, I want all expired media to return to scratch for ease of
administration, etc.
=20
I have one application group that, due to some security requirements,
cannot have any tape returned to scratch once it's been assigned.
=20
basically, the data in this environment is protected, so once it is
written to tape, those tapes are considered "protected".
=20
Right now, according to policy, once a disk is "protected", that's the
end of the line......it's tagged protect for ever, even if it's
overwritten with unprotected data.
=20
So, I need to create a volume pool for this application group, and I
would prefer for this volume group to be able to pull tapes from
scratch, IF necessary, but never return them to scratch.
=20
If I understand correctly, netbackup will only release tapes back to
scratch, if they were pulled from scratch to begin with, so if I ensure
that this pool is provisioned manually, it will never pull from scratch,
and therefore never return tapes to scratch......this could be a
possible solution, but I'm worried about the occasion where the pool was
underprovisioned and pulled a tape from scratch....once expired, it
would go back to scratch.
=20
Paul

------_=_NextPart_001_01C5A339.4CD6D9B2
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>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875432514-17082005><FONT =
face=3D"Courier New"=20
color=3D#0000ff size=3D2>IF you have a separate media server for this =
group and IF=20
you have a sophisticated robot you could possibly limit tape access to =
different=20
media servers.&nbsp; In other words media server B can't see tapes that =
start=20
with 333, while media server A can't see tapes that start with =
222.&nbsp; So=20
tapes would return to scratch but wouldn't be picked up by competing =
media=20
servers.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875432514-17082005><FONT =
face=3D"Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875432514-17082005><FONT =
face=3D"Courier New"=20
color=3D#0000ff size=3D2>I am just theorizing as I don't know for sure =
if this would=20
work for you.&nbsp; I'm looking at a similar issue, but with two masters =
sharing=20
the same ACS robotics.&nbsp; But in that case there are two separate =
volume=20
databases, not one.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><BR></DIV>
<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>Paul=20
Keating<BR><B>Sent:</B> Tuesday, August 16, 2005 9:36 AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
restrict only=20
one volume pool from returning expired media to =
Scratch.<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial size=3D2>in =
general, I want=20
all expired media to return to scratch for ease of administration,=20
etc.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial size=3D2>I have =
one=20
application group that, due to some security requirements, cannot have =
any tape=20
returned to scratch once it's been assigned.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial =
size=3D2>basically, the data=20
in this environment is protected, so once it is written to tape, those =
tapes are=20
considered "protected".</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial size=3D2>Right =
now, according=20
to policy, once a disk is "protected", that's the end of the =
line......it's=20
tagged protect for ever, even if it's overwritten with unprotected=20
data.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial size=3D2>So, I =
need to create=20
a volume pool for this application group, and I would prefer for this =
volume=20
group to be able to pull tapes from scratch, IF necessary, but never =
return them=20
to scratch.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial size=3D2>If I =
understand=20
correctly, netbackup will only release tapes back to scratch, if they =
were=20
pulled from scratch to begin with, so if I ensure that this pool is =
provisioned=20
manually, it will never pull from scratch, and therefore never return =
tapes to=20
scratch......this could be a possible solution, but I'm worried about =
the=20
occasion where the pool was underprovisioned and pulled a tape from=20
scratch....once expired, it would go back to =
scratch.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2>Paul</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C5A339.4CD6D9B2--