Space accounting for storage system snapshots
US-9753932-B1 · Sep 5, 2017 · US
US10552373B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10552373-B2 |
| Application number | US-201715694604-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 1, 2017 |
| Priority date | Feb 10, 2017 |
| Publication date | Feb 4, 2020 |
| Grant date | Feb 4, 2020 |
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.
A facility for snapshot space accounting for a storage system, such as a filesystem is disclosed. The facility enables users to quickly and easily determine the amount of storage space that would be released or recovered if a snapshot were to be purged. The facility may work in conjunction with, or as part of, a snapshot service. The facility maintains an expiration data structure and a count data structure and uses these data structures in implementing the disclosed snapshot space accounting techniques. The expiration data structure represents the life cycle of each snapshot element maintained by the facility while the count data structure represents, for pairs of snapshots, the size of the information stored in the snapshot data that expired and that spans the corresponding pair of snapshots.
Opening claim text (preview).
We claim: 1. A method, performed by a computing system having one or more processors, for space accounting in a storage system, the method comprising: determining a current epoch value for a plurality of blocks of data and a previous birthdate for each block of data in response to receiving a write request; employing the received write request to provide an expiration entry to an expiration data structure for two snapshot values of each data block, wherein each expiration entry includes an identifier, an associated previous birthdate, and the current epoch value; providing a count data structure, for each block of data, that includes an entry for a first snapshot value corresponding to the previous birthdate and a second snapshot value corresponding to the current epoch value; and increasing a size of the entry based on a size of an associated block of data. 2. The method of claim 1 , further comprising: in response to receiving a request to determine an amount of storage space to be recovered when an identified snapshot is purged from the storage system, determining a range of the identified snapshot; employing the range to determine a chronologically ordered pair of snapshots that includes the identified snapshot; and employing a size of the pair of snapshots to provide the amount of storage space recoverable by purging the identified snapshot. 3. The method of claim 1 , further comprising: receiving a request to determine a size of a chronologically ordered pair of snapshots; and generating the size based on a predetermined block size and a count value associated with each of the ordered pair of snapshots. 4. The method of claim 1 , further comprising: a graphical user interface that includes a plurality of visual elements associated with a plurality of snapshots for the plurality of data blocks, including: a first visual element having a width that represents an amount storage space to be recovered when a selected snapshot is purged; a second visual element having a height that represents a range for the selected snapshot; and wherein one or more of color, patterns, or shading are employed to provide additional information for one or more of the plurality of snapshots and the plurality of data blocks. 5. The method of claim 1 , further comprising: providing a separate epoch counter for each different entity using the storage space system, wherein a different entity includes one of a user or a snapshot policy. 6. The method of claim 1 , further comprising: identifying one or more deleted snapshots that are chronologically adjacent to a selected snapshot; and employing the one or more identified deleted snapshot to select a range for the selected snapshot. 7. The method of claim 1 , further comprising: storing an indication of the current value for the epoch counter in each of the plurality of blocks of data. 8. A computer-readable non-transitory media that stores instructions for space accounting in a storage system, wherein execution of the instructions by one or more processors performs actions, comprising: determining a current epoch value for a plurality of blocks of data and a previous birthdate for each block of data in response to receiving a write request; employing the received write request to provide an expiration entry to an expiration data structure for two snapshot values of each data block, wherein each expiration entry includes an identifier, an associated previous birthdate, and the current epoch value; providing a count data structure, for each block of data, that includes an entry for a first snapshot value corresponding to the previous birthdate and a second snapshot value corresponding to the current epoch value; and increasing a size of the entry based on a size of an associated block of data. 9. The media of claim 8 , further comprising: in response to receiving a request to determine an amount of storage space to be recovered when an identified snapshot is purged from the storage system, determining a range of the identified snapshot; employing the range to determine a chronologically ordered pair of snapshots that includes the identified snapshot; and employing a size of the pair of snapshots to provide the amount of storage space recoverable by purging the identified snapshot. 10. The media of claim 8 , further comprising: receiving a request to determine a size of a chronologically ordered pair of snapshots; and generating the size based on a predetermined block size and a count value associated with each of the ordered pair of snapshots. 11. The media of claim 8 , further comprising: a graphical user interface that includes a plurality of visual elements associated with a plurality of snapshots for the plurality of data blocks, including: a first visual element having a width that represents an amount storage space to be recovered when a selected snapshot is purged; a second visual element having a height that represents a range for the selected snapshot; and wherein one or more of color, patterns, or shading are employed to provide additional information for one or more of the plurality of snapshots and the plurality of data blocks. 12. The media of claim 8 , further comprising: providing a separate epoch counter for each different entity using the storage space system, wherein a different entity includes one of a user or a snapshot policy. 13. The media of claim 8 , further comprising: identifying one or more deleted snapshots that are chronologically adjacent to a selected snapshot; and employing the one or more identified deleted snapshot to select a range for the selected snapshot. 14. The media of claim 8 , further comprising: storing an indication of the current value for the epoch counter in each of the plurality of blocks of data. 15. An apparatus that provide for space accounting in a storage system, comprising: a memory that stores instructions; one or more processors that execute the instructions to perform actions, including: determining a current epoch value for a plurality of blocks of data and a previous birthdate for each block of data in response to receiving a write request; employing the received write request to provide an expiration entry to an expiration data structure for two snapshot values of each data block, wherein each expiration entry includes an identifier, an associated previous birthdate, and the current epoch value; providing a count data structure, for each block of data, that includes an entry for a first snapshot value corresponding to the previous birthdate and a second snapshot value corresponding to the current epoch value; and increasing a size of the entry based on a size of an associated block of data. 16. The apparatus of claim 15 , further comprising: in response to receiving a request to determine an amount of storage space to be recovered when an identified snapshot is purged from the storage system, determining a range of the identified snapshot; employing the range to determine a chronologically ordered pair of snapshots that includes the identified snapshot; and employing a size of the pair of snapshots to provide the amount of storage space recoverable by purging the identified snapshot. 17. The apparatus of claim 15 , further comprising: receiving a request to determine a size of a chronologically ordered pair of snapshots; and generating the size based on a predetermined block size and a count value associated with each of the ordered pair of snapshots. 18. The apparatus of claim 15 , further com
Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446) · CPC title
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16) · CPC title
File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06) · CPC title
characterised by the use of retention policies (retention policies for HSM systems G06F16/185) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.