Database management system backup and recovery management

US11537476B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11537476-B2
Application numberUS-202016829531-A
CountryUS
Kind codeB2
Filing dateMar 25, 2020
Priority dateMar 25, 2020
Publication dateDec 27, 2022
Grant dateDec 27, 2022

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

According to some embodiments, a system to manage database management system backups may include a plurality of database services. For each database service, a database backup resource (e.g., a human-readable structured document) may specify desired backup state information (e.g., a buffer size, a schedule, an amount of memory, etc.). A stateless backup operator component may then compare a present backup state of each database service with the associated desired backup state information. When a mismatch is identified between the present backup state of a database service and the associated desired backup state information, that database service may be automatically reconfigured (e.g., in connection with a recover job, backup job, backup configuration job, keystore backup job, etc.) in accordance with the desired backup state information.

First claim

Opening claim text (preview).

The invention claimed is: 1. A system to manage database management system backups, comprising: a plurality of database services; for each database service, a database backup resource that specifies desired backup state information associated with a recovery point objective and recovery time objective of a database service level agreement, wherein the desired backup state information includes backup and recovery operations along with data associated with a keystore backup job that provides database backup privacy and security; and a stateless backup operator component, including: a computer processor, and a computer memory coupled to the computer processor and storing instructions that, when executed by the computer processor, cause the stateless backup operator component to compare a present backup state of each database service with the associated desired backup state information, wherein when a mismatch is identified between the present backup state of a database service and the associated desired backup state information, that database service is automatically reconfigured in accordance with the desired backup state information. 2. The system of claim 1 , wherein the backup resource comprises a human-readable structured document. 3. The system of claim 1 , wherein the desired backup state information includes configuration information. 4. The system of claim 1 , wherein the desired backup state information includes database key information. 5. The system of claim 1 , wherein the stateless backup operator component periodically performs said comparison in regular intervals. 6. The system of claim 1 , wherein the stateless backup operator component is scaled up responsive to a load increase. 7. The system of claim 1 , wherein the stateless backup operator component is restarted responsive to a failure without impacting an availability of an associated database service. 8. The system of claim 1 , further comprising: a database services provider to create at least one database backup resource in response to a request received from a user. 9. The system of claim 1 , wherein the plurality of databases is associated with a hyper-scalar environment. 10. A computer-implemented method to manage database management system backups, comprising: for each of a plurality of database services, specifying a database backup resource that indicates desired backup state information associated with a recovery point objective and recovery time objective of a database service level agreement, wherein the desired backup state information includes backup and recovery operations along with data associated with a keystore backup job that provides database backup privacy and security; comparing, by a stateless backup operator component, a present backup state of each database service with the associated desired backup state information; and when a mismatch is identified between the present backup state of a database service and the associated desired backup state information, automatically reconfiguring that database service in accordance with the desired backup state information. 11. The method of claim 10 , wherein the backup resource comprises a human-readable structured document. 12. The method of claim 10 , wherein the desired backup state information includes database key information. 13. A non-transient, computer-readable medium storing instructions to be executed by a processor to perform a method to manage database management system backups, the method comprising: for each of a plurality of database services, specifying a database backup resource indicating desired backup state information associated with a recovery point objective and recovery time objective of a database service level agreement, wherein the desired backup state information includes backup and recovery operations along with data associated with a keystore backup job that provides database backup privacy and security; comparing, by a stateless backup operator component, a present backup state of each database service with the associated desired backup state information; and when a mismatch is identified between the present backup state of a database service and the associated desired backup state information, automatically reconfiguring that database service in accordance with the desired backup state information. 14. The medium of claim 13 , wherein the stateless backup operator component periodically performs said comparison in regular intervals. 15. The medium of claim 13 , wherein the stateless backup operator component is scaled up responsive to a load increase. 16. The medium of claim 13 , wherein the stateless backup operator component is restarted responsive to a failure without impacting an availability of an associated database service.

Assignees

Inventors

Classifications

  • Management of the data involved in backup or backup restore · CPC title

  • Backup restoration techniques · CPC title

  • Database-specific techniques · CPC title

  • Restarting or rejuvenating · CPC title

  • Ensuring data consistency and integrity · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11537476B2 cover?
According to some embodiments, a system to manage database management system backups may include a plurality of database services. For each database service, a database backup resource (e.g., a human-readable structured document) may specify desired backup state information (e.g., a buffer size, a schedule, an amount of memory, etc.). A stateless backup operator component may then compare a pre…
Who is the assignee on this patent?
Sap Se
What technology area does this patent fall under?
Primary CPC classification G06F11/1448. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Dec 27 2022 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).