<?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: EVA Continuous access in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808295#M20679</link>
    <description>Thank you much Uwe.&lt;BR /&gt;&lt;BR /&gt; That clears many things up for me. So the firmware handles most of the operations. If its not to much to ask, might you expand on "properly keeping track of the internal meta-data"...  just a brief note would suffice...is there a tool,script, or section in the GUI I should familiarize myself with ?</description>
    <pubDate>Tue, 20 Jun 2006 12:50:39 GMT</pubDate>
    <dc:creator>galenr4</dc:creator>
    <dc:date>2006-06-20T12:50:39Z</dc:date>
    <item>
      <title>EVA Continuous access</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808293#M20677</link>
      <description>Gentlemen/Madams- A question... Since the EVA stripes across all avilable disks there are no selected "raid groups" per se.How then does one determine exactly where that data is and how is it kept uncorrupted/in tact and synchronized during datatransfer during CA operations? I wouldn't know the block count to ensure my DR disk is the correct size to copy to if I don't know where the data is precisely. I hope you can visualize what I a,m saying here and trying to undeerstand the mechanism... Any insight is greatly appreciated. Thanx in advance</description>
      <pubDate>Mon, 19 Jun 2006 17:07:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808293#M20677</guid>
      <dc:creator>galenr4</dc:creator>
      <dc:date>2006-06-19T17:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Continuous access</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808294#M20678</link>
      <description>You can't determine on which disk drive which data block is stored. Even if you had found it out, it can change over time.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; how is it kept uncorrupted/in tact&lt;BR /&gt;&lt;BR /&gt;By properly keeping track of the internal meta data.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; synchronized during datatransfer during CA operations?&lt;BR /&gt;&lt;BR /&gt;That is a function of the controller firmware - if it does not - that would be a bug in the software.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I wouldn't know the block count to ensure my DR disk is the correct size to copy to if I don't know where the data is precisely.&lt;BR /&gt;&lt;BR /&gt;Sorry, I don't understand - the EVA firmware makes sure that the destination virtual disk has the same size like the source disk. In fact, it creates the destination virtual disk for you when you set up a copy-set.</description>
      <pubDate>Tue, 20 Jun 2006 12:39:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808294#M20678</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-06-20T12:39:13Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Continuous access</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808295#M20679</link>
      <description>Thank you much Uwe.&lt;BR /&gt;&lt;BR /&gt; That clears many things up for me. So the firmware handles most of the operations. If its not to much to ask, might you expand on "properly keeping track of the internal meta-data"...  just a brief note would suffice...is there a tool,script, or section in the GUI I should familiarize myself with ?</description>
      <pubDate>Tue, 20 Jun 2006 12:50:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808295#M20679</guid>
      <dc:creator>galenr4</dc:creator>
      <dc:date>2006-06-20T12:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Continuous access</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808296#M20680</link>
      <description>&amp;gt; might you expand on "properly keeping track of the internal meta-data"&lt;BR /&gt;&lt;BR /&gt;What I meant is: the integrity of the user data is ensured by not making programming errors in the controller firmware.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you will be responsible for managing / implementing CA EVA, I suggest you make yourself familiar with:&lt;BR /&gt;- Command View EVA - the main management GUI&lt;BR /&gt;- SSSU (Storage System Scripting Utility)&lt;BR /&gt;-- for simple automation tasks&lt;BR /&gt;- RSM (Replication Solutions Manager)&lt;BR /&gt;-- a framework for Business Copy and Continuous Access management tasks</description>
      <pubDate>Tue, 20 Jun 2006 13:06:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808296#M20680</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-06-20T13:06:12Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Continuous access</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808297#M20681</link>
      <description>GOTCHA... THANX AGAIN...downloading docs now !!!&lt;BR /&gt;&lt;BR /&gt;Much Obliged</description>
      <pubDate>Tue, 20 Jun 2006 13:08:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-continuous-access/m-p/3808297#M20681</guid>
      <dc:creator>galenr4</dc:creator>
      <dc:date>2006-06-20T13:08:31Z</dc:date>
    </item>
  </channel>
</rss>

