Opportunistic execution of secondary copy operations

Patent metadata

Field	Value
Publication number	US-9645891-B2
Application number	US-201414561046-A
Country	US
Kind code	B2
Filing date	Dec 4, 2014
Priority date	Dec 4, 2014
Publication date	May 9, 2017
Grant date	May 9, 2017

Abstract

Rather than relying on pre-defined scheduling of secondary copy operations such as backup jobs, the illustrative opportunistic approach initiates secondary copy operations based on changing operational conditions in a storage management system. An adaptive backup readiness score is based on a number of backup-readiness operational factors. An illustrative enhanced data agent which is associated with the target database application (or other executable component) may monitor the operational factors and determine the backup readiness score based on weights assigned to the respective operational factors. The enhanced data agent may evaluate recent backup jobs to determine which of the operational factors that contributed to the backup readiness score may have been most relevant. Based on the most-relevant analysis, the enhanced data agent may adapt the weights assigned to the monitored operational factors, so that the backup readiness score may be more suitable and responsive to ongoing operational conditions in the system.

First claim

What is claimed is:

1. A storage management system for opportunistically initiating a backup job based on a backup readiness score instead of based on a pre-defined schedule, the system comprising:
a client computing device comprising a database application and an associated data agent;
a primary storage device in communication with the client computing device, the primary storage device comprising a log file populated by the database application; and
a secondary storage device comprising a secondary copy of the log file;
wherein the data agent is configured to:
monitor a plurality of operational factors associated with at least one of the log file and the database application,
generate a backup readiness score based on at least one of the operational factors exceeding its respective threshold value, and
initiate a backup job for the log file based on the backup readiness score, wherein the secondary copy of the log file is a result of the backup job;

wherein a second backup job for the log file is based on a second backup readiness score which is based on an increased weight for a first operational factor in the plurality of operational factors, wherein the increased weight results from an evaluation of a plurality of executed backup jobs executed since a preceding evaluation.

2. A storage management system for opportunistically initiating a backup job based on a backup readiness score instead of based on a pre-defined schedule, the system comprising:
a client computing device comprising a database application and an associated data agent;
a primary storage device in communication with the client computing device, the primary storage device comprising a log file populated by the database application; and
a secondary storage device comprising a secondary copy of the log file;
wherein the data agent is configured to:
monitor a plurality of operational factors associated with at least one of the log file and the database application,
generate a backup readiness score based on at least one of the operational factors exceeding its respective threshold value, and
initiate a backup job for the log file based on the backup readiness score, wherein the secondary copy of the log file is a result of the backup job;

wherein a second backup job for the log file is based on a second backup readiness score which is based on an increased weight for a first operational factor in the plurality of operational factors, wherein the increased weight results from an evaluation of a plurality of executed backup jobs executed since a preceding evaluation, and wherein in the plurality of executed backup jobs the first operational factor most often, relative to the other operational factors, exceeded its respective threshold value.

3. A system for opportunistically initiating a backup job based on a backup readiness score instead of based on a pre-defined schedule, the system comprising:
a client computing device comprising a database application and an associated data agent;
a primary storage device in communication with the client computing device, the primary storage device comprising a log file populated by the database application; and
a secondary storage device comprising a secondary copy of the log file;
wherein the data agent is configured to:
monitor a plurality of operational factors associated with at least one of the log file and the database application,
generate a first backup readiness score that is based on the plurality of monitored operational factors, and
initiate a first backup job for the log file based on the backup readiness score, wherein the secondary copy of the log file is a result of the first backup job; and

wherein the data agent is further configured to:
evaluate a plurality of executed backup jobs that includes the first backup job, wherein in the plurality of executed backup jobs a first operational factor most often, relative to the other operational factors, exceeded its respective threshold value, and
initiate a second backup job of the log file based on a second backup readiness score which is based on an increased weight for the first operational factor, wherein the increased weight results from the evaluation of the plurality of executed backup jobs.

4. The system of claim 3 wherein the first backup readiness score is generated based on at least one of the operational factors exceeding its respective threshold value.

5. A method for opportunistically initiating a backup job in a storage management system based on a backup readiness score, the method comprising:
executing a database application on a client computing device, wherein the database application populates at least part of an associated log file;
monitoring, by a data agent, a plurality of operational factors associated with at least one of the database application and the log file populated at least in part by the database application;
generating, by the data agent, a first backup readiness score based on the plurality of operational factors;
initiating, by the data agent, a first backup job for the log file based on the backup readiness score, wherein the first backup job generates a first secondary copy of the log file;
evaluating, by the data agent, a plurality of executed backup jobs including the first backup job, wherein in the plurality of backup jobs a first operational factor most often exceeded, relative to the other operational factors, its respective threshold value;
generating, by the data agent, a second backup readiness score based on an increased weight for the first operational factor, wherein the increased weight results from the evaluating of the plurality of executed backup jobs; and
initiating, by the data agent, a second backup job of the log file based on the second backup readiness score, wherein the second backup job generates a second secondary copy of the log file.

6. The method of claim 5 wherein the first backup readiness score is generated when one or more of the operational factors exceeds a respective threshold value.

7. The method of claim 5 further comprising:
based on the evaluating of the plurality of backup jobs, adjusting, by the data agent, at least one weight associated with a corresponding second operational factor in the plurality of operational factors.

8. The method of claim 5 wherein the first backup job is initiated when the first backup readiness score exceeds a threshold value, and further wherein the second backup job is initiated when the second backup readiness score exceeds the threshold value.

Assignees

• Commvault Systems Inc

Inventors

• Ahn Jun H
• Ashraf Waqas
• Kumar Anup
• Vallabhaneni Brahmaiah

Classifications

• G06F11/1451

  by selection of backup contents · CPC title

• G06F11/3034

  where the computing system component is a storage system, e.g. DASD based or network based (digital input from or digital output to record carriers G06F3/06; digital recording or reproducing G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097) · CPC title

• G06F2201/80

  Database-specific techniques · CPC title

• G06F2201/88

  Monitoring involving counting · CPC title

• G06F11/1461 Primary

  Backup scheduling policy · CPC title