Optimizing the number and type of database backups to achieve a given recovery time objective (RTO)

Patent metadata

Field	Value
Publication number	US-9430335-B2
Application number	US-201314030168-A
Country	US
Kind code	B2
Filing date	Sep 18, 2013
Priority date	Sep 18, 2013
Publication date	Aug 30, 2016
Grant date	Aug 30, 2016

Abstract

A method of optimizing the number and type of database backups to achieve a given RTO is provided and may include receiving a RTO and receiving a heuristic for determining an amount of unencumbered processing time. A type of next backup, (i.e., a next backup), is determined wherein the type of next backup is an incremental backup when the sum of the heuristic, and the times to: restore the latest full backup, restore zero or more incremental backups, complete a current incremental backup, and perform a full backup is less than the received RTO, else the type of the next backup is a full backup. A time to schedule the next backup is scheduled based on the received RTO being a total of an amount of time to: complete the type of next backup; rollforward zero or more transaction log records; and to restore at least one backup.

First claim

What is claimed is:

1. A method of optimizing the number and type of database backups to achieve a given Recovery Time Objective (RTO) comprising:
receiving a user-defined RTO, wherein the RTO is configured for one or more databases or globally for a database management system (DBMS);
receiving a heuristic for determining an amount of unencumbered processing time;
determining a type of next backup corresponding to a next backup, wherein the type of next backup is an incremental backup when a sum of recovery times totals less than the received RTO, else the type of the next backup is a full backup; and
determining a time to schedule the next backup based on the received RTO being a total of:
an amount of time to complete the type of next backup;
an amount of time to rollforward zero or more transaction log records
wherein the zero or more transaction log records include one or more recoverable operations and wherein each of the one or more recoverable operations is associated with a recovery cost that is expressed as a multiple of base operation units; and
an amount of time to restore at least one backup.

2. The method of claim 1 , wherein the sum of the recovery times further comprises a total of:
an amount of time required to restore a latest full backup,
an amount of time to restore zero or more incremental backups,
an amount of time to complete a current incremental backup,
an amount of time corresponding to the heuristic; and
an amount of time to complete a full backup.

3. The method of claim 1 , wherein determining the type of next backup further comprises:
calculating a total amount of time by aggregating:
an amount of time to restore a full backup;
the amount of time to restore the zero or more incremental backups;
the amount of time to complete the current incremental backup;
the amount of time to complete the full backup; and
determining the type of next backup based on the calculated total amount of time and the received RTO.

4. The method of claim 1 , wherein determining a time to schedule the next backup further comprises:
when the received RTO is less than the total of:
the amount of time to complete the type of the next backup;
the amount of time to rollforward the zero or more transaction log records; and
the amount of time to restore the at least one backup;
issuing a message that the database is out of compliance with the received RTO; and
determining to start the next backup immediately.

5. The method of claim 1 , wherein calculating an amount of time to rollforward zero or more transaction log records further comprises:
monitoring and tracking recoverable operations as they occur during database execution; they occur;
storing a count and a type of the recoverable operations in a persistent store as extracting from the persistent store the recoverable operations, the count of
each of the recoverable operations, and a recovery cost associated with each of the recoverable operations; and
for each of the recoverable operations: multiplying the count by the associated recovery cost.

6. The method of claim 2 , wherein calculating the amount of time to restore zero or more incremental backups further comprises a sum of times to restore each of the zero or more incremental backups created since the last full backup.

7. The method of claim 1 , wherein the amount of time to restore the at least one backup further comprises:
a sum of times to restore each of the zero or more incremental backups created since a last full backup; or
an estimated time to restore a full backup.

8. A computer program product for optimizing the number and type of database backups to achieve a given Recovery Time Objective (RTO), the computer program product including a DBMS embodied on a computer readable storage medium, the DBMS including code executable by a processor to perform a method comprising:
receiving a user-defined RTO, wherein the RTO is configured for one or more databases or globally for a database management system (DBMS);
receiving a heuristic for determining an amount of unencumbered processing time;
determining a type of next backup corresponding to a next backup, wherein the type of next backup is an incremental backup when a sum of recovery times totals less than the received RTO, else the type of the next backup is a full backup; and
determining a time to schedule the next backup based on the received RTO being a total of:
an amount of time to complete the type of next backup;
an amount of time to rollforward zero or more transaction log records,
wherein the zero or more transaction log records include one or more recoverable operations and wherein each of the one or more recoverable operations is associated with a recovery cost that is expressed as a multiple of base operation units; and
an amount of time to restore at least one backup.

9. The computer program product of claim 8 , wherein the sum of recovery times further comprises a total of:
an amount of time required to restore a latest full backup,
an amount of time to restore zero or more incremental backups,
an amount time to complete a current incremental backup,
an amount of time corresponding to the heuristic; and
an amount of time to complete a full backup.

10. The computer program product of claim 8 , wherein determining the type of next backup further comprises:
calculating a total amount of time by aggregating:
an amount of time to restore a full backup;
the amount of time to restore zero or more incremental backups;
the amount of time to complete an incremental backup;
the amount of time to complete a full backup; and
determining the type of next backup based on the calculated total amount of time and the received RTO.

11. The computer program product of claim 8 , wherein determining a time to schedule the next backup further comprises:
when the received RTO is less than the total of:
the amount of time to complete the type of the next backup;
the amount of time to rollforward the zero or more transaction log records; and
the amount of time to restore the at least one backup;
issuing a message that the database is out of compliance with the received RTO; and
determining to start the next backup immediately.

12. The computer program product of claim 8 , wherein calculating the amount of time to rollforward zero or more transaction log records further comprises:
monitoring and tracking recoverable operations as they occur during database execution;
storing a count and a type of the recoverable operations in a persistent store as they occur;
extracting from the persistent store the recoverable operations, the count of each of the recoverable operations, and a recovery cost associated with each of the recoverable operations; and
for each of the recoverable operations: multiplying the count by the associated recovery cost.

13. The computer program product of claim 9 , wherein calculating the amount of time to restore zero or more incremental backups further comprises a sum of times to restore each of the zero or more incremental backups created since the last full backup.

14. A computer system for optimizing the number and type of database backups to achieve a given Recovery Time Objective (RTO), the computer system comprising one or more processors, one or more computer-readable storage devices, and a plurality of program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors, the plurality of program instructions comprising:
receiving a user-defined RTO, wherein the RTO is configured for one or mo

Assignees

• IBM

Inventors

• Jin Gary N
• Pearson Steven R
• Akulavenkatavara Prasadarao

Classifications

• G06F11/1451 Primary

  by selection of backup contents · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

• G06F11/1464

  for networked environments · CPC title

• G06F11/1461 Primary

  Backup scheduling policy · CPC title

• G06F2201/80

  Database-specific techniques · CPC title