<?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 on mounted production server in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789672#M534504</link>
    <description>Hi meem,&lt;BR /&gt;&lt;BR /&gt;What you are trying to do is standard procedure. Moving extents off a disk that is underutilized and making it usable on a more appropriate volume group. &lt;BR /&gt;&lt;BR /&gt;Just one word of caution, careless pvmove's, lvextend's etc can lead to the fragmentation of the extent space on LVM which is a prominent concept on the line of Monitoring Performance on LVM. And the obvious tool would be something like a generic unix tool like sar or let's say a more known form on HPUX called as glance.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
    <pubDate>Sat, 21 May 2011 20:12:50 GMT</pubDate>
    <dc:creator>Ismail Azad</dc:creator>
    <dc:date>2011-05-21T20:12:50Z</dc:date>
    <item>
      <title>pvmove on mounted production server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789669#M534501</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;is it safe to do pvmove on mounted production server?&lt;BR /&gt;&lt;BR /&gt;I'd like to remove PV from VG, after shrinking the FS as the utilization is low.&lt;BR /&gt;&lt;BR /&gt;it's hp-ux 11.11&lt;BR /&gt;&lt;BR /&gt;thank you</description>
      <pubDate>Thu, 19 May 2011 07:49:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789669#M534501</guid>
      <dc:creator>meem_1</dc:creator>
      <dc:date>2011-05-19T07:49:48Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove on mounted production server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789670#M534502</link>
      <description>pvmove will move the extents very carefully, checking the validity, then copying it, verifying the copy and then changing the extent map to point to the new location. AS such, it is very slow so any activity on that VG will be delayed until all the extents are moved. It should be safe on a production server, but like any data transfer, a hang or core dump or system crash could leave the VG damaged, possibly requiring a complete rebuild and restore.</description>
      <pubDate>Thu, 19 May 2011 12:45:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789670#M534502</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2011-05-19T12:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove on mounted production server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789671#M534503</link>
      <description>hello meem,&lt;BR /&gt;&lt;BR /&gt;better you post vgdisplay -v o/p for vg. &lt;BR /&gt;then tellme what you want. &lt;BR /&gt;pvmove is safe but must be used carefully.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Awadhesh</description>
      <pubDate>Fri, 20 May 2011 13:28:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789671#M534503</guid>
      <dc:creator>AwadheshPandey</dc:creator>
      <dc:date>2011-05-20T13:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove on mounted production server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789672#M534504</link>
      <description>Hi meem,&lt;BR /&gt;&lt;BR /&gt;What you are trying to do is standard procedure. Moving extents off a disk that is underutilized and making it usable on a more appropriate volume group. &lt;BR /&gt;&lt;BR /&gt;Just one word of caution, careless pvmove's, lvextend's etc can lead to the fragmentation of the extent space on LVM which is a prominent concept on the line of Monitoring Performance on LVM. And the obvious tool would be something like a generic unix tool like sar or let's say a more known form on HPUX called as glance.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
      <pubDate>Sat, 21 May 2011 20:12:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789672#M534504</guid>
      <dc:creator>Ismail Azad</dc:creator>
      <dc:date>2011-05-21T20:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: pvmove on mounted production server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789673#M534505</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;Its possible but if your server is having heavy IO this PV move will creating performance issue .&lt;BR /&gt;&lt;BR /&gt;BDD</description>
      <pubDate>Thu, 09 Jun 2011 11:01:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvmove-on-mounted-production-server/m-p/4789673#M534505</guid>
      <dc:creator>BDD</dc:creator>
      <dc:date>2011-06-09T11:01:04Z</dc:date>
    </item>
  </channel>
</rss>

