# US 2009/0268903 A1 · Network storage server with integrated encryption, compression and deduplication capability

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0268903 A1
- Document ID: US20090268903A1
- Status: Published application
- Kind: A1
- Application number: 12/110,046
- Filed: 2008-04-25
- Published: 2009-10-29
- Earliest claimed: 2008-04-25
- Assignees: NetApp, Inc.
- Inventors: Hristo Bojinov; Ananthan Subramanian
- Web page: https://patentgrep.com/patent/US20090268903A1

## CPC

- G06F 3/0622: {in relation to access}
- G06F 3/0625: {Power saving in storage systems}
- G06F 3/0641: {De-duplication techniques}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 11/1453: {using de-duplication of the data}
- G06F 12/0866: for peripheral storage systems, e.g. disk cache
- H04L 9/0836: {using tree structure or hierarchical structure}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- G06F 2212/264: Remote server
- G06F 2212/401: Compressed data
- H04L 2209/30: Compression, e.g. Merkle-Damgard construction
- H04L 2209/60: Digital content management, e.g. content distribution
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

A network storage server receives multiple write requests from a set of clients via a network and internally buffers multiple data blocks written by the write requests. At a consistency point, the storage server commits the data blocks to a nonvolatile mass storage facility. The consistency point process includes using a storage operating system in the network storage server to compress the data blocks, encrypt selected data blocks, and store the compressed and (possibly) encrypted data blocks in the nonvolatile mass storage facility. Data blocks can also be fingerprinted in parallel with compression and/or encryption, to facilitate subsequent deduplication. Data blocks can be indexed and classified according to content or attributes of the data. Encryption can be applied at different levels of logical container granularity, where a separate, unique cryptographic key is used for each encrypted data container.

## Claims

### Claim 1

A method of operation of a network storage server, the method comprising:
receiving a plurality of write requests at the network storage server from a set of clients;
buffering a plurality of data blocks written by the write requests in a cache in the network storage server;
at a consistency point, committing the plurality of data blocks written by the write requests to a nonvolatile mass storage facility, including using a storage operating system in the network storage server to
compress each of the data blocks,
encrypt each of the data blocks, and
store the compressed and encrypted data blocks in the nonvolatile mass storage facility; and
allowing at least one of the encrypted data blocks to be shared by a plurality of logical containers.

### Claim 2 (depends on 1)

A method as recited in claim 1, wherein using the storage operating system to encrypt each of the data blocks comprises using a file system manager to encrypt the data blocks.

### Claim 3 (depends on 2)

A method as recited in claim 2, wherein using the storage operating system to compress each of the data blocks comprises using the file system manager to compress the data blocks.

### Claim 4 (depends on 1)

A method as recited in claim 1, wherein allowing at least one of the encrypted data blocks to be shared by a plurality of logical containers comprises:
hashing an unencrypted version of each said data block to generate a unique fingerprint for each said data blocks and storing the unique fingerprint in a memory;
identifying duplicate data blocks based on fingerprints stored in the memory; and
coalescing the duplicate data blocks.

### Claim 5 (depends on 4)

A method as recited in claim 4, wherein allowing at least one of the encrypted data blocks to be shared by a plurality of logical containers comprises using the storage operating system in the network storage server to hash an unencrypted version of each of the data blocks, to identify the duplicate data blocks, and to coalesce the duplicate data blocks.

### Claim 6 (depends on 1)

A method as recited in claim 1, further comprising:
generating a digital signature for each said fingerprint, prior to storing the fingerprint in the memory; and
using the digital signatures of the fingerprints to detect tampering in one of the fingerprints.

### Claim 7 (depends on 1)

A method as recited in claim 1, wherein the network storage server maintains data in a hierarchical structure that includes a plurality of direct blocks as a lowest level of the structure and a plurality of levels of indirect blocks logically above the direct blocks in the structure.

### Claim 8 (depends on 7)

A method as recited in claim 7, wherein using the storage operating system to encrypt each of the data blocks comprises encrypting direct data blocks affected by the write requests but not indirect blocks affected by the write requests.

### Claim 9 (depends on 7)

A method as recited in claim 7, wherein using the storage operating system to encrypt each of the data blocks comprises encrypting direct data blocks affected by the write requests and indirect blocks affected by the write requests.

### Claim 10 (depends on 7)

A method as recited in claim 7, further comprising determining how many levels of indirect data blocks to encrypt, based upon a user-specified setting.

### Claim 11 (depends on 1)

A method as recited in claim 1, wherein using the storage operating system comprises using a plurality of encryption keys to encrypt data blocks.

### Claim 12 (depends on 11)

A method as recited in claim 11, wherein using the storage operating system to encrypt each of the data blocks comprises, for each of the data blocks, using a virtual volume block number of the data block and an encryption key to encrypt the data block, the virtual volume block number representing an address of the data block within a virtual volume that contains the data block.

### Claim 13 (depends on 11)

A method as recited in claim 11, wherein the storage operating system maintains data in a plurality of volumes, each volume containing a plurality of data blocks; and
wherein using the storage operating system to encrypt each of the data blocks comprises using a different encryption key for each of the volumes.

### Claim 14 (depends on 1)

A method as recited in claim 1, wherein the storage operating system maintains a plurality of logical containers at a plurality of levels of granularity;
the method further comprising allowing logical containers at each of the plurality of levels of granularity to be encrypted, by allowing encryption keys to be assigned to logical containers in each of the plurality of levels of granularity.

### Claim 15 (depends on 11)

A method as recited in claim 11, for each logical container to which an encryption key is assigned, storing said encryption key in a metadata container associated with the logical container.

### Claim 16 (depends on 11)

A method as recited in claim 11, wherein allowing logical containers at each of the plurality of levels of granularity to be encrypted comprises:
encrypting data at two or more levels of granularity in accordance with user inputs that specify logical containers to be encrypted at two or more levels of granularity.

### Claim 17 (depends on 16)

A method as recited in claim 16, wherein the plurality of levels of granularity comprise file level, directory level and volume level.

### Claim 18 (depends on 17)

A method as recited in claim 17, wherein allowing logical containers at each of the plurality of levels of granularity to be encrypted comprises:
encrypting data blocks of a file with a first encryption key; and
encrypting a directory which contains the file with a second encryption key.

### Claim 19 (depends on 18)

A method as recited in claim 18, wherein allowing logical containers at each of the plurality of levels of granularity to be encrypted further comprises:
encrypting a volume which contains the directory with a third encryption key.

### Claim 19 (depends on 11)

A method as recited in claim 11, further comprising encrypting each of the encryption keys with a wrapper encryption key.

### Claim 20 (depends on 11)

A method as recited in claim 11, further comprising changing the encryption key to be used for a particular data set at each of a plurality of consistency points.

### Claim 21 (depends on 1)

A method as recited in claim 1, further comprising using the storage operating system in the network storage server to digitally sign each of the data blocks, prior to storing each of the compressed and encrypted data blocks in the nonvolatile mass storage facility.

### Claim 22 (depends on 1)

A method as recited in claim 1, further comprising:
responding to a read request from one of the clients, by using the storage operating system in the network storage server to
access one of the compressed and encrypted data blocks in the nonvolatile mass storage facility;
decrypt and decompress the accessed data block; and
send the decrypted and decompressed data block to the client.

### Claim 23

A method comprising:
maintaining a plurality of logical containers at a plurality of levels of granularity in a network storage system; and
allowing logical containers at each of the plurality of levels of granularity to be encrypted, by allowing encryption keys to be assigned to logical containers at each of the plurality of levels of granularity, wherein allowing the logical containers to be encrypted includes, for each logical container to which an encryption key is assigned, storing said encryption key in a separate metadata container associated with the logical container.

### Claim 24 (depends on 23)

A method as recited in claim 23, wherein allowing logical containers to be encrypted at each of the plurality of levels of granularity comprises:
encrypting data at two or more levels of granularity in accordance with user inputs that specify logical containers to be encrypted in two or more levels of granularity.

### Claim 25 (depends on 24)

A method as recited in claim 24, wherein the plurality of levels of granularity level of granularity comprises file level, directory level and volume level.

### Claim 26

A network storage server comprising:
a processor;
a network interlace, coupled to the processor, through which to receive data access requests from a plurality of clients via a network;
a storage interface, coupled to the processor, through which to access a nonvolatile mass storage facility which stores data targeted by the data access requests; and
a storage operating system including
a protocol layer to process the data access requests, including translating between a protocol of the data access requests and an internal protocol;
a storage access layer to implement a redundancy protocol by storing data redundantly across a plurality of physical storage devices in the nonvolatile mass storage facility;
a storage manager, to operatively bridge the multi-protocol layer and the storage redundancy layer, to manage a plurality of hierarchical data sets in the nonvolatile mass storage facility, and to respond to data access requests for accessing one or more of the hierarchical data sets;
a key generator to generate a plurality of encryption keys;
a key cache to store the plurality of encryption keys;
encryption logic to identify data to be encrypted in response to the data access requests; and
a cryptographic engine to encrypt data identified as to be encrypted by using different ones of the plurality of encryption keys to encrypt different data sets.

### Claim 27 (depends on 26)

A network storage server as recited in claim 26, wherein the encryption logic is part of the storage manager.

### Claim 28 (depends on 26)

A network storage server as recited in claim 26, wherein the encryption logic is implemented logically below the storage manager.

### Claim 29 (depends on 26)

A network storage server as recited in claim 26, further comprising deduplication logic to allow at least one of the encrypted data blocks to be shared by a plurality of logical containers.

### Claim 30 (depends on 29)

A network storage server as recited in claim 29, further comprising hashing logic to generate a fingerprint of an unencrypted version of each said data block.

### Claim 31 (depends on 30)

A network storage server as recited in claim 30, further comprising:
duplicate detection logic to detect a duplicate of one of the data blocks based on the fingerprint of the data block.
