[Veritas-bu] Media open error 83

<!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 =
6.0.4419.22">
<TITLE>Media open error 83</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>We are experiencing repeated (but not reliably =
reproducible) error 83's.</FONT>
</P>

<P><FONT SIZE=3D2>Environment:</FONT>
</P>

<P><FONT SIZE=3D2>Brocade 2800 FC Switches</FONT>

<BR><FONT SIZE=3D2>Hitachi 9200 storage array</FONT>

<BR><FONT SIZE=3D2>Emulux LP800 FC PCI cards (in point to point mode =
with latest F/W and driver 4.21d)</FONT>

<BR><FONT SIZE=3D2>Quantum/ATL P2000 tape library with 2xIBM LTO =
drives</FONT>

<BR><FONT SIZE=3D2>FC/SCSI bridge in P2000 library is OEM'd by quantum =
from ATTO</FONT>

<BR><FONT SIZE=3D2>Backup server running NB3.4.1 (latest patches) on Sun =
E250 with Solaris 2.8 (latest SUN recommended patches)</FONT>

<BR><FONT SIZE=3D2>Clients: Windows 2000, Exchange 2000, Oracle 8.0.6, =
Solaris 2.6-2.8</FONT>
</P>

<P><FONT SIZE=3D2>We can launch manual backups of anything and be =
reasonably certain of a successful backup. Scheduled evening backups are =
inconsistent. For instance: last night we got a hot backup of exchange, =
but RMAN resulted in an 83 error. All subsequent backups were 83 errors. =
This morning we got a successful manual exchange mailbox backup, =
successful Solaris file backup and successful RMAN =
backup.....?????</FONT></P>

<P><FONT SIZE=3D2>We are getting limited messages in the NB server's =
messages file:</FONT>
</P>

<P><FONT SIZE=3D2>Sep 11 19:58:29 kalback tldcd[23332]: [ID 841094 =
daemon.error] TLD(0) Move_medium error: CHECK CONDITION</FONT>

<BR><FONT SIZE=3D2>Sep 11 19:58:29 kalback tldd[12926]: [ID 923197 =
daemon.error] TLD(0) drive 1 (device 0) is being DOWNED, status: Robotic =
dismount failure</FONT></P>

<P><FONT SIZE=3D2>Sep 11 19:58:29 kalback tldd[12926]: [ID 229259 =
daemon.error] Check integrity of the drive, drive path, and media</FONT>
</P>

<P><FONT SIZE=3D2>Has anyone out there encountered this kind of problem =
(even if the equipment does not match up)?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks in advance</FONT>
</P>

<P><FONT SIZE=3D2>Glen Thayer - Senior Operations Analyst</FONT>

<BR><FONT SIZE=3D2>Information Services - Kal Tire</FONT>

<BR><FONT SIZE=3D2>Phone: (250)558-3215</FONT>

<BR><FONT SIZE=3D2>gthayer AT kaltire DOT com &lt;<A =
HREF=3D"mailto:gthayer AT kaltire DOT com">mailto:gthayer AT kaltire DOT 
com</A>&gt; =
</FONT>

<BR><FONT SIZE=3D2>You'll like us, for more than our tires...</FONT>

<BR><FONT SIZE=3D2>2501 48th Avenue, Vernon, B.C. V1T 6N6</FONT>
</P>

</BODY>
</HTML>