<?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: Continuous Access basics... in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129417#M25892</link>
    <description>The DRG objects and Vdisks on the destination EVA are created automatically.&lt;BR /&gt;Last time I checked, a destination Vdisk MUST NOT even exist.</description>
    <pubDate>Tue, 15 Jan 2008 09:45:45 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2008-01-15T09:45:45Z</dc:date>
    <item>
      <title>Continuous Access basics...</title>
      <link>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129416#M25891</link>
      <description>i am curious how CA works. If you create a DR group on EVA1, does Command view Eva automatically create the destination DR group on EVA2? And does Command view EVA automatically create the destination VRAIDs? Or do i need to create the destination DR/VRAIDs by meself?&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Jan 2008 09:34:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129416#M25891</guid>
      <dc:creator>Timo Steylen</dc:creator>
      <dc:date>2008-01-15T09:34:21Z</dc:date>
    </item>
    <item>
      <title>Re: Continuous Access basics...</title>
      <link>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129417#M25892</link>
      <description>The DRG objects and Vdisks on the destination EVA are created automatically.&lt;BR /&gt;Last time I checked, a destination Vdisk MUST NOT even exist.</description>
      <pubDate>Tue, 15 Jan 2008 09:45:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129417#M25892</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-01-15T09:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: Continuous Access basics...</title>
      <link>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129418#M25893</link>
      <description>thanks!</description>
      <pubDate>Tue, 15 Jan 2008 10:43:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129418#M25893</guid>
      <dc:creator>Timo Steylen</dc:creator>
      <dc:date>2008-01-15T10:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: Continuous Access basics...</title>
      <link>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129419#M25894</link>
      <description>2 notes.&lt;BR /&gt;- The destination vdisk can be of different vraid type than the source&lt;BR /&gt;- The destination vdisk cannot be used by a server. It can be pressented but the server will not see it (until failover is done).&lt;BR /&gt;&lt;BR /&gt;Check administrator guide:&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01080802/c01080802.pdf" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01080802/c01080802.pdf&lt;/A&gt; &lt;BR /&gt;and planning guide:&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01080818/c01080818.pdf" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01080818/c01080818.pdf&lt;/A&gt;</description>
      <pubDate>Tue, 15 Jan 2008 21:07:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/continuous-access-basics/m-p/4129419#M25894</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2008-01-15T21:07:42Z</dc:date>
    </item>
  </channel>
</rss>

