# US 2021/0342226 A1 · Iterative integer programming with load balance for cyclic workloads

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0342226 A1
- Document ID: US20210342226A1
- Status: Published application
- Kind: A1
- Application number: 16/862,561
- Filed: 2020-04-29
- Published: 2021-11-04
- Earliest claimed: 2020-04-29
- Assignees: EMC IP Holding Company LLC
- Applicants: EMC IP Holding Company LLC
- Inventors: Hugo de Oliveira Barbalho; Tiago Salviano Calmon; Eduardo Vera Sousa
- Web page: https://patentgrep.com/patent/US20210342226A1

## CPC

- G06F 11/1461: {Backup scheduling policy}
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/065: {Replication mechanisms}
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 9/505: {considering the load}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1453: {using de-duplication of the data}
- G06F 11/1464: {for networked environments}
- G06F 11/1466: {to make the backup process non-disruptive}
- G06F 11/1469: {Backup restoration techniques}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A backup orchestrator for providing backup services to entities includes storage for storing recovery point objectives for the entities and a backup manager. The backup manager selects an optimization periodicity based a number of backups to be generated to meet a portion of the recovery point objectives; makes a determination that at least one of the portion of the recovery point objectives has a maximum allowable unbacked up period of time that is greater than the optimization periodicity; in response to the determination: load balances the number of backups across multiple optimization periods, based on the optimization periodicity, of a balanced backup schedule; selects a backup generation time for each of the to be generated backups in each of the optimization periods of the balanced backup schedule; and generates the number of backups using the balanced backup schedule.

## Claims

### Claim 1

A backup orchestrator for providing backup services to entities, comprising:
storage for storing recovery point objectives for the entities; and
a backup manager programmed to:
select an optimization periodicity based a number of backups to be generated to meet a portion of the recovery point objectives;
make a determination that at least one of the portion of the recovery point objectives has a maximum allowable unbacked up period of time that is greater than the optimization periodicity;
in response to the determination:
load balance the number of backups across multiple optimization periods, based on the optimization periodicity, of a balanced backup schedule;
select a backup generation time for each of the to be generated backups in each of the optimization periods of the balanced backup schedule; and
generate the number of backups using the balanced backup schedule.

### Claim 2 (depends on 1)

The backup orchestrator of claim 1, wherein the backup manager is further programmed to:
select a second optimization periodicity based a second number of backups to be generated to meet a second portion of the recovery point objectives;
make a determination that none of the second portion of the recovery point objectives has a maximum allowable unbacked up period of time that is greater than the second optimization periodicity;
in response to the determination:
add each backup to each optimization period of an unbalanced backup schedule;
select a backup generation time for each of the second number of backups in each of the optimization periods of the unbalanced backup schedule; and
generate the second number of backups using the unbalanced backup schedule.

### Claim 3 (depends on 1)

The backup orchestrator of claim 1, wherein load balancing the number of backups across multiple optimization periods of the balanced backup schedule comprises:
constraining the number of backups to placement across the multiple optimization periods based on, in part, a limit on a total duration for backup generation during each of the multiple optimization periods to obtain a backup periodization of the number of backups; and
adding backups of the number of backups to the respective periods of the balanced backup schedule based on the backup periodization.

### Claim 4 (depends on 3)

The backup orchestrator of claim 3, wherein the placements of the number of backups are further constrained based, in part, on a second limit on which backup storages, used to store the number of backups, can store the number of backups.

### Claim 5 (depends on 4)

The backup orchestrator of claim 4, wherein the second limit is adapted to aggregate a portion of the number of backups that are likely to include data that is duplicative of existing data stored in a backup storage of the backup storages.

### Claim 6 (depends on 3)

The backup orchestrator of claim 3, wherein the placements of the number of backups are further constrained based, in part, on times required to generate the number of backups.

### Claim 7 (depends on 3)

The backup orchestrator of claim 3, wherein the placements of the number of backups are further constrained based, in part, on maximum allowable unbacked up periods of time for the number of backups.

### Claim 8

A method for providing backup services to entities, comprising:
selecting an optimization periodicity based a number of backups to be generated to meet a portion of recovery point objectives associated with the number of backups;
making a determination that at least one of the portion of the recovery point objectives has a maximum allowable unbacked up period of time that is greater than the optimization periodicity;
in response to the determination:
load balancing the number of backups across multiple optimization periods of a balanced backup schedule demarcated by the optimization periodicity;
selecting a backup generation time for each of the to be generated backups in each of the optimization periods of the balanced backup schedule; and
generating the number of backups using the balanced backup schedule.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
selecting a second optimization periodicity based a second number of backups to be generated to meet a second portion of the recovery point objectives;
making a determination that none of the second portion of the recovery point objectives has a maximum allowable unbacked up period of time that is greater than the second optimization periodicity;
in response to the determination:
adding each backup to each optimization period of an unbalanced backup schedule;
selecting a backup generation time for each of the second number of backups in each of the optimization periods of the unbalanced backup schedule; and
generating the second number of backups using the unbalanced backup schedule.

### Claim 10 (depends on 8)

The method of claim 8, wherein load balancing the number of backups across multiple optimization periods of the balanced backup schedule comprises:
constraining the number of backups to placement across the multiple optimization periods based on, in part, a limit on a total duration for backup generation during each of the multiple optimization periods to obtain a backup periodization of the number of backups; and
adding backups of the number of backups to the respective periods of the balanced backup schedule based on the backup periodization.

### Claim 11 (depends on 10)

The method of claim 10, wherein the placements of the number of backups are further constrained based, in part, on a second limit on which backup storages, used to store the number of backups, can store the number of backups.

### Claim 12 (depends on 11)

The method of claim 11, wherein the second limit is adapted to aggregate a portion of the number of backups that are likely to include data that is duplicative of existing data stored in a backup storage of the backup storages.

### Claim 13 (depends on 10)

The method of claim 10, wherein the placements of the number of backups are further constrained based, in part, on times required to generate the number of backups.

### Claim 14 (depends on 10)

The method of claim 10, wherein the placements of the number of backups are further constrained based, in part, on maximum allowable unbacked up periods of time for the number of backups.

### Claim 15

A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for providing backup services to entities, the method comprising:
selecting an optimization periodicity based a number of backups to be generated to meet a portion of recovery point objectives associated with the number of backups;
making a determination that at least one of the portion of the recovery point objectives has a maximum allowable unbacked up period of time that is greater than the optimization periodicity;
in response to the determination:
load balancing the number of backups across multiple optimization periods of a balanced backup schedule demarcated by the optimization periodicity;
selecting a backup generation time for each of the to be generated backups in each of the optimization periods of the balanced backup schedule; and
generating the number of backups using the balanced backup schedule.

### Claim 16 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the method further comprises:
selecting a second optimization periodicity based a second number of backups to be generated to meet a second portion of the recovery point objectives;
making a determination that none of the second portion of the recovery point objectives has a maximum allowable unbacked up period of time that is greater than the second optimization periodicity;
in response to the determination:
adding each backup to each optimization period of an unbalanced backup schedule;
selecting a backup generation time for each of the second number of backups in each of the optimization periods of the unbalanced backup schedule; and
generating the second number of backups using the unbalanced backup schedule.

### Claim 17 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein load balancing the number of backups across multiple optimization periods of the balanced backup schedule comprises:
constraining the number of backups to placement across the multiple optimization periods based on, in part, a limit on a total duration for backup generation during each of the multiple optimization periods to obtain a backup periodization of the number of backups; and
adding backups of the number of backups to the respective periods of the balanced backup schedule based on the backup periodization.

### Claim 18 (depends on 17)

The non-transitory computer readable medium of claim 17, wherein the placements of the number of backups are further constrained based, in part, on a second limit on which backup storages, used to store the number of backups, can store the number of backups.

### Claim 19 (depends on 18)

The non-transitory computer readable medium of claim 18, wherein the second limit is adapted to aggregate a portion of the number of backups that are likely to include data that is duplicative of existing data stored in a backup storage of the backup storages.

### Claim 20 (depends on 17)

The non-transitory computer readable medium of claim 17, wherein the placements of the number of backups are further constrained based, in part, on times required to generate the number of backups.
