Synchronized backup and recovery of heterogeneous DBMSs using third party backup tool

• US 10,255,139 B2
• Filed: 07/26/2016
• Issued: 04/09/2019
• Est. Priority Date: 07/26/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Agarwal, Anant, Chavan, Mahendra, Marathe, Nandan, Pandit, Dipesh
• Primary Examiner(s): Gofman, Alex
• Assistant Examiner(s): Mian, Umar
• Application Number:
  US15/220,044
• Publication Number:
  US 20180032408A1
• Time in Patent Office: 987 Days
• Field of Search: None
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes

Abstract

Synchronized backup and recovery of heterogeneous DBMSs is described herein. An embodiment operates by receiving, by at least one processor, a request for a data backup process at a first server; creating, by at least one processor, a pipe between processes of the first sever and the data backup process; performing, by at least one processor, the data backup process according to an execution command sent from a second server; and sending, by at least one processor, a result of the data backup process from the second server to the first server when the data backup process has terminated.

Claims

1. A method, comprising:

receiving, by at least one processor, a request for a data backup process at a first server, wherein the first server comprises a database management system (DBMS), wherein the DBMS comprises data stored in a database of the DBMS;

creating, by the at least one processor, an infile and a pipe between processes of the first server and the data backup process;

accessing, by the at least one processor, a plurality of partitions of the database, including at least a first partition and a second partition;

determining, by the at least one processor, that the first partition is configured to store hot data and that the second partition is configured to store warm data, the warm data being less often used than the hot data;

executing, by the at least one processor, an execution command to perform the data backup process, wherein the execution command is received from a second server;

storing, by the at least one processor, the hot data of the first partition into at least one main table;

storing, by the at least one processor, the warm data of the second partition into at least one extended table;

writing, by the at least one processor, the at least one extended table to the infile;

reading, by the at least one processor, via at least one of the processes of the first server and the data backup process, backup data from the infile to the pipe;

sending, by the at least one processor, via the data backup process, the backup data from the pipe to an outfile on the second server; and

receiving, by the at least one processor, a result of the data backup process from the second server, at the first server, when the data backup process has terminated.

2. The method of claim 1, wherein the first and second servers are located on a host network.

3. The method of claim 1, wherein the first server supports dynamically tiered data.

4. The method of claim 1, further comprising:

comparing, by the at least one processor, the data written to the pipe to the infile, wherein the infile is created by the second server; and

determining, by the at least one processor, based on the comparing, which data to back up via a further request for a further data backup process.

5. The method of claim 1, further comprising:

recovering, by the at least one processor, backed up data, wherein recovering comprises;

executing, by the at least one processor, an execution command to perform a data restore; and

reading, by the at least one processor, data from a second pipe between processes of the first server and the data backup process.

6. The method of claim 1, further comprising encrypting, by the at least one processor, the backup data from the infile to the pipe.

7. A system, comprising memory and at least one processor communicatively coupled to the memory and configured to:

receive a request to perform a data backup process at a first server, wherein the first server comprises a database management system (DBMS), wherein the DBMS comprises data stored in a database of the DBMS;

create an infile and a pipe between processes of the first server and the data backup process;

access a plurality of partitions of the database, including at least a first partition and a second partition;

determine that the first partition is configured to store hot data and that the second partition is configured to store warm data, the warm data being less often used than the hot data;

execute an execution command to perform the data backup process, wherein the execution command is received from a second server;

store the hot data of the first partition into at least one main table;

store the warm data of the second partition into at least one extended table;

write the at least one extended table to the infile;

read, via at least one of the processes of the first server and the data backup process, backup data from the infile to the pipe;

send, via the data backup process, the backup data from the pipe to an outfile on the second server; and

receive a result of the data backup process from the second server, at the first server, when the data backup process has terminated.

8. The system of claim 7, wherein the first and second servers are located on a host network.

9. The system of claim 7, wherein to execute, the at least one processor is configured to:

write, by the at least one processor, the result of the data backup process to the outfile created by the first server.

10. The system of claim 7, wherein the second server supports dynamically tiered data.

11. The system of claim 7, wherein the at least one processor is further configured to encrypt the backup data from the infile to the pipe.

12. A tangible, non-transitory computer-readable storage device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

receiving a request for a data backup process at a first server, wherein the first server comprises a database management system (DBMS), wherein the DBMS comprises data stored in a database of the DBMS;

creating an infile and a pipe between processes of the first server and the data backup process;

accessing a plurality of partitions of the database, including at least a first partition and a second partition;

determining that the first partition is configured to store hot data and that the second partition is configured to store warm data, the warm data being less often used than the hot data;

executing an execution command to perform the data backup process wherein the execution command is received from a second server;

storing the hot data of the first partition into at least one main table;

storing the warm data of the second partition into at least one extended table;

writing the at least one extended table to the infile;

reading, via at least one of the processes of the first server and the data backup process, backup data from the infile to the pipe;

sending, via the data backup process, the backup data from the pipe to an outfile on the second server; and

receiving a result of the data backup process from the second server, at the first server, when the data backup process has terminated.

13. The non-transitory computer-readable storage device of claim 12, wherein the first and second servers are located on a host network.

14. The non-transitory computer-readable storage device of claim 12, wherein the first server supports dynamically tiered data.

15. The non-transitory computer-readable storage device of claim 12, the operations further comprising:

recovering backed-up data, wherein recovering comprises;

executing an execution command to perform a data restore; and

reading data from a second pipe between processes of the first server and the data backup process.

16. The non-transitory computer-readable storage device of claim 15, the operations further comprising:

creating a plurality of pipes according to the execution command to perform the data restore.

17. The non-transitory computer-readable storage device of claim 15, the operations further comprising:

writing data from a plurality of logs to a respective pipe.

18. The non-transitory computer-readable storage device of claim 17, the operations further comprising:

reading data written to the plurality of logs; and

sending a result based on the data read.