US 2023/0409441 A1Published application

Systems and methods for enforcing a recovery point objective (rpo) for a production database without generating secondary copies of the production database

AssigneeCommvault Systems, Inc.

InventorsChandresh Sharma, Saurabh Agrawal, Brahmaiah Vallabhaneni, Hetal Kapadia, Manoj Kumar Vijayan

Life of this patent

Estimating the term…

Loading patent…

Abstract

A disclosed framework enables virtually any aggressive Recovery Point Objective (RPO) to be enforced for a production database, without limitation on type of database management system (DBMS) or size of the production database. The framework overcomes technological barriers of the prior art, such as bottlenecks presented by a storage manager computer that traditionally managed database backups. To avoid the bottlenecks, an illustrative data storage management system does not engage the storage manager computer in storage operations that could impact the database RPO. Certain components are added and enhanced to autonomously capture database transaction logs, which are stored securely and persistently away from the DBMS. In a separate and less frequent operation, and with involvement of the storage manager computer, the illustrative system generates secondary copies in their final form. Meanwhile, temporary backup files can be used in restore operations without first being converted into secondary copies.

Claims20

Dependent claims

A computer-implemented method performed by one or more hardware processors, the method comprising:

activating a first data agent at a first computing device, wherein the first computing device hosts a database management system that comprises a first database, wherein the first data agent is associated with the database management system;
by the first data agent, converting a first set of transaction logs generated by the database management system into a first set of temporary backup files, wherein the first set of temporary backup files are in a backup format that comprises encryption;
based on a time interval of a recovery point objective (RPO) associated with the first database, transmitting the first set of temporary backup files over a persistent data pipeline connection to a second computing device;
by the second computing device, storing the first set of temporary backup files persistently at a data repository of the second computing device;
based on a second time interval that is greater than the time interval of the RPO, determining by the second computing device whether the data repository comprises any temporary backup files;
based on the second computing device determining that the data repository comprises at least one temporary backup file, performing a data storage job that converts the at least one temporary backup file into one or more secondary copies and storing the one or more secondary copies at a secondary storage that is distinct from the data repository,
wherein the data storage job comprises indexing the one or more secondary copies in an index maintained at the second computing device, and wherein the data storage job further comprises reporting information about the data storage job to a storage manager that executes on a third computing device, which is distinct from the first computing device and from the second computing device.

4 more elements

A system comprising:

a second computing device comprising one or more hardware processors, wherein the second computing device is communicatively coupled to a first computing device via a persistent data pipeline connection to a first data agent that executes at the first computing device, and wherein the first computing device additionally executes a database management system that comprises a first database, which is associated with a recovery point objective (RPO);
and
a third computing device comprising one or more hardware processors, wherein the third computing device executes a storage manager;
wherein the first computing device executing the first data agent is configured to:
convert a first set of transaction logs generated by the database management system into a first set of temporary backup files, wherein the first set of temporary backup files are in a backup format that comprises encryption, and
based on a time frequency of the RPO, transmit the first set of temporary backup files over the persistent data pipeline connection to the second computing device;
wherein the second computing device is configured to:
store the first set of temporary backup files persistently at a data repository that comprises one or more of a data storage volume and a folder configured at the second computing device, and
based on a second time frequency that is greater than the time frequency of the RPO, determine whether the data repository comprises any temporary backup files, and
based on determining that the data repository comprises at least one temporary backup file, perform a data storage job that:
converts the at least one temporary backup file into one or more secondary copies,
stores the one or more secondary copies at a secondary storage, which is distinct from the data repository,
indexes the one or more secondary copies in an index maintained at the second computing device, and
reports information about the data storage job to the storage manager at the third computing device;
and
wherein the third computing device executing the storage manager is configured to:
transmit the RPO to the first data agent, and afterwards not cause the first data agent to transmit the first set of temporary backup files over the persistent data pipeline connection to the second computing device, and
transmit the second time frequency to the second computing device, and afterwards not initiate the data storage job.

15 more elements

Dependencies are inferred from the claim text.