<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Locking SAN Tape Drives in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728303#M74426</link>
    <description>We have multiple VMS hosts connected through&lt;BR /&gt;an HP SAN to a shared HP tape-library.&lt;BR /&gt;&lt;BR /&gt;Is there any way for a host to somehow&lt;BR /&gt;"lock" a drive for its own use, so that&lt;BR /&gt;when another host tries to Allocate the&lt;BR /&gt;device it will see the device as&lt;BR /&gt;unavailable?</description>
    <pubDate>Thu, 09 Feb 2006 14:38:21 GMT</pubDate>
    <dc:creator>Jack Trachtman</dc:creator>
    <dc:date>2006-02-09T14:38:21Z</dc:date>
    <item>
      <title>Locking SAN Tape Drives</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728303#M74426</link>
      <description>We have multiple VMS hosts connected through&lt;BR /&gt;an HP SAN to a shared HP tape-library.&lt;BR /&gt;&lt;BR /&gt;Is there any way for a host to somehow&lt;BR /&gt;"lock" a drive for its own use, so that&lt;BR /&gt;when another host tries to Allocate the&lt;BR /&gt;device it will see the device as&lt;BR /&gt;unavailable?</description>
      <pubDate>Thu, 09 Feb 2006 14:38:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728303#M74426</guid>
      <dc:creator>Jack Trachtman</dc:creator>
      <dc:date>2006-02-09T14:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: Locking SAN Tape Drives</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728304#M74427</link>
      <description>Just "$ alloc" the drive by it name. SLS for example works this way. &lt;BR /&gt;$ alloc on node and it will not be available on the other nodes. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Feb 2006 16:56:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728304#M74427</guid>
      <dc:creator>Thomas Ritter</dc:creator>
      <dc:date>2006-02-09T16:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: Locking SAN Tape Drives</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728305#M74428</link>
      <description>Tom,&lt;BR /&gt;&lt;BR /&gt;$ ALLOCATE will work within nodes of a cluster.  I'm looking for something that&lt;BR /&gt;works across unrelated hosts.</description>
      <pubDate>Thu, 09 Feb 2006 19:10:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728305#M74428</guid>
      <dc:creator>Jack Trachtman</dc:creator>
      <dc:date>2006-02-09T19:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: Locking SAN Tape Drives</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728306#M74429</link>
      <description>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).</description>
      <pubDate>Fri, 10 Feb 2006 02:12:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728306#M74429</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-02-10T02:12:23Z</dc:date>
    </item>
    <item>
      <title>Re: Locking SAN Tape Drives</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728307#M74430</link>
      <description>Hi,&lt;BR /&gt;way is to use Data Protector or MDMS (layer of ABS) to sharing allocate informations.&lt;BR /&gt;Petr</description>
      <pubDate>Fri, 10 Feb 2006 07:12:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728307#M74430</guid>
      <dc:creator>Petr Spisek</dc:creator>
      <dc:date>2006-02-10T07:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: Locking SAN Tape Drives</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728308#M74431</link>
      <description>&lt;BR /&gt;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).</description>
      <pubDate>Fri, 10 Feb 2006 11:38:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728308#M74431</guid>
      <dc:creator>Tom O'Toole</dc:creator>
      <dc:date>2006-02-10T11:38:57Z</dc:date>
    </item>
    <item>
      <title>Re: Locking SAN Tape Drives</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728309#M74432</link>
      <description>Tom,&lt;BR /&gt;&lt;BR /&gt;Unfortunately we have seen what happens&lt;BR /&gt;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.</description>
      <pubDate>Mon, 13 Feb 2006 16:20:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/locking-san-tape-drives/m-p/3728309#M74432</guid>
      <dc:creator>Jack Trachtman</dc:creator>
      <dc:date>2006-02-13T16:20:47Z</dc:date>
    </item>
  </channel>
</rss>

