This is a multi-part message in MIME format.
------_=_NextPart_001_01C5A4DD.21B39AA8
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
So, if I understand correctly, when setting up a secondary media server,
I would configure the drives to see the media server as the "device
host" but select "drive is in a robotic library" and then select the
library that the drives are in, and enter the drive number, and the
master server will be the robotic control host, correct?
=20
that way, any backups to this secondary media server will only be able
to go to drives that have been allocated to it in the way?
=20
Might be a stupid question, but I'm building a new environment with
media servers, and the only way I've done it before is with several
separate "master/media server all in one" setups.
=20
Paul
=20
-----Original Message-----
From: Tschida, Tom (C)(STP) [mailto:tom.tschida AT guidant DOT com]=20
Sent: August 17, 2005 11:11 AM
To: Geyer, Gregory; Paul Keating;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] restrict only one volume pool from
returning expired media to Scratch.
=09
=09
That would work, but I don't believe you need a separate media
server. You could put several of the drives into it's own storage unit
group, and then set up barcode rules related to that STU group. Then
assign that STU group to the policy you're concerned about.
_____ =20
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Geyer,
Gregory
Sent: Wednesday, August 17, 2005 9:38 AM
To: Paul Keating; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] restrict only one volume pool from
returning expired media to Scratch.
=09
=09
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.
_____ =20
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.
=09
=09
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_01C5A4DD.21B39AA8
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.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2>So, if=20
I understand correctly, when setting up a secondary media server, I =
would=20
configure the drives to see the media server as the "device host" but =
select=20
"drive is in a robotic library" and then select the library that the =
drives are=20
in, and enter the drive number, and the master server will be the =
robotic=20
control host, correct?</FONT></SPAN></DIV>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2>that=20
way, any backups to this secondary media server will only be able =
to go to=20
drives that have been allocated to it in the way?</FONT></SPAN></DIV>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2>Might=20
be a stupid question, but I'm building a new environment with media =
servers, and=20
the only way I've done it before is with several separate "master/media =
server=20
all in one" setups.</FONT></SPAN></DIV>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2>Paul</FONT></SPAN></DIV>
<DIV><SPAN class=3D756433416-19082005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Tschida, Tom=20
(C)(STP) [mailto:tom.tschida AT guidant DOT com] <BR><B>Sent:</B> August 17, =
2005=20
11:11 AM<BR><B>To:</B> Geyer, Gregory; Paul Keating;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
restrict=20
only one volume pool from returning expired media to=20
Scratch.<BR><BR></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D535190615-17082005><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>That would work, but I don<SPAN=20
class=3D301160815-17082005>'</SPAN>t believe you need a separate media =
server. You could put several of the drives into it's own =
storage unit=20
group, and then set up barcode rules related to that STU<SPAN=20
class=3D301160815-17082005> group</SPAN>.<SPAN =
class=3D301160815-17082005> =20
Then assign that STU group to the policy you're concerned=20
about.</SPAN></FONT></FONT></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> =
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>Geyer,=20
Gregory<BR><B>Sent:</B> Wednesday, August 17, 2005 9:38 =
AM<BR><B>To:</B> Paul=20
Keating; veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: =
[Veritas-bu]=20
restrict only one volume pool from returning expired media to=20
Scratch.<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875432514-17082005><FONT=20
face=3D"Courier New" color=3D#0000ff size=3D2>IF you have a separate =
media server=20
for this group and IF you have a sophisticated robot you could =
possibly limit=20
tape access to different media servers. In other words media =
server B=20
can't see tapes that start with 333, while media server A can't see =
tapes that=20
start with 222. So tapes would return to scratch but wouldn't be =
picked=20
up by competing media servers.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875432514-17082005><FONT=20
face=3D"Courier New" color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D875432514-17082005><FONT=20
face=3D"Courier New" color=3D#0000ff size=3D2>I am just theorizing as =
I don't know=20
for sure if this would work for you. I'm looking at a similar =
issue, but=20
with two masters sharing the same ACS robotics. But in that case =
there=20
are two separate volume 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> =
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
restrict=20
only one volume pool from returning expired media to=20
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> </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=20
tape returned to scratch once it's been assigned.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial =
size=3D2>basically, the=20
data in this environment is protected, so once it is written to tape, =
those=20
tapes are considered "protected".</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial =
size=3D2>Right now,=20
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=20
unprotected data.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial size=3D2>So, =
I need to=20
create a volume pool for this application group, and I would prefer =
for this=20
volume group to be able to pull tapes from scratch, IF necessary, but =
never=20
return them to scratch.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </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=20
provisioned manually, it will never pull from scratch, and therefore =
never=20
return tapes to scratch......this could be a possible solution, but =
I'm=20
worried about the occasion where the pool was underprovisioned and =
pulled a=20
tape from scratch....once expired, it would go back to=20
scratch.</FONT></SPAN></DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D043592916-16082005><FONT face=3DArial=20
size=3D2>Paul</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C5A4DD.21B39AA8--
|
