Data processing method based on blockchain network and related product
US-2024419537-A1 · Dec 19, 2024 · US
US9239869B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9239869-B1 |
| Application number | US-201313890007-A |
| Country | US |
| Kind code | B1 |
| Filing date | May 8, 2013 |
| Priority date | May 8, 2013 |
| Publication date | Jan 19, 2016 |
| Grant date | Jan 19, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Various embodiments illustrated and described herein include systems, methods, and computer program products to protect NTFS deduplicated volumes. Some embodiments select a data protection mode from various modes to protect deduplicated volumes. Some data protection modes retrieve the deduplicated files and associated data chunks without rehydrating the files and send them to a replica. Some data protection modes rehydrate deduplicated files as they are retrieved, send the rehydrated files to the replica, and turn on deduplication at the replica so the files can be deduplicated on the replica. Deduplication settings can also be transferred to the replica so that deduplication on the replica mimics deduplication on the source. Some data protection modes replicate the deduplicated files to the replica.
Opening claim text (preview).
What is claimed is: 1. A method comprising: determining, by a first device, that a storage volume should be synchronized or replicated to a replica storage volume, wherein the storage volume comprises volume data, data chunks, deduplicated files, and deduplication setting data, wherein each of the data chunks corresponds to a plurality of the deduplicated files; in response to determining that the storage volume should be synchronized or replicated to the replica storage volume, determining, by the first device, whether the storage volume is configured or volume level synchronization, file level synchronization, or replication; in response to determining that the storage volume is configured for volume level synchronization, identifying, by the first device, a first folder, wherein the first folder comprises the volume data and a second folder, wherein the second folder comprises the data chunks; reading, by the first device, the data chunks from the second folder; reading, by the first device, the deduplication settings; reading, by the first device, the deduplicated files without rehydrating the deduplicated files; determining, by the first device, that the volume data is excluded from synchronization; in response to determining that the volume data is excluded from synchronization, skipping, by the first device, the volume data; and sending, by the first device, the deduplicated files, the deduplication setting data, and the data chunks to a second device that comprises the replica storage volume. 2. The method of claim 1 further comprising: in response to determining that the storage volume is configured for file level synchronization, reading, by the first device, the deduplicated files in a manner to rehydrate the deduplicated files; and sending, by the first device, the rehydrated files to the replica. 3. The method of claim 1 wherein the deduplication setting data comprises a schedule for deduplication. 4. A method of claim 2 , wherein determining that storage volume is configured for volume level synchronization comprises determining that an operating system of the first device and an operating system of the second device is Windows Server 2012, wherein determining that the storage volume is configured for file level synchronization comprises determining that the operating system of the first device is not Windows Server 2012. 5. The method of claim 1 further comprising: receiving, by the second device, the deduplicated files, the deduplication setting data, and the data chunks; writing, by the second device, the deduplicated files and the data chunks to the replica storage volume; and configuring, by the second device, deduplication of the replica storage volume in accordance with the deduplication setting data. 6. The method of claim 1 , wherein the deduplicated files comprise a sparse point and a reparse point, wherein the sparse point and the reparse point each comprise a reference to a data chunk of the data chunks, wherein reading the deduplicated files without rehydrating the deduplicated files comprises: sending, to a bypass mechanism, a request to read the deduplicated files; and reading, by the bypass mechanism, the deduplicated files without resolving the references that comprise the sparse point and the reparse point. 7. A system comprising a first device, wherein the first device comprises: a first processor; and a first computer readable storage medium comprising instructions executable by the first processor to cause the first device to, determine that a storage volume should be synchronized with a replica storage volume, wherein the storage volume comprises volume data, data chunks, deduplicated files, and deduplication setting data, wherein each of the data chunks corresponds to a plurality of the deduplicated files; in response to a determination that the storage volume should be synchronized with the replica storage volume, determine that the storage volume is configured for volume level synchronization; and in response to a determination that the storage volume is configured for volume level synchronization, identify a first folder, wherein the first folder comprises the volume data and a second folder, wherein the second folder comprises the data chunks; read the data chunks from the second folder; read the deduplication setting data; read the deduplicated files without rehydrating the deduplicated files; determine that the volume data is excluded from synchronization; in response to a determination that the volume data is excluded from synchronization, skip the volume data; and send the deduplicated files, the deduplication setting data, and the data chunks to a second device that comprises the replica storage volume. 8. The system of claim 7 wherein the first computer readable storage medium further comprises instructions executable by the first processor to cause the first device to: determine that the storage volume is configured for file level synchronization; and in response to a determination that the storage volume is configured for file level synchronization, read the deduplicated files in a manner to rehydrate the deduplicated files; and send the rehydrated files to the replica. 9. The system of claim 7 , wherein the first computer readable storage medium further comprises instructions executable by the first processor to cause the first device to: determine that the storage volume is configured for replication; and, in response to a determination that the storage volume is configured for replication, identify first changes to the deduplicated files using a filtering file driver; write the first changes to a journal file and the deduplicated files; identify second changes to the volume data; determine that the volume data is excluded from replication; in response to a determination that the volume data is excluded from replication, write the second changes to the volume data without writing the second changes to the journal file; and send the journal file to the second device. 10. The system of claim 7 further comprising the second device, wherein the second device comprises: a second processor; and a second computer readable storage medium comprising instructions executable by the processor to cause the second device to: receive, from the first device, the deduplicated files, the deduplication setting data, and the data chunks; write the deduplicated files and the data chunks to the replica storage volume; and configure deduplication of the replica storage volume in accordance with the deduplication setting data. 11. The system of claim 7 , wherein the deduplicated files comprise a sparse point and a reparse point, wherein the sparse point and the reparse point each comprise a reference to a data chunk of the data chunks, wherein the instructions executable by the processor to cause the first device to read the deduplicated files without rehydrating the deduplicated files comprise instructions executable by the processor to cause the first device to: send, to a bypass access mechanism, a request to read the deduplicated files; and read, by the bypass access mechanism, the duplicated files without resolving the references that comprise the sparse point and the reparse point. 12. The system of claim 7 , wherein the instructions executable by the first processor to cause the first device to determine that the storage volume is configured for volume level synchronization comprises instructions executable by the first processor to cause the first device to determine that an operating system of the first device and an operating system of the second device is
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.