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_01C1ECC4.7C2A80F0
Content-Type: text/plain;
charset="iso-8859-1"
You can "monitor" the job through the job viewer to get details. It'll tell
you which tape was mounted for the job. You can get the drive info after
that using the "vmoprcmd -d ds" command or via the device viewer.
-Mark
-----Original Message-----
From: Ajay Sharma [mailto:Ajay.Sharma AT hostcentric DOT com]
Sent: Thursday, April 25, 2002 5:24 PM
To: Donaldson, Mark; Ballowe, Charles; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] finding which tape is in the drive
Is there a way we know which drive/tape is running backups for which client.
Legato's nsrwatch is really good at that.
Ajay.
-----Original Message-----
From: Donaldson, Mark [mailto:Mark.Donaldson AT experianems DOT com]
Sent: Thursday, April 25, 2002 3:38 PM
To: 'Ballowe, Charles'; 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] finding which tape is in the drive
The electronic label (EVSN) is available via the "vmoprcmd -d ds" command.
-Mark
-----Original Message-----
From: Ballowe, Charles [ mailto:CBallowe AT usg DOT com <mailto:CBallowe AT usg
DOT com> ]
Sent: Thursday, April 25, 2002 3:20 PM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] finding which tape is in the drive
Is there an easy way (cmdline) to find which tape is in the drive
for a stand alone tape drive? My goal is to write a quick script
to expire the images on that tape using bpexpdate -ev, but I need
to know which one is in there. We have 3 weeks of tapes for this
test lab environment (one per day), retention set to 3 weeks,
so the images on the tapes would be expiring about 8 hours after
the run starts for the night. Not my design -- they just asked me
to fix it.
Charles Ballowe /"\
Unix System Administrator \ / ASCII Ribbon Campaign
cballowe AT usg DOT com X Against HTML Mail
x3896 / \
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu>
------_=_NextPart_001_01C1ECC4.7C2A80F0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Veritas-bu] finding which tape is in the drive</TITLE>
<META content="MSHTML 6.00.2715.400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=781154701-26042002><FONT face=Arial color=#0000ff size=2>You
can "monitor" the job through the job viewer to get details. It'll tell
you which tape was mounted for the job. You can get the drive info after
that using the "vmoprcmd -d ds" command or via the device
viewer.</FONT></SPAN></DIV>
<DIV><SPAN class=781154701-26042002><FONT face=Arial color=#0000ff
size=2>-Mark</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Ajay Sharma
[mailto:Ajay.Sharma AT hostcentric DOT com]<BR><B>Sent:</B> Thursday, April
25, 2002
5:24 PM<BR><B>To:</B> Donaldson, Mark; Ballowe, Charles;
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
finding
which tape is in the drive<BR><BR></FONT></DIV>
<DIV><SPAN class=410181923-25042002><FONT face=Arial color=#0000ff size=2>Is
there a way we know which drive/tape is running backups for which client.
Legato's nsrwatch is really good at that.</FONT></SPAN></DIV>
<DIV><SPAN class=410181923-25042002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=410181923-25042002><FONT face=Arial color=#0000ff
size=2>Ajay.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Donaldson, Mark
[mailto:Mark.Donaldson AT experianems DOT com]<BR><B>Sent:</B> Thursday,
April 25,
2002 3:38 PM<BR><B>To:</B> 'Ballowe, Charles';
'veritas-bu AT mailman.eng.auburn DOT edu'<BR><B>Subject:</B> RE:
[Veritas-bu]
finding which tape is in the drive<BR><BR></FONT></DIV>
<P><FONT size=2>The electronic label (EVSN) is available via the "vmoprcmd
-d ds" command.</FONT> <BR><FONT size=2>-Mark</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Ballowe, Charles [<A
href="mailto:CBallowe AT usg DOT com">mailto:CBallowe AT usg DOT
com</A>]</FONT> <BR><FONT
size=2>Sent: Thursday, April 25, 2002 3:20 PM</FONT> <BR><FONT size=2>To:
'veritas-bu AT mailman.eng.auburn DOT edu'</FONT> <BR><FONT size=2>Subject:
[Veritas-bu] finding which tape is in the drive</FONT> </P><BR>
<P><FONT size=2>Is there an easy way (cmdline) to find which tape is in the
drive</FONT> <BR><FONT size=2>for a stand alone tape drive? My goal is to
write a quick script</FONT> <BR><FONT size=2>to expire the images on that
tape using bpexpdate -ev, but I need</FONT> <BR><FONT size=2>to know which
one is in there. We have 3 weeks of tapes for this</FONT> <BR><FONT
size=2>test lab environment (one per day), retention set to 3 weeks,
</FONT><BR><FONT size=2>so the images on the tapes would be expiring about
8
hours after</FONT> <BR><FONT size=2>the run starts for the night. Not my
design -- they just asked me</FONT> <BR><FONT size=2>to fix it.</FONT>
</P><BR>
<P><FONT size=2>Charles
Ballowe
/"\</FONT> <BR><FONT size=2>Unix System
Administrator \
/ ASCII Ribbon Campaign</FONT> <BR><FONT
size=2>cballowe AT usg DOT
com
X Against HTML Mail</FONT> <BR><FONT
size=2>x3896
/ \</FONT> </P>
<P><FONT size=2>_______________________________________________</FONT>
<BR><FONT size=2>Veritas-bu maillist -
Veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=2><A
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"
target=_blank>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A></FONT>
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C1ECC4.7C2A80F0--
|