Operating System - OpenVMS
1753877 Members
7566 Online
108809 Solutions
New Discussion юеВ

Re: Locking SAN Tape Drives

 
SOLVED
Go to solution
Jack Trachtman
Super Advisor

Locking SAN Tape Drives

We have multiple VMS hosts connected through
an HP SAN to a shared HP tape-library.

Is there any way for a host to somehow
"lock" a drive for its own use, so that
when another host tries to Allocate the
device it will see the device as
unavailable?
6 REPLIES 6
Thomas Ritter
Respected Contributor

Re: Locking SAN Tape Drives

Just "$ alloc" the drive by it name. SLS for example works this way.
$ alloc on node and it will not be available on the other nodes.

Jack Trachtman
Super Advisor

Re: Locking SAN Tape Drives

Tom,

$ ALLOCATE will work within nodes of a cluster. I'm looking for something that
works across unrelated hosts.
Uwe Zessin
Honored Contributor

Re: Locking SAN Tape Drives

The host would have to send a SCSI "RESERVE UNIT" command, but I have never heard that you can do that from 'vanilla VMS'. More complex backup software can even lock the entire library, so that the operator cannot manually open the door(s).
.
Petr Spisek
Regular Advisor
Solution

Re: Locking SAN Tape Drives

Hi,
way is to use Data Protector or MDMS (layer of ABS) to sharing allocate informations.
Petr
Tom O'Toole
Respected Contributor

Re: Locking SAN Tape Drives


Have you (or anybody) tried to see what happens when you try to allocate and use a drive that's already in use by another system? I have been meaning to try this, but haven't yet had the opportunity (that is: don't want to mess with the production systems that use these drives).
Can you imagine if we used PCs to manage our enterprise systems? ... oops.
Jack Trachtman
Super Advisor

Re: Locking SAN Tape Drives

Tom,

Unfortunately we have seen what happens
when tape-drive usage isn't coordinated across hosts - we had one host tell the jukebox to grab a tape from one drive (being used on another host) and put it in another drive. The first host wound up with a hung device and we had to boot to free it.