<?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: Mounting snapshots for dev instances in Array Performance and Data Protection</title>
    <link>https://community.hpe.com/t5/array-performance-and-data/mounting-snapshots-for-dev-instances/m-p/6984597#M737</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Matthew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nimble snapshots are mostly read-only, so mounting a read-only snapshot for Oracle DBs won't really give you the functionality you're looking for. Therefore it's best to clone the volume from a Nimble snapshot, as it becomes a full writable volume, but still does not copy any of the back end data associated with it. Essentially, it's doing what you want it to do for your dev DB instance, yet it's not invalidating, modifying or corrupting your original snapshot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's no performance differential between snapshots or clones, and neither have an impact performance wise on the parent volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps answer your question?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Aug 2015 17:27:16 GMT</pubDate>
    <dc:creator>Nick_Dyer</dc:creator>
    <dc:date>2015-08-21T17:27:16Z</dc:date>
    <item>
      <title>Mounting snapshots for dev instances</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/mounting-snapshots-for-dev-instances/m-p/6984596#M736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need to create a development instance of an Oracle database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the impact if I mount a snapshot of a LUN versus cloning the LUN completely?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2015 02:25:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/mounting-snapshots-for-dev-instances/m-p/6984596#M736</guid>
      <dc:creator>matt_mitchell</dc:creator>
      <dc:date>2015-08-21T02:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: Mounting snapshots for dev instances</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/mounting-snapshots-for-dev-instances/m-p/6984597#M737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Matthew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nimble snapshots are mostly read-only, so mounting a read-only snapshot for Oracle DBs won't really give you the functionality you're looking for. Therefore it's best to clone the volume from a Nimble snapshot, as it becomes a full writable volume, but still does not copy any of the back end data associated with it. Essentially, it's doing what you want it to do for your dev DB instance, yet it's not invalidating, modifying or corrupting your original snapshot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's no performance differential between snapshots or clones, and neither have an impact performance wise on the parent volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps answer your question?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2015 17:27:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/mounting-snapshots-for-dev-instances/m-p/6984597#M737</guid>
      <dc:creator>Nick_Dyer</dc:creator>
      <dc:date>2015-08-21T17:27:16Z</dc:date>
    </item>
  </channel>
</rss>

