Method and system for retrieving backup parameters for recovery

US10534760B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-10534760-B1
Application numberUS-201313905746-A
CountryUS
Kind codeB1
Filing dateMay 30, 2013
Priority dateMay 30, 2013
Publication dateJan 14, 2020
Grant dateJan 14, 2020

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.

Retrieving backup parameters for recovery is described. A clone copy is created of a backup file stored on a disk. The clone copy is stored on an external destination node including an external disk and/or a tape. Backup parameters are stored to a backup catalog. The backup parameters identify a location of the clone copy. A request is received to recover the clone copy. The backup parameters are retrieved from the backup catalog. The clone copy is recovered from the external destination node based on the backup parameters. The clone copy is restored to a database associated with the backup file.

First claim

Opening claim text (preview).

What is claimed is: 1. A system for retrieving backup parameters for recovery, the system comprising: a processor-based third-party backup application executed on a first server and configured to: create, by the third-party backup application executed on the first server, a clone copy of a backup file stored on a disk associated with a second server, the backup file being a copy of a database state of a database, the backup file being created by a backup tool that is native to a third server of a database management system; store, by the third-party backup application, the clone copy on an external destination node comprising at least one of an external disk and a tape associated with the first server; store, by the third-party backup application, a primary copy of backup parameters to a backup catalog stored on the second server and a secondary copy of the backup parameters on the first server, wherein the backup parameters identify a location of the clone copy, the backup catalog only being associated with the database; receive, by the third-party backup application, a request from the backup tool that is native to the third server of the database management system to recover the clone copy from the external destination node, the backup tool requesting the clone copy of the backup file after determining the backup file stored on the server is corrupt or absent; retrieve, by the third-party backup application, in response to receiving the request from the backup tool, the primary copy of the backup parameters from the backup catalog stored on the second server; recover, by the third-party backup application, the clone copy from the external destination node based on the backup parameters; and provide, by the third-party backup application, the clone copy to the backup tool, the backup tool restoring the clone copy of the backup file to a corrupted database associated with the backup file. 2. The system of claim 1 , wherein the processor-based third-party backup application is further configured to store the secondary copy of the backup parameters to a standard directory location on the first server. 3. The system of claim 2 , wherein the processor-based third-party backup application is further configured to: determine whether the primary copy of the backup parameters are absent from the backup catalog; and retrieve the secondary copy of the backup parameters from the standard directory location on the first server in response to a determination that the backup parameters are absent from the backup catalog. 4. The system of claim 3 , wherein retrieving the secondary copy of the backup parameters from the standard directory location comprises using backup parameters that are most recently stored in the standard directory location and untried at recovering the clone copy to recover the clone copy from the external destination node. 5. The system of claim 1 , wherein the processor-based third-party backup application is further configured to: determine whether the clone copy is moved from the location to an alternative location; and store a primary copy of the updated backup parameters to the backup catalog in response to a determination that the clone copy is moved from the location to an alternative location. 6. The system of claim 5 , wherein the processor-based third-party backup application is further configured to store a secondary copy of the updated backup parameters to a standard directory location. 7. The system of claim 1 , wherein providing, by the third-party backup application, the clone copy to the backup tool comprises using automatic channel settings to restore the clone copy to the database associated with the backup file; and wherein the backup parameters further identify a location of the database associated with the backup copy. 8. A computer-implemented method for retrieving backup parameters for recovery, the method comprising: creating, by the third-party backup application executed on the first server, a clone copy of a backup file stored on a disk associated with a second server, the backup file being a copy of a database state of a database, the backup file being created by a backup tool that is native to a third server of a database management system; storing, by the third-party backup application, the clone copy on an external destination node comprising at least one of an external disk and a tape associated with the first server; storing, by the third-party backup application, a primary copy of backup parameters to a backup catalog stored on the second server and a secondary copy of the backup parameters on the first server, wherein the backup parameters identify a location of the clone copy, the backup catalog only being associated with the database; receiving, by the third-party backup application, a request from the backup tool that is native to the third server of the database management system to recover the clone copy from the external destination node, the backup tool requesting the clone copy of the backup file after determining the backup file stored on the server is corrupt or absent; retrieving, by the third-party backup application, in response to receiving the request from the backup tool, the primary copy of the backup parameters from the backup catalog stored on the second server; recovering, by the third-party backup application, the clone copy from the external destination node based on the backup parameters; and providing, by the third-party backup application, the clone copy to the backup tool, the backup tool restoring the clone copy of the backup file to a corrupted database associated with the backup file. 9. The method of claim 8 , wherein the method further comprises storing the secondary copy of the backup parameters to a standard directory location on the first server. 10. The method of claim 9 , wherein the method further comprises: determining whether the primary copy of the backup parameters are absent from the backup catalog; and retrieving the secondary copy of the backup parameters from the standard directory location on the first server in response to a determination that the backup parameters are absent from the backup catalog. 11. The method of claim 10 , wherein retrieving the secondary copy of the backup parameters from the standard directory location comprises using backup parameters that are most recently stored in the standard directory location and untried at recovering the clone copy to recover the clone copy from the external destination node. 12. The method of claim 8 , wherein the method further comprises: determining whether the clone copy is moved from the location to an alternative location; and storing a primary copy of the updated backup parameters to the backup catalog in response to a determination that the clone copy is moved from the location to an alternative location. 13. The method of claim 12 , wherein the method further comprises storing a secondary copy of the updated backup parameters to a standard directory location. 14. The method of claim 8 , wherein providing, by the third-party backup application, the clone copy to the backup tool comprises using automatic channel settings to restore the clone copy to the database associated with the backup file; and wherein the backup parameters further identify a location of the database associated with the backup copy. 15. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein, the computer-readable program code adapted to be executed by one or more processors to implement a method for r

Assignees

Inventors

Classifications

  • Ensuring data consistency and integrity · CPC title

  • Backup restoration techniques · CPC title

  • G06F16/21Primary

    Design, administration or maintenance of databases · CPC title

  • by selection of backup contents · CPC title

  • Management of the backup or restore process · 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 US10534760B1 cover?
Retrieving backup parameters for recovery is described. A clone copy is created of a backup file stored on a disk. The clone copy is stored on an external destination node including an external disk and/or a tape. Backup parameters are stored to a backup catalog. The backup parameters identify a location of the clone copy. A request is received to recover the clone copy. The backup parameters a…
Who is the assignee on this patent?
Emc Corp, Emc Ip Holding Co Llc
What technology area does this patent fall under?
Primary CPC classification G06F16/2365. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jan 14 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).