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_01C0DE04.F3866300
Content-Type: text/plain;
charset="iso-8859-1"
Duane,
Check out TechNote 230047
(http://seer.support.veritas.com/docs/230047.htm) from Veritas's site. It
covers the procedures for decommissioning a media server.
Paul
-----Original Message-----
From: Duane Schultz [mailto:duane AT connect.com DOT au]
Sent: Wednesday, May 16, 2001 2:09 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Problems with available_media and state DBBACKUP
We've had some issues at our site with changes in configuration of media
servers, with some media servers losing their drives and becoming simple
clients.
It seems that the machines that used to be media servers may have had media
database information stored on them for the media that they were writing
and tracking, and since they have been decommisioned, the media which they
had configured is giving us grief - the status column in the
available_media report is showing them as DBBACKUP, which from the code
seems to be the catch-all status for when the mediaid cannot be found in
any database.
What should I be doing to fix this ? Reimporting the media doesn't seem to
get anywhere. I still have a filesystem with the data from the previous
installation, but restoring it, restarting the daemons and trying it
again doesn't seem to get anywhere.
What is the procedure for moving media around between media servers ? Is
there a simple way, or is it a matter of nuke the media information and
reimport ?
--
| Duane Schultz System Manager |
| duane AT connect.com DOT au connect.com.au pty ltd |
| Tel: +61 3 9251 3676 Level 9, 114 Albert Road |
| Fax: +61 3 9251 3666 South Melbourne 3205 Australia |
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C0DE04.F3866300
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Problems with available_media and state =
DBBACKUP</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Duane,</FONT>
<BR> <FONT SIZE=3D2>Check out =
TechNote 230047 (<A =
HREF=3D"http://seer.support.veritas.com/docs/230047.htm"; =
TARGET=3D"_blank">http://seer.support.veritas.com/docs/230047.htm</A>) =
from Veritas's site. It covers the procedures for decommissioning =
a media server.</FONT></P>
<P><FONT SIZE=3D2>Paul</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Duane Schultz [<A =
HREF=3D"mailto:duane AT connect.com DOT au">mailto:duane AT connect.com DOT
au</A>]</F=
ONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, May 16, 2001 2:09 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Problems with available_media =
and state DBBACKUP</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>We've had some issues at our site with changes in =
configuration of media</FONT>
<BR><FONT SIZE=3D2>servers, with some media servers losing their drives =
and becoming simple</FONT>
<BR><FONT SIZE=3D2>clients.</FONT>
</P>
<P><FONT SIZE=3D2>It seems that the machines that used to be media =
servers may have had media</FONT>
<BR><FONT SIZE=3D2>database information stored on them for the media =
that they were writing</FONT>
<BR><FONT SIZE=3D2>and tracking, and since they have been =
decommisioned, the media which they</FONT>
<BR><FONT SIZE=3D2>had configured is giving us grief - the status =
column in the</FONT>
<BR><FONT SIZE=3D2>available_media report is showing them as DBBACKUP, =
which from the code</FONT>
<BR><FONT SIZE=3D2>seems to be the catch-all status for when the =
mediaid cannot be found in</FONT>
<BR><FONT SIZE=3D2>any database.</FONT>
</P>
<P><FONT SIZE=3D2>What should I be doing to fix this ? Reimporting the =
media doesn't seem to</FONT>
<BR><FONT SIZE=3D2>get anywhere. I still have a filesystem with the =
data from the previous</FONT>
<BR><FONT SIZE=3D2>installation, but restoring it, restarting the =
daemons and trying it</FONT>
<BR><FONT SIZE=3D2>again doesn't seem to get anywhere.</FONT>
</P>
<P><FONT SIZE=3D2>What is the procedure for moving media around between =
media servers ? Is</FONT>
<BR><FONT SIZE=3D2>there a simple way, or is it a matter of nuke the =
media information and</FONT>
<BR><FONT SIZE=3D2>reimport ?</FONT>
</P>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>| Duane =
Schultz  =
;  =
; System Manager |</FONT>
<BR><FONT SIZE=3D2>| =
duane AT connect.com DOT au &nbs=
p; connect.com.au pty ltd |</FONT>
<BR><FONT SIZE=3D2>| Tel: +61 3 9251 =
3676 &n=
bsp; Level 9, 114 Albert Road |</FONT>
<BR><FONT SIZE=3D2>| Fax: +61 3 9251 =
3666 South Melbourne 3205 =
Australia |</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C0DE04.F3866300--
|
