[Veritas-bu] Best practice on vault

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_01C469B3.553E4BE8
Content-Type: text/plain

We are currently in the process of implementing Vault (4.5-FP6).  Currently
our librarian's do not have access to the netback server.  I am trying to
figure out the best way to handle tape removal and insertion.

Under our previous home grown system there was a small applet that allowed
them to initiate commands on the master server without logging in or having
access to the system.  Initially we continued to use that system to eject
the tapes but the deferred reports would never run.  So how should I set up
for them to remove the tapes?   They would prefer to be able to initiate the
eject so they don't have to wait if there are more tapes than the cap can
handle.  It is my understanding that if you specify immediate eject in a
vault profile that vault will move tapes to the cap until it is full then
check every five minutes to see if there is room to move more.  They don't
like the idea of having to wait up to 5 minutes for the final tapes to be
ejected.  Furthermore with my custom app they were able to put tapes in as
they took tapes out.  How will vault handle that?  Will it see the new
tapes, move them into slots and continue or will it continue to wait or will
it fail?  I considered just modifying my app to allow them to initiate and
eject vault policy but I run into another issue.  If I run the database
backup during the duplication with a separate eject policy the separate
eject does not eject the database tape.  If I put the database backup into
the separate eject policy how can I let the librarians know when that step
is done since the catalog backup takes a bit?

Should I enable telnet services on the server (windows2000 sp4) and give
them access to the vltmenu (would that even work?)

Thanks


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law.  Any unauthorized
review, use, disclosure or distribution is prohibited.  If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.
------_=_NextPart_001_01C469B3.553E4BE8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3DUS-ASCI=
I">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2657.7=
3">
<TITLE>Best practice on vault</TITLE>
</HEAD>
<BODY>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">We are cu=
rrently in the process of implementing Vault (4.5-FP6).&nbsp; Currently o=
ur librarian</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">'</FON=
T><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">s do not have access to=
 the netback server.&nbsp; I am trying to figure out the best way to hand=
le tape removal and insertion.</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Under our=
 previous home grown system there was a small applet</FONT> <FONT COLOR=3D=
"#000080" SIZE=3D2 FACE=3D"Arial">that</FONT><FONT COLOR=3D"#000080" SIZE=
=3D2 FACE=3D"Arial"></FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Aria=
l">allowed them to initiate commands on the master server without logging=
 in or having access to the system.&nbsp; Initially</FONT> <FONT COLOR=3D=
"#000080" SIZE=3D2 FACE=3D"Arial">we continued to use that system to ejec=
t the tapes but the deferred reports would never run.&nbsp; So how should=
 I set up for them to remove the tapes?&nbsp;&nbsp; They would prefer to =
be able to initiate the eject so they don</FONT><FONT COLOR=3D"#000080" S=
IZE=3D2 FACE=3D"Arial">'</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"A=
rial">t have to wait if there are more tapes than the cap can handle.&nbs=
p; It is my understanding that if you specify immediate eject in a vault =
profile that vault will move tapes to the cap until it is full then check=
 every five minutes to see if there is room to move more.&nbsp; They don<=
/FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">'</FONT><FONT COLOR=
=3D"#000080" SIZE=3D2 FACE=3D"Arial">t like the idea of having to wait up=
 to 5 minutes for the final tapes to be</FONT> <FONT COLOR=3D"#000080" SI=
ZE=3D2 FACE=3D"Arial">ejected.&nbsp; Furthermore with my custom app they =
were able to put tapes in as they took tapes out.&nbsp; How will vault ha=
ndle that?&nbsp; Will it see the new tapes, move them into slots and cont=
inue or will it continue to wait</FONT><FONT COLOR=3D"#000080" SIZE=3D2 F=
ACE=3D"Arial"> or will it fail?&nbsp; I considered just modifying my app =
to allow them to initiate and eject vault policy but I run into another i=
ssue.&nbsp; If I run the</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"=
Arial">database</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> ba=
ckup during the duplication with a separate eject policy the separate eje=
ct does not eject the database tape.&nbsp; If I put the database backup i=
nto the separate eject policy how can I let the librarians know when that=
 step is done</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">sinc=
e the catalog backup takes a bit?</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Should I =
enable telnet services on the server (windows2000 sp4) and give them acce=
ss to the vltmenu (would</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"=
Arial">that</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> even w=
ork?)</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Thanks</F=
ONT></P>

</BODY>
</HTML>

<BR>
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,=20
is for the sole use of the intended recipient(s) and may contain confiden=
tial
and privileged information or otherwise be protected by law.  Any unautho=
rized
review, use, disclosure or distribution is prohibited.  If you are not th=
e
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.


------_=_NextPart_001_01C469B3.553E4BE8--