Database recovery after system copy

US9740576B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9740576-B2
Application numberUS-201414553400-A
CountryUS
Kind codeB2
Filing dateNov 25, 2014
Priority dateNov 25, 2014
Publication dateAug 22, 2017
Grant dateAug 22, 2017

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.

A system includes reception, at a target database system, of a request to recover a backup created by a source database system into the target database system, where the request comprises a system identifier of the source database system, determination of a backup tool configuration file associated with the source database system based on the system identifier of the source database system, request of a recovery of the backup into the target database system using the backup tool configuration file, copying of a backup catalog of the source database system into a storage location associated with the target database system, and appending of a system change marker to the copied backup catalog, wherein the system change marker comprises the system identifier of the source database system.

First claim

Opening claim text (preview).

What is claimed is: 1. A computing system comprising: a memory storing processor-executable program code; and a processor to execute the processor-executable program code in order to cause the computing system to: receive, at a target database system, a request to recover a backup created by a source database system into the target database system, where the request comprises a system identifier of the source database system, and determine a backup tool configuration file associated with the source database system based on the system identifier of the source database system; request a recovery of the backup into the target database system using the backup tool configuration file; copy a backup catalog of the source database system into a storage location associated with the target database system; append a system change marker to the copied backup catalog; operate the target database system to create one or more log backups; receive a command to recover the target database system based on one of the one or more log backups; initialize a token with a value of a system identifier of the target database system; identify a record of the backup catalog associated with the one of the log backups; associate the record with the value of the token; determine whether an earlier record of the backup catalog includes a system change marker; and if the earlier record of the backup catalog includes a system change marker, replace the value of the token with a value of a system identifier specified by the system change marker, and if the earlier record of the backup catalog does not include a system change marker, associate the earlier record with the value of the token, wherein the system change marker comprises the system identifier of the source database system. 2. A computing system according to claim 1 , wherein if the earlier record of the backup catalog includes a system change marker, the processor is further to execute the processor-executable program code in order to cause the computing system to: identify a second earlier record of the backup catalog; and associate the second earlier record with the replaced value of the token. 3. A computing system according to claim 2 , wherein the second earlier record is associated with a data backup, and wherein the processor is further to execute the processor-executable program code in order to cause the computing system to: recover the data backup into the target database system using the replaced value of the token; and replay the backup associated with the earlier record using the token value associated with the earlier record. 4. A computing system according to claim 2 , wherein the second earlier record is associated with a log backup, and wherein the processor is further to execute the processor-executable program code in order to cause the computing system to: identify a third earlier record of the backup catalog associated with a data backup; associate the third earlier record with the replaced value of the token; recover the data backup into the target database system using the replaced value of the token; replay the log backup associated with the second earlier record using the replaced value of the token; and replay the backup associated with the earlier record using the token value associated with the earlier record. 5. A non-transitory computer-readable medium storing program code, the program code executable by a processor of a computing system to cause the computing system to: receive, at a target database system, a request to recover a backup created by a source database system into the target database system, where the request comprises a system identifier of the source database system, and determine a backup tool configuration file associated with the source database system based on the system identifier of the source database system; request a recovery of the backup into the target database system using the backup tool configuration file; copy a backup catalog of the source database system into a storage location associated with the target database system; append a system change marker to the copied backup catalog; operate the target database system to create one or more log backups; receive a command to recover the target database system based on one of the one or more log backups; initialize a token with a value of a system identifier of the target database system; identify a record of the backup catalog associated with the one of the log backups; associate the record with the value of the token; determine whether an earlier record of the backup catalog includes a system change marker; and if the earlier record of the backup catalog includes a system change marker, replace the value of the token with a value of a system identifier specified by the system change marker, and if the earlier record of the backup catalog does not include a system change marker, associate the earlier record with the value of the token, wherein the system change marker comprises the system identifier of the source database system and wherein if the earlier record of the backup catalog includes a system change marker, the program code is further executable by a processor of a computing system to cause the computing system to identify a second earlier record of the backup catalog and associate the second earlier record with the replaced value of the token. 6. A non-transitory computer-readable medium according to claim 5 , wherein the second earlier record is associated with a data backup, and wherein the program code is further executable by a processor of a computing system to cause the computing system to: recover the data backup into the target database system using the replaced value of the token; and replay the backup associated with the earlier record using the token value associated with the earlier record. 7. A non-transitory computer-readable medium according to claim 5 , wherein the second earlier record is associated with a log backup, and wherein the program code is further executable by a processor of a computing system to cause the computing system to: identify a third earlier record of the backup catalog associated with a data backup; associate the third earlier record with the replaced value of the token; recover the data backup into the target database system using the replaced value of the token; replay the log backup associated with the second earlier record using the replaced value of the token; and replay the backup associated with the earlier record using the token value associated with the earlier record. 8. A computer-implemented method comprising: receiving, at a target database system, a request to recover a backup created by a source database system into the target database system, where the request comprises a system identifier of the source database system, and determining a backup tool configuration file associated with the source database system based on the system identifier of the source database system; requesting a recovery of the backup into the target database system using the backup tool configuration file; copying a backup catalog of the source database system into a storage location associated with the target database system; appending a system change marker to the copied backup catalog; operating the target database system to create one or more log backups; receiving a command to recover the target database system based on one of the one or more log backups; initializing a token with a value of a system identifier of the target database system; identifying a record of the backup catalog associated with the one of the log backups; associating the record with the value of the token; determining whether an

Assignees

Inventors

Classifications

  • Database-specific techniques · CPC title

  • by selection of backup contents · CPC title

  • Backup restoration techniques · 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 US9740576B2 cover?
A system includes reception, at a target database system, of a request to recover a backup created by a source database system into the target database system, where the request comprises a system identifier of the source database system, determination of a backup tool configuration file associated with the source database system based on the system identifier of the source database system, req…
Who is the assignee on this patent?
Schefe Andre, Vorsprach Bernd, Hempelmann Henrik, and 4 more
What technology area does this patent fall under?
Primary CPC classification G06F11/1469. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Aug 22 2017 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 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).