Client-side repository in a networked deduplicated storage system
US-9104623-B2 · Aug 11, 2015 · US
US10229133B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10229133-B2 |
| Application number | US-201715474730-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 30, 2017 |
| Priority date | Jan 11, 2013 |
| Publication date | Mar 12, 2019 |
| Grant date | Mar 12, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A high availability distributed, deduplicated storage system according to certain embodiments is arranged to include multiple deduplication database media agents. The deduplication database media agents store signatures of data blocks stored in secondary storage. In addition, the deduplication database media agents are configured as failover deduplication database media agents in the event that one of the deduplication database media agents becomes unavailable.
Opening claim text (preview).
What is claimed is: 1. A method of performing a storage operation in a distributed, deduplicated storage system, comprising: receiving, at a first secondary storage computing device, a request from a client computing device to perform a storage operation corresponding to a first data block, wherein a plurality of deduplication database computing devices are communicatively coupled to the first secondary storage computing device, wherein the plurality of deduplication database computing devices comprises a first deduplication database computing device and a second deduplication database computing device, wherein the first deduplication database computing device is configured to store a first subset of signature blocks and is designated as a failover deduplication database computing device for the second deduplication database computing device, and wherein the second deduplication database computing device is configured to store a second subset of signature blocks that is different than the first subset of signature blocks; in response to the request and using one or more processors, identifying that the second deduplication database computing device is assigned to store a first signature corresponding to the first data block; determining that the first signature is not stored in the second deduplication database computing device due to an unavailability of the second deduplication database computing device and is instead stored in the first deduplication database computing device, wherein the first subset of signature blocks comprises a first signature block, and wherein the first signature block comprises the first signature, an indication of a location of the first data block in a secondary storage device, and a value representing a number of references to the first data block in the secondary storage device; wherein said determining includes querying a failover index using the first signature, and receiving an indication, from the failover index, that the first signature is stored in the first deduplication database computing device; and in response to determining that the first signature is not stored in the second deduplication database computing device and is instead stored in the first deduplication database computing device, querying the first deduplication database computing device instead of the second deduplication database computing device for the first signature and the location of the first data block in the secondary storage device, wherein querying the first deduplication database computing device for the first signature causes the first deduplication database computing device to increment the value representing the number of references to the first data block in the secondary storage device. 2. The method of claim 1 , wherein the first signature is stored in the first deduplication database computing device instead of the second deduplication database computing device because the second deduplication database computing device was unavailable when the first signature block was stored in the first deduplication database computing device. 3. The method of claim 1 , wherein the storage operation comprises a pruning operation. 4. The method of claim 3 , wherein querying the first deduplication database computing device for the first signature causes the first deduplication database computing device to decrement the value representing the number of references to the first data block in the secondary storage device. 5. The method of claim 4 , further comprising deleting the first data block from the secondary storage device in response to a determination that the decremented value is zero. 6. The method of claim 1 , wherein identifying that the second deduplication database computing device is assigned to store the first signature corresponding to the first data block further comprises: determining a second signature of the first data block; performing a modulo operation on the second signature; and identifying that the second deduplication database computing device is assigned to store the first data block based on a result of the performed modulo operation. 7. The method of claim 1 , wherein each deduplication database computing device of the plurality of deduplication database computing devices is identified as a failover deduplication database computing device to another one of the plurality of deduplication database computing devices. 8. The method of claim 1 , wherein a third deduplication database computing device in the plurality of deduplication database computing devices is designated as a failover deduplication database computing device for the first deduplication database computing device, and wherein the second deduplication database computing device is designated as a failover deduplication database computing device for the third deduplication database computing device. 9. A distributed deduplicated storage system, comprising: a first deduplication database computing device configured to store a first subset of signature blocks; a second deduplication database computing device configured to store a second subset of signature blocks, wherein the first deduplication database computing device is designated as a failover deduplication database computing device for the second deduplication database computing device, and wherein the second subset of signature blocks is different than the first subset of signature blocks; and a secondary storage computing device communicatively coupled to the first deduplication database computing device and the second deduplication database computing device, the secondary storage computing device comprising one or more processors and storage, wherein the secondary storage computing device is configured to: receive a request to perform a storage operation corresponding to a first data block, identify that the second deduplication database computing device is assigned to store a first signature corresponding to the first data block, determine that the first signature is not stored in the second deduplication database computing device due to an unavailability of the second deduplication database computing device and is instead stored in the first deduplication database computing device, wherein the first subset of signature blocks comprises a first signature block, and wherein the first signature block comprises the first signature, an indication of a location of the first data block in a secondary storage device, and a value representing a number of references to the first data block in the secondary storage device, wherein said determining includes querying a failover index using the first signature, and receiving an indication, from the failover index, that the first signature is stored in the first deduplication database computing device; and in response to the determination that the first signature is not stored in the second deduplication database computing device and is instead stored in the first deduplication database computing device, query the first deduplication database computing device instead of the second deduplication database computing device for the first signature and the location of the first data block in the secondary storage device, wherein querying the first deduplication database computing device for the first signature causes the first deduplication database computing device to increment or decrement the value representing the number of references to the first data block in the secondary storage device. 10. The system of claim 9 , wherein the first signature is stored in the first deduplication database computing device instead of the second deduplication database computing device because the second deduplication database computing de
Database-specific techniques · CPC title
Physics · mapped topic
using de-duplication of the data · CPC title
by selection of backup contents · CPC title
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.