<?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: URGENT: renaming volume group in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841061#M635604</link>
    <description>Hi Saulius,&lt;BR /&gt;&lt;BR /&gt;you should not worry...vgexport/vgimport will not impact your data in your vg...&lt;BR /&gt;But keep a backup of your system ;-)&lt;BR /&gt;&lt;BR /&gt;- create a new mapfile&lt;BR /&gt;vgexport -p -m /tmp/vg.map /dev/vg02&lt;BR /&gt;- shutdown your database&lt;BR /&gt;- umount the filesystem&lt;BR /&gt;- deactivate the vg&lt;BR /&gt;vgchange -a n /dev/vg02&lt;BR /&gt;- then edit your mapfile (replace the vgname)&lt;BR /&gt;- create "new" /dev/vgnewname &lt;BR /&gt;- do mknod and so on&lt;BR /&gt;- now vgimport:&lt;BR /&gt;vgimport -m /tmp/vg.map /dev/vgnewname /dev/dsk/cxtyd0&lt;BR /&gt;&lt;BR /&gt;- if you have many disks you can use an  insertfile where you entry all your disks&lt;BR /&gt;&lt;BR /&gt;vgimport -m /tmp/vg.map -f infile /dev/vgnewname&lt;BR /&gt;&lt;BR /&gt;- then mount your filesystems&lt;BR /&gt;- start your database&lt;BR /&gt;&lt;BR /&gt;Good luck!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 08 Nov 2002 07:56:46 GMT</pubDate>
    <dc:creator>Elif Gius</dc:creator>
    <dc:date>2002-11-08T07:56:46Z</dc:date>
    <item>
      <title>URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841054#M635597</link>
      <description>Sorry for capitals, but I'm in the very bad situation as system admin. I have allready installed and running production application on the borrowed disks, which resides on /dev/vg02. Now we bought our own disks (actually it's array accessed through FC HBA), and we need somehow replace theese borrowed disks with our ones. &lt;BR /&gt;How to move data I understand, but how to "rename" /dev/vg03 (our disks) to /dev/vg02 (assuming that we remove all physical disks which provide PE for all LV in vg02). Note that destroying data in vg02 is not acceptable :(. &lt;BR /&gt;The worst thing, that I have no expierence with HPUX (two months or so)&lt;BR /&gt;&lt;BR /&gt;HELP! :'(&lt;BR /&gt;&lt;BR /&gt;Saulius</description>
      <pubDate>Fri, 08 Nov 2002 06:11:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841054#M635597</guid>
      <dc:creator>Saulius_1</dc:creator>
      <dc:date>2002-11-08T06:11:41Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841055#M635598</link>
      <description>The only way you can actually rename a volume group is during the vgimport process. You can't *just rename it*.&lt;BR /&gt;&lt;BR /&gt;If you going to create /dev/vg03 and copy the data, why do you need to need to rename it (vg02) at all.&lt;BR /&gt;Once you have migrated everything across to the new volumes and are satisfied with the new set up, all you have to do is a vgexport of /dev/vg02 to remove it and the disks from your system.</description>
      <pubDate>Fri, 08 Nov 2002 06:21:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841055#M635598</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-11-08T06:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841056#M635599</link>
      <description>check these hp doc&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062937554" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062937554&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062683936" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062683936&lt;/A&gt;</description>
      <pubDate>Fri, 08 Nov 2002 06:34:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841056#M635599</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-11-08T06:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841057#M635600</link>
      <description>check these hp doc&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062937554" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062937554&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062683936" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062683936&lt;/A&gt;</description>
      <pubDate>Fri, 08 Nov 2002 06:35:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841057#M635600</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-11-08T06:35:43Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841058#M635601</link>
      <description>check these hp doc&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062937554" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062937554&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062683936" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062683936&lt;/A&gt;</description>
      <pubDate>Fri, 08 Nov 2002 06:37:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841058#M635601</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-11-08T06:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841059#M635602</link>
      <description>The main problem is, that software is using informix database, which is using partitions of type RAW. I have no idea, how DB accesses these partitions, and I have bad suspicion, that they are accessed like /dev/vg02/lvol554, not in some wise way :(.&lt;BR /&gt;So I plan to copy everything when informix is down, and to start informix "like nothing changed". What do you think ? Is it possible NOT to configure application (it's third party one, not ours), and to change those damn disks :(.&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Nov 2002 07:17:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841059#M635602</guid>
      <dc:creator>Saulius_1</dc:creator>
      <dc:date>2002-11-08T07:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841060#M635603</link>
      <description>What about data consistency when doing vgexport/import ?&lt;BR /&gt;Do these commands affect any side user data ? Or it's only system tables under /etc/ dir change.</description>
      <pubDate>Fri, 08 Nov 2002 07:23:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841060#M635603</guid>
      <dc:creator>Saulius_1</dc:creator>
      <dc:date>2002-11-08T07:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841061#M635604</link>
      <description>Hi Saulius,&lt;BR /&gt;&lt;BR /&gt;you should not worry...vgexport/vgimport will not impact your data in your vg...&lt;BR /&gt;But keep a backup of your system ;-)&lt;BR /&gt;&lt;BR /&gt;- create a new mapfile&lt;BR /&gt;vgexport -p -m /tmp/vg.map /dev/vg02&lt;BR /&gt;- shutdown your database&lt;BR /&gt;- umount the filesystem&lt;BR /&gt;- deactivate the vg&lt;BR /&gt;vgchange -a n /dev/vg02&lt;BR /&gt;- then edit your mapfile (replace the vgname)&lt;BR /&gt;- create "new" /dev/vgnewname &lt;BR /&gt;- do mknod and so on&lt;BR /&gt;- now vgimport:&lt;BR /&gt;vgimport -m /tmp/vg.map /dev/vgnewname /dev/dsk/cxtyd0&lt;BR /&gt;&lt;BR /&gt;- if you have many disks you can use an  insertfile where you entry all your disks&lt;BR /&gt;&lt;BR /&gt;vgimport -m /tmp/vg.map -f infile /dev/vgnewname&lt;BR /&gt;&lt;BR /&gt;- then mount your filesystems&lt;BR /&gt;- start your database&lt;BR /&gt;&lt;BR /&gt;Good luck!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Nov 2002 07:56:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841061#M635604</guid>
      <dc:creator>Elif Gius</dc:creator>
      <dc:date>2002-11-08T07:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841062#M635605</link>
      <description>Thank you all for you answers, I hope you have saved my sleep :), because I will try to do everything in practice. The best thing is, that I have found mapping of informix database &amp;lt;-&amp;gt; disks, (there are links in /dev). So vg renaming is not so crucial. &lt;BR /&gt;</description>
      <pubDate>Fri, 08 Nov 2002 08:04:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841062#M635605</guid>
      <dc:creator>Saulius_1</dc:creator>
      <dc:date>2002-11-08T08:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841063#M635606</link>
      <description>Saulius&lt;BR /&gt;&lt;BR /&gt;It is important to know how to copy the raw volume. You should check your informix manuals. You would propably use the dd command to do it. Just be sure to find that out.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Gerhard</description>
      <pubDate>Mon, 11 Nov 2002 08:13:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841063#M635606</guid>
      <dc:creator>Gerhard Roets</dc:creator>
      <dc:date>2002-11-11T08:13:05Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841064#M635607</link>
      <description>I know I'm a little late, I've been out of town.&lt;BR /&gt;If you have MirrorDisk/UX you could have added the new disks into the existing volume group.  Mirrored your logical volumes to the new disks.  Decremented the mirrors and removed the old disks.  This could all be done on-line.&lt;BR /&gt;If you do not have MirrorDisk, could Informix do the mirroring?  I know you can with Oracle.&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Nov 2002 15:56:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841064#M635607</guid>
      <dc:creator>Dave Wherry</dc:creator>
      <dc:date>2002-11-18T15:56:57Z</dc:date>
    </item>
    <item>
      <title>Re: URGENT: renaming volume group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841065#M635608</link>
      <description>Thanks for reply. I have already migrated to the VA7400 (forum info was VERY helpfull). &lt;BR /&gt;However I will keep in mind that MirrorDisk utility exists and might save my sleep ;).</description>
      <pubDate>Tue, 19 Nov 2002 05:30:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/urgent-renaming-volume-group/m-p/2841065#M635608</guid>
      <dc:creator>Saulius_1</dc:creator>
      <dc:date>2002-11-19T05:30:47Z</dc:date>
    </item>
  </channel>
</rss>

