Techniques for backup management are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for backup management comprising the steps of receiving power level information from a backup client, determining a factor, based at least in part on the power level information, affecting a backup time window for the backup client, identifying a portion of data of the backup client for backup based on the determination, and providing an instruction to the backup client communicating the identified portion of data.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for backup management comprising the steps of: receiving power level information from a backup client; determining a factor, based at least in part on the power level information, affecting an amount of backup resources available during a backup time window for the backup client, wherein the factor includes at least an indication of an importance of one or more files; determining, based on the factor, at least one process to terminate on the backup client to reduce power consumption; identifying a portion of data of the backup client for backup, wherein a size of the portion of data is based on the factor; reducing processing required for the portion of data, wherein the reduction in processing comprises at least one of skipping encryption, skipping de-duplication, skipping compression, or skipping anti-virus scan; changing a backup checkpoint interval based at least in part on a power level of the power level information such that a first checkpoint interval when the power level is below a threshold level is more frequent than a second checkpoint interval when the power level is above the threshold level; and providing an instruction containing an indication of the at least one process to terminate and the identified portion of data to the backup client.
A backup management system optimizes backup processes based on client power levels. It receives power level information from a client device and determines a factor influencing available backup resources. This factor considers the importance of files and determines processes on the client to terminate to reduce power consumption. It identifies a portion of data for backup, adjusting its size based on the calculated factor. Processing requirements are reduced by skipping encryption, deduplication, compression, or anti-virus scanning. The system adjusts backup checkpoint intervals based on power level, increasing frequency when power is low. Finally, it sends an instruction to the client specifying processes to terminate and the data portion for backup.
2. The method of claim 1 , wherein the factor affecting a backup time window for the backup client comprises a remaining time the backup client is available for backup based on the power level information.
The backup management method described above, where the factor affecting available backup resources further includes the remaining time the backup client is available for backup as determined by its power level. Therefore, the system considers how long the client can be backed up based on its current power status when deciding how much and which data to backup.
3. The method of claim 1 , wherein the factor affecting a backup time window for the backup client comprises a network bandwidth measurement of a network link to the backup client.
The backup management method described above, where the factor affecting available backup resources further includes network bandwidth measurements to the backup client. The system assesses the network connection speed to the client to influence the backup strategy. Lower bandwidth might result in smaller backups or less frequent checkpointing to avoid overwhelming the network.
4. The method of claim 1 , wherein the factor affecting a backup time window for the backup client comprises at least one of a CPU load of a network element available to receive data from the backup client and disk resources of a network element available to receive data from the backup client.
The backup management method described above, where the factor affecting available backup resources further includes the CPU load and disk resources of the network element receiving the data from the backup client. The backup process adapts based on server-side constraints like CPU utilization or disk capacity on the backup server.
5. The method of claim 1 , wherein the factor affecting a backup time window for the backup client comprises a priority associated with data of the backup client.
The backup management method described above, where the factor affecting available backup resources further includes a priority associated with the data on the backup client. Critical data will be prioritized for backup even under low power conditions, potentially at the expense of backing up less important files.
6. The method of claim 1 , wherein the determination of the factor affecting the backup time window for the backup client comprises a comparison of the priority of a backup of the backup client with a backup priority of one or more other backup clients.
The backup management method described above, where determining the factor that affects available backup resources includes comparing the backup priority of the current backup client against the backup priorities of other clients. If other clients have higher priority, the current client may receive fewer resources or a smaller backup window.
7. The method of claim 6 , further comprising altering an amount of backup resources available for a backup client based on the comparison.
The backup management method described above, further comprising altering the amount of backup resources allocated to a backup client based on the comparison of backup priorities among multiple clients. The system dynamically adjusts resource allocation to different clients based on their relative backup importance.
8. The method of claim 1 , wherein the instruction comprises an instruction specifying a type of backup to perform.
The backup management method described above, where the instruction sent to the client specifies the type of backup to perform. This allows the backup server to dictate whether the client should perform a full, incremental, or differential backup.
9. The method of claim 8 , wherein the type of backup to perform comprises at least one of: a full backup, an incremental backup, and a differential backup.
The backup management method described above, where the type of backup to perform is selected from the group comprising a full backup, an incremental backup, and a differential backup. This provides flexibility in choosing the most appropriate backup type based on the client's power level and other factors.
10. The method of claim 1 , further comprising receiving data from the backup client.
The backup management method described above, further comprising receiving the identified data from the backup client. This confirms the system then retrieves the backed up data from the client device after sending the instruction.
11. An article of manufacture for backup management, the article of manufacture comprising: at least one non-transitory processor readable storage medium; and instructions stored on the at least one non-transitory processor readable storage medium; wherein the instructions are configured to be readable from the at least one non-transitory processor readable storage medium by at least one processor and thereby cause the at least one processor to operate so as to: receive power level information from a backup client; determine a factor, based at least in part on the power level information, affecting an amount of resources available during a backup time window for the backup client, wherein the factor includes at least an indication of an importance of one or more files; determine, based on the factor, at least one process to terminate on the backup client to reduce power consumption; identify a portion of data of the backup client for backup, wherein a size of the portion of data is based on the factor; reduce processing required for the portion of data, wherein the reduction in processing comprises at least one of skipping encryption, skipping de-duplication, skipping compression, or skipping anti-virus scan; change a backup checkpoint interval based at least in part on a power level of the power level information such that a first checkpoint interval when the power level is below a threshold level is more frequent than a second checkpoint interval when the power level is above the threshold level; and provide an instruction containing an indication of the at least one process to terminate and the identified portion of data to the backup client.
An article of manufacture (e.g. a software program) for backup management includes a non-transitory storage medium and instructions to: receive power level information from a client device; determine a factor influencing available backup resources considering the importance of files and determine processes on the client to terminate to reduce power consumption; identify a portion of data for backup, adjusting its size based on the factor; reduce processing requirements by skipping encryption, deduplication, compression, or anti-virus scanning; adjust backup checkpoint intervals based on power level, increasing frequency when power is low; and send an instruction to the client specifying processes to terminate and the data portion for backup.
12. A system for backup management comprising: memory; and one or more processors communicatively coupled to the memory; wherein the one or more processors are configured to: receive power level information from a backup client; determine a factor, based at least in part on the power level information, affecting an amount of backup resources available during a backup time window for the backup client, wherein the factor includes at least an indication of an importance of one or more files; determine, based on the factor, at least one process to terminate on the backup client to reduce power consumption; identify a portion of data of the backup client for backup, wherein a size of the portion of data is based on the factor; reduce processing required for the portion of data, wherein the reduction in processing comprises at least one of skipping encryption, skipping de-duplication, skipping compression, or skipping anti-virus scan; change a backup checkpoint interval based at least in part on a power level of the power level information such that a first checkpoint interval when the power level is below a threshold level is more frequent than a second checkpoint interval when the power level is above the threshold level; and provide an instruction containing an indication of the at least one process to terminate and the identified portion of data to the backup client communicating the identified portion of data.
A backup management system includes memory and one or more processors that: receive power level information from a client device; determine a factor influencing available backup resources considering the importance of files and determine processes on the client to terminate to reduce power consumption; identify a portion of data for backup, adjusting its size based on the factor; reduce processing requirements by skipping encryption, deduplication, compression, or anti-virus scanning; adjust backup checkpoint intervals based on power level, increasing frequency when power is low; and send an instruction to the client specifying processes to terminate and the data portion for backup.
13. The system of claim 12 , wherein the factor affecting a backup time window for the backup client comprises a remaining time the backup client is available for backup based on the power level information.
The backup management system described above, where the factor affecting available backup resources further includes the remaining time the backup client is available for backup as determined by its power level. Therefore, the system considers how long the client can be backed up based on its current power status when deciding how much and which data to backup.
14. The system of claim 12 , wherein the factor affecting a backup time window for the backup client comprises a network bandwidth measurement of a network link to the backup client.
The backup management system described above, where the factor affecting available backup resources further includes network bandwidth measurements to the backup client. The system assesses the network connection speed to the client to influence the backup strategy. Lower bandwidth might result in smaller backups or less frequent checkpointing to avoid overwhelming the network.
15. The system of claim 12 , wherein the factor affecting a backup time window for the backup client comprises at least one of a CPU load of a network element available to receive data from the backup client and disk resources of a network element available to receive data from the backup client.
The backup management system described above, where the factor affecting available backup resources further includes the CPU load and disk resources of the network element receiving the data from the backup client. The backup process adapts based on server-side constraints like CPU utilization or disk capacity on the backup server.
16. The system of claim 12 , wherein the determination of the factor affecting the backup time window for the backup client comprises a comparison of the priority of a backup of the backup client with a backup priority of one or more other backup clients.
The backup management system described above, where determining the factor that affects available backup resources includes comparing the backup priority of the current backup client against the backup priorities of other clients. If other clients have higher priority, the current client may receive fewer resources or a smaller backup window.
17. The system of claim 12 , wherein the instruction comprises an instruction specifying a type of backup to perform.
The backup management system described above, where the instruction sent to the client specifies the type of backup to perform. This allows the backup server to dictate whether the client should perform a full, incremental, or differential backup.
18. The system of claim 12 , wherein the one or more processors are further configured to receive data from the backup client.
The backup management system described above, where the one or more processors are further configured to receive the identified data from the backup client. This confirms the system then retrieves the backed up data from the client device after sending the instruction.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
January 4, 2010
June 20, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.