US 11,669,409 B2
Application migration between environments
Zhicong Wang, San Francisco, CA (US); Benjamin Meadowcroft, San Jose, CA (US); Biswaroop Palit, Mountain View, CA (US); Atanu Chakraborty, New Delhi (IN); Hardik Vohra, Mountain View, CA (US); Abhay Mitra, Bangalore Karnataka (IN); Saurabh Goyal, Bangalore Karnataka (IN); Sanjari Srivastava, Bangalore Karnataka (IN); Swapnil Agarwal, Bangalore Karnataka (IN); Rahil Shah, Mumbai (IN); Mudit Malpani, Mountain View, CA (US); Janmejay Singh, Bangalore Karnataka (IN); Ajay Arvind Bhave, Bangalore Karnataka (IN); and Prateek Pandey, Santa Clara, CA (US)
Assigned to Rubrik, Inc., Palo Alto, CA (US)
Filed by Rubrik, Inc., Palo Alto, CA (US)
Filed on Oct. 22, 2019, as Appl. No. 16/660,262.
Application 16/660,262 is a continuation of application No. 16/018,013, filed on Jun. 25, 2018, granted, now 10,503,612.
Prior Publication US 2020/0050518 A1, Feb. 13, 2020
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 11/14 (2006.01); G06F 9/455 (2018.01); G06F 11/20 (2006.01)
CPC G06F 11/1469 (2013.01) [G06F 9/45558 (2013.01); G06F 11/203 (2013.01); G06F 11/2023 (2013.01); G06F 2009/45575 (2013.01); G06F 2201/84 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method for failover and failback of an application between a primary compute infrastructure and a secondary compute infrastructure, the method comprising:
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.