[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::sls

Title:	Storage Library System

Moderator:	COOKIE::REUTER

Created:	Sun Oct 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2270
Total number of notes:	7850

2235.0. "how to ignore a failed drive in a TapeLibrary ?" by ATZIS3::PIEBER (chaos has many faces) Thu Apr 03 1997 05:44

    Hi folks,
    
    when using a TL826 with it's 6 drives, is there any chance to convince
    MDMS, that one drive has failed due to hardware problems and hence it
    should not attempt to direct any requests from ABS towards it ?
    
    We have this TL826 and if one drive out of six fails then we need to be
    able to continue to do backups, until the hardware gets fixed. This is
    an essential part of the message about redundancy and fault tolerance.
    
    We tried to leave out the drive from the media triplet and restart
    MDMS, but this comes up with an error message, telling it's not
    satisfied with the empty drive spec. What we did to spare out drive 4 
    was:
    
    Drives_x = D0,D1,D2,D3,,D5
                           !
                           +-- this should keep MDMS informed about the
    relation between VMS Drive names and jukebox positions. But this does
    not seem to be the right path.
    
    Maybe I could leave out D4 *AND* D5, sacrifying an additional drive
    for the sake of continued operation on four drives at least - I have
    not tried this yet. However, what if D0 fails ?
    
    Any clues ?
    
    Thanks,
    Ewald.

T.R Title User Personal
Name Date Lines

2235.1 Remove the extra comma in Drives_x CX3PST::WSC217::SWANK David Fri Apr 04 1997 14:38 24

T.R	Title	User	Personal Name	Date	Lines
2235.1	Remove the extra comma in Drives_x	CX3PST::WSC217::SWANK	David	`Fri Apr 04 1997 14:38`	24
	> We tried to leave out the drive from the media triplet and restart > MDMS, but this comes up with an error message, telling it's not > satisfied with the empty drive spec. What we did to spare out drive 4 > was: > > Drives_x = D0,D1,D2,D3,,D5 > ! > +-- this should keep MDMS informed about the > relation between VMS Drive names and jukebox positions. But this does > not seem to be the right path. Actually its the TAPE_JUKEBOXES jukebox name assignment that determines the association between the jukebox's drive position and the VMS drive device; <tl810>:=<node>::<robot-device>:,<node>::<tape-0>:,<node>::<tape-1>:,... Change your Drives_x to the following; Drives_x = D0,D1,D2,D3,D5 The extract comma delimiter is confussing things. \David

>    We tried to leave out the drive from the media triplet and restart
>    MDMS, but this comes up with an error message, telling it's not
>    satisfied with the empty drive spec. What we did to spare out drive 4 
>    was:
>    
>    Drives_x = D0,D1,D2,D3,,D5
>                           !
>                           +-- this should keep MDMS informed about the
>    relation between VMS Drive names and jukebox positions. But this does
>    not seem to be the right path.


Actually its the TAPE_JUKEBOXES jukebox name assignment that determines the
association between the jukebox's drive position and the VMS drive device;

	<tl810>:=<node>::<robot-device>:,<node>::<tape-0>:,<node>::<tape-1>:,...

Change your Drives_x to the following;

	Drives_x = D0,D1,D2,D3,D5

The extract comma delimiter is confussing things.

\David