Application migration between environments

A system for failover and failback of an application between a primary compute infrastructure and a secondary compute infrastructure, the system comprising:

• one or more processors;
• a memory including machine-readable instructions which, when executed by the one or more processors, causes the system to perform operations comprising, at least:
• generating primary snapshots of virtual machines of the application in the primary compute infrastructure before the failover at a frequency defined by a service level agreement;
• transferring the primary snapshots to the secondary compute infrastructure for deployment as virtual machines in the secondary compute infrastructure;
• receiving secondary snapshots of the virtual machines of the application in the secondary compute infrastructure, the secondary snapshots being generated during the failover from the primary compute infrastructure to the secondary compute infrastructure at the frequency defined by the service level agreement, wherein a first data management and storage (DMS) cluster is coupled to the primary compute infrastructure to generate the primary snapshots and a second DMS cluster is coupled to the secondary compute infrastructure to generate the secondary snapshots, and wherein the frequency for generating the primary and secondary snapshots is shared by the first DMS cluster and the second DMS cluster;
• initiating the failback from the secondary compute infrastructure to the primary compute infrastructure;
• constructing a current state of the application by combining the primary snapshots generated before the failover and the secondary snapshots generated during the failover;
• and
• deploying the application in the current state by deploying virtual machines on the primary compute infrastructure.

A non-transitory computer-readable medium comprising instructions that when executed by a processor configures the processor to perform operations including:

• generating primary snapshots of virtual machines of the application in the primary compute infrastructure before the failover at a frequency defined by a service level agreement;
• transferring the primary snapshots to the secondary compute infrastructure for deployment as virtual machines in the secondary compute infrastructure;
• receiving secondary snapshots of the virtual machines of the application in the secondary compute infrastructure, the secondary snapshots being generated during the failover from the primary compute infrastructure to the secondary compute infrastructure at the frequency defined by the service level agreement, wherein a first data management and storage (DMS) cluster is coupled to the primary compute infrastructure to generate the primary snapshots and a second DMS cluster is coupled to the secondary compute infrastructure to generate the secondary snapshots, and wherein the frequency for generating the primary and secondary snapshots is shared by the first DMS cluster and the second DMS cluster;
• initiating the failback from the secondary compute infrastructure to the primary compute infrastructure;
• constructing a current state of the application by combining the primary snapshots generated before the failover and the secondary snapshots generated during the failover;
• and
• deploying the application in the current state by deploying virtual machines on the primary compute infrastructure.