<?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: Prepare for Cluster Migration in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265777#M659469</link>
    <description>Thx</description>
    <pubDate>Wed, 08 Dec 2010 15:21:33 GMT</pubDate>
    <dc:creator>Jacky Wing</dc:creator>
    <dc:date>2010-12-08T15:21:33Z</dc:date>
    <item>
      <title>Prepare for Cluster Migration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265771#M659459</link>
      <description>I have a two node cluster with an EVA system. I want to present all the vdisks of the cluster to a third system. &lt;BR /&gt;I want to do that since I want to prepare for cluster migration to new systems. I want to be able to present disks and note the paths and ... so I can vgexport / vgimport later on without any surprises. &lt;BR /&gt;&lt;BR /&gt;Am i able to present the vdisks without corrupting the data? all I will be doing is:&lt;BR /&gt;- ioscan -fnC disks&lt;BR /&gt;- ioscan -m dsf&lt;BR /&gt;- vgimport from the old system &amp;amp; be sure that the architecture is preserved&lt;BR /&gt;- create directory without activating the volume group &amp;amp; mounting&lt;BR /&gt;- preparing cluster configuration and cmcheckconf without cmapplyconf&lt;BR /&gt;&lt;BR /&gt;what do you think?</description>
      <pubDate>Wed, 08 Dec 2010 10:52:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265771#M659459</guid>
      <dc:creator>Jacky Wing</dc:creator>
      <dc:date>2010-12-08T10:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: Prepare for Cluster Migration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265772#M659460</link>
      <description>Your steps look reasonable.  You will probably have to 'zone' the LUNs on the array to appear on the third node.</description>
      <pubDate>Wed, 08 Dec 2010 14:13:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265772#M659460</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2010-12-08T14:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: Prepare for Cluster Migration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265773#M659462</link>
      <description>at some stage in the plan you WILL have to test whether the devices work by activating the volume group, even if only in read-only mode.&lt;BR /&gt;Likewise the directory mount points must be tested&lt;BR /&gt;&lt;BR /&gt;Make sure that the new node has the same SG version and pacth as the existing nodes prior to adding it in to the cluster</description>
      <pubDate>Wed, 08 Dec 2010 14:18:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265773#M659462</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2010-12-08T14:18:36Z</dc:date>
    </item>
    <item>
      <title>Re: Prepare for Cluster Migration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265774#M659463</link>
      <description>Thank you for replying.&lt;BR /&gt;the cluster is not the same, it is a new cluster with new name.&lt;BR /&gt;My question is:&lt;BR /&gt;&lt;BR /&gt;- Can I present the luns to the new system, vgimport the architecture from the old system, create the directories, prepare the cluster config, check it  ---- All that without disrupting the running cluster. &lt;BR /&gt;&lt;BR /&gt;Does the above actions lead to a corrupted data on the luns? I will not activate the vg nor I will mount the directories.&lt;BR /&gt;&lt;BR /&gt;When all above is done, can I apply the cluster conf (also without disrupting the nodes running?)</description>
      <pubDate>Wed, 08 Dec 2010 14:50:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265774#M659463</guid>
      <dc:creator>Jacky Wing</dc:creator>
      <dc:date>2010-12-08T14:50:14Z</dc:date>
    </item>
    <item>
      <title>Re: Prepare for Cluster Migration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265775#M659465</link>
      <description>Hey;&lt;BR /&gt;&lt;BR /&gt;- Can I present the luns to the new system, vgimport the architecture from the old system, create the directories, prepare the cluster config, check it ---- All that without disrupting the running cluster.&lt;BR /&gt;&lt;BR /&gt;Yes&lt;BR /&gt;&lt;BR /&gt;Does the above actions lead to a corrupted data on the luns? I will not activate the vg nor I will mount the directories.&lt;BR /&gt;&lt;BR /&gt;No&lt;BR /&gt;&lt;BR /&gt;When all above is done, can I apply the cluster conf (also without disrupting the nodes running?)&lt;BR /&gt;&lt;BR /&gt;yes&lt;BR /&gt;&lt;BR /&gt;The cmquerycl, cmcheckconf and cmapplyconf commands don't write to any shared disk.  it will check to see if you *have* any shared disks but doesn't write to them at all.&lt;BR /&gt;&lt;BR /&gt;On second thought: you can do all that if you're using a quorum server.  If you're not, you'll need a lock disk which, presumably, will be in one of the shared volume groups.  &lt;BR /&gt;&lt;BR /&gt;So, short version: you can do all of the above as outlined under the assumption that you're using a quorum server.&lt;BR /&gt;&lt;BR /&gt;HTH;&lt;BR /&gt;&lt;BR /&gt;Doug O'Leary</description>
      <pubDate>Wed, 08 Dec 2010 14:58:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265775#M659465</guid>
      <dc:creator>Doug O'Leary</dc:creator>
      <dc:date>2010-12-08T14:58:59Z</dc:date>
    </item>
    <item>
      <title>Re: Prepare for Cluster Migration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265776#M659467</link>
      <description>Thank you Doug, &amp;amp; all.&lt;BR /&gt;&lt;BR /&gt;Actually I have a 1 GB lun for the lock, I prefer it this way, less prone to errors.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Dec 2010 15:19:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265776#M659467</guid>
      <dc:creator>Jacky Wing</dc:creator>
      <dc:date>2010-12-08T15:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: Prepare for Cluster Migration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265777#M659469</link>
      <description>Thx</description>
      <pubDate>Wed, 08 Dec 2010 15:21:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/prepare-for-cluster-migration/m-p/5265777#M659469</guid>
      <dc:creator>Jacky Wing</dc:creator>
      <dc:date>2010-12-08T15:21:33Z</dc:date>
    </item>
  </channel>
</rss>

