<?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: pvmove in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585174#M715985</link>
    <description>You can not use pvmove if VG activated in shared mode.</description>
    <pubDate>Thu, 18 Oct 2001 15:12:48 GMT</pubDate>
    <dc:creator>Vitaliy Kushenrov</dc:creator>
    <dc:date>2001-10-18T15:12:48Z</dc:date>
    <item>
      <title>pvmove</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585169#M715980</link>
      <description>Hi,&lt;BR /&gt;My system is running with MCSG&lt;BR /&gt;Can i use pvmove command even if my system is running ? or must i desactivate MCSG and then use pvmove ?&lt;BR /&gt;&lt;BR /&gt; thanks for your replies.</description>
      <pubDate>Wed, 26 Sep 2001 09:27:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585169#M715980</guid>
      <dc:creator>Matrah</dc:creator>
      <dc:date>2001-09-26T09:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585170#M715981</link>
      <description>No, you should be able to do the pvmove without affecting the application.  However, since the VG information for this VG will be changed, its best to do a vgexport from this machine after the pvmove and then vgimport the new map files onto the other nodes in the cluster.&lt;BR /&gt;&lt;BR /&gt;-Santosh</description>
      <pubDate>Wed, 26 Sep 2001 09:33:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585170#M715981</guid>
      <dc:creator>Santosh Nair_1</dc:creator>
      <dc:date>2001-09-26T09:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585171#M715982</link>
      <description>Remember that new disks, must be accesible by others hosts in cluster.</description>
      <pubDate>Wed, 26 Sep 2001 09:41:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585171#M715982</guid>
      <dc:creator>David Navarro</dc:creator>
      <dc:date>2001-09-26T09:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585172#M715983</link>
      <description>&lt;BR /&gt;If your pvmoving to a new disk youve added to a VG which is in an MCSG package then yes, at some point you will need to deactivate MCSG and export the VG and reimport it on the other SG node so it also knows about the new disk.&lt;BR /&gt;&lt;BR /&gt;But actually doing the pvmove, you can do online anytime, no need to deactivate MCSG. But for the SG failover to work you may need to do the above.&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Sep 2001 10:01:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585172#M715983</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2001-09-26T10:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585173#M715984</link>
      <description>There should be no reason to halt the cluster throughout the 'pvmove' process.  &lt;BR /&gt;&lt;BR /&gt;   /etc/lvmtab contains the list of disks for each VG.  Should you desire to remove a disk from a VG, it can be done while the package is up using a vgreduce command.&lt;BR /&gt;&lt;BR /&gt;   If you have added a disk to a VG on one server, the other server's lvmtab can be updated without halting the cluster by merely vgexporting and vgimporting the volume group there (use a map file that contains the VGID to ease the process.  VGID is loaded in the map file using the -s option of vgexport)</description>
      <pubDate>Wed, 26 Sep 2001 12:06:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585173#M715984</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2001-09-26T12:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585174#M715985</link>
      <description>You can not use pvmove if VG activated in shared mode.</description>
      <pubDate>Thu, 18 Oct 2001 15:12:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove/m-p/2585174#M715985</guid>
      <dc:creator>Vitaliy Kushenrov</dc:creator>
      <dc:date>2001-10-18T15:12:48Z</dc:date>
    </item>
  </channel>
</rss>

