Indexing for deduplication

• US 20120158674A1
• Filed: 12/20/2010
• Published: 06/21/2012
• Est. Priority Date: 12/20/2010
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Lillibridge, Mark David
• Application Number:
  US12/973,830
• Publication Number:
  US 20120158674A1
• Time in Patent Office: Days
• US Class Current: 707/692
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06

Abstract

Systems and methods of indexing for deduplication are disclosed. An example method includes providing a first table in a first storage and a second table in a second storage. The method also includes looking up a key in the first table. If the key is not found in the first table, the key is looked up in the second table. If the key is found in the second table, the key is copied from the second table to the first table. If the entry is not found or in the second table, an entry with the key is inserted in the first table. The method also includes applying an operation to the entry associated with the key in the first table. The method also includes merging data of the first table with data of the second table when the first table is full to produce a new version of the second table that replaces a previous version.

Claims

1. A method of indexing for deduplication, comprising:

providing a first table in a first storage and a second table in a second storage;

looking up a key in the first table, and;

if the key is not found in the first table, looking up the key in the second table;

if the key is found in the second table, copying an associated entry for the key from the second table to the first table;

if the key is not found in the first table and the key is not found in the second table, inserting an entry with the key in the first table;

applying an operation to an entry associated with the key in the first table; and

merging data of the first table with data of the second table when the first table is full to produce a new version of the second table that replaces a previous version of the second table.

2. The method of claim 1, wherein the key is a hash of a piece of data.

3. The method of claim 2, wherein the second table at least maps hashes of stored blocks to information identifying where the blocks are stored.

4. The method of claim 3, wherein applying the operation to the entry includes at least one of:

incrementing a reference count for a stored block, decrementing a reference count for the stored block, and updating the information for the stored block.

5. The method of claim 1, wherein the first storage is a static or dynamic random access memory (SRAM or DRAM) and the second storage is a flash memory.

6. The method of claim 1, wherein the first storage is a static or dynamic random access memory (SRAM or DRAM) and the second storage is at least one hard disk drive.

7. The method of claim 1, wherein merging the data of first table with the data of the second table further comprises:

producing the new version of the second table from entries of the second table associated with keys not in the first table, and the entries of the first table; and

emptying the first table.

8. The method of claim 7, wherein entries of the first table marked for deletion are not included in the new version of the second table.

9. The method of claim 7, wherein merging the data of first table with the data of the second table further comprises:

sequentially writing out the new version of the second table to the second storage.

10. The method of claim 1, wherein looking up the key in the second table is by reading only a single page from the second storage with a high probability.

11. The method of claim 10, wherein looking up the key in the second table further comprises:

maintaining a data structure in the first storage;

identifying a page of the second storage containing any entry of the second table associated with the key, using the data structure and without accessing the second storage;

reading the identified page of the second storage from the second storage.

12. The method of claim 1, further comprising:

providing a third table in the second storage;

merging the second table with the third table when the second table is full to produce a new version of the third table to replace a previous version of the third table; and

emptying the second table.

13. A system comprising:

a first storage for storing a first table;

a second storage for storing a second table;

an update agent configured to look up a key in the first table, and;

if the key is not found in the first table, look up the key in the second table;

if the key is found in the second table, copy an associated entry for the key from the second table to the first table;

if the key is not found in the first table and the key is not found in the second table, insert an entry with the key in the first table;

apply an operation to an entry associated with the key in the first table; and

wherein data of the first table is merged with data of the second table when the first table is full to produce a new version of the second table that replaces a previous version of the second table.

14. The system of claim 13, wherein the first storage is a random access memory (RAM) and the second storage is one of a flash memory, a memrister-based memory, and a phase change memory.

15. The system of claim 13, wherein the data of the first table is merged with the data of the second table by:

producing the new version of the second table from entries of the second table associated with keys not in the first table, and the entries of the first table; and

emptying the first table.

16. The system of claim 13, wherein the update agent when looking up the key in the second table determines a page to read from the second storage using a hash.

17. The system of claim 13, wherein the data structure of the second table uses overflow pages.

18. The system of claim 13, wherein the second storage includes at least a third table, wherein the data of the second table is merged with the data of the third table when the second table is full to produce a new version of the third table that replaces a previous version of the third table.

19. The system of claim 13, wherein entries with a reference count of zero are not included in the new version of the second table.

20. The system of claim 13, wherein the key is a hash of a piece of data being deduplicated.