Systems and methods for retaining and using data block signatures in data protection operations
US-9239687-B2 · Jan 19, 2016 · US
US12450129B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12450129-B2 |
| Application number | US-202418744769-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 17, 2024 |
| Priority date | Jun 17, 2022 |
| Publication date | Oct 21, 2025 |
| Grant date | Oct 21, 2025 |
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 disclosed framework enables virtually any aggressive Recovery Point Objective (RPO) to be enforced for a production database, without limitation on type of database management system (DBMS) or size of the production database. The framework overcomes technological barriers of the prior art, such as bottlenecks presented by a storage manager computer that traditionally managed database backups. To avoid the bottlenecks, an illustrative data storage management system does not engage the storage manager computer in storage operations that could impact the database RPO. Certain components are added and enhanced to autonomously capture database transaction logs, which are stored securely and persistently away from the DBMS. In a separate and less frequent operation, and with involvement of the storage manager computer, the illustrative system generates secondary copies in their final form. Meanwhile, temporary backup files can be used in restore operations without first being converted into secondary copies.
Opening claim text (preview).
What is claimed is: 1. A system comprising: a first computing device comprising one or more first hardware processors, wherein the first computing device is in communication with a second computing device comprising one or more second hardware processors; and wherein the second computing device is configured to: host a database management system that comprises a first database, convert a first set of transaction logs generated by the database management system into a first set of temporary backup files, wherein the first set of temporary backup files are in a backup format that that is distinct from a data format that is native to the database management system, and based on a time interval of a recovery point objective (RPO) that is associated with the first database, transmit the first set of temporary backup files to the first computing device; and wherein the first computing device is configured to: store the first set of temporary backup files at a first data storage, based on a second time interval that is greater than the time interval of the RPO, make a determination that the first data storage comprises at least one temporary backup file received from the second computing device, and based on the determination: (i) convert the at least one temporary backup file into one or more secondary copies, (ii) store the one or more secondary copies at a secondary storage that is distinct from the first data storage, and (iii) index the one or more secondary copies in an index. 2. The system of claim 1 , wherein the system further comprises a third computing device comprising one or more third hardware processors, which is configured to: host a storage manager, receive, from the first computing device, information about a data storage job performed by the first computing device, wherein the data storage job comprises the (i) convert operation, the (ii) store operation at the secondary storage, and the (iii) index operation, which are performed by the first computing device, and store the information about the data storage job at a management database maintained by the storage manager, wherein the management database is distinct from the first database. 3. The system of claim 2 , wherein the storage manager is further configured to: receive a request to restore data to the first database, initiate a restore job at the first computing device, wherein the restore job is based on a second set of temporary backup files that comprise the data to be restored to the first database; wherein the first computing device is further configured to transmit the second set of temporary backup files to the second computing device; and wherein the second computing device is further configured to convert the second set of temporary backup files into a second set of transaction logs, wherein the second set of transaction logs are in the data format that is native to the database management system. 4. The system of claim 1 , wherein a first data agent hosted by the second computing device is configured to convert the first set of transaction logs generated by the database management system into the first set of temporary backup files, and to transmit the first set of temporary backup files to the first computing device. 5. The system of claim 4 , wherein the first data agent hosted by the second computing device is configured to communicate with the first computing device via a persistent data pipeline connection. 6. The system of claim 4 , wherein the first data agent is configured to: receive the RPO from a storage manager that is hosted by a third computing device, and subsequently, based on the RPO, to transmit the first set of temporary backup files to the first computing device without receiving instructions to do so from the storage manager. 7. The system of claim 1 , wherein the first computing device is further configured to, based on the second time interval, initiate a data storage job that comprises the (i) convert operation, the (ii) store operation at the secondary storage, and the (iii) index operation. 8. The system of claim 1 , wherein the first computing device is further configured to determine, based on the second time interval, that the first computing device should initiate a data storage job that comprises the (i) convert operation, the (ii) store operation at the secondary storage, and the (iii) index operation. 9. The system of claim 8 , wherein to initiate the data storage job, the first computing device is further configured to request a job identifier from a storage manager that is hosted by a third computing device. 10. The system of claim 1 , wherein the first data storage comprises one or more of a data storage volume and a folder configured at the first computing device, and wherein a second data agent, which is hosted by the first computing device, is associated with a file system that comprises the one or more of the data storage volume and the folder. 11. A system comprising: a first computing device comprising one or more hardware processors, wherein the first computing device is communicatively coupled to a second computing device that executes a database management system that comprises a first database; a third computing device comprising one or more hardware processors, wherein the third computing device executes a storage manager; and wherein the system is configured with a recovery point objective (RPO) for the first database; wherein the second computing device is configured to: convert a first set of transaction logs generated by the database management system into a first set of temporary backup files, wherein the first set of temporary backup files are in a backup format that is distinct from a data format that is native to the database management system, and based on a time frequency of the RPO, transmit the first set of temporary backup files to the first computing device; wherein the first computing device is configured to: store the first set of temporary backup files at a first data storage, and based on a second time frequency that is greater than the time frequency of the RPO, determine whether the first data storage comprises any temporary backup files, and based on determining that the first data storage comprises at least one temporary backup file, perform a data storage job that: converts the at least one temporary backup file into one or more secondary copies, stores the one or more secondary copies at a secondary storage, which is distinct from the first data storage, and reports information about the data storage job to the storage manager at the third computing device; and wherein the third computing device executing the storage manager is configured to: before the data storage job, transmit to the first computing device, one or more of: the RPO and the second time frequency. 12. The system of claim 11 , wherein the second computing device is configured to, without receiving instructions from the storage manager: generate the first set of temporary backup files, and, based on the time frequency of the RPO, transmit the first set of temporary backup files to the first computing device. 13. The system of claim 11 , wherein a first data agent executing at the second computing device is configured to, without receiving instructions from the storage manager: determine, based on the time frequency of the RPO, that the first data agent should transmit the first set of temporary backup files to the first computing device. 14. The system of claim 11 , wherein the first computing device is further configured to: without receiving instructions from the storage
Backup restoration techniques · CPC title
by selection of backup contents · CPC title
Database-specific techniques · CPC title
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
Timestamp · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.