Hi Savin,
this sort of thing, where a physical drive is in service mode or
disabled on one node, while it's enabled on another, seems to be fairly
normal.
What could've happened here is that there is a problem with the physical
tape drive which has caused it to be put into service mode when it was
used on node one; then node two used the same physical drive and
encountered the same problem, so it was put in service mode
automatically, also; but the server either didn't use that same physical
drive, or didn't encounter the problem, so its drive is still enabled
within Networker.
I don't believe Networker automatically disables all logical drives for
a particular physical drive when it encounters an error, which is
probably why you're seeing what you're seeing.
HTH,
John
> -----Original Message-----
> From: Rehan, Savin [mailto:savin.rehan AT HP DOT COM]
> Sent: Tuesday, 3 June 2003 00:39
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] Using DDS 6.13 problem
>
>
> Has anybody come across this.
>
> We have a small 2 drive library ( tape0 tape1) on SAN . We
> use DDS to share the devices. Today we noticed that tape0 (
> shared on 3 clients including backup server ) was showing it
> was in service mode for the 2 remote servers but actual
> drive was showing as enabled . It doesnt seem to make sense.
> Anybody have any ideas ?
>
>
> Savin
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|