<?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: Snapclone On EVA in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195737#M5429</link>
    <description>Doing the clone puts an additional burden on the controllers and disks. Also, if I recall correctly, you cannot present the clone to the same server under UP-UX. Well, many operating systems cannot cope with 'redundant' meta data on the disks.&lt;BR /&gt;&lt;BR /&gt;In our lab I once had a Windows server stalling the access to a LUN from which a snapshot was taken, but that was due to an old version of Secure Path.&lt;BR /&gt;&lt;BR /&gt;There might be a problem when you are creating multiple snapshots of the same LUN. There is a special way to toggle the snapshot cache to write-through, but it will decrease performance to the parent LUNs. I would not make such a change without a real need. See if you can test your whole configuration under load before you put it into real use.&lt;BR /&gt;&lt;BR /&gt;I'll be doing a BC EVA implementation with HP-UX PA-RISC servers in about 2-4 weeks. While we very likely will not use clones you might be interested in the results anyway?</description>
    <pubDate>Wed, 18 Feb 2004 13:19:10 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2004-02-18T13:19:10Z</dc:date>
    <item>
      <title>Snapclone On EVA</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195736#M5428</link>
      <description>We want to use the snapclone feature on a Eva under hp/ux itanium servers.&lt;BR /&gt;We have heard about problems with the controllers and their intensive usage when using this option.&lt;BR /&gt;have you informations about that?&lt;BR /&gt;thanks&lt;BR /&gt;tmj</description>
      <pubDate>Wed, 18 Feb 2004 12:31:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195736#M5428</guid>
      <dc:creator>Mme Jonnaert</dc:creator>
      <dc:date>2004-02-18T12:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: Snapclone On EVA</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195737#M5429</link>
      <description>Doing the clone puts an additional burden on the controllers and disks. Also, if I recall correctly, you cannot present the clone to the same server under UP-UX. Well, many operating systems cannot cope with 'redundant' meta data on the disks.&lt;BR /&gt;&lt;BR /&gt;In our lab I once had a Windows server stalling the access to a LUN from which a snapshot was taken, but that was due to an old version of Secure Path.&lt;BR /&gt;&lt;BR /&gt;There might be a problem when you are creating multiple snapshots of the same LUN. There is a special way to toggle the snapshot cache to write-through, but it will decrease performance to the parent LUNs. I would not make such a change without a real need. See if you can test your whole configuration under load before you put it into real use.&lt;BR /&gt;&lt;BR /&gt;I'll be doing a BC EVA implementation with HP-UX PA-RISC servers in about 2-4 weeks. While we very likely will not use clones you might be interested in the results anyway?</description>
      <pubDate>Wed, 18 Feb 2004 13:19:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195737#M5429</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-02-18T13:19:10Z</dc:date>
    </item>
    <item>
      <title>Re: Snapclone On EVA</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195738#M5430</link>
      <description>Hi Tmj,&lt;BR /&gt;&lt;BR /&gt;The snapclones are faster for smaller LUN Sizes... on the same DG.&lt;BR /&gt;&lt;BR /&gt;A good alternative si to use the clone feature in Vxfs, you can achieve all the same functions without the additional space overhead of the snapclone.&lt;BR /&gt;&lt;BR /&gt;Hope this helps..&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Orrin.</description>
      <pubDate>Wed, 18 Feb 2004 21:48:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195738#M5430</guid>
      <dc:creator>Orrin</dc:creator>
      <dc:date>2004-02-18T21:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Snapclone On EVA</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195739#M5431</link>
      <description>Snapshot = Space conservative and almost no time to make.  We use this!&lt;BR /&gt;&lt;BR /&gt;Snapclone = Full copy that takes time to make.  If you are attempting to make a backup copy of a 500GB database, this can take a couple of hours to create.&lt;BR /&gt;&lt;BR /&gt;While the snapclone is available almost immediately for usage, your EVA performance will be degredated until the copy is completed.  We DO NOT use this!&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Feb 2004 23:38:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195739#M5431</guid>
      <dc:creator>Mike Naime</dc:creator>
      <dc:date>2004-02-18T23:38:34Z</dc:date>
    </item>
    <item>
      <title>Re: Snapclone On EVA</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195740#M5432</link>
      <description>I'd like to humbly correct Uwe's statement about not being able to mount snapclone's on the same host...  This most certainly can be done in HPUX.  I haven't done it with an EVA, but do it routinely with EMC's, XP's, and VA storage systems.  HP wrote a command called vgchgid for when EMC for came out with the BCV (business continuity volume) for hpux 5-10 years ago.  This command changes the VGID that is saved in the VGRA (volume group reserved area) or at least that where I think it is stored...&lt;BR /&gt;&lt;BR /&gt;To use it just do "vgchgid /dev/rdsk/c0t0d0" then do your vgimport, vgchange, fsck, mount.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;JJ&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Mar 2004 14:51:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195740#M5432</guid>
      <dc:creator>JJ Urich</dc:creator>
      <dc:date>2004-03-26T14:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: Snapclone On EVA</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195741#M5433</link>
      <description>Ah. That's good to know. The BC administration guide explicitly states that it is not supported by BC itself. I will keep this in mind when I get back to the system administrator with whom I should implement BC.&lt;BR /&gt;&lt;BR /&gt;I am not familiar with LVM - what is one supposed to do when the VG is made of multiple PVs?</description>
      <pubDate>Fri, 26 Mar 2004 15:32:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/snapclone-on-eva/m-p/3195741#M5433</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-03-26T15:32:55Z</dc:date>
    </item>
  </channel>
</rss>

