Granted Patent B2

US 9,639,429 · App. 14/274,614 · Granted May 2, 2017

Abstract

Claims (66)

1. A method for pre-provisioning validated database snapshots, the method comprising:

receiving a plurality of point-in-time copies of a source database, the plurality of point-in-time copies received based on a first predefined schedule;

storing a plurality of database blocks associated with the plurality of point-in-time copies on a storage system;

receiving transaction logs corresponding to transactions executed in the source database;

creating a plurality of recovery milestones based on a second predefined schedule, wherein the recovery milestones are created at a frequency higher than a frequency at which point-in-time copies of the source database are received, each recovery milestone comprising database blocks corresponding to a state of the source database at a point in time, wherein one or more database blocks are shared across two or more recovery milestones, the creating comprising:

creating a first recovery milestone by applying transaction logs to the plurality of database blocks associated with a point-in-time copy of the source database, and

creating one or more subsequent recovery milestones by applying transaction logs to database blocks of the first recovery milestone or by applying transaction logs to database blocks of another recovery milestone created based on the first recovery milestone;

receiving a request to provision a virtual database representing a state of the source database at a first point in time;

identifying a recovery milestone based on the first point in time; and

provisioning the requested virtual database based on the identified recovery milestone, the virtual database configured to provide access to database blocks associated with the recovery milestone to a target system.

2. The method of claim 1 , wherein identifying the recovery milestone based on the first point-in-time comprises

responsive to the first point in time matching the point in time of a particular recovery milestone, using the particular recovery milestone as the identified recovery milestone.

3. The method of claim 1 , wherein responsive to the first point in time not matching point in times of any of the recovery milestones, identifying the recovery milestone comprises selecting a recovery milestone with a point in time closest to and occurring prior to the first point in time, and wherein provisioning the requested virtual database comprises:

updating the database blocks of the identified recovery milestone by applying transaction logs to database blocks of the identified recovery milestone; and

provisioning the requested virtual database using the updated database blocks.

4. The method of claim 3 , further comprising:

creating a new recovery milestone based on the updated database blocks corresponding to the virtual database.

5. The method of claim 1 , further comprising:

validating the recovery milestone created to determine whether the recovery milestone can be used to create a consistent snapshot of the source database.

6. The method of claim 5 , wherein validating the recovery milestone comprises:

identifying a problem associated with creation of a recovery milestone; and

responsive to identifying the problem, taking actions to fix the problem in advance of the request to create a virtual database based on the recovery milestone.

7. The method of claim 6 , wherein the actions for fixing the problem comprise, receiving a recent version of a vendor library and using the recent version of the vendor library for creating the recovery milestone.

8. The method of claim 1 , wherein the source database performs logging for a set of tables and disables logging for tables outside the set of tables, the method further comprising:

responsive to the provisioned virtual database receiving a query based on one or more tables outside the set of tables, disallowing the query.

9. A method for pre-provisioning validated database snapshots, the method comprising:

receiving a plurality of point-in-time copies of a source database, the plurality of point-in-time copies received based on a first predefined schedule;

storing a plurality of database blocks associated with the plurality of point-in-time copies on a storage system;

receiving transaction logs corresponding to transactions executed in the source database; and

creating a plurality of recovery milestones based on a second predefined schedule, wherein the recovery milestones are created at a frequency higher than a frequency at which point-in-time copies of the source database are received, each recovery milestone comprising database blocks corresponding to a state of the source database at a point in time, wherein one or more database blocks are shared across two or more recovery milestones, and wherein a recovery milestone is created in advance of receiving a request for creation of a virtual database for the point-in-time of the recovery milestone, the creating comprising:

creating a first recovery milestone by applying transaction logs to the plurality of database blocks associated with a point-in-time copy of the source database, and

creating one or more subsequent recovery milestones by applying transaction logs to database blocks of the first recovery milestone or by applying transaction logs to database blocks of another recovery milestone created based on the first recovery milestone.

10. The method of claim 9 , further comprising:

receiving request to create a virtual database representing a state of the source database at a first point in time;

responsive to the first point in time matching point in time of a recovery milestone, selecting the matching recovery milestone; and

provisioning the requested virtual database based on the database blocks of the selected recovery milestone.

11. The method of claim 9 , further comprising:

receiving request to create a virtual database representing a state of the source database at a first point in time;

responsive to the first point in time not matching point in times of any of the recovery milestones, selecting a recovery milestone with a point in time closest to and occurring prior to the requested point in time; and

provisioning the requested virtual database based on the database blocks of the selected recovery milestone.

12. The method of claim 9 , wherein creating each recovery milestone further comprises:

validating the recovery milestone created to determine whether the recovery milestone can be used to create a consistent snapshot of the source database.

13. The method of claim 12 , wherein validating the recovery milestone comprises:

responsive to determining that a set of transaction logs corresponding to the recovery milestone are corrupted, determining that the recovery milestone is invalid.

14. The method of claim 12 , wherein validating the recovery milestone comprises:

responsive to the determining that the recovery milestone is invalid, executing steps to identify a defect resulting in creation of the invalid recovery milestone and executing steps to fix the defect.

15. The method of claim 9 , wherein the source database performs logging for a set of tables and disables logging for tables outside the set of tables, the method further comprising:

responsive to the provisioned virtual database receiving a query based on one or more tables outside the set of tables, disallowing the query.

16. A computer program product having a non-transitory computer-readable storage medium storing computer program modules configured to execute on a computer processor, the computer program modules comprising instructions for:

receiving a plurality of point-in-time copies of a source database, the plurality of point-in-time copies received based on a first predefined schedule;

storing a plurality of database blocks associated with the plurality of point-in-time copies on a storage system;

receiving transaction logs corresponding to transactions executed in the source database;

creating a plurality of recovery milestones based on a second predefined schedule, wherein the recovery milestones are created at a frequency higher than a frequency at which point-in-time copies of the source database are received, each recovery milestone comprising database blocks corresponding to a state of the source database at a point in time, wherein one or more database blocks are shared across two or more recovery milestones, the creating comprising:

creating a first recovery milestone by applying transaction logs to the plurality of database blocks associated with a point-in-time copy of the source database, and

creating one or more subsequent recovery milestones by applying transaction logs to database blocks of the first recovery milestone or by applying transaction logs to database blocks of another recovery milestone created based on the first recovery milestone;

receiving a request to provision a virtual database representing a state of the source database at a first point in time;

identifying a recovery milestone based on the first point in time; and

provisioning the requested virtual database based on the identified recovery milestone, the virtual database configured to provide access to database blocks associated with the recovery milestone to a target system.

17. The computer program product of claim 16 , wherein identifying the recovery milestone comprises, selecting a recovery milestone with a point in time closest to and occurring prior to the requested point in time and wherein provisioning the requested virtual database comprises:

applying transaction logs to the database blocks of the identified recovery milestone to create a database snapshot corresponding to the requested point in time; and

provisioning the requested virtual database comprising the database blocks of the database snapshot created.

18. The computer program product of claim 16 , wherein validating the recovery milestone comprises:

responsive to determining that a set of transaction logs corresponding to the recovery milestone are corrupted, determining that the recovery milestone is invalid; and

responsive to the determining that the recovery milestone is invalid, executing steps to identify a defect resulting in creation of the invalid recovery milestone and executing steps to fix the defect.

19. The computer program product of claim 16 , wherein the source database performs logging for a set of tables and disables logging for tables outside the set of tables, the computer program modules further comprising instructions for:

responsive to the provisioned virtual database receiving a query based on one or more tables outside the set of tables, disallowing the query.

Assignments (17)