<?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: P4300 Backup Options in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/p4300-backup-options/m-p/6024573#M6590</link>
    <description>&lt;P&gt;are you using thin provisioning on the primary volumes?&amp;nbsp; If you are, and 300GB is size of a single snapshot you are pretty much stuck.&amp;nbsp; You need one snapshot on the primary site because it is critical for creating the NEXT snapshot&amp;nbsp; otherwise how would the system know what change information to send remote?&amp;nbsp; If that size is too large, its either because you aren't using thin provisioning or its simply because the amount of data changed over your time period is that large.&amp;nbsp; If its the latter you have one of two options... 1.&amp;nbsp; reduce the amount of data that changes with each snapshot.&amp;nbsp; 2.&amp;nbsp; increase the frequency of the snapshots.&lt;/P&gt;</description>
    <pubDate>Tue, 09 Apr 2013 12:40:47 GMT</pubDate>
    <dc:creator>oikjn</dc:creator>
    <dc:date>2013-04-09T12:40:47Z</dc:date>
    <item>
      <title>P4300 Backup Options</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/p4300-backup-options/m-p/6024153#M6586</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm currently running a three shelf P4300 setup. &amp;nbsp;We purchased a VSA license and have a box off site. &amp;nbsp;I have each volume on the production P4300 set to run a remote snapshot off to the VSA. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I didn't realize at the time of implementation was that the snapshot live on both the VSA and on the production SAN. &amp;nbsp;So for a loaded 300 GB volume, I've got 300 GB tied up in a snapshot that I don't need on the production server. &amp;nbsp;This seems like a lot of wasted space to me. &amp;nbsp;Is there anything I can do differently with my current setup(software is up to date at 10.5)? &amp;nbsp;Do I have any other options beyond the current set up?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any advice.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2013 03:22:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/p4300-backup-options/m-p/6024153#M6586</guid>
      <dc:creator>imc_2</dc:creator>
      <dc:date>2013-04-09T03:22:43Z</dc:date>
    </item>
    <item>
      <title>Re: P4300 Backup Options</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/p4300-backup-options/m-p/6024573#M6590</link>
      <description>&lt;P&gt;are you using thin provisioning on the primary volumes?&amp;nbsp; If you are, and 300GB is size of a single snapshot you are pretty much stuck.&amp;nbsp; You need one snapshot on the primary site because it is critical for creating the NEXT snapshot&amp;nbsp; otherwise how would the system know what change information to send remote?&amp;nbsp; If that size is too large, its either because you aren't using thin provisioning or its simply because the amount of data changed over your time period is that large.&amp;nbsp; If its the latter you have one of two options... 1.&amp;nbsp; reduce the amount of data that changes with each snapshot.&amp;nbsp; 2.&amp;nbsp; increase the frequency of the snapshots.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2013 12:40:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/p4300-backup-options/m-p/6024573#M6590</guid>
      <dc:creator>oikjn</dc:creator>
      <dc:date>2013-04-09T12:40:47Z</dc:date>
    </item>
  </channel>
</rss>

