Client data driven smart backup scheduler

A system comprising:

• a processor;
• and memory configured to store one or more sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of:
• configuring first, second, and third threshold limits, the first threshold limit corresponding to a data change at which a backup of a client should be triggered, the second threshold limit corresponding to a maximum time interval at which the backup should be triggered, and the third threshold limit corresponding to a utilization of resources at the client above which the backup should not be triggered;
• monitoring an amount of data change since a last backup of the client, an elapsed time since the last backup, and a level of resource utilization at the client;
• determining that at least one of the amount of data change has reached the first threshold limit or the elapsed time has reached the second threshold limit;
• and
• preventing the backup of the client from occurring because the level of resource utilization at the client is above the third threshold limit, wherein the client is associated with a virtual machine, and the processor further carries out the steps of:
• monitoring the amount of data change by issuing a first changed block request to a virtual machine manager of the virtual machine for blocks of the virtual machine that have changed;
• maintaining a first listing of changed blocks as reported by the virtual machine manager in response to the first changed block request;
• postponing the backup to a later time when the level of resource utilization at the client has decreased;
• at the later time, issuing a second changed block request to the virtual machine manager for blocks of the virtual machine that have changed;
• receiving a second listing of changed blocks as reported by the virtual machine manager in response to the second changed block request, wherein the virtual machine manager reports blocks that have changed since the first changed block request, the virtual machine manager thereby having reset a changed block tracker for the virtual machine upon receiving the first changed block request;
• and
• calculating, at the later time, blocks to be backed up using the first listing of changed blocks and the second listing of changed blocks.

A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein, the computer-readable program code adapted to be executed by one or more processors to implement a method comprising:

• configuring first, second, and third threshold limits, the first threshold limit corresponding to a data change at which a backup of a client should be triggered, the second threshold limit corresponding to a maximum time interval at which the backup should be triggered, and the third threshold limit corresponding to a utilization of resources at the client above which the backup should not be triggered;
• monitoring an amount of data change since a last backup of the client, an elapsed time since the last backup, and a level of resource utilization at the client;
• determining that at least one of the amount of data change has reached the first threshold limit or the elapsed time has reached the second threshold limit;
• and
• preventing the backup of the client from occurring because the level of resource utilization at the client is above the third threshold limit, wherein the client is associated with a virtual machine, and the method further comprises:
• monitoring the amount of data change by issuing a first changed block request to a virtual machine manager of the virtual machine for blocks of the virtual machine that have changed;
• maintaining a first listing of changed blocks as reported by the virtual machine manager in response to the first changed block request;
• postponing the backup to a later time when the level of resource utilization at the client has decreased;
• at the later time, issuing a second changed block request to the virtual machine manager for blocks of the virtual machine that have changed;
• receiving a second listing of changed blocks as reported by the virtual machine manager in response to the second changed block request, wherein the virtual machine manager reports blocks that have changed since the first changed block request, the virtual machine manager thereby having reset a changed block tracker for the virtual machine upon receiving the first changed block request;
• and
• calculating, at the later time, blocks to be backed up using the first listing of changed blocks and the second listing of changed blocks.