Unified snapshot storage management, using an enhanced storage manager and enhanced media agents
US-2016142483-A1 · May 19, 2016 · US
US10303550B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10303550-B2 |
| Application number | US-201815868854-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 11, 2018 |
| Priority date | Apr 21, 2015 |
| Publication date | May 28, 2019 |
| Grant date | May 28, 2019 |
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.
The illustrative storage management system uses snapshot technologies and performs block-level analysis thereof and to synthesize full backups of a database, regardless of the database management system (DBMS) and content of the database and without involving native DBMS utilities. Synthetic full copies are created efficiently and use network transport resources sparingly. Successive snapshots of the database may be hardware snapshots and/or software snapshots. The illustrative storage management system tracks which data blocks in the database change over time after a baseline full copy is saved to secondary storage. Only the changed blocks are subsequently moved to secondary storage as incremental backups and are indexed for future reference. A synthetic full backup of the database, at a given point in time, may be created by synthesizing the original full backup with changed blocks from any number of later incremental backups. The synthetic full backup comprises pointers to appropriate data blocks, ignoring intermediate changes, and pointing to the most current data block in secondary storage relative to the given point in time chosen for the synthetic full backup. The illustrative storage management system may restore the synthetic full backup without native DBMS utilities.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer-readable medium storing instructions that, when executed by a computing device, which comprises one or more processors and computer memory, cause the computing device to perform operations comprising: storing a copy of a first snapshot of a database to a storage device, wherein a database management system (DBMS) performs operations that change data in the database; after the first snapshot, generating a plurality of successive snapshots of the database, wherein for a given successive snapshot: (i) receiving identifiers of changed data blocks within the given successive snapshot that changed in the database relative to corresponding data blocks in an immediately preceding snapshot of the database, wherein the changed data blocks are identified by a filter that is independent of data block content, (ii) extracting the changed data blocks from the given successive snapshot based on the received identifiers, (iii) storing to the storage device a corresponding incremental backup of the database, based on the given successive snapshot and comprising the changed data blocks extracted from the given successive snapshot of the database, and (iv) indexing the changed data blocks that are in the corresponding incremental backup; based on the indexing, generating a synthetic full block-level backup of the database represented at a given point in time, by consolidating the copy of the first snapshot of the database with data blocks that are most current relative to the given point in time, based on pointers to data blocks that are most current relative to the given point in time, including pointers to changed data blocks, and skipping over intermediate changed data blocks that are not most current relative to the given point in time, as found in: (a) the copy of the first snapshot of the database, and (b) one or more of the incremental backups of the database based on corresponding successive snapshots; storing the synthetic full block-level backup of the database to the storage device; and restoring the database from the synthetic full block-level backup in the storage device without using a native restore feature of the database management system, wherein the restoring is independent of database content. 2. The non-transitory computer-readable medium of claim 1 wherein the copy of the first snapshot comprises all data blocks in the first snapshot. 3. The non-transitory computer-readable medium of claim 1 wherein the restored database comprises all data blocks of the database at the time a most recent snapshot was generated in the plurality of successive snapshots. 4. The non-transitory computer-readable medium of claim 1 wherein a media agent that executes on the computing device performs the operations comprising: the storing of the copy of the first snapshot, the receiving, the extracting, the storing of the corresponding incremental backup, the generating of the synthetic full block-level backup, and the storing of the synthetic full block-level backup. 5. The non-transitory computer-readable medium of claim 1 wherein the synthetic full block-level backup is independent of the database management system. 6. A method for generating a full block-level backup copy of a database in a data storage management system, the method comprising: storing a copy of a first snapshot of the database to a storage device, wherein a database management system (DBMS) performs operations that change data in the database, and wherein the storing operation is performed by a media agent component of the data storage management system, which executes on a first computing device comprising one or more processors and computer memory; after the first snapshot, generating a plurality of successive snapshots of the database, wherein for a given successive snapshot: (i) receiving, by the media agent, identifiers of changed data blocks within the given successive snapshot that changed in the database relative to corresponding data blocks in an immediately preceding snapshot of the database, wherein the changed data blocks are identified by a filter that is independent of data block content, (ii) extracting, by the media agent, the changed data blocks from the given successive snapshot based on the received identifiers, and (iii) storing, by the media agent to the storage device, a corresponding incremental backup of the database, based on the given successive snapshot and comprising the changed data blocks extracted from the given successive snapshot of the database, and (iv) indexing, by the media agent, the changed data blocks that are in the corresponding incremental backup; based on the indexing, generating, by the media agent, a synthetic full block-level backup of the database represented at a given point in time, by consolidating the copy of the first snapshot of the database with data blocks that are most current relative to the given point in time, based on pointers to data blocks that are most current relative to the given point in time, including pointers to changed data blocks, and skipping over intermediate changed data blocks that are not most current relative to the given point in time, as found in: (a) the copy of the first snapshot of the database, and (b) one or more of the incremental backups based on corresponding successive snapshots; storing, by the media agent, the synthetic full block-level backup of the database to the storage device; and restoring the database from the synthetic full block-level backup in the storage device without using a native restore feature of the database management system, wherein the restoring is independent of database content. 7. The method of claim 6 wherein the synthetic full block-level backup is independent of database content. 8. The method of claim 6 wherein the synthetic full block-level backup is independent of the database management system. 9. The method of claim 6 wherein the plurality of successive snapshots of the database are generated by a storage device that also stores the database. 10. The method of claim 6 wherein the plurality of successive snapshots of the database are generated by a computing device that hosts the database management system. 11. The method of claim 6 wherein the restored database comprises all data blocks of the database at the time a most recent snapshot was generated in the plurality of successive snapshots. 12. The method of claim 6 further comprising: monitoring, by a data agent component of the data storage management system, write operations performed by the database management system that change data in the database; and identifying, by the filter within the data agent, changed data blocks which changed in the database relative to corresponding data blocks in an immediately preceding snapshot of the database, wherein identifiers of the changed data blocks are received by the media agent from the data agent. 13. The method of claim 6 wherein the media agent receives the identifiers of the changed data blocks which changed in the database relative to corresponding data blocks in an immediately preceding snapshot of the database from a data agent that monitors write operations performed by the database management system that result in the changed data blocks. 14. A data storage management system comprising: a first computing device that executes a database management system (DBMS), which operates upon a database, wherein the first computing device comprises one or more processors and computer memory; a first storage device in communication with the first computing device, wherein the storage devic
Database-specific techniques · CPC title
using file system or storage system metadata · CPC title
by selection of backup contents · CPC title
Error detection; Error correction; Monitoring (error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00) · CPC title
Backup restoration techniques · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.