Initiating backups based on data changes
Initiating backups based on data changes is described. A system identifies an amount of data changed for a client since a previous backup operation for the client. The system determines whether the amount of data changed meets a threshold requirement. The system initiates a backup operation for the client if the amount of data changed meets the threshold requirement.
1. A system for initiating backups based on data changes, the system comprising:
a processor-based application, which when executed on a computer, will cause the processor to:
identify, by a daemon process running on a client computing device, at a time before a next scheduled operation for the client computing device, an amount of data changed since a previous backup operation by accessing, via a write tracking driver in communication with the daemon process, a block-based bitmap for data changes, wherein the write tracking driver identifies input and output operations associated with the client computing device and stores a record of the input and the output operations in the block-based bitmap;
determine, by the daemon process, whether the identified amount of data changed meets or exceeds a threshold requirement, at least one of the amount of data changed or the threshold requirement being based on at least one of a total amount of data changed for the client, an amount of data changed for the client relative to a total amount of data for the client, or an amount of data changed for the client per a period of time;
initiate, by the daemon process in communication with a backup/restore application over a network, a backup operation via the backup/restore application before the next scheduled backup operation for the client computing device when the identified amount of data changed meets or exceeds the threshold requirement;
monitor the amount of data changed from the previous backup operation when the identified amount of data changed is below the threshold requirement; and
initiate a backup operation before the next scheduled backup operation for the client computing device when the monitored amount of data changed meets or exceeds the threshold requirement.
2. The system of claim 1 , wherein identifying the amount of data changed for the client since the previous backup operation for the client further includes identifying a plurality of time stamps corresponding to a plurality of files and comparing the plurality of time stamps to a time associated with the previous backup operation.
3. The system of claim 1 , wherein the client comprises a plurality of clients.
4. The system of claim 1 , wherein the threshold requirement is configurable by at least one of a system administrator and a user of the client.
5. The system of claim 1 , wherein the processor-based application further causes the processor to identify the amount of data changed for the client since the previous backup operation for the client in response to a determination that the amount of data changed does not meet the threshold requirement.
6. A computer-implemented method for initiating backups based on data changes, the method being executed by a computer processor and comprising:
identifying, by a daemon process running on a client computing device, at a time before a next scheduled operation for the client computing device, an amount of data changed since a previous backup operation by accessing, via a write tracking driver in communication with the daemon process, a block-based bitmap for data changes, wherein the write tracking driver identifies input and output operations associated with the client computing device and stores a record of the input and the output operations in the block-based bitmap;
determining, by the daemon process, whether the identified amount of data changed meets or exceeds a threshold requirement;
initiating, by the daemon process in communication with a backup/restore application over a network, a backup operation via the backup/restore application before the next scheduled backup operation for the client computing device when the identified amount of data changed meets or exceeds the threshold requirement;
monitoring the amount of data changed from the previous backup operation when the identified amount of data changed is below the threshold requirement, at least one of the amount of data changed or the threshold requirement being based on at least one of a total amount of data changed for the client, an amount of data changed for the client relative to a total amount of data for the client, or an amount of data changed for the client per a period of time; and
initiating a backup operation before the next scheduled backup operation for the client computing device when the monitored amount of data changed meets or exceeds the threshold requirement.
7. The method of claim 6 , wherein identifying the amount of data changed for the client since the previous backup operation for the client further includes identifying a plurality of time stamps corresponding to a plurality of files and comparing the plurality of time stamps to a time associated with the previous backup operation.
8. The method of claim 6 , wherein the client comprises a plurality of clients.
9. The method of claim 6 , wherein the threshold requirement is configurable by at least one of a system administrator and a user of the client.
10. The method of claim 6 , wherein the method further comprises identifying the amount of data changed for the client since the previous backup operation for the client in response to a determination that the amount of data changed does not meet the threshold requirement.
11. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein to be executed by one or more processors, the program code including instructions to:
identify, by a daemon process running on a client computing device, at a time before a next scheduled operation for the client computing device, an amount of data changed since a previous backup operation by accessing, via a write tracking driver in communication with the daemon process, a block-based bitmap for data changes, wherein the write tracking driver identifies input and output operations associated with the client computing device and stores a record of the input and the output operations in the block-based bitmap;
determine, by the daemon process, whether the identified amount of data changed meets or exceeds a threshold requirement;
initiate, by the daemon process in communication with a backup/restore application over a network, a backup operation via the backup/restore application before the next scheduled backup operation for the client computing device when the identified amount of data changed meets or exceeds the threshold requirement;
monitor the amount of data changed from the previous backup operation when the identified amount of data changed is below the threshold requirement, at least one of the amount of data changed or the threshold requirement being based on at least one of a total amount of data changed for the client, an amount of data changed for the client relative to a total amount of data for the client, or an amount of data changed for the client per a period of time; and
initiate a backup operation before the next scheduled backup operation for the client computing device when the monitored amount of data changed meets or exceeds the threshold requirement.
12. The computer program product of claim 11 , wherein identifying the amount of data changed for the client since the previous backup operation for the client further includes identifying a plurality of time stamps corresponding to a plurality of files and comparing the plurality of time stamps to a time associated with the previous backup operation.
13. The computer program product of claim 11 , wherein the client comprises a plurality of clients.
14. The computer program product of claim 11 , wherein the threshold requirement is configurable by at least one of a system administrator and a user of the client.