<?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: Presenting Virtual Disk in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082720#M27672</link>
    <description>Yes - just present the snapclone, and you don't have to worry about changing the replication settings and you can always snaplclone again if you think you messed up the copy of the data.</description>
    <pubDate>Wed, 10 Oct 2007 12:09:31 GMT</pubDate>
    <dc:creator>McCready</dc:creator>
    <dc:date>2007-10-10T12:09:31Z</dc:date>
    <item>
      <title>Presenting Virtual Disk</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082715#M27667</link>
      <description>I have a continous access replication between two sites. I want to be able to present the destination copy of a DR group. In windows it is giving me an error each time i try to present.&lt;BR /&gt;do you have any idea?&lt;BR /&gt;&lt;BR /&gt;How to get the controller World Wide Node Name?&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Oct 2007 08:53:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082715#M27667</guid>
      <dc:creator>Jacky Wing</dc:creator>
      <dc:date>2007-10-08T08:53:00Z</dc:date>
    </item>
    <item>
      <title>Re: Presenting Virtual Disk</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082716#M27668</link>
      <description>Hi.&lt;BR /&gt;All destination disks in DR have to be presented like read only. It's not recommended to present read only disks to windows OS. It should caused problems like bluescreen in past. &lt;BR /&gt;For real CA cluster with MS Win cluster you have to buy CLX extension for MS cluster and this CLX will allow you to create automatic presentation and change of source-destination in cluster environment.&lt;BR /&gt;have a nice day</description>
      <pubDate>Mon, 08 Oct 2007 10:10:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082716#M27668</guid>
      <dc:creator>mmax</dc:creator>
      <dc:date>2007-10-08T10:10:42Z</dc:date>
    </item>
    <item>
      <title>Re: Presenting Virtual Disk</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082717#M27669</link>
      <description>The destination vdisks should not be visible to the servers as the multipath component and/or the volume management can become confused due to duplicate devices.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; World Wide Node Name&lt;BR /&gt;&lt;BR /&gt;Many ways...&lt;BR /&gt;The WWNN is shown on the OCP and on the Command View EVA's storage system properties page. In most cases, there are also one or two stickers (with the barcode) left and right from the controllers which show the controller WWNN and the checksum.&lt;BR /&gt;You can also see it in SSSU or in the Fibre Channel switch's name server - on Brocade switches this is 'nsShow' ('nsAliasShow' can be helpful, too).&lt;BR /&gt;And you can see it in the Full Featured MPIO's MMC plugin.&lt;BR /&gt;And maybe I have forgotten some more places ;-)</description>
      <pubDate>Mon, 08 Oct 2007 13:42:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082717#M27669</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-10-08T13:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: Presenting Virtual Disk</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082718#M27670</link>
      <description>&lt;!--!*#--&gt;We create a copy of the disks in the DR group by&lt;BR /&gt;- first suspending the replication&lt;BR /&gt;- doing a snapclone into a container of each of the disks in the DR group&lt;BR /&gt;- resuming the replication&lt;BR /&gt;- then present the disks to the intended system.&lt;BR /&gt;If you do the above using an RSM or SSSU script it can complete very quickly.&lt;BR /&gt;&lt;BR /&gt;Of course, doing the above costs us more disk space, but it has a variety of pluses, including allowing us to keep replication going while we test the ability to present the disks to the system at our DR site. &lt;BR /&gt;</description>
      <pubDate>Mon, 08 Oct 2007 20:32:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082718#M27670</guid>
      <dc:creator>McCready</dc:creator>
      <dc:date>2007-10-08T20:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: Presenting Virtual Disk</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082719#M27671</link>
      <description>McCready,&lt;BR /&gt;&lt;BR /&gt;You mean i should present the Snapclone, right? &lt;BR /&gt;Suspend&lt;BR /&gt;Create snapclone&lt;BR /&gt;Resume&lt;BR /&gt;Present Snapclone&lt;BR /&gt;?&lt;BR /&gt;</description>
      <pubDate>Wed, 10 Oct 2007 12:03:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082719#M27671</guid>
      <dc:creator>Jacky Wing</dc:creator>
      <dc:date>2007-10-10T12:03:23Z</dc:date>
    </item>
    <item>
      <title>Re: Presenting Virtual Disk</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082720#M27672</link>
      <description>Yes - just present the snapclone, and you don't have to worry about changing the replication settings and you can always snaplclone again if you think you messed up the copy of the data.</description>
      <pubDate>Wed, 10 Oct 2007 12:09:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/presenting-virtual-disk/m-p/4082720#M27672</guid>
      <dc:creator>McCready</dc:creator>
      <dc:date>2007-10-10T12:09:31Z</dc:date>
    </item>
  </channel>
</rss>

