Abstract:
A processing method for duplicated data includes the following steps. A query request is received from a client, in which the query request includes a requested fingerprint value. A hash tank corresponding to the requested fingerprint value in a memory is searched for the requested fingerprint value. When the requested fingerprint value does not exist in the hash tank corresponding to the requested fingerprint value, the following steps are executed. An addition table in the memory is searched for the requested fingerprint value; and when the requested fingerprint value exists in the addition table, an invalid duplicate message is sent to the client.
Abstract:
A data restoration method for data de-duplication uses to restore partial data of a target file of a client, includes the client queries a file attribute of a source file corresponding to the target file from a storage server; the client compares whether the file attribute of the target file is the same as the file attribute of the source file; if the file attributes of the target file and the source file are different, segmentation processing is performed on the target file to generate segmentation data blocks and corresponding fingerprints; after obtaining all the fingerprints of the source file from the storage server, the client compares a difference between the fingerprints of the source file and the target file; the client obtains corresponding segmentation data blocks from the storage server according to the different fingerprints and overwrites the obtained segmentation data blocks to corresponding positions in the target file.
Abstract:
A method, system, and program product for ensuring consistency of dynamically changing volumes comprising creating a production change map for a first volume; wherein the production change map is marked to represent pending IO, creating a replication change map for a second volume; wherein the replication change map is marked to represent pending IO, transferring a first signature corresponding to a portion of the first volume to the replication volume, wherein the signature does not include the portion marked as pending IO in the production change map, comparing the first signature to a second signature, the second signature corresponding to a portion of the replication volume corresponding to the portion of the production volume; wherein portions marked as dirty in the replication change map are not included in the signature.
Abstract:
A system and method are described for coordinating deduplication operations and backup operations of a storage volume. In one embodiment, a request is identified to eliminate duplicate data from a storage volume. The storage volume may be scheduled to be backed up on a periodic basis. The duration of time required to complete an operation to eliminate duplicate data from the storage volume may be determined. The determination may be based on the amount of data modified on the storage volume since the last operation to eliminate duplicate data from the storage volume. The determined duration of time may be used to schedule the start time of the operation to eliminate duplicate data such that the operation is completed prior to the next scheduled backup of the storage volume. The operation may be initiated at the scheduled start time, ensuring the operation is completed prior to the next scheduled backup.
Abstract:
Described are techniques for representing a data segment comprising. A list of one or more tokens representing one or more data portions included in the data segment is received. A unique identifier uniquely identifying said data segment from other data segments is received. A signature value determined in accordance with said list of tokens and said unique identifier is received. The list of tokens, said unique identifier, and said signature value are stored as information corresponding to said data segment.
Abstract:
A first computational platform generates a data structure that indicates a set of blocks, wherein the indicated set of blocks have to be rewritten to revert a logical storage structure stored in the first computational platform to a previous state. An Input/Output (I/O) request that corresponds to a read operation on a selected block of the logical storage structure is received. A determination is made from the data structure that the selected block has to be rewritten to revert the logical storage structure stored in the first computational platform to the previous state. The first computational platform receives the selected block from a second computational platform, in response to a request made by the first computational platform to the second computational platform for the selected block.
Abstract:
A common backup format of a backup rights object according to embodiments of the present invention has the following features: License information that is not critical for cryptographic security of the rights object is kept in “plain text” with a well defined syntax in a first data container, license information that is critical for cryptographic security of the rights object is stored in cryptographically protected form that is specific for the originating device to which the rights object is bound to in a second data container, and the rights object is cryptographically signed by the originating device such that it may not be manipulated. The signature is stored in a third data container.
Abstract:
Data deduplication in a storage system, achieving high performance due to minimal overhead during a backup operation, reduced disk read operations to locate duplicate data and minimal impact for restore operations involving deduplicated data.
Abstract:
Methods and systems for efficient and accurate re-starting of data transfers using volatile data transfer mechanisms, such as pipes, following an error. According to one embodiment, portions of the transferred data can be saved in a fallback file. In addition, checkpoint commands can be periodically provided, upon which much of the data in the fallback file can be overwritten. During the original transmission, the data that has passed through the mechanism can be counted, and a signature for the data that has passed can be accumulated. After certain error conditions, the data in the fallback file can be recovered and passed to the receiving process and the transmission can then be resumed at the point where it had left off. After other errors requiring a complete re-start, a second signature of the re-transmitted data can be accumulated and original and second signatures compared to determine if the data is valid.
Abstract:
Methods, systems and computer program products for providing shared file back-ups in a repository. Methods include receiving metadata of a file to be backed-up from a client. A global directory of back-up files is accessed. The global directory includes back-up file metadata and back-up file pointers corresponding to each of the back-up files in the repository. It is determined if the metadata matches one of the back-up file metadatas. If the metadata matches one of the back-up file metadatas, then the back-up file pointer corresponding to the matching back-up file metadata is added to a client directory of client back-up files in the repository.