System and method for prioritizing backup generation
A production host includes storage for storing backup priorities of entities and backup windows during which a system, of which the production host is a member, is predicted to have sufficient computing resources to generate a backup for an entity of the entities and a backup manager that identifies a backup generation event for the entity; in response to identifying the backup generation event: identifying an earliest potential backup window of the backup windows; making a determination that the earliest potential backup window of the backup windows is reserved for a second entity of the entities; in response to making the determination: identifying that a backup priority of the backup priorities that is associated with the entity is greater than a second backup priority of the backup priorities that is associated with the second entity; and providing the backup services to the entity during the earliest potential backup window.
1. A production host for providing backup services to entities, comprising:
storage for storing:
backup priorities of the entities, and
backup windows during which a system, of which the production host is a member, is predicted to have sufficient computing resources to generate a backup for an entity of the entities; and
a backup manager programmed to:
identify a backup generation event for the entity;
in response to identifying the backup generation event:
identify an earliest potential backup window of the backup windows;
make a determination that the earliest potential backup window of the backup windows is reserved for a second entity of the entities;
in response to making the determination:
identify that a backup priority of the backup priorities that is associated with the entity is greater than a second backup priority of the backup priorities that is associated with the second entity; and
provide the backup services to the entity during the earliest potential backup window,
identify an occurrence of a priority change event associated with the entity; and
in response to identifying the occurrence of the priority change event, send a priority change notification to one or more other backup managers, the one or more other backup managers comprising a second backup manager associated with the second entity,
wherein the priority change notification specifies a change in the backup priority associated with the entity, and
wherein each of the backup manager and the one or more other backup managers maintains an independent copy of the backup priority.
2. The production host of claim 1 , wherein the backup manager is further programmed to:
in response to making the determination:
reserve the earliest potential backup window for the entity; and
send a conflict notification to the second entity,
wherein the conflict notification is adapted to cause a new backup window to be reserved for the second entity.
3. The production host of claim 1 , wherein the backup priorities of the entities are based, at least in part, on respective quantities of data associated with each of the entities that are in an unbacked up state.
4. The production host of claim 1 , wherein the backup priorities of the entities are based, at least in part, on types of workloads being performed by the entities.
5. The production host of claim 1 , wherein the backup generation event is a quantity of data associated with the entity that is in an unbacked up state exceeding a threshold.
6. The production host of claim 1 , wherein providing the backup services to the entity during the earliest potential backup window comprises:
generating a backup of the entity; and
storing a copy of the backup in a backup storage that is distinct from the production host.
7. A method for providing backup services to entities, comprising:
identifying a backup generation event for an entity;
in response to identifying the backup generation event:
identifying an earliest potential backup window of backup windows for providing the backup services;
making a determination that the earliest potential backup window of the backup windows is reserved for a second entity of the entities;
in response to making the determination:
identifying that a backup priority that is associated with the entity is greater than a second backup priority that is associated with the second entity; and
providing the backup services to the entity during the earliest potential backup window;
identifying an occurrence of a priority change event associated with the entity;
in response to identifying the occurrence of the priority change event, sending a priority change notification to one or more other backup managers, the one or more other backup managers comprising a second backup manager associated with the second entity,
wherein the priority change notification specifies a change in the backup priority associated with the entity, and
wherein each of the backup manager and the one or more other backup managers maintains an independent copy of the backup priority.
8. The method of claim 7 , wherein method further comprises:
in response to making the determination:
reserving the earliest potential backup window for the entity; and
sending a conflict notification to the second entity,
wherein the conflict notification is adapted to cause a new backup window to be reserved for the second entity.
9. The method of claim 7 , wherein the backup priority and the second backup priority are based, at least in part, on quantities of data associated with the entity and the second entity, respectively, that are in an unbacked up state.
10. The method of claim 7 , wherein the backup priority and the second backup priority are based, at least in part, on types of workloads being performed by the entity and the second entity, respectively.
11. The method of claim 7 , wherein the backup generation event is a quantity of data associated with the entity that is in an unbacked up state exceeding a threshold.
12. The method of claim 7 , wherein providing the backup services to the entity during the earliest potential backup window comprises:
generating a backup of the entity; and
storing a copy of the backup in a backup storage that is distinct from a production host that generated the backup of the entity.
13. 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:
identifying a backup generation event for an entity;
in response to identifying the backup generation event:
identifying an earliest potential backup window of backup windows for providing the backup services;
making a determination that the earliest potential backup window of the backup windows is reserved for a second entity of the entities;
in response to making the determination:
identifying that a backup priority that is associated with the entity is greater than a second backup priority that is associated with the second entity; and
providing the backup services to the entity during the earliest potential backup window;
identifying an occurrence of a priority change event associated with the entity; and
in response to identifying the occurrence of the priority change event, sending a priority change notification to one or more other backup managers, the one or more other backup managers comprising a second backup manager associated with the second entity,
wherein the priority change notification specifies a change in the backup priority associated with the entity, and
wherein each of the backup manager and the one or more other backup managers maintains an independent copy of the backup priority.
14. The non-transitory computer readable medium of claim 13 , wherein method further comprises:
in response to making the determination:
reserving the earliest potential backup window for the entity; and
sending a conflict notification to the second entity,
wherein the conflict notification is adapted to cause a new backup window to be reserved for the second entity.
15. The non-transitory computer readable medium of claim 13 , wherein the backup priority and the second backup priority are based, at least in part, on quantities of data associated with the entity and the second entity, respectively, that are in an unbacked up state.
16. The non-transitory computer readable medium of claim 13 , wherein the backup priority and the second backup priority are based, at least in part, on types of workloads being performed by the entity and the second entity, respectively.
17. The non-transitory computer readable medium of claim 13 , wherein the backup generation event is a quantity of data associated with the entity that is in an unbacked up state exceeding a threshold.