Allocating and managing cloud computing resources for disaster recovery
View Patent ↗A method, executed by a computer, for allocating resources includes assigning resiliency attributes to a server having a workload, linking each server to a partner resource, duplicating the workload of each server in an offsite location accessible to the partner resource, detecting a disaster event, and transferring the workload of the server automatically to the partner resource. In some embodiments, the partner resource is a plurality of pool servers. The partner resource may be calculated by performing a capacity analysis. The partner resource may not a specifically assigned resource until a disaster occurs. In some embodiments, the workload is duplicated such that the recovery point objective of the workload is minimized. A computer program product and computer system corresponding to the methods are also disclosed herein.
1. A method of allocating resources, the method comprising:
assigning a plurality of resiliency attributes to each server of a plurality of servers at a server site, wherein each server has a server workload, and wherein the plurality of resiliency attributes include one or more of a mirroring attribute, a backup attribute, a storage availability attribute, a consistency group attribute, and a service level agreement attribute;
linking each server to at least one partner resource of a plurality of partner resources using a central provisioning engine, wherein the plurality of partner resources include at least one idle partner resource that has no workload and at least one preempt partner resource that has a preempt partner resource workload, and wherein the central provisioning engine determines whether each server is partnered with an idle partner resource or a preempt partner resource according to the server's resiliency attributes and the server's server workload;
determining that there is a disaster at the server site; and
responsive to determining that there is a disaster at the server site, transferring the server workload of each server on its corresponding partner resource, wherein transferring the server workload of a server whose partner resource is an idle partner resource comprises the idle partner resource assuming the server workload, and wherein transferring the server workload of a server whose partner resource is a preempt partner resource comprises the preempt partner resource abandoning its preempt partner resource workload in favor of the server workload.
2. The method of claim 1 , wherein the partner resource comprises a plurality of pool servers.
3. The method of claim 1 , wherein the partner resource is calculated by performing a capacity analysis using a central provisioning engine.
4. The method of claim 1 , wherein the partner resource is not a specifically assigned resource until a disaster occurs.
5. The method of claim 1 , wherein duplicating the server workload further comprises reducing a recovery point objective of the server workload by not confirming a write-to-disk as complete until the write-to-disk is written to at least two logical storage units, wherein the at least two logical storage units are not local to each other.
6. A computer program product for allocating resources, the computer program product comprising:
a computer readable storage medium and program instructions stored on the computer readable storage medium, the program instructions comprising instructions to:
assign a plurality of resiliency attributes to each server of a plurality of servers at a server site, wherein each server has a server workload, and wherein the plurality of resiliency attributes include one or more of a mirroring attribute, a backup attribute, a storage availability attribute, a consistency group attribute, and a service level agreement attribute;
link each server to at least one partner resource of a plurality of partner resources using a central provisioning engine, wherein the plurality of partner resources include at least one idle partner resource that has no workload and at least one preempt partner resource that has a preempt partner resource workload, and wherein the central provisioning engine determines whether each server is partnered with an idle partner resource or a preempt partner resource according to the server's resiliency attributes and the server's server workload;
determine that there is a disaster at the server site; and
responsive to determining that there is a disaster at the server site, transfer the server workload of each server on its corresponding partner resource, wherein transferring the server workload of a server whose partner resource is an idle partner resource comprises the idle partner resource assuming the server workload, and wherein transferring the server workload of a server whose partner resource is a preempt partner resource comprises the preempt partner resource abandoning its preempt partner resource workload in favor of the server workload.
7. The computer program product of claim 6 , wherein the partner resource comprises a plurality of pool servers.
8. The computer program product of claim 6 , wherein the partner resource is calculated by performing a capacity analysis using a central provisioning engine.
9. The computer program product of claim 6 , wherein the partner resource is not a specifically assigned resource until a disaster occurs.
10. The computer program product of claim 6 , wherein the instructions to duplicate the server workload further comprise instructions to reduce a recovery point objective of the server workload by not confirming a write-to-disk as complete until the write-to-disk is written to at least two logical storage units, wherein the at least two logical storage units are not local to each other.
11. A computer system for allocating resources, the computer system comprising:
one or more computer processors;
one or more computer readable storage media; program instructions stored therein for execution by at least one of the one or more computer processors, the program instructions comprising instructions to:
assign a plurality of resiliency attributes to each server of a plurality of servers at a server site, wherein each server has a server workload, and wherein the plurality of resiliency attributes include one or more of a mirroring attribute, a backup attribute, a storage availability attribute, a consistency group attribute, and a service level agreement attribute;
link each server to at least one partner resource of a plurality of partner resources using a central provisioning engine, wherein the plurality of partner resources include at least one idle partner resource that has no workload and at least one preempt partner resource that has a preempt partner resource workload, and wherein the central provisioning engine determines whether each server is partnered with an idle partner resource or a preempt partner resource according to the server's resiliency attributes and the server's server workload;
determine that there is a disaster at the server site; and
responsive to determining that there is a disaster at the server site, transfer the server workload of each server on its corresponding partner resource, wherein transferring the server workload of a server whose partner resource is an idle partner resource comprises the idle partner resource assuming the server workload, and wherein transferring the server workload of a server whose partner resource is a preempt partner resource comprises the preempt partner resource abandoning its preempt partner resource workload in favor of the server workload.
12. The computer system of claim 11 , wherein the partner resource is calculated by performing a capacity analysis using a central provisioning engine.
13. The computer system of claim 11 , wherein the partner resource is not a specifically assigned resource until a disaster occurs.
14. The computer system of claim 11 , wherein the instructions to duplicate the server workload further comprise instructions to reduce a recovery point objective of the server workload by not confirming a write-to-disk as complete until the write-to-disk is written to at least two logical storage units.