<?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 Snapshots – An Overview in Array Performance and Data Protection</title>
    <link>https://community.hpe.com/t5/array-performance-and-data/snapshots-an-overview/m-p/6986833#M1096</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;In the storage world, snapshots are a point-in-time copy of data. They have been around for some time and are increasingly being used by IT to protect stored data. A snapshot copies the metadata (nee index) of the data instead of copying the data itself. This means taking a snapshot is almost always instantaneous. This is one of the primary advantages of storage-based snapshots—they eliminate backup windows. In traditional backup deployments, applications either have to be taken off-line or suffer from degraded performance during backups (which is why traditional backups typically happen during off-peak hours). This means snapshot-based backups can be taken more frequently, improving recovery point objectives. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;For more information, read the blogs:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;– &lt;A href="https://community.hpe.com/nimble-blogpost/1001"&gt;O Snapshot: What Art Thou?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;– &lt;A href="https://community.hpe.com/nimble-blogpost/1004"&gt;Snapshot: Part Deux&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2013 04:26:11 GMT</pubDate>
    <dc:creator>nimble-admin47</dc:creator>
    <dc:date>2013-01-30T04:26:11Z</dc:date>
    <item>
      <title>Snapshots – An Overview</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/snapshots-an-overview/m-p/6986833#M1096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;In the storage world, snapshots are a point-in-time copy of data. They have been around for some time and are increasingly being used by IT to protect stored data. A snapshot copies the metadata (nee index) of the data instead of copying the data itself. This means taking a snapshot is almost always instantaneous. This is one of the primary advantages of storage-based snapshots—they eliminate backup windows. In traditional backup deployments, applications either have to be taken off-line or suffer from degraded performance during backups (which is why traditional backups typically happen during off-peak hours). This means snapshot-based backups can be taken more frequently, improving recovery point objectives. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;For more information, read the blogs:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;– &lt;A href="https://community.hpe.com/nimble-blogpost/1001"&gt;O Snapshot: What Art Thou?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;– &lt;A href="https://community.hpe.com/nimble-blogpost/1004"&gt;Snapshot: Part Deux&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2013 04:26:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/snapshots-an-overview/m-p/6986833#M1096</guid>
      <dc:creator>nimble-admin47</dc:creator>
      <dc:date>2013-01-30T04:26:11Z</dc:date>
    </item>
  </channel>
</rss>

