This is a multi-part message in MIME format.
------_=_NextPart_001_01C339B1.BE1ECA3F
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Ok. I am seeing the sam thing. For me, I vote for number 2 below.
=20
I know for a fact that I have had improperly decomissioned Media Servers.
=20
The big question for me is How do I fix it?
=20
Rob Thelen.
-----Original Message-----
From: scott.kendall AT abbott DOT com [mailto:scott.kendall AT abbott DOT com]
Sent: Monday, June 23, 2003 12:38 PM
To: navadeepan sithambaram
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] available_media givies wrong info
The full list of volumes in the the VolDB, but it doesn't know about NBU ty=
pe stuff (netbackup status, kbytes, # restores, expiration, etc.). That is=
all in the MediaDB, which is on each media server.=20
vmquery queries the VolDB and then uses commands like bpmedialist to get th=
e NBU info it needs for the report.=20
If the report finds a volume that is in the VolDB with an assigned status, =
but can't find it in any of the MediaDBs, this is what is returned.=20
Two possible causes are:=20
1.) a media server was down (or ltid was down) when you ran the report.=20
2.) a media server was assigned the tape, but has since been improperly de=
commisioned (e.g. the MediaDB wasn't tranferred to another media server bef=
ore it was shut off).=20
- Scott=20
navadeepan sithambaram <navadeepan AT yahoo.co DOT uk>=20
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu=20
04/16/2003 01:21 AM=20
=20
To: veritas-bu AT mailman.eng.auburn DOT edu=20
cc: =20
Subject: [Veritas-bu] available_media givies wrong info
Hi All,
i am facing a strange situation.
I am running NB4.5 with MP3 on SOlaris 7 as Master
Server. When i run available_media command on Master
server, it lists the media status.
but strangely on some volume pools , on some media, it
gives status column as "DBBACKUP"
but when i check thro jnbSA , it shows the status
correctly. I am able to read the contents of the tape
and also able to restore/backup using that media.
any clue on this????
Thanks in Advance
Regds
Navadeepan
Unix Administrator
**********************************************************************
This transmission may contain information that is privileged, confidential =
and/or exempt from disclosure under applicable law. If you are not the inte=
nded recipient, you are hereby notified that any disclosure, copying, distr=
ibution, or use of the information contained herein (including any reliance=
thereon) is STRICTLY PROHIBITED. If you received this transmission in erro=
r, please immediately contact the sender and destroy the material in its en=
tirety, whether in electronic or hard copy format. Thank you
**********************************************************************
------_=_NextPart_001_01C339B1.BE1ECA3F
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D577270118-23062003>Ok. I am seeing the sam thing. For m=
e, I=20
vote for number 2 below.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D577270118-23062003></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D577270118-23=
062003>I know=20
for a fact that I have had improperly decomissioned Media=20
Servers.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D577270118-23062003></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D577270118-23=
062003>The=20
big question for me is How do I fix it?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D577270118-23062003></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D577270118-23=
062003>Rob=20
Thelen.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN class=3D577270118-23062003>
<P><FONT face=3D"Cooper Black" color=3D#000000 size=3D2><SPAN=20
class=3D577270118-23062003> </SPAN></FONT></SPAN></FONT><FONT face=3DT=
ahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> scott.kendall AT abbott DOT
co=
m=20
[mailto:scott.kendall AT abbott DOT com]<BR><B>Sent:</B> Monday, June 23, 2003
12:=
38=20
PM<BR><B>To:</B> navadeepan sithambaram<BR><B>Cc:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> Re: [Veritas-bu]=20
available_media givies wrong info<BR><BR></FONT></P></DIV>
<BLOCKQUOTE><BR><FONT face=3DArial size=3D2>The full list of volumes in the=
the=20
VolDB, but it doesn't know about NBU type stuff (netbackup status, kbytes=
, #=20
restores, expiration, etc.). That is all in the MediaDB, which is o=
n=20
each media server.</FONT> <BR><BR><FONT face=3DArial size=3D2>vmquery que=
ries the=20
VolDB and then uses commands like bpmedialist to get the NBU info it need=
s for=20
the report.</FONT> <BR><BR><FONT face=3DArial size=3D2>If the report find=
s a=20
volume that is in the VolDB with an assigned status, but can't find it in=
any=20
of the MediaDBs, this is what is returned.</FONT> <BR><BR><FONT face=3DAr=
ial=20
size=3D2>Two possible causes are:</FONT> <BR><BR><FONT face=3DArial size=
=3D2>1.)=20
a media server was down (or ltid was down) when you ran the=20
report.</FONT> <BR><BR><FONT face=3DArial size=3D2>2.) a media serv=
er was=20
assigned the tape, but has since been improperly decommisioned (e.g. the=
MediaDB wasn't tranferred to another media server before it was shut=20
off).</FONT> <BR><BR><FONT face=3DArial size=3D2>- Scott</FONT> <BR>
<TABLE width=3D"100%">
<TBODY>
<TR vAlign=3Dtop>
<TD><FONT face=3DArial color=3D#0000ff size=3D2></FONT>
<TD><FONT face=3Dsans-serif size=3D1><B>navadeepan sithambaram=20
<navadeepan AT yahoo.co DOT uk></B></FONT> <BR><FONT
face=3Dsans-ser=
if=20
size=3D1>Sent by: veritas-bu-admin AT mailman.eng.auburn DOT
edu</FONT>=20
<P><FONT face=3Dsans-serif size=3D1>04/16/2003 01:21 AM</FONT> <BR>=
</P>
<TD><FONT face=3DArial size=3D1> </FONT><B=
R><FONT=20
face=3Dsans-serif size=3D1> To: &=
nbsp;=20
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT=20
face=3Dsans-serif size=3D1> cc: &=
nbsp;=20
</FONT> <BR><FONT face=3Dsans-serif size=3D1> &n=
bsp;=20
Subject: [Veritas-bu]=20
available_media givies wrong info</FONT></TR></TBODY></TABLE><FONT=
face=3D"Courier New" size=3D2>Hi All,<BR>i am facing a strange situation=
.<BR>I am=20
running NB4.5 with MP3 on SOlaris 7 as Master<BR>Server. When i run=20
available_media command on Master<BR>server, it lists the media status.<B=
R>but=20
strangely on some volume pools , on some media, it<BR>gives status column=
as=20
"DBBACKUP"<BR>but when i check thro jnbSA , it shows the status<BR>correc=
tly.=20
I am able to read the contents of the tape<BR>and also able to restore/ba=
ckup=20
using that media.<BR>any clue on this????<BR>Thanks in=20
Advance<BR><BR>Regds<BR>Navadeepan<BR>Unix=20
Administrator<BR></FONT></BLOCKQUOTE><FONT SIZE=3D3><BR>
<BR>
**********************************************************************<BR>
This transmission may contain information that is privileged, confidential =
and/or exempt from disclosure under applicable law. If you are not the inte=
nded recipient, you are hereby notified that any disclosure, copying, distr=
ibution, or use of the information contained herein (including any reliance=
thereon) is STRICTLY PROHIBITED. If you received this transmission in erro=
r, please immediately contact the sender and destroy the material in its en=
tirety, whether in electronic or hard copy format. Thank you<BR>
**********************************************************************<BR>
</FONT>
</BODY></HTML>
------_=_NextPart_001_01C339B1.BE1ECA3F--
|
