<?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 CA license capacity problem in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416342#M31097</link>
    <description>IO should be written into the source log file only when the access to the destination is disrupted. Are the CA links ok?</description>
    <pubDate>Fri, 08 May 2009 18:52:17 GMT</pubDate>
    <dc:creator>IBaltay</dc:creator>
    <dc:date>2009-05-08T18:52:17Z</dc:date>
    <item>
      <title>eva CA license capacity problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416340#M31095</link>
      <description>We have used 979G of 1TB of CA license capacity in our eva storage system. When we expand a vdisk which is in a data replication group to 140G from 120G,the Command View display this vdisk allocated capacity and requested capacity unknown, operational state is null. dr group state is logging(not merging). We try to remove the vdisk dr group but failed. Does anyone have a solution ?</description>
      <pubDate>Fri, 08 May 2009 18:05:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416340#M31095</guid>
      <dc:creator>ZQiang</dc:creator>
      <dc:date>2009-05-08T18:05:51Z</dc:date>
    </item>
    <item>
      <title>Re: eva CA license capacity problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416341#M31096</link>
      <description>hi,&lt;BR /&gt;there are couple of questions here:&lt;BR /&gt;&lt;BR /&gt;1.are you using the enhanced asynchronous replication mode?&lt;BR /&gt;&lt;BR /&gt;2. do you have enough free space on the source and destination EVA?&lt;BR /&gt;&lt;BR /&gt;Note&lt;BR /&gt;Logging means that CA writes into the log only&lt;BR /&gt;Merging means that CA is reading from the log and sent to the destination vdisk.&lt;BR /&gt;</description>
      <pubDate>Fri, 08 May 2009 18:49:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416341#M31096</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-05-08T18:49:01Z</dc:date>
    </item>
    <item>
      <title>Re: eva CA license capacity problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416342#M31097</link>
      <description>IO should be written into the source log file only when the access to the destination is disrupted. Are the CA links ok?</description>
      <pubDate>Fri, 08 May 2009 18:52:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416342#M31097</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-05-08T18:52:17Z</dc:date>
    </item>
    <item>
      <title>Re: eva CA license capacity problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416343#M31098</link>
      <description>We have enough free space and dr-group is in synchronous mode.CA-link is good.</description>
      <pubDate>Mon, 11 May 2009 14:30:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-ca-license-capacity-problem/m-p/4416343#M31098</guid>
      <dc:creator>ZQiang</dc:creator>
      <dc:date>2009-05-11T14:30:57Z</dc:date>
    </item>
  </channel>
</rss>

