Optimizing a data deduplication system using client authentication information

• US 8,615,798 B2
• Filed: 06/29/2007
• Issued: 12/24/2013
• Est. Priority Date: 06/29/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Smith, Mark A.
• Primary Examiner(s): Orgad, Edan
• Assistant Examiner(s): Baum, Ronald
• Application Number:
  US11/772,066
• Publication Number:
  US 20090007261A1
• Time in Patent Office: 2,370 Days
• Field of Search: 726/21
• US Class Current: 726/21
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

The present invention provides a method and system of receiving data in a data store in a server computer system. In an exemplary embodiment, the method and system include (1) receiving client authentication information of a client computer system, (2) receiving a data signature of the data from the client computer system, and (3) attempting to locate in the data store at least one data chunk with a stored data signature equal to the received data signature.

Claims

1. A method for optimizing a data deduplication storage system in a non-staged storage environment using client authentication information, comprising:

receiving, by a data deduplication storage system, authentication information of a host system of a client of said deduplication system;

receiving, by said deduplication system, a data signature from said client, the data signature representing particular data to be received by said deduplication system;

determining whether a data chunk corresponding to the data signature is stored in said deduplication system and whether said deduplication system is stateful or stateless if the data signature is not stored in said deduplication system, wherein the data chunk is stored in said deduplication system if there is a data signature stored being equal in value to the received data signature;

in response to said determining that a data chunk is not stored in said deduplication system for a corresponding data signature received and that said deduplication system is stateless, said deduplication system, notifies said client that the particular data are not stored, receives the particular data from said client, and stores;

the particular data, the data signature representing said particular data, and said client authentication information as the guarantor of the data signature;

in response to said determining that a data chunk is not stored in said deduplication system for a corresponding data signature received and that said deduplication system is stateful, said deduplication system, notifies said client that the particular data are not stored, receives the particular data from said client, stores the particular data, and uses previously received data signature representing said particular data and previously received client authentication information as the guarantor of the data signature;

in response to said determining that a data chunk is stored in said deduplication system, said deduplication system reads a guarantor of a stored data signature corresponding to the data chunk stored and determines whether the guarantor is trusted by said client, wherein said deduplication system performs deduplication of said particular data by indicating that said particular data does not need to be received from said client when the guarantor is trusted by said client or calculates and stores a new data signature for the data chunk stored and then marks the new data signature as verified when the guarantor is not trusted by said client; and

wherein a guarantor is determined to be trusted by a host system of a client of said deduplication system if the received client authentication information is equal in value to the stored client authentication information, and using the guarantor reduces said deduplication system'"'"'s verification of client data signatures such that data signatures only need to be verified for a new client of previously stored data.

2. The method of claim 1, wherein the guarantor is determined to be trusted by a client if the stored data signature for the located data chunk is marked as verified.

3. The method of claim 1, wherein the guarantor is determined to be trusted by a client if the guarantor is included in a list of trusted guarantors for the client.

4. The method of claim 1, wherein the guarantor is determined not to be trusted by a client if:

the stored data signature for the located data chunk is not marked as verified,

the received client authentication information is not equal to the stored client authentication information of the stored data signature; and

the guarantor is not included in a list of trusted guarantors for the client.

5. A computer program product for optimizing a data deduplication storage system in a non-staged storage environment using client authentication information, the computer program product comprising a non-transitory computer readable storage medium having computer readable program code embodied therewith, said program code being executable by a data deduplication enabled storage system to:

receive, by a data deduplication storage system, authentication information of said client of said deduplication system;

receive, by said deduplication system, a data signature from said client, the data signature representing particular data to be received by said deduplication system;

determine whether system a data chunk corresponding to the data signature is stored in said deduplication system, wherein the data chunk is stored in said deduplication system if there is a data signature stored being equal in value to the received data signature;

in response to said determine that a data chunk is not stored in said deduplication system for a corresponding data signature received and that said deduplication system is stateless, said deduplication system, notifies said client that the particular data are not stored, receives the particular data from said client, and stores;

the particular data, the data signature representing said particular data, and said client authentication information as the guarantor of the data signature;

in response to said determine that a data chunk is not stored in said deduplication system for a corresponding data signature received and that said deduplication system is stateful, said deduplication system, notifies said client that the particular data are not stored, receives the particular data from said client, stores the particular data, and uses previously received data signature representing said particular data and previously received client authentication information as the guarantor of the data signature;

in response to said determine that a data chunk is stored in said deduplication system, said deduplication system reads a guarantor of a stored data signature corresponding to the data chunk stored and determines whether the guarantor is trusted by said client, wherein said deduplication system performs de-duplication of said particular data by indicating that said particular data does not need to be received from said client when the guarantor is trusted by said client or calculates and stores a new data signature for the data chunk stored and then marks the new data signature as verified when the guarantor is not trusted by said client; and

wherein a guarantor is determined to be trusted by a host system of a client of said deduplication system if the received client authentication information is equal in value to the stored client authentication information, and using the guarantor reduces said deduplication system'"'"'s verification of client data signatures such that data signatures only need to be verified for a new client of previously stored data.

6. The computer program product of claim 5, wherein the guarantor is determined to be trusted by a client if the stored data signature for the located data chunk is marked as verified.

7. The computer program product of claim 5, wherein the guarantor is determined to be trusted by a client if the guarantor is included in a list of trusted guarantors for the client.

8. The method of claim 5, wherein the guarantor is determined not to be trusted by a client if:

the stored data signature for the located data chunk is not marked as verified,

the received client authentication information is not equal to the stored client authentication information of the stored data signature; and

the guarantor is not included in a list of trusted guarantors for the client.