<?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 Dedup Container in StoreOnce in StoreOnce Backup Storage</title>
    <link>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7068842#M1555</link>
    <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;are there any docs / info's available on the Storence dedup containers.&lt;/P&gt;&lt;P&gt;Came across this term when working with support on some consistency checks.&lt;/P&gt;&lt;P&gt;Could find any thing in Google or hpe sites.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance.&lt;/P&gt;&lt;P&gt;VK&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 06 Nov 2019 12:45:37 GMT</pubDate>
    <dc:creator>ssd-sso-san</dc:creator>
    <dc:date>2019-11-06T12:45:37Z</dc:date>
    <item>
      <title>Dedup Container in StoreOnce</title>
      <link>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7068842#M1555</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;are there any docs / info's available on the Storence dedup containers.&lt;/P&gt;&lt;P&gt;Came across this term when working with support on some consistency checks.&lt;/P&gt;&lt;P&gt;Could find any thing in Google or hpe sites.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance.&lt;/P&gt;&lt;P&gt;VK&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2019 12:45:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7068842#M1555</guid>
      <dc:creator>ssd-sso-san</dc:creator>
      <dc:date>2019-11-06T12:45:37Z</dc:date>
    </item>
    <item>
      <title>Re: Dedup Container in StoreOnce</title>
      <link>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7068977#M1556</link>
      <description>&lt;P&gt;Dear VK,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;StoreOnce dedup containers are the internal software architectural components for every store that you create from the GUI. The stores run on the service sets, and the underlying raw data will be processed by these stores ( dedupe items).&lt;/P&gt;&lt;P&gt;A dedupe item number is used to reference a cartridge in a VTL, a folder in a NAS share or an object in a Catalyst store.&lt;/P&gt;&lt;P&gt;There is a separate deduplication store per VTL/Share/Catalyst store.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2019 13:10:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7068977#M1556</guid>
      <dc:creator>AshrafK</dc:creator>
      <dc:date>2019-11-07T13:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: Dedup Container in StoreOnce</title>
      <link>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7068998#M1557</link>
      <description>&lt;P&gt;Tx Ashraf.&amp;nbsp;&amp;nbsp;These answers&amp;nbsp;helped&amp;nbsp;, but still picture is not that clear.&lt;/P&gt;&lt;P&gt;Any documents / diagrams that you got to help here. ?&lt;/P&gt;&lt;P&gt;Tx in Advance&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2019 16:15:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7068998#M1557</guid>
      <dc:creator>ssd-sso-san</dc:creator>
      <dc:date>2019-11-07T16:15:41Z</dc:date>
    </item>
    <item>
      <title>Re: Dedup Container in StoreOnce</title>
      <link>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7069400#M1558</link>
      <description>&lt;P&gt;Dear VK,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand it is not easy to picture the internal complex architecture of the StoreOnce by words.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am sorry to say that the information you are looking for is “classified”. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have included one example, snippet of log info though, and I hope it helps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Example.PNG" style="width: 307px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/112732i6E05B0573426C3B4/image-size/large?v=v2&amp;amp;px=2000" role="button" title="Example.PNG" alt="Example.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you look at the diagram, a service set runs on the server node, and the stores run on the service set. There is a separate deduplication store per Catalyst store ( it can also be of type VTL/ NAS share).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please note each store is a separate dedupe domain. Two stores will not be deduping against each other. So, the underlying raw data will be processed by these stores.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2019 11:49:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7069400#M1558</guid>
      <dc:creator>AshrafK</dc:creator>
      <dc:date>2019-11-12T11:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: Dedup Container in StoreOnce</title>
      <link>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7069402#M1559</link>
      <description>&lt;P&gt;Thank You Ashraf.&lt;/P&gt;&lt;P&gt;Though there are many questions still around.&lt;/P&gt;&lt;P&gt;Appreciate your response. Closing this thread.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2019 12:08:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeonce-backup-storage/dedup-container-in-storeonce/m-p/7069402#M1559</guid>
      <dc:creator>ssd-sso-san</dc:creator>
      <dc:date>2019-11-12T12:08:00Z</dc:date>
    </item>
  </channel>
</rss>

