US9436723B2 - Segment deduplication system with compression of segments - Google Patents
Segment deduplication system with compression of segments Download PDFInfo
- Publication number
- US9436723B2 US9436723B2 US14/271,246 US201414271246A US9436723B2 US 9436723 B2 US9436723 B2 US 9436723B2 US 201414271246 A US201414271246 A US 201414271246A US 9436723 B2 US9436723 B2 US 9436723B2
- Authority
- US
- United States
- Prior art keywords
- segment
- compressed
- segments
- data
- compression
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000006835 compression Effects 0.000 title claims description 59
- 238000007906 compression Methods 0.000 title claims description 59
- 238000013507 mapping Methods 0.000 claims description 48
- 238000000034 method Methods 0.000 claims description 39
- 238000004590 computer program Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 32
- 230000008569 process Effects 0.000 description 21
- 230000006870 function Effects 0.000 description 11
- 230000006837 decompression Effects 0.000 description 9
- 238000013478 data encryption standard Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000004557 technical material Substances 0.000 description 1
Images
Classifications
-
- G06F17/30371—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
-
- G06F17/30067—
-
- G06F17/30286—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0608—Saving storage space on storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/064—Management of blocks
- G06F3/0641—De-duplication techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0683—Plurality of storage devices
-
- H—ELECTRICITY
- H03—ELECTRONIC CIRCUITRY
- H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
- H03M7/00—Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
- H03M7/30—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
- H03M7/3059—Digital compression and data reduction techniques where the original information is represented by a subset or similar information, e.g. lossy compression
- H03M7/3064—Segmenting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1453—Management of the data involved in backup or backup restore using de-duplication of the data
-
- H—ELECTRICITY
- H03—ELECTRONIC CIRCUITRY
- H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
- H03M7/00—Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
- H03M7/30—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
Definitions
- Segment data duplication storage system store data in a space efficient manner by only storing a newly received segment in the event that an identical segment to the newly received segment has not been previously stored.
- some user of storage systems would like the ability to encrypt data prior to storing in order to ensure security. Encryption, however, typically does not allow an identical segment to be identified and thereby eliminating the efficiency of the deduplication system.
- some deduplication systems would like to use a compression for the data that is requested to be stored. However, compression typically does not allow an identical segment to be identified and thereby eliminating the efficiency of the deduplication system.
- FIG. 1 is a block diagram illustrating an embodiment of a system for storage for data.
- FIG. 2 is a block diagram illustrating an embodiment of a segment storage engine.
- FIG. 3 is a block diagram illustrating an embodiment of a storage user system.
- FIG. 4 is a flow diagram illustrating an embodiment of a process for storing data.
- FIG. 5 is a flow diagram illustrating a process for retrieving data.
- FIG. 6 is a block diagram illustrating an embodiment of a storage user system.
- FIG. 7 is a flow diagram illustrating an embodiment of a process for storing data.
- FIG. 8 is a flow diagram illustrating a process for retrieving data.
- FIG. 9 is a block diagram illustrating an embodiment of a storage user system.
- FIG. 10 is a flow diagram illustrating an embodiment of a process for storing data.
- FIG. 11 is a flow diagram illustrating a process for retrieving data.
- FIG. 12A is a block diagram illustrating an embodiment of data structures.
- FIG. 12B is a block diagram illustrating an embodiment of data relations.
- FIG. 13A is a block diagram illustrating an embodiment of data relations.
- FIG. 13B is a block diagram illustrating an embodiment of data relations.
- FIG. 13C is a block diagram illustrating an embodiment of data relations.
- the invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor.
- these implementations, or any other form that the invention may take, may be referred to as techniques.
- the order of the steps of disclosed processes may be altered within the scope of the invention.
- a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task.
- the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
- a segment deduplication system with compression of segments comprises a processor and a memory.
- the processor is configured to receive and compress segments and determine whether a compressed segment has been previously stored.
- the compressed segment is determined by breaking a data stream, a data block, or a data file into one or more segments and compressing each of the one or more segments. In the event that the compressed segment has not been previously stored, the compressed segment is stored.
- a system for reading compressed data comprises a deduplicated storage device and a processor.
- the processor is configured to retrieve one or more compressed segments from the deduplicated storage device.
- the one or more compressed segments were determined by breaking a data stream, a data block, or a data file into one or more segments and compressing each of the one or more segments.
- the processor is further configured to decompress the segments and assemble the segments to reconstruct the data stream, the data block, or the data file.
- a segment deduplication system with encryption of segments comprises a processor and a memory.
- the processor is configured to receive and encrypted segment and determine whether the encrypted segment has been previously stored.
- the encrypted segment is determined by breaking a data stream, a data block, or a data file into one or more segments and encrypting each of the one or more segments. In the event that the encrypted segment has not been previously stored, the encrypted segment is stored.
- a system for reading encrypted data comprises a deduplicated storage device and a processor.
- the processor is configured to retrieve one or more encrypted segments from the deduplicated storage device.
- the one or more encrypted segments were determined by breaking a data stream, a data block, or a data file into one or more segments and encrypting each of the one or more segments.
- the processor is further configured to decrypt the segments and assemble the segments to reconstruct the data stream, the data block, or the data file.
- a system for storing encrypted and compressed data comprises a processor configured to determine whether an encrypted compressed segment has been previously stored.
- the encrypted compressed segment was determined by breaking a data stream, a data block, or a data file into one or more segments and compressing and then encrypting each of the one or more segments. In the event that the encrypted compressed segment has not been previously stored, the encrypted compressed segment is stored.
- a system for reading encrypted compressed data comprises a deduplicated storage device and a processor.
- the processor is configured to decrypt one or more encrypted compressed segments stored in the deduplicated storage device.
- the one or more encrypted compressed segments were determined by breaking a data stream, a data block, or a data file into one or more segments and compressing and then encrypting each of the one or more segments.
- the processor is further configured to decompress the one or more decrypted compressed segments and assemble the one or more decrypted decompressed segments to reconstruct the data stream, the data block, or the data file.
- encryption of segment(s) provides security for data content of the segment(s) during transmission between systems and during storage while still providing efficient deduplication storage of segment(s).
- compression of segment(s) provides bandwidth savings during transmission between systems and storage space savings during storage while still providing efficient deduplication storage of segment(s).
- FIG. 1 is a block diagram illustrating an embodiment of a system for storage for data.
- storage system 100 is accessed by a user using storage user system 110 or by storage user system 110 via network 108 .
- network 108 comprises one or more of a wired network, a wireless network, a local area network, a wide area network, the Internet, or any other appropriate network.
- Storage system 100 comprises system interface 102 , segment storage engine 104 , and a plurality of storage units (represented in FIG. 1 by storage unit 112 , storage unit 114 , storage unit 116 , and storage unit 118 ).
- Storage system 100 is replicated using replica storage system 106 .
- a storage unit is replicated by storing segments and metadata stored on the storage unit to another storage unit.
- Storage user system 110 breaks a file, a data stream, or a data block into segment(s) (e.g., boundaries are identified for one or more segments—for example, a hash function operates on a portion of the content of the file; when the hash function is equal to a value, is a minimum value, is a maximum value, is between a minimum and maximum length, and/or is an extrema value within a window of the file, etc. a segment boundary is determined). Segment boundaries are determined such that two similar files, data streams, or data blocks have the goal of having the same segments for identical portions of the files, data streams, or data blocks, and different segments for the non-identical portions of the files, data streams, or data blocks.
- segment boundaries are determined such that two similar files, data streams, or data blocks have the goal of having the same segments for identical portions of the files, data streams, or data blocks, and different segments for the non-identical portions of the files, data streams, or data blocks.
- the segment determination is based on the content of the data (e.g., using value(s) calculated based on data content), not based on the content (e.g., byte count, file criteria, etc.), or a combination of content based criteria and non-content based criteria.
- storage user system 110 encrypts and/or compresses the segments.
- Storage user system 110 sends the segment(s) (e.g., compressed segments, encrypted segments, compressed encrypted segments, etc.) to be stored by storage system 100 via network 108 .
- information regarding how to reconstruct the file, the data stream, or the data block is also sent from storage user system 110 to storage system 100 and/or is stored by storage user system 110 , or any other appropriate action for the information.
- Storage system 100 receives the segment using system interface 102 .
- Segment storage engine 104 stores the segments in a storage unit (e.g., storage unit 112 , storage unit 114 , storage unit 116 , or storage unit 118 ).
- a storage unit comprises a storage device, multiple storage devices, a portion of a storage device, a hard drive, an array of drives, a semiconductor memory, or any other appropriate storage unit.
- Segment storage engine 104 only stores a segment in a storage unit if the segment has not been previously stored in the storage unit.
- an identifier e.g., a digital fingerprint, Secure Hash Algorithm hash value, a Rabin hash, etc.
- a digital fingerprint e.g., a digital fingerprint, Secure Hash Algorithm hash value, a Rabin hash, etc.
- the identifier for a given segment is determined using storage system 100 , using storage user system 110 , or any other appropriate system.
- an identifier is sent along with an associated segment from storage user system 110 to storage system 100 .
- Storage user system 110 requests one or more segments that is/are stored on storage system 100 via network 108 .
- Storage system 100 receives the request using system interface 102 .
- Segment storage engine 104 finds the segments used to store a file, data stream, or data block in the appropriate storage unit(s).
- the one or more segments are sent to storage user system 110 via network 108 .
- Storage user system 110 uses the one or more segments to reconstruct a file, data stream, or data block.
- the segment(s) are decrypted and/or decompressed or any other appropriate processing in order to reconstruct the desired file, data stream, or data block.
- encryption, decryption, compression, and/or decompression systems used are any appropriate systems that are compatible with a data segment deduplication system—for example, a system where a given encrypted and/or compressed segment can be used to identify whether an identical segment that has also been similarly encrypted and/or compressed has been previously stored.
- hardware and/or software components or accelerators or one or more processors are used for compression, decompression, encryption, and/or decryption, or any other appropriate combination of hardware and/or software.
- storage user system 110 is one of a plurality of storage user systems and each of the plurality can use different or similar compression/decompression and/or encryption systems, and/or different keys for similar encryption systems.
- FIG. 2 is a block diagram illustrating an embodiment of a segment storage engine.
- the system of FIG. 2 is used to implement segment storage engine 104 of FIG. 1 .
- segment storage engine 200 comprises interface 202 , duplicate eliminator filter 206 , index 210 , and segment storage unit interface 212 .
- Segment storage engine 200 receives segment(s) using interface 202 .
- Duplicate eliminator 206 identifies whether a newly received segment has already been stored in segment storage unit(s).
- Index 210 is used to locate stored segments in storage unit(s) using storage unit interface 212 .
- Interface 202 receives a request to retrieve segment(s). Interface 202 communicates with index 210 to locate appropriate segments stored in storage units via storage unit interface 212 . Appropriate segment(s) is/are provided via interface 202 in response to the request.
- metadata information is stored associated with a segment—for example, segment identifier, source system, session information, user information, host information, key information, encryption type, compression information, compression type, format information, pad information, associated file, data stream, or data block, etc.
- FIG. 3 is a block diagram illustrating an embodiment of a storage user system.
- storage user system 300 of FIG. 3 is used to implement storage user system 110 of FIG. 1 .
- storage user system 300 comprises storage device 302 , storage device 304 , storage device 306 , storage interface 308 , data segmenter/data reassembler 310 , segment encrypter/segment decrytper 312 , interface 314 which is coupled to network 320 , mapping storage 316 , key storage 318 , and user interface 322 which is able to be accessed by user 324 .
- User 324 is able to request via user interface 322 that a file, data stream, or data block is to be stored.
- Storage interface 308 receives a file, data stream, or data block to be processed from storage device 302 , storage device 304 , or storage device 306 .
- storage interface 308 receives a file, data stream, or data block from an external storage device (not shown in FIG. 3 ), an external system (not shown in FIG. 3 ), or any other appropriate internal or external component, device, or system.
- the file, data stream, or data block is processed by data segmenter/data reassembler 310 .
- Data segmenter/data reassembler 310 breaks the file, data stream, or data block into segments.
- the file, data stream, or data block is broken into segments by identifying segment boundaries using a content-based technique (e.g., a function is calculated at various locations of a data item, when the function is equal to a value or when the value is a minimum, a maximum, or other extrema value relative to other function values calculated for the data item), a non-content-based technique (e.g., based on data item property—for example, byte length, title, creation date), or any other appropriate technique.
- a content-based technique e.g., a function is calculated at various locations of a data item, when the function is equal to a value or when the value is a minimum, a maximum, or other extrema value relative to other function values calculated for the data item
- a non-content-based technique e.g
- a segment is restricted to a minimum and/or maximum length, to a minimum or maximum number of segments per data item, or any other appropriate limitation.
- Data segmenter/data reassembler 310 further processes information to indicate the segment(s) mapping to the file, data stream, or data block so that the file, data stream, or data block can be reconstructed from the segment(s).
- a list of fingerprints is used to indicate a mapping of segment(s) that are associated with a file, data stream, or data block. Mapping information is stored using mapping storage 316 .
- Segment encrypter/segment decrypter 312 encrypts the segment(s).
- the encryption and decryption system is compatible with being able to store the segment(s) using a deduplication system—for example, there is a one to one correspondence between a given segment and the encrypted version of the given segment so that it can be identified by using the encrypted version of the given segment whether the given segment in its encrypted form has been previously stored. Note that this somewhat degrades the strength of possible encryption systems that can be used, however the overall system performance of having an encrypted deduplication system outweighs for some applications the selection of encryption system with the required properties.
- encryption system and/or decryption system comprise(s) a stream cipher (e.g., Rivest Cipher 4 (RC4), Rivest Cipher 5 (RC5), etc.), a cipher feedback system, electronic code book system, advanced encryption standard (AES), data encryption standard (DES), or any other appropriate system.
- a fixed block cipher system is used by padding a segment to a fixed block size before encrypting or depadding after decrypting.
- the encrypted segment is transferred to a system coupled to storage user system 300 via interface 314 and network 320 .
- User 324 is able to request via user interface 322 that a file, data stream, or data block is to be retrieved.
- Information stored in mapping storage 316 is used by data segmenter/data reassembler 310 to determine which encrypted segment(s) to request to be retrieved from a deduplicating segment storage system (e.g., storage system 100 of FIG. 1 ).
- the encrypted segment(s) are transferred via network 320 and interface 314 and decrypted using segment encrypter/segment decrypter 312 .
- Segmenter encrypter/segment decrypter 312 uses information stored in key storage 318 to decrypt encrypted segment(s).
- keys stored in key storage 318 are associated with segments based at least in part on one or more of the following: a user, a source system, a session, or any other appropriate manner of assigning keys associated with a file, data stream, or data block.
- Data segmenter/data reassemble 310 reassembles the decrypted segment(s) to restore the file, data stream, or data block.
- FIG. 4 is a flow diagram illustrating an embodiment of a process for storing data.
- the data stream(s), data file(s), or data block(s) is/are broken into segment(s).
- segment(s) are encrypted.
- encrypted segment(s) is/are transferred.
- the encrypted segment(s) is/are transferred from a data user system to a storage system.
- metadata information is transferred associated with the encrypted segment(s)—for example, a segment identifier, a source identifier, a user identifier, a host identifier, a session identifier, an encryption type, an encryption key, a format type, a pad type, an associated file, data stream, or data block, etc.
- an encrypted segment is selected to be processed.
- a check is performed before transferring the encrypted segment to determine whether the encrypted segment has been previously stored and transfer of the full segment is only performed in the event that the encrypted segment has not been previously stored.
- a reference is stored to the previously stored encrypted segment, if appropriate.
- a reference is stored in the event that the reference is useful in being able to retrieve the encrypted segment with respect to retrieving the data stream(s), data block(s), or file(s) associated with the segment that has been encrypted and is determined to be identical to a previously stored encrypted segment.
- the reference is stored in an index that associates a mapping between data stream(s), data block(s), or file(s) and the segment(s) determined from the data stream(s), data block(s), or file(s).
- a reference or indication is transferred to a user storage system.
- the selected encrypted segment is stored.
- An index entry is stored indicating the location at which the selected encrypted segment is stored.
- the index entry comprises digital fingerprint, a SHA-1 hash, Rabin Hash or any other appropriate identifier that is used to identify whether an identical segment has been previously stored.
- the index entry is transferred to a user storage system.
- FIG. 5 is a flow diagram illustrating a process for retrieving data.
- the stored encrypted segment(s) needed to restore a data file, data stream, or data block are retrieved.
- the encrypted segment(s) are transferred.
- the retrieved segment(s) are sent from a storage system to a storage user system.
- the encrypted segment(s) are decrypted.
- the data file, data stream, or data block is restored by reassembling the decrypted segment(s).
- FIG. 6 is a block diagram illustrating an embodiment of a storage user system.
- storage user system 600 of FIG. 6 is used to implement storage user system 110 of FIG. 1 .
- storage user system 600 comprises storage device 602 , storage device 604 , storage device 606 , storage interface 608 , data segmenter/data reassemble 610 , segment compress/segment decompress 612 , interface 614 which is coupled to network 620 , mapping storage 616 , compression storage 618 , and user interface 622 which is able to be accessed by user 624 .
- User 624 is able to request via user interface 622 that a file, data stream, or data block is to be stored.
- Storage interface 608 receives a file, data stream, or data block to be processed from storage device 602 , storage device 604 , or storage device 606 .
- storage interface 608 receives a file, data stream, or data block from an external storage device (not shown in FIG. 6 ), an external system (not shown in FIG. 6 ), or any other appropriate internal or external component, device, or system.
- the file, data stream, or data block is processed by data segmenter/data reassembler 610 .
- Data segmenter/data reassembler 610 breaks the file, data stream, or data block into segments.
- the file, data stream, or data block is broken into segments by identifying segment boundaries using a content-based technique (e.g., a function is calculated at various locations of a data item, when the function is equal to a value or when the value is a minimum, a maximum, or other extrema value relative to other function values calculated for the data item), a non-content-based technique (e.g., based on data item property—for example, byte length, title, creation date), or any other appropriate technique.
- a content-based technique e.g., a function is calculated at various locations of a data item, when the function is equal to a value or when the value is a minimum, a maximum, or other extrema value relative to other function values calculated for the data item
- a non-content-based technique e.g
- a segment is restricted to a minimum and/or maximum length, to a minimum or maximum number of segments per data item, or any other appropriate limitation.
- Data segmenter/data reassembler 610 further processes information to indicate the segment(s) mapping to the file, data stream, or data block so that the file, data stream, or data block can be reconstructed from the segment(s).
- a list of fingerprints is used to indicate a mapping of segment(s) that are associated with a file, data stream, or data block. Mapping information is stored using mapping storage 616 .
- Segment compress/segment decompress 612 compresses the segment(s).
- the compression and decompression system is compatible with being able to store the segment(s) using a deduplication system—for example, there is a one to one correspondence between a given segment and the compressed version of the given segment so that it can be identified by using the compressed version of the given segment whether the given segment in its compressed form has been previously stored.
- compression system and/or decompression system comprise(s) a lossless compression/decompression system, a Huffman coding system, a Lempel-Ziv Welch coding system, or any other appropriate system.
- the compressed segment is transferred to a system coupled to storage user system 600 via interface 614 and network 620 .
- User 624 is able to request via user interface 622 that a file, data stream, or data block is to be retrieved.
- Information stored in mapping storage 616 is used by data segmenter/data reassembler 610 to determine which compressed segment(s) to request to be retrieved from a deduplicating segment storage system (e.g., storage system 100 of FIG. 1 ).
- the compressed segment(s) are transferred via network 620 and interface 614 and decompressed using segment compress/segment decompress 612 .
- Segment compress/segment decompress 612 uses information stored in compression storage 618 to decompress compressed segment(s).
- compression information stored in compression storage 618 are associated with segments based at least in part on one or more of the following: a user, a source system, a session, or any other appropriate manner of assigning compression information associated with a file, data stream, or data block.
- Data segmenter/data reassemble 310 reassembles the decompressed segment(s) to restore the file, data stream, or data block.
- FIG. 7 is a flow diagram illustrating an embodiment of a process for storing data.
- the data stream(s), data file(s), or data block(s) is/are broken into segment(s).
- segment(s) are compressed.
- compressed segment(s) is/are transferred.
- the compressed segment(s) is/are transferred from a data user system to a storage system.
- metadata information is transferred associated with the compressed segment(s)—for example, a segment identifier, a source identifier, a user identifier, a host identifier, a session identifier, an compression type, an compressor state, a format type, an associated file, data stream, or data block, etc.
- a compressed segment is selected to be processed.
- a check is performed before transferring the compressed segment to determine whether the compressed segment has been previously stored and transfer of the full segment is only performed in the event that the compressed segment has not been previously stored.
- a reference is stored to the previously stored compressed segment, if appropriate.
- a reference is stored in the event that the reference is useful in being able to retrieve the compressed segment with respect to retrieving the data stream(s), data block(s), or file(s) associated with the segment that has been compressed and is determined to be identical to a previously stored compressed segment.
- the reference is stored in an index that associates a mapping between data stream(s), data block(s), or file(s) and the segment(s) determined from the data stream(s), data block(s), or file(s).
- a reference or indication is transferred to a user storage system.
- the selected compressed segment is stored.
- An index entry is stored indicating the location at which the selected compressed segment is stored.
- the index entry comprises digital fingerprint, a SHA-1 hash, Rabin Hash or any other appropriate identifier that is used to identify whether an identical segment has been previously stored.
- the index entry is transferred to a user storage system.
- FIG. 8 is a flow diagram illustrating a process for retrieving data.
- the stored compressed segment(s) needed to restore a data file, data stream, or data block are retrieved.
- the compressed segment(s) are transferred.
- the retrieved segment(s) are sent from a storage system to a storage user system.
- the compressed segment(s) are decompressed.
- the data file, data stream, or data block is restored by reassembling the decompressed segment(s).
- FIG. 9 is a block diagram illustrating an embodiment of a storage user system.
- storage user system 900 of FIG. 9 is used to implement storage user system 110 of FIG. 1 .
- storage user system 900 comprises storage device 902 , storage device 904 , storage device 906 , storage interface 908 , data segmenter/data reassembler 910 , segment compress/segment decompress 912 , segment encrypter/segment decrytper 914 , interface 922 which is coupled to network 924 , mapping storage 916 , compression storage 918 , key storage 920 , and user interface 926 which is able to be accessed by user 928 .
- Storage interface 908 receives a file, data stream, or data block to be processed from storage device 902 , storage device 904 , or storage device 906 .
- storage interface 908 receives a file, data stream, or data block from an external storage device (not shown in FIG. 3 ), an external system (not shown in FIG. 3 ), or any other appropriate internal or external component, device, or system.
- the file, data stream, or data block is processed by data segmenter/data reassembler 910 .
- Data segmenter/data reassembler 910 breaks the file, data stream, or data block into segments.
- the file, data stream, or data block is broken into segments by identifying segment boundaries using a content-based technique (e.g., a function is calculated at various locations of a data item, when the function is equal to a value or when the value is a minimum, a maximum, or other extrema value relative to other function values calculated for the data item), a non-content-based technique (e.g., based on data item property—for example, byte length, title, creation date), or any other appropriate technique.
- a content-based technique e.g., a function is calculated at various locations of a data item, when the function is equal to a value or when the value is a minimum, a maximum, or other extrema value relative to other function values calculated for the data item
- a non-content-based technique e.g
- a segment is restricted to a minimum and/or maximum length, to a minimum or maximum number of segments per data item, or any other appropriate limitation.
- Data segmenter/data reassembler 910 further processes information to indicate the segment(s) mapping to the file, data stream, or data block so that the file, data stream, or data block can be reconstructed from the segment(s).
- a list of fingerprints is used to indicate a mapping of segment(s) that are associated with a file, data stream, or data block. Mapping information is stored using mapping storage 916 .
- Segment compress/segment decompress 912 compresses the segment(s).
- the compression and decompression system is compatible with being able to store the segment(s) using a deduplication system—for example, there is a one to one correspondence between a given segment and the compressed version of the given segment so that it can be identified by using the compressed version of the given segment whether the given segment in its compressed form has been previously stored.
- compression system and/or decompression system comprise(s) a lossless compression/decompression system, a Huffman coding system, a Lempel-Ziv Welch coding system, or any other appropriate system.
- Segment encrypter/segment decrypter 912 encrypts the compressed segment(s).
- the encryption and decryption system is compatible with being able to store the compressed segment(s) using a deduplication system—for example, there is a one to one correspondence between a given compressed segment and the encrypted version of the given compressed segment so that it can be identified by using the encrypted version of the given compressed segment whether the given compressed segment in its encrypted form has been previously stored. Note that this somewhat degrades the strength of possible encryption systems that can be used, however the overall system performance of having an encrypted deduplication system outweighs for some applications the selection of encryption system with the required properties.
- encryption system and/or decryption system comprise(s) a stream cipher (e.g., Rivest Cipher 4 (RC4), Rivest Cipher 5 (RC5), etc.), a cipher feedback system, electronic code book, advanced encryption standard (AES), data encryption standard (DES), or any other appropriate system.
- a fixed block cipher system is used by padding a segment to a fixed block size before encrypting or depadding after decrypting.
- the encrypted compressed segment is transferred to a system coupled to storage user system 900 via interface 922 and network 924 .
- User 928 is able to request via user interface 926 that a file, data stream, or data block is to be retrieved.
- Information stored in mapping storage 916 is used by data segmenter/data reassembler 910 to determine which encrypted compressed segment(s) to request to be retrieved from a deduplicating segment storage system (e.g., storage system 100 of FIG. 1 ).
- the encrypted compressed segment(s) are transferred via network 924 and interface 922 and decrypted using segment encrypter/segment decrypter 914 .
- Segmenter encrypter/segment decrypter 914 uses information stored in key storage 920 to decrypt encrypted compressed segment(s).
- keys stored in key storage 920 are associated with segments based at least in part on one or more of the following: a user, a source system, a session, or any other appropriate manner of assigning keys associated with a file, data stream, or data block.
- Segment compress/segment decompress 912 uses information stored in compression storage 918 to decompress decrypted compressed segment(s).
- compression information stored in compression storage 918 are associated with segments based at least in part on one or more of the following: a user, a source system, a session, or any other appropriate manner of assigning compression information associated with a file, data stream, or data block.
- Data segmenter/data reassemble 910 reassembles the decompressed decrypted segment(s) to restore the file, data stream, or data block.
- FIG. 10 is a flow diagram illustrating an embodiment of a process for storing data.
- the data stream(s), data file(s), or data block(s) is/are broken into segment(s).
- segment(s) are compressed.
- segment(s) are encrypted.
- compressed encrypted segment(s) is/are transferred.
- the compressed encrypted segment(s) is/are transferred from a data user system to a storage system.
- metadata information is transferred associated with the compressed encrypted segment(s)—for example, a segment identifier, a source identifier, a user identifier, a host identifier, a session identifier, a compression type, a compressor state, an encryption type, an encryption key, a format type, a pad type, an associated file, data stream, or data block, etc.
- a compressed encrypted segment is selected to be processed.
- a check is performed before transferring the compressed encrypted segment to determine whether the encrypted segment has been previously stored and transfer of the full segment is only performed in the event that the compressed encrypted segment has not been previously stored.
- a reference is stored to the previously stored compressed encrypted segment, if appropriate.
- a reference is stored in the event that the reference is useful in being able to retrieve the compressed encrypted segment with respect to retrieving the data stream(s), data block(s), or file(s) associated with the segment that has been compressed and encrypted and is determined to be identical to a previously stored compressed encrypted segment.
- the reference is stored in an index that associates a mapping between data stream(s), data block(s), or file(s) and the segment(s) determined from the data stream(s), data block(s), or file(s).
- a reference or indication is transferred to a user storage system.
- the selected compressed encrypted segment is stored.
- An index entry is stored indicating the location at which the selected compressed encrypted segment is stored.
- the index entry comprises digital fingerprint, a SHA-1 hash, Rabin Hash or any other appropriate identifier that is used to identify whether an identical segment has been previously stored.
- the index entry is transferred to a user storage system.
- FIG. 11 is a flow diagram illustrating a process for retrieving data.
- the stored compressed encrypted segment(s) needed to restore a data file, data stream, or data block are retrieved.
- the compressed encrypted segment(s) are transferred.
- the retrieved segment(s) are sent from a storage system to a storage user system.
- the compressed encrypted segment(s) are decrypted.
- the decrypted compressed segment(s) is/are decompressed.
- the data file, data stream, or data block is restored by reassembling the decompressed decrypted segment(s).
- FIG. 12A is a block diagram illustrating an embodiment of data structures.
- data item 1200 comprises a data stream, data block, or data file.
- Data item 1200 is broken into set of segments 1210 of variable length. In some embodiments, the segments are of fixed length.
- Set of segments 1210 comprises one or more segments—represented in FIG. 12A by S 1 , S 2 , S 3 , S 4 , and S N .
- FIG. 12B is a block diagram illustrating an embodiment of data relations.
- ID data is associated with ID segment1 , ID segment2 , ID segment3 , ID segment4 , up to ID segmentN .
- the association relationship comprises that data of ID IDdata can be reconstructed or reassembled using a set of segments with ID's of, ID segment2 , ID segment3 , ID segment4 , up to ID segmentN .
- data relations of FIG. 12B are stored using mapping storage (e.g., mapping storage 316 of FIG. 3 , mapping storage 616 of FIG. 6 and/or mapping storage 916 of FIG. 9 ).
- FIG. 13A is a block diagram illustrating an embodiment of data relations.
- a mapping between a data item ID and source ID, user ID, host ID, and format type is depicted.
- An ID for a data item is associated with a source of source ID (e.g., a system source identifier), a user with user ID (e.g., a user identifier that generated, requested to be stored, requested to be retrieved the data item), a host with host ID (e.g., a host system associated with a user), and a format of format type (e.g., stream, block, file, backup, raw, tape format, etc.).
- source ID e.g., a system source identifier
- user with user ID e.g., a user identifier that generated, requested to be stored, requested to be retrieved the data item
- a host with host ID e.g., a host system associated with a user
- a format of format type e.g., stream,
- mapping storage e.g., mapping storage 316 of FIG. 3 , mapping storage 616 of FIG. 6 and/or mapping storage 916 of FIG. 9 ).
- FIG. 13B is a block diagram illustrating an embodiment of data relations.
- An ID for a segment is associated with an encryption of encryption type (e.g., AES, DES, etc.), a key used for encrypting (e.g., a key comprising 128 bits, 256 bits, an alphanumeric string, etc.), and a padding of padding type (e.g., a type of padding added to a variable length segment to achieve a data length compatible with the encryption type, zero pads, data pattern pad, etc.).
- AES AES
- DES DES
- a key used for encrypting e.g., a key comprising 128 bits, 256 bits, an alphanumeric string, etc.
- a padding of padding type e.g., a type of padding added to a variable length segment to achieve a data length compatible with the encryption type, zero pads, data pattern pad, etc.
- FIG. 13C is a block diagram illustrating an embodiment of data relations.
- An ID for a segment is associated with a compression of compression type (e.g., Huffman coding system, a Lempel-Ziv Welch coding system, etc.) and a state used for compressing (e.g., a key comprising 128 bits, 256 bits, an alphanumeric string, etc).
- a compression of compression type e.g., Huffman coding system, a Lempel-Ziv Welch coding system, etc.
- a state used for compressing e.g., a key comprising 128 bits, 256 bits, an alphanumeric string, etc.
- any combination of compression related information or other appropriate associated information is mapped with data segment ID.
- data relations of FIG. 13C are stored using compression storage (e.g., compression storage 618 of FIG. 6 and/or compression storage 918 of FIG. 9 ).
Abstract
Description
Claims (12)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/271,246 US9436723B2 (en) | 2009-06-09 | 2014-05-06 | Segment deduplication system with compression of segments |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/455,951 US8762348B2 (en) | 2009-06-09 | 2009-06-09 | Segment deduplication system with compression of segments |
US14/271,246 US9436723B2 (en) | 2009-06-09 | 2014-05-06 | Segment deduplication system with compression of segments |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/455,951 Continuation US8762348B2 (en) | 2009-06-09 | 2009-06-09 | Segment deduplication system with compression of segments |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140330797A1 US20140330797A1 (en) | 2014-11-06 |
US9436723B2 true US9436723B2 (en) | 2016-09-06 |
Family
ID=43301494
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/455,951 Active 2030-02-17 US8762348B2 (en) | 2009-06-09 | 2009-06-09 | Segment deduplication system with compression of segments |
US14/271,246 Active US9436723B2 (en) | 2009-06-09 | 2014-05-06 | Segment deduplication system with compression of segments |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/455,951 Active 2030-02-17 US8762348B2 (en) | 2009-06-09 | 2009-06-09 | Segment deduplication system with compression of segments |
Country Status (1)
Country | Link |
---|---|
US (2) | US8762348B2 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150234616A1 (en) * | 2009-06-25 | 2015-08-20 | Emc Corporation | System and method for providing long-term storage for data |
US10572172B2 (en) | 2018-04-20 | 2020-02-25 | EMC IP Holding Company LLC | Multi-granular data reduction for remote data replication |
US10776029B2 (en) | 2018-12-21 | 2020-09-15 | Dell Products, L.P. | System and method for dynamic optimal block size deduplication |
US20220309030A1 (en) * | 2021-03-29 | 2022-09-29 | EMC IP Holding Company LLC | System and method for data-layout aware decompression and verification using a hardware accelerator chain |
US20220342610A1 (en) * | 2021-04-21 | 2022-10-27 | EMC IP Holding Company LLC | Intelligent metadata compression |
Families Citing this family (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8291183B2 (en) | 2009-01-15 | 2012-10-16 | Emc Corporation | Assisted mainframe data de-duplication |
US8731190B2 (en) * | 2009-06-09 | 2014-05-20 | Emc Corporation | Segment deduplication system with encryption and compression of segments |
US8510275B2 (en) * | 2009-09-21 | 2013-08-13 | Dell Products L.P. | File aware block level deduplication |
US9740704B2 (en) * | 2010-01-28 | 2017-08-22 | Hewlett Packard Enterprise Development Lp | Method and apparatus for random access of data stored in a sequential manner |
US8838551B2 (en) * | 2011-10-21 | 2014-09-16 | International Business Machines Corporation | Multi-level database compression |
US9104971B1 (en) * | 2012-06-29 | 2015-08-11 | Emc Corporation | Automated end-to-end sales process of storage appliances of storage systems using predictive modeling |
US9384218B2 (en) * | 2012-08-21 | 2016-07-05 | Emc Corporation | Format identification for fragmented image data |
CN103001863B (en) * | 2012-11-27 | 2015-09-09 | 中国科学院声学研究所 | Packet quick copy method, packet read method |
US9306997B2 (en) | 2013-01-16 | 2016-04-05 | Cisco Technology, Inc. | Method for optimizing WAN traffic with deduplicated storage |
US9300748B2 (en) | 2013-01-16 | 2016-03-29 | Cisco Technology, Inc. | Method for optimizing WAN traffic with efficient indexing scheme |
US9509736B2 (en) | 2013-01-16 | 2016-11-29 | Cisco Technology, Inc. | Method for optimizing WAN traffic |
US20140215094A1 (en) * | 2013-01-29 | 2014-07-31 | Anders Nordin | Method and system for data compression |
US9116849B2 (en) * | 2013-03-13 | 2015-08-25 | Intel Corporation | Community-based de-duplication for encrypted data |
US9367575B1 (en) * | 2013-06-28 | 2016-06-14 | Veritas Technologies Llc | System and method for managing deduplication between applications using dissimilar fingerprint types |
US9246890B2 (en) * | 2014-02-18 | 2016-01-26 | Oracle International Corporation | PGP encrypted data transfer |
US9003200B1 (en) * | 2014-09-22 | 2015-04-07 | Storagecraft Technology Corporation | Avoiding encryption of certain blocks in a deduplication vault |
US9916320B2 (en) * | 2015-04-26 | 2018-03-13 | International Business Machines Corporation | Compression-based filtering for deduplication |
US10310774B2 (en) * | 2015-12-24 | 2019-06-04 | Intel Corporation | Techniques for data storage protection and integrity checking |
US10691340B2 (en) * | 2017-06-20 | 2020-06-23 | Samsung Electronics Co., Ltd. | Deduplication of objects by fundamental data identification |
US10860555B2 (en) | 2018-08-27 | 2020-12-08 | Dell Products, L.P. | Method and apparatus for two tier data deduplication using weighted graphs |
US11017108B2 (en) | 2018-10-30 | 2021-05-25 | International Business Machines Corporation | Storage unification with security management |
US11392551B2 (en) * | 2019-02-04 | 2022-07-19 | EMC IP Holding Company LLC | Storage system utilizing content-based and address-based mappings for deduplicatable and non-deduplicatable types of data |
US11221778B1 (en) * | 2019-04-02 | 2022-01-11 | Pure Storage, Inc. | Preparing data for deduplication |
EP3973687A4 (en) * | 2019-05-22 | 2023-09-13 | Myota, Inc. | Method and system for distributed data storage with enhanced security, resilience, and control |
US11797486B2 (en) | 2022-01-03 | 2023-10-24 | Bank Of America Corporation | File de-duplication for a distributed database |
Citations (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6438468B1 (en) | 2000-11-28 | 2002-08-20 | Honeywell International Inc. | Systems and methods for delivering data updates to an aircraft |
US6523114B1 (en) | 1994-12-14 | 2003-02-18 | Sony Corporation | Method and apparatus for embedding authentication information within digital data |
US6667700B1 (en) | 2002-10-30 | 2003-12-23 | Nbt Technology, Inc. | Content-based segmentation scheme for data compression in storage and transmission including hierarchical segment representation |
US20040199669A1 (en) | 2003-04-04 | 2004-10-07 | Riggs Nicholas Dale | Apparatus and method for efficiently and securely transferring files over a communications network |
US20050131990A1 (en) | 2003-12-04 | 2005-06-16 | Acpana Business Systems Inc. | Data backup system and method |
US20050131939A1 (en) * | 2003-12-16 | 2005-06-16 | International Business Machines Corporation | Method and apparatus for data redundancy elimination at the block level |
US20050278525A1 (en) | 2001-03-26 | 2005-12-15 | Microsoft Corporation | Encrypted key cache |
CN1758587A (en) | 2005-09-06 | 2006-04-12 | 宏碁股份有限公司 | Data processing method |
US7143251B1 (en) * | 2003-06-30 | 2006-11-28 | Data Domain, Inc. | Data storage using identifiers |
US20070208893A1 (en) * | 2006-02-23 | 2007-09-06 | Microsoft Corporation | File-based compression on a fat volume |
US20070239946A1 (en) * | 2006-04-11 | 2007-10-11 | Data Domain, Inc. | Efficient data storage using two level delta resemblance |
CN101158954A (en) | 2007-11-07 | 2008-04-09 | 上海爱数软件有限公司 | Method for recognizing repeat data in computer storage |
US20080098083A1 (en) | 2006-10-19 | 2008-04-24 | Oracle International Corporation | System and method for data de-duplication |
US20080243953A1 (en) * | 2007-03-30 | 2008-10-02 | Weibao Wu | Implementing read/write, multi-versioned file system on top of backup data |
US20080256143A1 (en) * | 2007-04-11 | 2008-10-16 | Data Domain, Inc. | Cluster storage using subsegmenting |
US20090012990A1 (en) * | 2005-04-01 | 2009-01-08 | International Business Machines Corporation | System and program for joining source table rows with target table rows |
CN101409713A (en) | 2007-06-08 | 2009-04-15 | 索尼株式会社 | Content distribution system, distribution server, terminal, and content distributing method |
US7567188B1 (en) * | 2008-04-10 | 2009-07-28 | International Business Machines Corporation | Policy based tiered data deduplication strategy |
US7584338B1 (en) | 2005-09-27 | 2009-09-01 | Data Domain, Inc. | Replication of deduplicated storage system |
US20090234870A1 (en) * | 2008-03-14 | 2009-09-17 | International Business Machines Corporation | Ordering compression and deduplication of data |
US20090268903A1 (en) | 2008-04-25 | 2009-10-29 | Netapp, Inc. | Network storage server with integrated encryption, compression and deduplication capability |
US20100011031A1 (en) * | 2006-12-28 | 2010-01-14 | Arcsight, Inc. | Storing log data efficiently while supporting querying |
US20100198797A1 (en) | 2009-02-05 | 2010-08-05 | Wideman Roderick B | Classifying data for deduplication and storage |
US20100228800A1 (en) * | 2009-03-06 | 2010-09-09 | Bluearc Uk Limited | Data Compression in a File Storage System |
US20100332818A1 (en) * | 2009-06-30 | 2010-12-30 | Anand Prahlad | Cloud storage and networking agents, including agents for utilizing multiple, different cloud storage sites |
US20110194688A1 (en) | 2008-06-03 | 2011-08-11 | Thales | Method and System Making it Possible to Protect After Compression the Confidentiality of the Data of a Video Stream During Its Transmission |
US8117464B1 (en) | 2008-04-30 | 2012-02-14 | Netapp, Inc. | Sub-volume level security for deduplicated data |
US8379841B2 (en) | 2006-03-23 | 2013-02-19 | Exegy Incorporated | Method and system for high throughput blockwise independent encryption/decryption |
Family Cites Families (65)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5450562A (en) * | 1992-10-19 | 1995-09-12 | Hewlett-Packard Company | Cache-based data compression/decompression |
JP2831602B2 (en) * | 1995-01-13 | 1998-12-02 | 富士通株式会社 | Compressed data management device and compressed data management method |
US6041396A (en) * | 1996-03-14 | 2000-03-21 | Advanced Micro Devices, Inc. | Segment descriptor cache addressed by part of the physical address of the desired descriptor |
US6000009A (en) * | 1997-05-06 | 1999-12-07 | International Business Machines Corporation | Method and apparatus for allocation of disk memory space for compressed data records |
US6032197A (en) * | 1997-09-25 | 2000-02-29 | Microsoft Corporation | Data packet header compression for unidirectional transmission |
US6061475A (en) * | 1998-03-20 | 2000-05-09 | Axcess, Inc. | Video compression apparatus and method |
US7082162B2 (en) * | 1999-04-17 | 2006-07-25 | Pts Corporation | Segment-based encoding system including segment-specific metadata |
KR100343766B1 (en) * | 1999-06-08 | 2002-07-20 | 마쯔시다덴기산교 가부시키가이샤 | Video signal shuffling, encoding, decoding apparatus and program recording medium |
US6976165B1 (en) * | 1999-09-07 | 2005-12-13 | Emc Corporation | System and method for secure storage, transfer and retrieval of content addressable information |
US6658423B1 (en) * | 2001-01-24 | 2003-12-02 | Google, Inc. | Detecting duplicate and near-duplicate files |
US6577254B2 (en) * | 2001-11-14 | 2003-06-10 | Hewlett-Packard Development Company, L.P. | Data compression/decompression system |
US8019788B1 (en) * | 2002-09-30 | 2011-09-13 | Siemens Product Lifecycle Management Software Inc. | Data compression and file segmentation in directmodel JT datastores |
US6928526B1 (en) * | 2002-12-20 | 2005-08-09 | Datadomain, Inc. | Efficient data storage system |
US7263233B2 (en) * | 2002-12-26 | 2007-08-28 | Intel Corporation | Apparatus and method for data compressibility test |
US9678967B2 (en) * | 2003-05-22 | 2017-06-13 | Callahan Cellular L.L.C. | Information source agent systems and methods for distributed data storage and management using content signatures |
US8200775B2 (en) * | 2005-02-01 | 2012-06-12 | Newsilike Media Group, Inc | Enhanced syndication |
WO2005050385A2 (en) * | 2003-11-13 | 2005-06-02 | Commvault Systems, Inc. | System and method for performing integrated storage operations |
JP5173427B2 (en) * | 2004-11-08 | 2013-04-03 | イノパス・ソフトウェアー・インコーポレーテッド | Compressed read-only memory file system (CRMFS) image update |
US7966327B2 (en) * | 2004-11-08 | 2011-06-21 | The Trustees Of Princeton University | Similarity search system with compact data structures |
WO2006052242A1 (en) * | 2004-11-08 | 2006-05-18 | Seirad, Inc. | Methods and systems for compressing and comparing genomic data |
US7079053B2 (en) * | 2004-11-29 | 2006-07-18 | Honeywell International Inc. | Method and system for value-based data compression |
US7320008B1 (en) * | 2004-12-20 | 2008-01-15 | Veritas Operating Corporation | Data protection mechanism |
US7549058B1 (en) * | 2005-06-30 | 2009-06-16 | Mavs Lab. Inc. | Method and apparatus for encrypting and decrypting digital data |
US8156563B2 (en) * | 2005-11-18 | 2012-04-10 | Sandisk Technologies Inc. | Method for managing keys and/or rights objects |
US20070143459A1 (en) * | 2005-12-19 | 2007-06-21 | Lucent Technologies Inc. | Protection of privacy-sensitive information through redundancy, encryption and distribution of information |
US8832045B2 (en) * | 2006-04-07 | 2014-09-09 | Data Storage Group, Inc. | Data compression and storage techniques |
US7860843B2 (en) * | 2006-04-07 | 2010-12-28 | Data Storage Group, Inc. | Data compression and storage techniques |
US20080126357A1 (en) * | 2006-05-04 | 2008-05-29 | Wambo, Inc. | Distributed file storage and transmission system |
DE102006027030A1 (en) * | 2006-06-08 | 2007-12-13 | Wittkötter, Erland, Dr. | Device and method for protected distribution of electronic documents |
US20070300031A1 (en) * | 2006-06-22 | 2007-12-27 | Ironkey, Inc. | Memory data shredder |
US7921077B2 (en) * | 2006-06-29 | 2011-04-05 | Netapp, Inc. | System and method for managing data deduplication of storage systems utilizing persistent consistency point images |
US7504969B2 (en) * | 2006-07-11 | 2009-03-17 | Data Domain, Inc. | Locality-based stream segmentation for data deduplication |
US7995759B1 (en) * | 2006-09-28 | 2011-08-09 | Netapp, Inc. | System and method for parallel compression of a single data stream |
US7797323B1 (en) * | 2006-10-11 | 2010-09-14 | Hewlett-Packard Development Company, L.P. | Producing representative hashes for segments of a file |
US8635194B2 (en) * | 2006-10-19 | 2014-01-21 | Oracle International Corporation | System and method for data compression |
US8041641B1 (en) * | 2006-12-19 | 2011-10-18 | Symantec Operating Corporation | Backup service and appliance with single-instance storage of encrypted data |
US7840537B2 (en) * | 2006-12-22 | 2010-11-23 | Commvault Systems, Inc. | System and method for storing redundant information |
US7769971B2 (en) * | 2007-03-29 | 2010-08-03 | Data Center Technologies | Replication and restoration of single-instance storage pools |
US20080243878A1 (en) * | 2007-03-29 | 2008-10-02 | Symantec Corporation | Removal |
WO2008138008A1 (en) * | 2007-05-08 | 2008-11-13 | Riverbed Technology, Inc | A hybrid segment-oriented file server and wan accelerator |
JP2008287519A (en) * | 2007-05-17 | 2008-11-27 | Keiko Ogawa | Data encryption, transmission and saving system and removable medium |
US7873828B2 (en) * | 2007-08-07 | 2011-01-18 | Optica Technologies, Inc. | Method and apparatus for encrypting and decrypting data to/from an ESCON tape system |
US9128882B2 (en) * | 2007-08-08 | 2015-09-08 | Qualcomm Incorporated | Mobile client device driven data backup |
US20090049260A1 (en) * | 2007-08-13 | 2009-02-19 | Upadhyayula Shivarama Narasimh | High performance data deduplication in a virtual tape system |
CN101398752B (en) * | 2007-09-29 | 2011-08-31 | 国际商业机器公司 | Overlapping command access unit and method |
US8549326B2 (en) * | 2007-10-20 | 2013-10-01 | Blackout, Inc. | Method and system for extending encrypting file system |
US8332404B2 (en) * | 2007-10-25 | 2012-12-11 | Hewlett-Packard Development Company, L.P. | Data processing apparatus and method of processing data |
US8266430B1 (en) * | 2007-11-29 | 2012-09-11 | Emc Corporation | Selective shredding in a deduplication system |
US8166260B2 (en) * | 2008-04-18 | 2012-04-24 | Netapp, Inc. | Method and system for managing inactive snapshot blocks |
US8275177B2 (en) * | 2008-05-23 | 2012-09-25 | Oracle America, Inc. | System and method for media fingerprint indexing |
US8645333B2 (en) * | 2008-05-29 | 2014-02-04 | International Business Machines Corporation | Method and apparatus to minimize metadata in de-duplication |
US8108353B2 (en) * | 2008-06-11 | 2012-01-31 | International Business Machines Corporation | Method and apparatus for block size optimization in de-duplication |
US8041907B1 (en) * | 2008-06-30 | 2011-10-18 | Symantec Operating Corporation | Method and system for efficient space management for single-instance-storage volumes |
US8250043B2 (en) * | 2008-08-19 | 2012-08-21 | Netapp, Inc. | System and method for compression of partially ordered data sets |
US8572409B2 (en) * | 2008-09-26 | 2013-10-29 | Stephen P. Spackman | Method and apparatus for non-redundant encrypted storage |
US10057641B2 (en) * | 2009-03-25 | 2018-08-21 | Sony Corporation | Method to upgrade content encryption |
US8205065B2 (en) * | 2009-03-30 | 2012-06-19 | Exar Corporation | System and method for data deduplication |
US8401181B2 (en) * | 2009-06-09 | 2013-03-19 | Emc Corporation | Segment deduplication system with encryption of segments |
US8731190B2 (en) * | 2009-06-09 | 2014-05-20 | Emc Corporation | Segment deduplication system with encryption and compression of segments |
US8204862B1 (en) * | 2009-10-02 | 2012-06-19 | Symantec Corporation | Systems and methods for restoring deduplicated data |
US8423520B2 (en) * | 2009-11-23 | 2013-04-16 | Dell Products L.P. | Methods and apparatus for efficient compression and deduplication |
US8819452B2 (en) * | 2009-11-25 | 2014-08-26 | Cleversafe, Inc. | Efficient storage of encrypted data in a dispersed storage network |
US9501365B2 (en) * | 2009-12-28 | 2016-11-22 | Netapp, Inc. | Cloud-based disaster recovery of backup data and metadata |
US20120095968A1 (en) * | 2010-10-17 | 2012-04-19 | Stephen Gold | Storage tiers for different backup types |
US8682873B2 (en) * | 2010-12-01 | 2014-03-25 | International Business Machines Corporation | Efficient construction of synthetic backups within deduplication storage system |
-
2009
- 2009-06-09 US US12/455,951 patent/US8762348B2/en active Active
-
2014
- 2014-05-06 US US14/271,246 patent/US9436723B2/en active Active
Patent Citations (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6523114B1 (en) | 1994-12-14 | 2003-02-18 | Sony Corporation | Method and apparatus for embedding authentication information within digital data |
US6438468B1 (en) | 2000-11-28 | 2002-08-20 | Honeywell International Inc. | Systems and methods for delivering data updates to an aircraft |
US20050278525A1 (en) | 2001-03-26 | 2005-12-15 | Microsoft Corporation | Encrypted key cache |
US6667700B1 (en) | 2002-10-30 | 2003-12-23 | Nbt Technology, Inc. | Content-based segmentation scheme for data compression in storage and transmission including hierarchical segment representation |
US20040199669A1 (en) | 2003-04-04 | 2004-10-07 | Riggs Nicholas Dale | Apparatus and method for efficiently and securely transferring files over a communications network |
US7143251B1 (en) * | 2003-06-30 | 2006-11-28 | Data Domain, Inc. | Data storage using identifiers |
US20050131990A1 (en) | 2003-12-04 | 2005-06-16 | Acpana Business Systems Inc. | Data backup system and method |
US7401194B2 (en) | 2003-12-04 | 2008-07-15 | Acpana Business Systems Inc. | Data backup system and method |
US20050131939A1 (en) * | 2003-12-16 | 2005-06-16 | International Business Machines Corporation | Method and apparatus for data redundancy elimination at the block level |
US20090012990A1 (en) * | 2005-04-01 | 2009-01-08 | International Business Machines Corporation | System and program for joining source table rows with target table rows |
CN1758587A (en) | 2005-09-06 | 2006-04-12 | 宏碁股份有限公司 | Data processing method |
US7584338B1 (en) | 2005-09-27 | 2009-09-01 | Data Domain, Inc. | Replication of deduplicated storage system |
US20070208893A1 (en) * | 2006-02-23 | 2007-09-06 | Microsoft Corporation | File-based compression on a fat volume |
US8379841B2 (en) | 2006-03-23 | 2013-02-19 | Exegy Incorporated | Method and system for high throughput blockwise independent encryption/decryption |
US20070239946A1 (en) * | 2006-04-11 | 2007-10-11 | Data Domain, Inc. | Efficient data storage using two level delta resemblance |
US20080098083A1 (en) | 2006-10-19 | 2008-04-24 | Oracle International Corporation | System and method for data de-duplication |
US20100011031A1 (en) * | 2006-12-28 | 2010-01-14 | Arcsight, Inc. | Storing log data efficiently while supporting querying |
US20080243953A1 (en) * | 2007-03-30 | 2008-10-02 | Weibao Wu | Implementing read/write, multi-versioned file system on top of backup data |
US20080256143A1 (en) * | 2007-04-11 | 2008-10-16 | Data Domain, Inc. | Cluster storage using subsegmenting |
CN101409713A (en) | 2007-06-08 | 2009-04-15 | 索尼株式会社 | Content distribution system, distribution server, terminal, and content distributing method |
CN101158954A (en) | 2007-11-07 | 2008-04-09 | 上海爱数软件有限公司 | Method for recognizing repeat data in computer storage |
US20090234870A1 (en) * | 2008-03-14 | 2009-09-17 | International Business Machines Corporation | Ordering compression and deduplication of data |
US7567188B1 (en) * | 2008-04-10 | 2009-07-28 | International Business Machines Corporation | Policy based tiered data deduplication strategy |
US20090268903A1 (en) | 2008-04-25 | 2009-10-29 | Netapp, Inc. | Network storage server with integrated encryption, compression and deduplication capability |
US8117464B1 (en) | 2008-04-30 | 2012-02-14 | Netapp, Inc. | Sub-volume level security for deduplicated data |
US20110194688A1 (en) | 2008-06-03 | 2011-08-11 | Thales | Method and System Making it Possible to Protect After Compression the Confidentiality of the Data of a Video Stream During Its Transmission |
US20100198797A1 (en) | 2009-02-05 | 2010-08-05 | Wideman Roderick B | Classifying data for deduplication and storage |
US20100228800A1 (en) * | 2009-03-06 | 2010-09-09 | Bluearc Uk Limited | Data Compression in a File Storage System |
US20100332818A1 (en) * | 2009-06-30 | 2010-12-30 | Anand Prahlad | Cloud storage and networking agents, including agents for utilizing multiple, different cloud storage sites |
Non-Patent Citations (2)
Title |
---|
Khalid Sayood, "An Introduction to Data Compression". 2006. |
Sayood, Khalid, "Introduction to Data Compression", 2006. |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150234616A1 (en) * | 2009-06-25 | 2015-08-20 | Emc Corporation | System and method for providing long-term storage for data |
US10108353B2 (en) * | 2009-06-25 | 2018-10-23 | EMC IP Holding Company LLC | System and method for providing long-term storage for data |
US10572172B2 (en) | 2018-04-20 | 2020-02-25 | EMC IP Holding Company LLC | Multi-granular data reduction for remote data replication |
US10776029B2 (en) | 2018-12-21 | 2020-09-15 | Dell Products, L.P. | System and method for dynamic optimal block size deduplication |
US20220309030A1 (en) * | 2021-03-29 | 2022-09-29 | EMC IP Holding Company LLC | System and method for data-layout aware decompression and verification using a hardware accelerator chain |
US11657018B2 (en) * | 2021-03-29 | 2023-05-23 | EMC IP Holding Company LLC | System and method for data-layout aware decompression and verification using a hardware accelerator chain |
US20220342610A1 (en) * | 2021-04-21 | 2022-10-27 | EMC IP Holding Company LLC | Intelligent metadata compression |
US11836388B2 (en) * | 2021-04-21 | 2023-12-05 | EMC IP Holding Company LLC | Intelligent metadata compression |
Also Published As
Publication number | Publication date |
---|---|
US8762348B2 (en) | 2014-06-24 |
US20100312800A1 (en) | 2010-12-09 |
US20140330797A1 (en) | 2014-11-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9710333B2 (en) | Segment deduplication system with encryption and compression of segments | |
US9436723B2 (en) | Segment deduplication system with compression of segments | |
US8401181B2 (en) | Segment deduplication system with encryption of segments | |
EP2441260B1 (en) | Segment deduplication system with encryption segments | |
US10691340B2 (en) | Deduplication of objects by fundamental data identification | |
US9690802B2 (en) | Stream locality delta compression | |
US7912986B2 (en) | Secure block read and write protocol for remotely stored files | |
US9479616B2 (en) | Systems and methods for transformation of logical data objects for storage | |
US8751462B2 (en) | Delta compression after identity deduplication | |
US8300823B2 (en) | Encryption and compression of data for storage | |
US9323773B2 (en) | Systems and methods for transformation of logical data objects for storage | |
US8799543B2 (en) | Method and system for transformation of logical data objects for storage | |
EP4135200A1 (en) | Systems, methods, and apparatus for dividing and compressing data | |
CN114521260A (en) | Method and system for data deduplication and compression in untrusted storage systems | |
EP4134818A1 (en) | Systems, methods, and apparatus for dividing and encrypting data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: DATA DOMAIN LLC, DELAWARE Free format text: CONVERSION;ASSIGNOR:DATA DOMAIN, INC.;REEL/FRAME:033745/0444 Effective date: 20091217 Owner name: DATA DOMAIN HOLDING, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DATA DOMAIN LLC;REEL/FRAME:033743/0508 Effective date: 20091222 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DATA DOMAIN HOLDING, INC.;REEL/FRAME:033743/0510 Effective date: 20091231 Owner name: DATA DOMAIN, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LUMB, CHRISTOPHER R.;REEL/FRAME:033743/0506 Effective date: 20090717 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT, TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 |
|
AS | Assignment |
Owner name: EMC IP HOLDING COMPANY LLC, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EMC CORPORATION;REEL/FRAME:040203/0001 Effective date: 20160906 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., T Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:053546/0001 Effective date: 20200409 |
|
AS | Assignment |
Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MOZY, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MAGINATICS LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL INTERNATIONAL, L.L.C., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: AVENTAIL LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |