<?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 Re: Volume Groups Question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258196#M332575</link>
    <description>You can read attached PDF for refernce.&lt;BR /&gt;&lt;BR /&gt;May help you.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;SKR</description>
    <pubDate>Tue, 26 Aug 2008 19:15:40 GMT</pubDate>
    <dc:creator>SKR_1</dc:creator>
    <dc:date>2008-08-26T19:15:40Z</dc:date>
    <item>
      <title>Volume Groups Question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258194#M332573</link>
      <description>What is the difference between activating volume groups in exclusive mode versus shared mode? When are they used? What are the considerations in their implementation?</description>
      <pubDate>Tue, 26 Aug 2008 18:28:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258194#M332573</guid>
      <dc:creator>Waqar Razi</dc:creator>
      <dc:date>2008-08-26T18:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Groups Question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258195#M332574</link>
      <description>Shared mode is for MC Service Guard.  &lt;BR /&gt;&lt;BR /&gt;Active / Passive sharing of disk devices and their configuration.&lt;BR /&gt;&lt;BR /&gt;If you do not use SG then exclusive is the default.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Aug 2008 18:31:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258195#M332574</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2008-08-26T18:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Groups Question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258196#M332575</link>
      <description>You can read attached PDF for refernce.&lt;BR /&gt;&lt;BR /&gt;May help you.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;SKR</description>
      <pubDate>Tue, 26 Aug 2008 19:15:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258196#M332575</guid>
      <dc:creator>SKR_1</dc:creator>
      <dc:date>2008-08-26T19:15:40Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Groups Question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258197#M332576</link>
      <description>SLVM is a mechanism that permits multiple systems in an MC/LockManager cluster to share (read/write) disk resources in the form of volume groups. The objective is a highly available system by providing direct access to disks from multiple nodes and by supporting mirrored disks, thereby eliminating single points of failure.&lt;BR /&gt;&lt;BR /&gt;SLVM permits a two system cluster to have read/write access to a volume group by activating the volume group in shared mode.&lt;BR /&gt;&lt;BR /&gt;SLVM is designed to be used only by specialized distributed applications (such as Oracle Parallel Server) that use raw access to disks, rather than going through a file system. The applications must provide their own concurrency control for their data, as well as transaction logging and recovery facilities, as appropriate. Applications that are not network aware, such as file systems, will not be supported on volume groups activated in shared mode.&lt;BR /&gt;&lt;BR /&gt;SLVM requires services provided by MC/LockManager and thus only clusters that have MC/LockManager will be able to use shared activation.&lt;BR /&gt;&lt;BR /&gt;The following commands have been modified to support SLVM requirements:&lt;BR /&gt;&lt;BR /&gt;    *&lt;BR /&gt;&lt;BR /&gt;      vgchange&lt;BR /&gt;&lt;BR /&gt;      The first release of 10.0 supported the "a -e" activation mode or exclusive mode. ********(Exclusive mode permits only one of the two nodes to have read /write access to the volume group the other may have read access but not read/write access.)********&lt;BR /&gt;&lt;BR /&gt;      For 10.10, vgchange has been modified to support the shared activation mode. It now has the "-c y -S y" option to mark the attributes of the volume group as shareable and the "-a s" option to the activate the volume group in shared mode.&lt;BR /&gt;    *&lt;BR /&gt;&lt;BR /&gt;      vgdisplay vgdisplay will show the current activation mode.</description>
      <pubDate>Tue, 26 Aug 2008 19:37:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258197#M332576</guid>
      <dc:creator>Grayh</dc:creator>
      <dc:date>2008-08-26T19:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Groups Question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258198#M332577</link>
      <description>Hi Razi,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If ur doing &lt;BR /&gt;#vgchange -a e &lt;VG name=""&gt;&lt;BR /&gt;&lt;BR /&gt;This is for activating vg in exclusive mode&lt;BR /&gt;means only one node can read/write/access to that Vg.&lt;BR /&gt;&lt;BR /&gt;#vgchange -a s &lt;VGNAME&gt;&lt;BR /&gt;this is for activating vg in share mode so more than one node read/write/access it&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Atul&lt;/VGNAME&gt;&lt;/VG&gt;</description>
      <pubDate>Wed, 27 Aug 2008 03:01:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-groups-question/m-p/4258198#M332577</guid>
      <dc:creator>Prashanth Waugh</dc:creator>
      <dc:date>2008-08-27T03:01:46Z</dc:date>
    </item>
  </channel>
</rss>

