Maintenance management on backup storage systems
Maintenance management on backup storage systems. Specifically, the disclosed method and system derive backup storage system load from a collection of profiled load factoring features. The backup storage system load may subsequently drive whether maintenance operations may be deferred to projected non-peak load times or, alternatively, may be permitted to proceed.
1. A method for maintenance management, comprising:
detecting a trigger for a first maintenance operation;
in response to detecting the trigger for the first maintenance operation:
profiling, for a first point-in-time, a plurality of load factoring features;
computing a first current load factor using the plurality of load factoring features for the first point-in-time;
making a first determination that the first current load factor at least meets a permissible load factor;
making a second determination that a number of deferments for the first maintenance operation exceeds a deferment threshold; and
performing, based on the first and second determinations, the first maintenance operation.
2. The method of claim 1 , wherein the first maintenance operation performs one selected from a group consisting of purging expired data, purging expired jobs, and compressing stored data.
3. The method of claim 1 , wherein the plurality of load factoring features comprises at least one application-type load factoring feature, at least one operating system (OS)-type load factoring feature, and at least one infrastructure-type load factoring feature.
4. The method of claim 1 , further comprising:
detecting a trigger for a second maintenance operation;
in response to detecting the trigger for the second maintenance operation:
profiling, for a second point-in-time, the plurality of load factoring features;
computing a second current load factor using the plurality of load factoring features for the second point-in-time;
making a third determination that the second current load factor is below the permissible load factor; and
performing, based on the third determination, the second maintenance operation.
5. The method of claim 1 , further comprising:
detecting a trigger for a second maintenance operation;
in response to detecting the trigger for the second maintenance operation:
profiling, for a second point-in-time, the plurality of load factoring features;
computing a second current load factor using the plurality of load factoring features for the second point-in-time;
making a third determination that the second current load factor at least meets the permissible load factor; and
deferring, based on the third determination, the second maintenance operation to a later point-in-time.
6. The method of claim 5 , wherein the later point-in-time comprises a non-peak load time when at least one selected from a group consisting of a data backup operation, a data cloning operation, and a data recovery operation, is not expected to be performed.
7. The method of claim 6 , further comprising:
prior to deferring the second maintenance operation:
predicting a plurality of non-peak load times based on a plurality of historical load factors and the second current load factor,
wherein the plurality of non-peak load times comprises the non-peak load time.
8. The method of claim 7 , further comprising:
prior to predicting the plurality of non-peak load times:
obtaining a second number of deferments for the second maintenance operation; and
making a fourth determination that the second number of deferments does not exceed the deferment threshold,
wherein deferring the second maintenance operation to the later point-in-time is further based on the fourth determination.
9. A non-transitory computer readable medium (CRM) comprising computer readable program code, which when executed by a computer processor, enables the computer processor to:
detect a trigger for a first maintenance operation;
in response to detecting the trigger for the first maintenance operation:
profile, for a first point-in-time, a plurality of load factoring features;
compute a first current load factor using the plurality of load factoring features for the first point-in-time;
make a first determination that the first current load factor at least meets a permissible load factor;
make a second determination that a number of deferments for the first maintenance operation exceeds a deferment threshold; and
perform, based on the first and second determinations, the first maintenance operation.
10. The non-transitory CRM of claim 9 , wherein the first maintenance operation performs one selected from a group consisting of purging expired data, purging expired jobs, and compressing stored data.
11. The non-transitory CRM of claim 9 , wherein the plurality of load factoring features comprises at least one application-type load factoring feature, at least one operating system (OS)-type load factoring feature, and at least one infrastructure-type load factoring feature.
12. The non-transitory CRM of claim 9 , comprising computer readable program code, which when executed by the computer processor, further enables the computer processor to:
detect a trigger for a second maintenance operation;
in response to detecting the trigger for the second maintenance operation:
profile, for a second point-in-time, the plurality of load factoring features;
compute a second current load factor using the plurality of load factoring features for the second point-in-time;
make a third determination that the second current load factor is below the permissible load factor; and
perform, based on the third determination, the second maintenance operation.
13. The non-transitory CRM of claim 9 , comprising computer readable program code, which when executed by the computer processor, further enables the computer processor to:
detect a trigger for a second maintenance operation;
in response to detecting the trigger for the second maintenance operation:
profile, for a second point-in-time, the plurality of load factoring features;
compute a second current load factor using the plurality of load factoring features for the second point-in-time;
make a third determination that the second current load factor at least meets the permissible load factor; and
defer, based on the third determination, the second maintenance operation to a later point-in-time.
14. The non-transitory CRM of claim 13 , wherein the later point-in-time comprises a non-peak load time when at least one selected from a group consisting of a data backup operation, a data cloning operation, and a data recovery operation, is not expected to be performed.
15. The non-transitory CRM of claim 14 , comprising computer readable program code, which when executed by the computer processor, further enables the computer processor to:
prior to deferring the second maintenance operation:
predict a plurality of non-peak load times based on a plurality of historical load factors and the second current load factor,
wherein the plurality of non-peak load times comprises the non-peak load time.
16. The non-transitory CRM of claim 15 , comprising computer readable program code, which when executed by the computer processor, further enables the computer processor to:
prior to predicting the plurality of non-peak load times:
obtain a second number of deferments for the second maintenance operation; and
make a fourth determination that the second number of deferments does not exceed the deferment threshold,
wherein deferring the second maintenance operation to the later point-in-time is further based on the fourth determination.
17. A backup storage system, comprising:
a storage array; and
a computer processor operatively connected to the storage array, and programmed to:
detect a trigger for a first maintenance operation;
in response to detecting the trigger for the first maintenance operation:
profile, for a first point-in-time, a plurality of load factoring features;
compute a first current load factor using the plurality of load factoring features for the first point-in-time;
make a first determination that the first current load factor at least meets a permissible load factor;
make a second determination that a number of deferments for the first maintenance operation exceeds a deferment threshold; and
perform, based on the first and second determinations, the first maintenance operation.
18. The backup storage system of claim 17 , wherein the first maintenance operation performs one selected from a group consisting of purging expired data, purging expired jobs, and compressing stored data.
19. The backup storage system of claim 17 , wherein the plurality of load factoring features comprises at least one application-type load factoring feature, at least one operating system (OS)-type load factoring feature, and at least one infrastructure-type load factoring feature.
20. The backup storage system of claim 17 , wherein the computer processor is further programmed to:
detect a trigger for a second maintenance operation;
in response to detecting the trigger for the second maintenance operation:
profile, for a second point-in-time, the plurality of load factoring features;
compute a second current load factor using the plurality of load factoring features for the second point-in-time;
make a third determination that the second current load factor at least meets the permissible load factor; and
defer, based on the third determination, the second maintenance operation to a later point-in-time.