<?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: Importing a VG in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251927#M331701</link>
    <description>Hi Anubhav,&lt;BR /&gt;&lt;BR /&gt;How you are exporting Vg &lt;BR /&gt;use -p -s -v -m option with vgexport.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;vjta</description>
    <pubDate>Mon, 22 Dec 2008 08:09:35 GMT</pubDate>
    <dc:creator>vjta</dc:creator>
    <dc:date>2008-12-22T08:09:35Z</dc:date>
    <item>
      <title>Importing a VG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251922#M331696</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I have rp4440 running HP-UX 11iV1 connected to EMC Clarion storage. We connected another rp4440 to the same storage and presented the same LUNS so that we can bring the new machine in cluster using SG. After I presented the LUNs to the new machine(HOST2), and I got the error message while importing the VG to the new host. Soon i realized the reason behind this. it was happening because, the LUN which had path, c2t1d0 at Host1 is having different path at Host2. Then I unpresented the LUNs and changed the HOST IDs on the LUN. It solved the problem however, i like to know. Will it be a problem, same LUN presented to two hosts have different paths, as far SG is a problem.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Aug 2008 07:25:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251922#M331696</guid>
      <dc:creator>Anubhav Dhingra</dc:creator>
      <dc:date>2008-08-14T07:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a VG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251923#M331697</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;No I do not believe it will be a problem to present the same lun to two different service guard nodes with different paths.&lt;BR /&gt;&lt;BR /&gt;It will make it harder to administer and the volume group activation code in the packages will have to be different.&lt;BR /&gt;&lt;BR /&gt;It would be better if both nodes have the same path but its not a strict requirement.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 14 Aug 2008 07:34:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251923#M331697</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-08-14T07:34:28Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a VG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251924#M331698</link>
      <description>Serviceguard will not worry if the paths differ across Serviceguard nodes, as LVM or VxVM manage and take care of this for you.&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Aug 2008 07:40:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251924#M331698</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2008-08-14T07:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a VG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251925#M331699</link>
      <description>Hi Anubhav,&lt;BR /&gt;&lt;BR /&gt;The best way is the cluster should be symmetrical.If currently ur using diff path from diff. node .It will not create any problem but it will be very difficult to do the troubleshooting when problem will arise.&lt;BR /&gt;&lt;BR /&gt;Reagrds&lt;BR /&gt;Atul</description>
      <pubDate>Thu, 14 Aug 2008 08:10:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251925#M331699</guid>
      <dc:creator>Prashanth Waugh</dc:creator>
      <dc:date>2008-08-14T08:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a VG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251926#M331700</link>
      <description>Hi Anubhav&lt;BR /&gt;&lt;BR /&gt;Recomended is to have same path&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Sanjeev</description>
      <pubDate>Thu, 14 Aug 2008 08:36:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251926#M331700</guid>
      <dc:creator>Sharma Sanjeev</dc:creator>
      <dc:date>2008-08-14T08:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a VG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251927#M331701</link>
      <description>Hi Anubhav,&lt;BR /&gt;&lt;BR /&gt;How you are exporting Vg &lt;BR /&gt;use -p -s -v -m option with vgexport.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;vjta</description>
      <pubDate>Mon, 22 Dec 2008 08:09:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-vg/m-p/4251927#M331701</guid>
      <dc:creator>vjta</dc:creator>
      <dc:date>2008-12-22T08:09:35Z</dc:date>
    </item>
  </channel>
</rss>

