Non-blocking backup in a log replay node for tertiary initialization

US11226876B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11226876-B2
Application numberUS-201816014206-A
CountryUS
Kind codeB2
Filing dateJun 21, 2018
Priority dateJun 21, 2018
Publication dateJan 18, 2022
Grant dateJan 18, 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.

Disclosed herein are system, method, and computer program product embodiments for non-blocking backup for tertiary initialization in a log replay only node. An embodiment operates by performing a standard log replay on a secondary server and briefly suspending the standard log replay in response to tertiary initialization. Further, the secondary server may determine backup block information and perform a page-aligned backup process from the secondary server to a tertiary server. Additionally, the secondary server may determine log replay block information, and perform a modified log replay concurrently with the backup process based on the backup block information.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for initializing a tertiary server within a three-tiered replication system, comprising: receiving log information associated with a primary server, the log information corresponding to first database operations performed at the primary server; performing, by the secondary server, a standard log replay over the log information; temporarily suspending the standard log replay at a position of the log information; determining backup block information, the backup block information including backup block identifiers identifying one or more backup blocks of the secondary server to be backed up during a page-aligned backup process and a status of the backup process; performing the page-aligned backup process from the secondary server to the tertiary server, the page-aligned backup process associated with second database operations performed prior to the position; and performing, by the secondary server, a modified log replay based on the backup block information and the log information. 2. The method of claim 1 , wherein suspending the standard log replay at the position of the log information, comprises suspending the standard log replay at a recovery checkpoint of the log information. 3. The method of claim 1 , wherein performing the modified log replay based on the backup block information and the log information, comprises: determining replay block identifiers identifying one or more replay blocks to be modified by third database operations performed after the position; and determining, based on the backup information, that none of the backup block identifiers are the same as the replay block identifiers; and replaying the log information. 4. The method of claim 1 , wherein performing the modified log replay based on the backup block information and the log information, comprises: determining that the backup process is complete based on the backup block information; and replaying the log information. 5. The method of claim 1 , wherein the backup block identifiers are initial backup block identifiers, and performing the modified log replay based on the backup block information and the log information, comprises: determining initial replay block identifiers identifying one or more replay blocks to be modified by third database operations performed after the position; and determining modified replay block identifiers corresponding to the initial replay block identifiers having a matching backup block identifier of the backup block identifiers; determining a first page including a first block of the modified replay block identifiers; determining a second page including a last block of the modified replay block identifiers; determining a range of the one or more replay blocks spanning from the first page to the second page; determining log replay backup blocks of the one or more backup blocks, the log replay backup blocks corresponding to the range; and determining modified backup block identifiers by removing the initial backup block identifiers corresponding to the log replay backup blocks. 6. The method of claim 5 , wherein performing the page-aligned backup process from the secondary server to the tertiary server, comprises: performing the page-aligned backup process based on the modified backup block identifiers. 7. The method of claim 1 , wherein the one or more backup blocks are encrypted backup blocks, and performing the page-aligned backup process from the secondary server to the tertiary server, comprises: determining clear text backup blocks based on decrypting the encrypted backup blocks; and backing up the clear text backup blocks to the tertiary server. 8. The method of claim 1 , wherein the primary server includes at least one of an in-memory row store or an in-memory column store database. 9. The method of claim 1 , wherein the secondary server includes a log replay only server that does not include at least one of a transaction manager, checkpoint capabilities, or a backup manager. 10. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising: receiving log information associated with a primary server, the log information corresponding to first database operations performed at the primary server; performing, by the secondary server, a standard log replay over the log information; temporarily suspending the standard log replay at a position of the log information; determining backup block information, the backup block information including backup block identifiers identifying one or more backup blocks of the secondary server to be backed up during a page-aligned backup process and a status of the backup process; performing the page-aligned backup process from the secondary server to a tertiary server, the page-aligned backup process associated with second database operations performed prior to the position; and performing a modified log replay based on the backup block information and the log information. 11. The non-transitory computer-readable device of claim 10 , wherein the one or more backup blocks are encrypted backup blocks, and performing the page-aligned backup process from the secondary server to the tertiary server, comprises: determining clear text backup blocks based on decrypting the encrypted backup blocks; and backing up the clear text backup blocks to the tertiary server. 12. The non-transitory computer-readable device of claim 10 , wherein suspending the standard log replay at the position of the log information, comprises suspending the standard log replay at a recovery checkpoint of the log information. 13. The non-transitory computer-readable device of claim 10 , wherein the backup block identifiers are initial backup block identifiers, and performing the modified log replay based on the backup block information and the log information, comprises: determining initial replay block identifiers identifying one or more replay blocks to be modified by third database operations performed after the position; and determining modified replay block identifiers corresponding to the initial replay block identifiers having a matching backup block identifier of the backup block identifiers; determining a first page including a first block of the modified replay block identifiers; determining a second page including a last block of the modified replay block identifiers; determining a range of the one or more replay blocks spanning from the first page to the second page; determining log replay backup blocks of the one or more backup blocks, the log replay backup blocks corresponding to the range; and determining modified backup block identifiers by removing the initial backup block identifiers corresponding to the log replay backup blocks. 14. The non-transitory computer-readable device of claim 13 , wherein performing the page-aligned backup process from the secondary server to the tertiary server, comprises: performing the page-aligned backup process based on the modified backup block identifiers. 15. The non-transitory computer-readable device of claim 10 , wherein the secondary server includes a log replay only server that does not include at least one of a transaction manager, checkpoint capabilities, or a backup manager. 16. A secondary server system, comprising: a memory; and at least one processor coupled to the memory and configured to: receive log information associated with a primary server, the log information corresponding to first databas

Assignees

Inventors

Classifications

  • Backup restoration techniques · CPC title

  • for networked environments · CPC title

  • Database-specific techniques · CPC title

  • Monitoring of transactions · CPC title

  • eliminating a faulty processor or activating a spare · 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 US11226876B2 cover?
Disclosed herein are system, method, and computer program product embodiments for non-blocking backup for tertiary initialization in a log replay only node. An embodiment operates by performing a standard log replay on a secondary server and briefly suspending the standard log replay in response to tertiary initialization. Further, the secondary server may determine backup block information and…
Who is the assignee on this patent?
Sap Se
What technology area does this patent fall under?
Primary CPC classification G06F11/2028. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jan 18 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 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).