Global memory as non-volatile random access memory for guest operating systems
US-8990520-B1 · Mar 24, 2015 · US
US9892002B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9892002-B1 |
| Application number | US-201715496032-A |
| Country | US |
| Kind code | B1 |
| Filing date | Apr 25, 2017 |
| Priority date | Dec 19, 2013 |
| Publication date | Feb 13, 2018 |
| Grant date | Feb 13, 2018 |
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.
Systems and techniques are provided for incremental Continuous Data Protection (iCDP) as a process to secure frequent, and space efficient, versions of consistent point-in-time images of a group of volumes using snapshot technology. The system described herein provides for automation to create and manage frequent snapshots of defined groups of volumes. The incremental approach of the system described herein provides a convenient way to roll back to prior point-in-time versions to investigate data damage due to processing errors or other forms of corruption. The intervals between versions may be controlled. The system beneficially provides for identifying, monitoring, and reclaiming use of log space in log devices in connection with managing recovery and roll back capabilities of the system to desired data versions for purposes of data protection.
Opening claim text (preview).
What is claimed is: 1. A method for providing data protection in a storage system, comprising: storing a plurality of point-in-time versions of data of a source volume in the storage system; in connection with a write to the data stored in the source volume, storing at least one log entry in a log device corresponding to a particular point-in-time version of the data prior to the write, wherein subsequent point-in-time versions after the particular point-in-time version share the at least one log entry until a subsequent write to the data stored in the source volume is performed, wherein the point-in-time versions and the at least one log entry enable the storage system to revert from a current data state to a one or more point-in-time states defined by the point-in-time versions; and terminating at least one point-in-time version according to at least one criterion, wherein the at least one point-in-time version is selected based on an amount of reclaimed space in the log device resulting from termination of the at least one point-in-time version, the log device being separate from the source volume. 2. The method according to claim 1 , wherein terminating the at least one point in time version of the source volume reclaims log space on the log device. 3. The method according to claim 1 , further comprising: analyzing how the terminating of the at least one point-in-time version affects log capacity of the log device. 4. The method according to claim 1 , wherein terminating the at least one point in time version enables reversion to any desired prior storage state. 5. The method according to claim 4 , wherein terminating the at least one point-in-time version includes identification of the point-in-time versions to enable reversion to any desired prior storage state in a way that minimizes use of log space on the log device. 6. The method according to claim 1 , further comprising: providing an interface device that receives a query concerning the at least one criterion and outputs results of the termination of the at least one point-in-time version. 7. The method according to claim 1 , further comprising: controlling an interval between times when each of the plurality of point-in-time versions is stored. 8. A non-transitory computer readable medium storing software for providing data protection in a storage system, the software comprising: executable code that stores a plurality of point-in-time versions of data of a source volume in the storage system; executable code that, in connection with a write to the data stored in the source volume, stores at least one log entry in a log device corresponding to a particular point-in-time version of the data prior to the write, wherein subsequent point-in-time versions after the particular point-in-time version share the at least one log entry until a subsequent write to the data stored in the source volume is performed, wherein the point-in-time versions and the at least one log entry enable the storage system to revert from a current data state to a one or more point-in-time states defined by the point-in-time versions; and executable code that terminates at least one point-in-time version according to at least one criterion, wherein the at least one point-in-time version is selected based on an amount of reclaimed space in the log device resulting from termination of the at least one point-in-time version, the log device being separate from the source volume. 9. The non-transitory computer readable medium according to claim 8 , wherein terminating the at least one point-in-time version reclaims log space on the log device. 10. The non-transitory computer readable medium according to claim 9 , further comprising executable code that analyzes how the terminating of the at least one point-in-time version affects log capacity of the log device. 11. The non-transitory computer readable medium according to claim 8 , terminating the at least point-in-time version enables reversion to any desired prior storage state. 12. The non-transitory computer readable medium according to claim 11 , wherein the executable code that terminates the at least one point-in-time version includes executable code that identifies of the point-in-time versions to enable reversion to any desired prior storage state in a way that minimizes use of log space on the log device. 13. The non-transitory computer readable medium according to claim 8 , further comprising: executable code that provides an interface that receives a query concerning the at least one criterion and outputs results of the termination of the at least one point-in-time version. 14. The non-transitory computer readable medium according to claim 8 , further comprising: executable code that controls the interval between times when each of the plurality of point-in-time versions is stored. 15. A data protection system, comprising: at least one storage device that stores a source volume of data; at least one log device that stores log entries corresponding to the data stored on the source volume; a non-transitory computer readable medium storing software that, when executed by at least one processor, provides data protection, the software including: executable code that stores a plurality of point-in-time versions of data from the source volume in the storage device; executable code that, in connection with a write to the data stored in the source volume, stores at least one log entry in the log device corresponding to a particular point-in-time version of the data prior to the write, wherein subsequent point-in-time versions after the particular point-in-time version share the at least one log entry until a subsequent write to the data stored in the source volume is performed, wherein the point-in-time versions and the at least one log entry enable the storage system to revert from a current data state to a one or more point-in-time states defined by the point-in-time versions; and executable code that terminates at least one point-in-time version according to at least one criterion, wherein the at least one point-in-time version is selected based on an amount of reclaimed space in the log device resulting from termination of the at least one point-in-time version, the log device being separate from the source volume. 16. The data protection system according to claim 15 , wherein terminating the at least one point-in-time version reclaims log space on the log device. 17. The data protection system according to claim 15 , wherein terminating the at least one point-in-time version enables reversion to any desired prior storage state. 18. The data protection system according to claim 17 , wherein the executable code that terminates the at least one point-in-time version includes executable code that identifies the point-in-time versions to enable reversion to any desired prior storage state in a way that minimizes use of log space on the log device. 19. The data protection system according to claim 15 , further comprising: an interface that receives a query concerning the at least one criterion and outputs results of the termination of the at least one point-in-time version. 20. The data protection system according to claim 15 , wherein the software further comprises: executable code that controls the interval between times when each of the plurality of point-in-time versions is stored according to the results.
Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title
where the computing system component is a storage system, e.g. DASD based or network based (digital input from or digital output to record carriers G06F3/06; digital recording or reproducing G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097) · CPC title
by selection of backup contents · CPC title
involving logging of persistent data for recovery · CPC title
Plurality of storage devices · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.