Opportunistic execution of secondary copy operations

Patent metadata

Field	Value
Publication number	US-10474538-B2
Application number	US-201715474077-A
Country	US
Kind code	B2
Filing date	Mar 30, 2017
Priority date	Dec 4, 2014
Publication date	Nov 12, 2019
Grant date	Nov 12, 2019

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 backup jobs based on a backup readiness score instead of based on a pre-defined schedule, the system comprising:
a client computing device comprising an application and an associated data agent;
a first data storage device in communication with the client computing device, the first data storage device comprising a log file populated by the application; and
a second data 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 application,
generate a backup-readiness score based on at least one of the operational factors exceeding a respective threshold value, and
initiate a backup job of 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 the data agent is further configured to:
increase a weight for a first operational factor among the plurality of operational factors, based on analyzing a plurality of previously-executed backup jobs,
evaluate a second backup-readiness score which is based on the increased weight, and
initiate a second backup job of the log file based on the second backup-readiness score.

2. The storage management system of claim 1 wherein the plurality of operational factors comprises at least one of:
(i) a measure of the amount of storage space occupied by the log file;
(ii) a measure of the amount of storage space occupied by the log file since a preceding backup job was initiated;
(iii) a number of log file entries generated since the preceding backup job;
(iv) a number of application transactions executed since the preceding backup job was initiated;
(v) a measure of elapsed time since the preceding backup was initiated;
(vi) a measure of activity of the application during a period of time;
(vii) a measure of usage of the first data storage device during a period of time;
(viii) a measure of usage, by the application, of the first data storage device during a period of time; and
(ix) a measure of usage of the client computing device during a period of time.

3. The storage management system of claim 1 wherein a given backup job of the log file lacks a pre-defined schedule and instead the backup job is initiated when an evaluated backup-readiness score exceeds a threshold value.

4. The storage management system of claim 1 wherein a given backup-readiness score is based on the plurality of monitored operational factors, and is further based on a weight assigned to each respective operational factor.

5. The storage management system of claim 1 wherein the plurality of operational factors further comprises a manufacturer-specific parameter associated with at least one of the application and the first data storage device.

6. The storage management system of claim 1 further comprising a storage manager for managing the backups of the log file, wherein the storage manager instructs the data agent when to initiate a given backup job.

7. The storage management system of claim 1 wherein a given backup job comprises at least one of: a secondary copy operation, a deduplication operation, an encryption operation, and a compression operation.

8. A storage management system for opportunistically initiating backups based on a backup-readiness score instead of based on a pre-defined schedule, the system comprising:
a client computing device comprising an application and an associated data agent;
a first data storage device in communication with the client computing device, the first data storage device comprising a log file populated by the application; and
a second data 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 application,
generate a backup-readiness score based on at least one of the operational factors exceeding a respective threshold value, and
initiate a backup of the log file based on the backup-readiness score, wherein the secondary copy of the log file is a result of the backup;

wherein the data agent is further configured to:
based on evaluating by the data agent of a plurality of executed backups executed since a preceding evaluation, increase a weight for a first operational factor among the plurality of operational factors, and
initiate a second backup of the log file based on a second backup-readiness score which is based on the increased weight; and

wherein the plurality of operational factors comprises at least one of:
(i) a measure of the amount of storage space occupied by the log file;
(ii) a measure of the amount of storage space occupied by the log file since a preceding backup job was initiated;
(iii) a number of log file entries generated since the preceding backup job;
(iv) a number of application transactions executed since the preceding backup job was initiated;
(v) a measure of elapsed time since the preceding backup was initiated;
(vi) a measure of activity of the application during a period of time;
(vii) a measure of usage of the first data storage device during a period of time;
(viii) a measure of usage, by the application, of the first data storage device during a period of time; and
(ix) a measure of usage of the client computing device during a period of time.

9. The storage management system of claim 8 wherein a given backup of the log file lacks a pre-defined schedule and instead the backup is initiated when the backup readiness score exceeds a threshold value.

10. The storage management system of claim 8 wherein a given backup-readiness score is based on the plurality of monitored operational factors, and is further based on a weight assigned to each respective operational factor.

11. The storage management system of claim 8 wherein a given backup is initiated when a respective backup-readiness score exceeds a threshold value.

12. The storage management system of claim 8 wherein the data agent is further configured to:
adjust at least one weight assigned to a corresponding operational factor in the plurality of operational factors, based on the evaluating by the data agent of a plurality of executed backups executed since a preceding evaluation.

13. The storage management system of claim 8 wherein the plurality of operational factors further comprises a manufacturer-specific parameter associated with at least one of the application and the first data storage device.

14. The storage management system of claim 8 wherein the plurality of operational factors further comprises a version-specific parameter associated with the application.

15. The storage management system of claim 8 further comprising a storage manager for managing the backups of the log file.

16. The storage management system of claim 8 wherein a given backup comprises at least one of: a secondary copy operation, a deduplication operation, an encryption operation, and a compression operation.

17. A computer-readable medium, excluding transitory propagating signals, storing instructions that, when executed by at least one computing device comprising one or more processors and corresponding computer memory, cause the computing device to perform operations comprising:
executing a database application on the computing device, wherein the database application populates at least part of an associated log file;
monitoring, by a data agent executing on th

Assignees

• Commvault Systems Inc

Inventors

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

Classifications

• G06F11/1453

  using de-duplication of the data · CPC title

• G06F2201/88

  Monitoring involving counting · CPC title

• G06F2201/80

  Database-specific techniques · CPC title

• 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