Incremental inline journaling in a journaled file system
US-2020201826-A1 · Jun 25, 2020 · US
US11733907B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11733907-B2 |
| Application number | US-202016985348-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 5, 2020 |
| Priority date | Aug 5, 2020 |
| Publication date | Aug 22, 2023 |
| Grant date | Aug 22, 2023 |
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.
Disaster recovery operations are disclosed. A copy of data may include segments and delta journals or journals. RTO can be reduced by pre-processing the delta journals after the segments and delta journals are uploaded. The RTO is improved during recovery because the need to process the delta journals is eliminated. Applying the delta journals can be performed to both reduce cost and RTO using graphs.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: generating a backup of data for a point in time based on a bitmap, wherein each entry in the bitmap corresponds to a segment of the data and each marked bit corresponds to a segment that has changed in the data, wherein each segment has a fixed size, by: performing a synchronization process by reading segments of the data corresponding to the marked bits; and during the synchronization process, generating a delta journal, wherein the delta journal includes chunks corresponding to data overwritten by writes applied to segments that are yet to be synchronized by the synchronization process, wherein each chunk has an unfixed size; loading metadata associated with the delta journal stored in cloud storage, wherein the delta journal and segments are associated with the backup that corresponds to the point in time; processing the delta journal to create new delta journals that are based on offsets and segment indexes of the chunks included in the delta journal; grouping the new delta journals based on the segment indexes; overwriting the segments based on the new delta journals such that first chunks included in the chunks and associated with a particular segment are applied at the same time. 2. The method of claim 1 , further comprising removing the delta journal from storage. 3. The method of claim 1 , further comprising generating a graph from the segments and the delta journal associated with the backup. 4. The method of claim 3 , further comprising looping the segments and looping the new delta journals. 5. The method of claim 4 , wherein looping the segments includes persisting data of the segments in memory and wherein looping the new delta journals includes downloading the chunks identified in the new delta journals, persisting the chunks in the memory, and determining segment indices for the chunks. 6. The method of claim 5 , wherein some of the chunks are associated with more than one index. 7. The method of claim 5 , further comprising applying the chunks to the segments in memory and storing the segments in the cloud storage. 8. The method of claim 3 , further comprising performing a snapshot to obtain the backup. 9. The method of claim 1 , further comprising removing the delta journal from the cloud storage. 10. The method of claim 1 , wherein the backup corresponds to a point-in-time after the new delta journals are applied to the segments. 11. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising: generating a backup of data for a point in time based on a bitmap, wherein each entry in the bitmap corresponds to a segment of the data and each marked bit corresponds to a segment that has changed in the data, wherein each segment has a fixed size, by: performing a synchronization process by reading segments of the data corresponding to the marked bits; and during the synchronization process, generating a delta journal, wherein the delta journal includes chunks corresponding to data overwritten by writes applied to segments that are yet to be synchronized by the synchronization process, wherein each chunk has an unfixed size; loading metadata associated with the delta journal stored in cloud storage, wherein the delta journal and segments are associated with the backup that corresponds to the point in time; processing the delta journal to create new delta journals that are based on offsets and segment indexes of the chunks included in the delta journal; grouping the new delta journals based on the segment indexes; overwriting the segments based on the new delta journals such that first chunks included in the chunks and associated with a particular segment are applied at the same time. 12. The non-transitory storage medium of claim 11 , the operations further comprising removing the delta journal from storage. 13. The non-transitory storage medium of claim 11 , the operations further comprising generating a graph from the segments and the delta journal associated with the backup. 14. The non-transitory storage medium of claim 13 , the operations further comprising looping the segments and looping the new delta journals. 15. The non-transitory storage medium of claim 14 , wherein looping the segments includes persisting data of the segments in memory and wherein looping the new delta journals includes downloading the chunks identified in the new delta journals, persisting the chunks in the memory, and determining segment indices for the chunks. 16. The non-transitory storage medium of claim 15 , wherein some of the chunks are associated with more than one index. 17. The non-transitory storage medium of claim 15 , further comprising applying the chunks to the segments in memory and storing the segments in the cloud storage. 18. The non-transitory storage medium of claim 13 , the operations further comprising performing a snapshot to obtain the backup. 19. The non-transitory storage medium of claim 11 , the operations further comprising removing the delta journal from the cloud storage. 20. The non-transitory storage medium of claim 11 , wherein the backup corresponds to a point-in-time after the new delta journals are applied to the segments.
Replication mechanisms · CPC title
Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS] · CPC title
in relation to data integrity, e.g. data losses, bit errors · CPC title
Command handling arrangements, e.g. command buffers, queues, command scheduling · CPC title
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.