<?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 cloned Volume Group in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969128#M614656</link>
    <description>Hi Dave,&lt;BR /&gt;&lt;BR /&gt;1) Nope - You need to: A) create the /dev/vg_name dir B) mknod -c 64 0x??????  where ?????? is a unique number not used by an existing VG &lt;BR /&gt;And remember to use the -s on both vgexport &amp;amp; vgimport. This assumes these are the *same* LUNs that system A was using that system B can now see. Make sure system A no longer has visibility of these LUNs when you do the destructive vgexport on it.&lt;BR /&gt;&lt;BR /&gt;2) I don't think this will work because at some point you should remove the old VG &amp;amp; that will wipe the VGID off the PVs - but I could be wrong here.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Jeff</description>
    <pubDate>Wed, 22 Mar 2006 14:09:39 GMT</pubDate>
    <dc:creator>Jeff Schussele</dc:creator>
    <dc:date>2006-03-22T14:09:39Z</dc:date>
    <item>
      <title>Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969127#M614655</link>
      <description>I'm looking to do two things clones in two separate HP-UX environments in the near future.&lt;BR /&gt;&lt;BR /&gt;1. I want to clone a set of luns (all one VG) from one server and mount/import them on another server.&lt;BR /&gt;&lt;BR /&gt;2. I want to clone a set of luns (again all one VG) and import them on the same host as a different VG.&lt;BR /&gt;&lt;BR /&gt;For #1, can I simply do a vgscan and then a vgimport? &lt;BR /&gt;&lt;BR /&gt;For #2, is it the same?&lt;BR /&gt;&lt;BR /&gt;Thanks...&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Wed, 22 Mar 2006 14:02:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969127#M614655</guid>
      <dc:creator>David Silvestri</dc:creator>
      <dc:date>2006-03-22T14:02:30Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969128#M614656</link>
      <description>Hi Dave,&lt;BR /&gt;&lt;BR /&gt;1) Nope - You need to: A) create the /dev/vg_name dir B) mknod -c 64 0x??????  where ?????? is a unique number not used by an existing VG &lt;BR /&gt;And remember to use the -s on both vgexport &amp;amp; vgimport. This assumes these are the *same* LUNs that system A was using that system B can now see. Make sure system A no longer has visibility of these LUNs when you do the destructive vgexport on it.&lt;BR /&gt;&lt;BR /&gt;2) I don't think this will work because at some point you should remove the old VG &amp;amp; that will wipe the VGID off the PVs - but I could be wrong here.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Jeff</description>
      <pubDate>Wed, 22 Mar 2006 14:09:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969128#M614656</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2006-03-22T14:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969129#M614657</link>
      <description>Hi Dave:&lt;BR /&gt;&lt;BR /&gt;The process of 'vgexport' and 'vgimport' accomodates both.  You don't need to 'vgscan'.&lt;BR /&gt;&lt;BR /&gt;In your second question, you are really asking how to change the name of a volume group.  To do that:&lt;BR /&gt;&lt;BR /&gt;# unmount the volume group's logical volumes&lt;BR /&gt;# vgchange -a n /dev/oldvg&lt;BR /&gt;# vgexport -m /tmp/vgmap /dev/oldvg&lt;BR /&gt;# mkdir /dev/newvg&lt;BR /&gt;# mknod /dev/newvg/group c 64 0xNN0000 #...where N is unique&lt;BR /&gt;# vgimport -m /tmp/vgmap /dev/newvg /dev/dsk/pvpath ...&lt;BR /&gt;# vgchange -a y /dev/newvg&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 22 Mar 2006 14:10:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969129#M614657</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-03-22T14:10:38Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969130#M614658</link>
      <description>Shalom Dave,&lt;BR /&gt;&lt;BR /&gt;Your methodology might be a step toward sharing, but cloning? No.&lt;BR /&gt;&lt;BR /&gt;I'd do a vgexport in preview mode, take the map file and use it to import onto the next machine, but this method probably has the same problem.&lt;BR /&gt;&lt;BR /&gt;You might be able to do this on your disk array. EVA-3000 have extensive features for cloning luns. Then present the clone to the second machine.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 22 Mar 2006 14:12:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969130#M614658</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-03-22T14:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969131#M614659</link>
      <description>Thanks for the quick responses... I think I should elaborate a little due to some of the answers.&lt;BR /&gt;&lt;BR /&gt;When I mention cloning, I'm talking about cloning from a back end storage array... not something within HP.&lt;BR /&gt;&lt;BR /&gt;For the second option. I need to clone a drive, and mount it to back it up, on the same server. I was wondering if you can clone the drive, and then import it as a new VG group... i.e. clone vg01 and import as vg99.&lt;BR /&gt;&lt;BR /&gt;Thanks again...&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Wed, 22 Mar 2006 15:24:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969131#M614659</guid>
      <dc:creator>David Silvestri</dc:creator>
      <dc:date>2006-03-22T15:24:02Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969132#M614660</link>
      <description>Dave,&lt;BR /&gt;&lt;BR /&gt;You can clone the drive and import it on the same server.  The command that accomplishes this is 'vgchgid'.&lt;BR /&gt;&lt;BR /&gt;Once you have the clone presented:&lt;BR /&gt;&lt;BR /&gt;vgchgid /dev/rdsk/cXtXdX&lt;BR /&gt;mkdir /dev/vgNN&lt;BR /&gt;mknod /dev/vgNN/group c 64 0xnn0000&lt;BR /&gt;vgimport /dev/vgNN /dev/dsk/cXtXdX&lt;BR /&gt;vgchange -a y vgNN&lt;BR /&gt;&lt;BR /&gt;Then you can mount your logical volumes on whatever filesystems you wanted.  The onyl trouble I have ever had with this is that I usually have to do an fsck before mounting the volumes.&lt;BR /&gt;&lt;BR /&gt;Hope it helps&lt;BR /&gt;John</description>
      <pubDate>Wed, 22 Mar 2006 15:33:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969132#M614660</guid>
      <dc:creator>John Payne_2</dc:creator>
      <dc:date>2006-03-22T15:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969133#M614661</link>
      <description>Oops, then the thing I always forget.&lt;BR /&gt;&lt;BR /&gt;vgcfgbackup /dev/vgNN&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;John</description>
      <pubDate>Wed, 22 Mar 2006 15:35:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969133#M614661</guid>
      <dc:creator>John Payne_2</dc:creator>
      <dc:date>2006-03-22T15:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969134#M614662</link>
      <description>Hi David,&lt;BR /&gt;John's step will work perfectly. The only reason you need do fsck is because your source lun in open status i,e it is active. If possible, unmount the source before you start the clone process.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Sathish</description>
      <pubDate>Wed, 22 Mar 2006 22:03:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969134#M614662</guid>
      <dc:creator>sathish kannan</dc:creator>
      <dc:date>2006-03-22T22:03:45Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969135#M614663</link>
      <description>Thanks for all the responses...&lt;BR /&gt;&lt;BR /&gt;I guess it's time to go play :)&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Thu, 23 Mar 2006 10:46:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969135#M614663</guid>
      <dc:creator>David Silvestri</dc:creator>
      <dc:date>2006-03-23T10:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: Importing a cloned Volume Group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969136#M614664</link>
      <description>Using the responses I was directed to the command vgchgid (which I'd never used before). &lt;BR /&gt;&lt;BR /&gt;The man page for the command gives a step by step procedure on how to mount a clone on the same server.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Thu, 23 Mar 2006 10:48:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/importing-a-cloned-volume-group/m-p/4969136#M614664</guid>
      <dc:creator>David Silvestri</dc:creator>
      <dc:date>2006-03-23T10:48:16Z</dc:date>
    </item>
  </channel>
</rss>

