<?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: Data migration and Mirroring in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927542#M634474</link>
    <description>Rita - I read your post but the difference here is that I must re-use the VG name.&lt;BR /&gt;&lt;BR /&gt;John - I didn't you could import an exported VG with an alternate name.  What must you do to accomplish this?</description>
    <pubDate>Fri, 14 Mar 2003 14:55:08 GMT</pubDate>
    <dc:creator>Darren Gibbs</dc:creator>
    <dc:date>2003-03-14T14:55:08Z</dc:date>
    <item>
      <title>Data migration and Mirroring</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927538#M634470</link>
      <description>We are migrating data from an XP256 to an XP1024.  I'd like to use Mirror/DiskUX to do the migration, but I need to re-create the VG's to handle the larger LUN on the XP1024.  Is my best option to perform a tape backup/restore on my SAN attached library?&lt;BR /&gt;&lt;BR /&gt;BTW - I have to keep the same VG names as our Sybase database is using raw devices and requires the same path name to the device.</description>
      <pubDate>Fri, 14 Mar 2003 14:23:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927538#M634470</guid>
      <dc:creator>Darren Gibbs</dc:creator>
      <dc:date>2003-03-14T14:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: Data migration and Mirroring</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927539#M634471</link>
      <description>Firstly, you need to remember that Mirror/DiskUX functions at the logical volume level within a VG, so you would have set up the XP1024 within the same VG as the XP256.&lt;BR /&gt;&lt;BR /&gt;I would lean towards tape, myself.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Mar 2003 14:28:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927539#M634471</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2003-03-14T14:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: Data migration and Mirroring</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927540#M634472</link>
      <description>I recently migrated data from an Old EMC array to a new one and had the same issue has you with having to recreate the vg's.&lt;BR /&gt;&lt;BR /&gt;Jim &amp;amp; John gave me some great pointers that have proved invaluable in migrating data from array to array.  And although I still have more to go...to date...it has worked seamlessly with NO errors.&lt;BR /&gt;&lt;BR /&gt;Take a look at this thread that recommends the fbackup/frecover option.  And the tips about cleaning up you hardware path.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x520f31ec5e34d711abdc0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x520f31ec5e34d711abdc0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Rgrds,&lt;BR /&gt;Rita&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Mar 2003 14:36:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927540#M634472</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2003-03-14T14:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: Data migration and Mirroring</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927541#M634473</link>
      <description>If you can temporarily connect both XP's then you could:&lt;BR /&gt;&lt;BR /&gt;1.  Create your new VG with a different name.&lt;BR /&gt;2.  Create your new LV's&lt;BR /&gt;3.  Use dd to copy old to new LV's.&lt;BR /&gt;4.  Export both VG's then import the new one with the old one's name.&lt;BR /&gt;&lt;BR /&gt;This avoids tape and you can consider the old VG as a backup until everything has been tested on the new XP.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Mar 2003 14:41:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927541#M634473</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2003-03-14T14:41:34Z</dc:date>
    </item>
    <item>
      <title>Re: Data migration and Mirroring</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927542#M634474</link>
      <description>Rita - I read your post but the difference here is that I must re-use the VG name.&lt;BR /&gt;&lt;BR /&gt;John - I didn't you could import an exported VG with an alternate name.  What must you do to accomplish this?</description>
      <pubDate>Fri, 14 Mar 2003 14:55:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-migration-and-mirroring/m-p/2927542#M634474</guid>
      <dc:creator>Darren Gibbs</dc:creator>
      <dc:date>2003-03-14T14:55:08Z</dc:date>
    </item>
  </channel>
</rss>

