<?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 server + data migration using continuous access in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/server-data-migration-using-continuous-access/m-p/4504316#M40570</link>
    <description>Hello Friends,&lt;BR /&gt;Following is a sceneario: Company has two datacenters: Ohio-datacenter &amp;amp; Michigan-datacenter. &lt;BR /&gt;datacenter in michigan will be shut down eventually.&lt;BR /&gt;&lt;BR /&gt;Need to move servers and their applications from a michigan datacenter to ohio-datacenter. Windows and HP-UX servers &lt;BR /&gt;&lt;BR /&gt;connected to XP and EVA arrays via brocade switches in both datacenters. Could you please tell me the action plan on &lt;BR /&gt;&lt;BR /&gt;migrating servers with their applications using continuous Access from michigan datacenter to ohio datacenter and &lt;BR /&gt;&lt;BR /&gt;ultimately add them to the existing fabric in ohio datacenter?.&lt;BR /&gt;My plan is as follows, please suggest if you know a better plan:&lt;BR /&gt;&lt;BR /&gt;1) Create PVOLS on michigan datacenter server named "michiserv" using storage from local array.&lt;BR /&gt;2) Create SVOLS on ohio datacenter server named "ohioserv" using storage from local array using continuous access.&lt;BR /&gt;3) After sync is complete between the pvols and svols, split the SVOLS on "ohioserv" and configure them as PVOLS.&lt;BR /&gt;4) Physically move "michiserv" from michigan to ohio.&lt;BR /&gt;5) Allocate storage on michiserv from same array as ohioserv.&lt;BR /&gt;6) Configure SVOLS on michiserv.&lt;BR /&gt;7) Split the SVOL after sync and use as PVOLS.&lt;BR /&gt;8) Return storage on server ohioserv.&lt;BR /&gt;&lt;BR /&gt;Please tell me if you know a better migration plan using continuous access.&lt;BR /&gt;I would appreciate if you could give me raid manager/HP-UX commands to follow this plan. &lt;BR /&gt;&lt;BR /&gt;I appreicate your response.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 28 Sep 2009 18:55:37 GMT</pubDate>
    <dc:creator>white221g</dc:creator>
    <dc:date>2009-09-28T18:55:37Z</dc:date>
    <item>
      <title>server + data migration using continuous access</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/server-data-migration-using-continuous-access/m-p/4504316#M40570</link>
      <description>Hello Friends,&lt;BR /&gt;Following is a sceneario: Company has two datacenters: Ohio-datacenter &amp;amp; Michigan-datacenter. &lt;BR /&gt;datacenter in michigan will be shut down eventually.&lt;BR /&gt;&lt;BR /&gt;Need to move servers and their applications from a michigan datacenter to ohio-datacenter. Windows and HP-UX servers &lt;BR /&gt;&lt;BR /&gt;connected to XP and EVA arrays via brocade switches in both datacenters. Could you please tell me the action plan on &lt;BR /&gt;&lt;BR /&gt;migrating servers with their applications using continuous Access from michigan datacenter to ohio datacenter and &lt;BR /&gt;&lt;BR /&gt;ultimately add them to the existing fabric in ohio datacenter?.&lt;BR /&gt;My plan is as follows, please suggest if you know a better plan:&lt;BR /&gt;&lt;BR /&gt;1) Create PVOLS on michigan datacenter server named "michiserv" using storage from local array.&lt;BR /&gt;2) Create SVOLS on ohio datacenter server named "ohioserv" using storage from local array using continuous access.&lt;BR /&gt;3) After sync is complete between the pvols and svols, split the SVOLS on "ohioserv" and configure them as PVOLS.&lt;BR /&gt;4) Physically move "michiserv" from michigan to ohio.&lt;BR /&gt;5) Allocate storage on michiserv from same array as ohioserv.&lt;BR /&gt;6) Configure SVOLS on michiserv.&lt;BR /&gt;7) Split the SVOL after sync and use as PVOLS.&lt;BR /&gt;8) Return storage on server ohioserv.&lt;BR /&gt;&lt;BR /&gt;Please tell me if you know a better migration plan using continuous access.&lt;BR /&gt;I would appreciate if you could give me raid manager/HP-UX commands to follow this plan. &lt;BR /&gt;&lt;BR /&gt;I appreicate your response.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Sep 2009 18:55:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/server-data-migration-using-continuous-access/m-p/4504316#M40570</guid>
      <dc:creator>white221g</dc:creator>
      <dc:date>2009-09-28T18:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: server + data migration using continuous access</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/server-data-migration-using-continuous-access/m-p/4504317#M40571</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;HPUX&lt;BR /&gt;&lt;BR /&gt;for HPUX it can be done without the CA, only by means of the LVM mirroring including EVAs, that could be connected as the XP external storages. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Windows&lt;BR /&gt;&lt;BR /&gt;here we need CA PVOLs/SVOLs, for swapping the roles you can use the Raid manager (RM) tool (CLI)&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01807131/c01807131.pdf?jumpid=reg_R1002_USEN" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01807131/c01807131.pdf?jumpid=reg_R1002_USEN&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Via the RM, you can save the time needed for additional full CA synch copies, because only the roles of PVOL/SVOL could be swapped and there is no need to split and recreate the pairs...</description>
      <pubDate>Tue, 29 Sep 2009 13:07:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/server-data-migration-using-continuous-access/m-p/4504317#M40571</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-09-29T13:07:38Z</dc:date>
    </item>
  </channel>
</rss>

