<?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 LVM problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265820#M333497</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;I am confused! We've migrated 3 volume groups from one machine to another, that was some months ago...&lt;BR /&gt;Now I wanted to erase the vgs information from the original machine and I made a vgreduce instead of a vgexport. In the target machine the disks stayed unavailable on one of the 3  vg and the database stoped.&lt;BR /&gt;My questions are:&lt;BR /&gt;- Why the disks stayed unavailable only in one of the vgs?&lt;BR /&gt;- Can I recover from this with a vgcfgrestore? If so, should I do it on the target or on the original machine?&lt;BR /&gt;I hope someone had experienced a situation like this and can help me here.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;R&lt;BR /&gt;</description>
    <pubDate>Tue, 09 Sep 2008 16:24:15 GMT</pubDate>
    <dc:creator>Ramones</dc:creator>
    <dc:date>2008-09-09T16:24:15Z</dc:date>
    <item>
      <title>LVM problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265820#M333497</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I am confused! We've migrated 3 volume groups from one machine to another, that was some months ago...&lt;BR /&gt;Now I wanted to erase the vgs information from the original machine and I made a vgreduce instead of a vgexport. In the target machine the disks stayed unavailable on one of the 3  vg and the database stoped.&lt;BR /&gt;My questions are:&lt;BR /&gt;- Why the disks stayed unavailable only in one of the vgs?&lt;BR /&gt;- Can I recover from this with a vgcfgrestore? If so, should I do it on the target or on the original machine?&lt;BR /&gt;I hope someone had experienced a situation like this and can help me here.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;R&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Sep 2008 16:24:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265820#M333497</guid>
      <dc:creator>Ramones</dc:creator>
      <dc:date>2008-09-09T16:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: LVM problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265821#M333498</link>
      <description>&amp;gt; We've migrated 3 volume groups from one machine to another, that was some months ago...&lt;BR /&gt;These VGs were not completely migrated if they were still connected to the original server. Leaving them still connected to the original server was a very bad thing. When you move disks from one server to another first you vgexport and then you disconnect them from one server and connect them to another.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Why the disks stayed unavailable only in one of the vgs&lt;BR /&gt;Probably becasue the disks of the other VGs were not visible on the original server.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Can I recover...&lt;BR /&gt;Yes. If you have a saved vgXX.conf file on the new server you should do it on the new server and forget about the original one.</description>
      <pubDate>Tue, 09 Sep 2008 16:47:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265821#M333498</guid>
      <dc:creator>TTr</dc:creator>
      <dc:date>2008-09-09T16:47:49Z</dc:date>
    </item>
    <item>
      <title>Re: LVM problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265822#M333499</link>
      <description>is there only one disk in each vg? did you run vgreduce on only one vg? If so that would be why the other vg's were ok. can you post a vggisplay -v &lt;VG&gt; from the target?&lt;/VG&gt;</description>
      <pubDate>Tue, 09 Sep 2008 16:49:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265822#M333499</guid>
      <dc:creator>Court Campbell</dc:creator>
      <dc:date>2008-09-09T16:49:48Z</dc:date>
    </item>
    <item>
      <title>Re: LVM problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265823#M333500</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;We've managed to recover with vgcfgrestore. I know we should had disconnect the disks and made vgexport when we've migrated the vgs. The thing is we may need a roolback the day after...and we make alot of things in alot of machines at the same time...it was a mistake, it happens...the good news is that we could recover.&lt;BR /&gt;Thanks anyway...&lt;BR /&gt;R</description>
      <pubDate>Tue, 09 Sep 2008 17:54:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-problem/m-p/4265823#M333500</guid>
      <dc:creator>Ramones</dc:creator>
      <dc:date>2008-09-09T17:54:58Z</dc:date>
    </item>
  </channel>
</rss>

