<?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 HP Continuous Access Behaviour in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230686#M59196</link>
    <description>We're currently doing some testing with CA between two EVA's with an ISL of 50MBit.&lt;BR /&gt;&lt;BR /&gt;We created a 50GB Vdisk with one Virtual machine of 10GB on it.&lt;BR /&gt;&lt;BR /&gt;We started replication from one site to the other which took about 2-3 hours.&lt;BR /&gt;&lt;BR /&gt;When we failover to the other side, HP CA start sycning the other way and replicates the entire Vdisk to the original side, knowing that the data is 99% the same. So, every time we failover/failback the Vdisk is replicated entirely (we presume)&lt;BR /&gt;&lt;BR /&gt;Is this normal behaviour? I thought that HP CA would Check what's left of the LUN on the source side and only move the delta's?&lt;BR /&gt;&lt;BR /&gt;?</description>
    <pubDate>Wed, 17 Mar 2010 18:00:00 GMT</pubDate>
    <dc:creator>IvanForceville</dc:creator>
    <dc:date>2010-03-17T18:00:00Z</dc:date>
    <item>
      <title>HP Continuous Access Behaviour</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230686#M59196</link>
      <description>We're currently doing some testing with CA between two EVA's with an ISL of 50MBit.&lt;BR /&gt;&lt;BR /&gt;We created a 50GB Vdisk with one Virtual machine of 10GB on it.&lt;BR /&gt;&lt;BR /&gt;We started replication from one site to the other which took about 2-3 hours.&lt;BR /&gt;&lt;BR /&gt;When we failover to the other side, HP CA start sycning the other way and replicates the entire Vdisk to the original side, knowing that the data is 99% the same. So, every time we failover/failback the Vdisk is replicated entirely (we presume)&lt;BR /&gt;&lt;BR /&gt;Is this normal behaviour? I thought that HP CA would Check what's left of the LUN on the source side and only move the delta's?&lt;BR /&gt;&lt;BR /&gt;?</description>
      <pubDate>Wed, 17 Mar 2010 18:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230686#M59196</guid>
      <dc:creator>IvanForceville</dc:creator>
      <dc:date>2010-03-17T18:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: HP Continuous Access Behaviour</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230687#M59197</link>
      <description>That does not sound correct. Can you give a little more technical details about your EVA configuration ? (firmware revision, using sync/async replication, ...)</description>
      <pubDate>Wed, 17 Mar 2010 18:29:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230687#M59197</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-03-17T18:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: HP Continuous Access Behaviour</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230688#M59198</link>
      <description>We have two EVA4400's with FW 09522xxx and are using Async replication.&lt;BR /&gt;&lt;BR /&gt;Distance between sites is 50-60km.&lt;BR /&gt;&lt;BR /&gt;When we failover to the other side, it takes about 1,5 hours to synchronize towards the original side, knowing that there is only 1 Virtual Machine on the LUN which hasn't changed.&lt;BR /&gt;&lt;BR /&gt;Tested this a few times today.</description>
      <pubDate>Wed, 17 Mar 2010 18:35:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230688#M59198</guid>
      <dc:creator>IvanForceville</dc:creator>
      <dc:date>2010-03-17T18:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: HP Continuous Access Behaviour</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230689#M59199</link>
      <description>Do you switch to sync mode before the failover?</description>
      <pubDate>Wed, 17 Mar 2010 18:40:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230689#M59199</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-03-17T18:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: HP Continuous Access Behaviour</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230690#M59200</link>
      <description>Not realy... But honestly, I need to check. It appears that the copy is in Sync mode but we definately don't explicitly set it.</description>
      <pubDate>Wed, 17 Mar 2010 18:42:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230690#M59200</guid>
      <dc:creator>IvanForceville</dc:creator>
      <dc:date>2010-03-17T18:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: HP Continuous Access Behaviour</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230691#M59201</link>
      <description>Looks like you're doing an UNPLANNED failover, so a full copy is done.&lt;BR /&gt;&lt;BR /&gt;Read the RSM user guide, it's the best way to understand Continuous Access.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02012745/c02012745.pdf" target="_blank"&gt;http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02012745/c02012745.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Look for "PLANNED failover"</description>
      <pubDate>Thu, 18 Mar 2010 07:31:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230691#M59201</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2010-03-18T07:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: HP Continuous Access Behaviour</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230692#M59202</link>
      <description>Guys,&lt;BR /&gt;&lt;BR /&gt;You we're correct. There is a difference between Planned and Unplanned failover... Since we were using Vmware Site Recovery Manager to do the failover the process was automated... didn't catch it.&lt;BR /&gt;&lt;BR /&gt;Thx... close case.</description>
      <pubDate>Tue, 23 Mar 2010 08:45:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hp-continuous-access-behaviour/m-p/5230692#M59202</guid>
      <dc:creator>IvanForceville</dc:creator>
      <dc:date>2010-03-23T08:45:18Z</dc:date>
    </item>
  </channel>
</rss>

