Systems and methods for backing-up an eventually-consistent database in a production cluster
US-2019294509-A1 · Sep 26, 2019 · US
US10817387B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10817387-B2 |
| Application number | US-201816116694-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 29, 2018 |
| Priority date | Aug 29, 2018 |
| Publication date | Oct 27, 2020 |
| Grant date | Oct 27, 2020 |
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.
Input information comprising an identifier of a production instance is received. The input information indicating a given time a live database from the production instance is to be restored to in a temporary copy of the production instance. Based at least on the input information, backup data associated with the live database from production instance is identified. Based on the backup data, it is determined whether resource capacity is available for restoring the backup data to the temporary copy of the production instance. In response to determining the resource capacity is available, the temporary copy of the production instance is generated. The backup data is restored to the temporary copy of the production instance to represent a state of the live database from the production instance at the given time.
Opening claim text (preview).
What is claimed is: 1. A computer system comprising: memory; and one or more hardware processors coupled to the memory, wherein the memory comprises computer instructions that, when executed by the one or more hardware processors, cause the computer system to: receive input information comprising an identifier of a production instance, the input information indicating a given time a live database from the production instance is to be restored to in a temporary copy of the production instance; identify, based at least on the input information, backup data associated with the live database from production instance; determine, based on the backup data, whether resource capacity is available for restoring the backup data to the temporary copy of the production instance; in response to determining the resource capacity is available based on a first resource capacity check, generate the temporary copy of the production instance and restore the backup data to the temporary copy of the production instance to represent a state of the live database from the production instance at the given time; in response to determining the resource capacity is not available based on the first resource capacity check, generate the temporary copy of the production instance and perform a second resource capacity check; and in response to determining the resource capacity is available based on the second resource capacity check, restore the backup data to the temporary copy of the production instance to represent the state of the live database from the production instance at the given time. 2. The computer system according to claim 1 , wherein the memory comprises computer instructions that, when executed by the one or more hardware processors, cause the computer system to provide a hosted client instance operating as the production instance over a network interface for communicatively coupling with a remote client device. 3. The computer system according to claim 2 , wherein the input information comprising the identifier of the production instance is received responsive to an incident created by a user of the remote client device to perform a predetermined operation. 4. The computer system according to claim 3 , wherein the predetermined operation includes one or more of: (i) a debug operation for debugging one or more of the temporary copy of the production instance and the backup data restored to the temporary copy of the production instance; (ii) a data recovery operation for recovering lost data for the production instance based on the backup data restored to the temporary copy of the production instance; (iii) a scripting operation for running a predetermined script on the backup data restored to the temporary copy of the production instance before running the script on the production instance; and (iv) a software update operation for applying a software update to the temporary copy of the production instance before applying the software update to the production instance. 5. The computer system according to claim 1 , wherein the computer instructions that, when executed by the one or more hardware processors, cause the computer system to identify the backup data associated with the live database from the production instance comprise computer instructions that, when executed by the one or more hardware processors, cause the computer system to: identify, from among a plurality of backup files associated with the live database from the production instance, a backup file that corresponds to the given time; and identify, from among a plurality of bin log files associated with the live database from the production instance, a bin log file corresponding to a temporal window that includes the given time. 6. The computer system according to claim 5 , wherein the computer instructions that, when executed by the one or more hardware processors, cause the computer system to restore the backup data to the temporary copy of the production instance comprise computer instructions that, when executed by the one or more hardware processors, cause the computer system to: restore the backup file to the temporary copy of the production instance; and roll forward, from among a plurality of transactions listed in the identified bin log file, one or more transactions onto the restored backup file up to a specific transaction sequence number corresponding to the given time. 7. The computer system according to claim 1 , wherein the backup data includes at least one of a backup file and a bin log file, and wherein the computer instructions that, when executed by the one or more hardware processors, cause the computer system to determine whether the resource capacity is available comprise computer instructions that, when executed by the one or more hardware processors, cause the computer system to determine whether the resource capacity is available based on a file size of the at least one of the backup file and the bin log file. 8. The computer system according to claim 1 , wherein the memory comprises computer instructions that, when executed by the one or more hardware processors, cause the computer system to automatically retire the temporary copy of the production instance after a predetermined period of time has elapsed. 9. A method comprising: receiving input information comprising an identifier of a production instance, the input information indicating a given time a live database from the production instance is to be restored to in a temporary copy of the production instance; identifying, based at least on the input information, backup data associated with the live database from production instance; determining, based on the backup data, whether resource capacity is available for restoring the backup data to the temporary copy of the production instance; in response to determining the resource capacity is available based on a first resource capacity check, generating the temporary copy of the production instance and restoring the backup data to the temporary copy of the production instance to represent a state of the live database from the production instance at the given time; in response to determining the resource capacity is not available based on the first resource capacity check, generating the temporary copy of the production instance and perform a second resource capacity check; and in response to determining the resource capacity is available based on the second resource capacity check, restoring the backup data to the temporary copy of the production instance to represent the state of the live database from the production instance at the given time. 10. The method according to claim 9 , comprising providing a hosted client instance operating as the production instance over a network interface for communicatively coupling with a remote client device. 11. The method according to claim 10 , wherein the input information comprising the identifier of the production instance is received responsive to an incident created by a user of the remote client device to perform a predetermined operation. 12. The method according to claim 11 , wherein the predetermined operation includes one or more of: (i) a debug operation for debugging one or more of the temporary copy of the production instance and the backup data restored to the temporary copy of the production instance; (ii) a data recovery operation for recovering lost data for the production instance based on the backup data restored to the temporary copy of the production instance; (iii) a scripting operation for running a predetermined script on the backup data restored to the temporary copy of the production instance before running the script on the pro
Backup restoration techniques · CPC title
Ensuring data consistency and integrity · CPC title
with a single idle spare processing component · CPC title
Timestamp · CPC title
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.