Cloud restart for vm failover and capacity management

Patent metadata

Field	Value
Publication number	US-2021224168-A1
Application number	US-202016744876-A
Country	US
Kind code	A1
Filing date	Jan 16, 2020
Priority date	Jan 16, 2020
Publication date	Jul 22, 2021
Grant date	—

Abstract

A method of restarting a virtual machine (VM) running in a cluster in a first data center, in a second data center, includes: transmitting images of VMs, including a first VM, running in the cluster of hosts at a first point in time to the second data center for replication in the second data center; generating difference data representing a difference in an image of the first VM at a second point in time and the image of the first VM at the first point in time; transmitting the difference data to the second data center; setting the first VM to be inactive in the first data center; and communicating with a control plane in the second data center to set as active, and power on, a VM in the second data center using the replicated image of the first VM updated with the difference data.

First claim

We claim:

1 . A method of restarting a virtual machine running in a cluster of hosts in a first data center, in a second data center, the method comprising:
(a) transmitting images of virtual machines, including a first virtual machine, running in the cluster of hosts at a first point in time to the second data center for replication in the second data center; (b) generating difference data representing a difference in an image of the first virtual machine at a second point in time and the image of the first virtual machine at the first point in time; (c) transmitting the difference data to the second data center; (d) setting the first virtual machine to be inactive in the first data center; and (e) communicating with a control plane in the second data center to set as active, and power on, a virtual machine in the second data center using the replicated image of the first virtual machine after updating the replicated image using the difference data.

2 . The method of claim 1 , wherein the cluster of hosts is not assigned a spare host in the first data center.

3 . The method of claim 1 , wherein the first data center is an on-premise data center serving one tenant and the second data center is a cloud data center serving a plurality of tenants.

4 . The method of claim 1 , wherein steps (b) through (e) are carried out upon detecting that one of the hosts in the cluster of hosts has failed and determining that no other hosts in the cluster of hosts has sufficient resources to run the first virtual machine therein.

5 . The method of claim 4 , further comprising:
after setting the first virtual machine to be inactive in the first data center, upon detecting that sufficient resources have been freed up in one of the hosts in the cluster of hosts to run the first virtual machine therein, notifying the control plane in the second data center that the sufficient resources have been freed up.

6 . The method of claim 5 , further comprising:
updating the image of the first virtual machine with data received from the second data center in response to said notifying; and setting as active, and powering on, the first virtual machine using the updated image of the first virtual machine.

7 . The method of claim 1 , wherein steps (b) through (e) are carried out for all of the virtual machines running in one of the hosts in the cluster of hosts that has failed.

8 . The method of claim 1 , wherein the second data center is a disaster recovery data center and step (a) is repeated according to a recovery point objective that is set for the cluster of hosts.

9 . The method of claim 7 , wherein steps (b) through (e) are carried out for all of the virtual machines running in the cluster of hosts according to a recovery time objective that has been set for the cluster of hosts.

10 . A computer system comprising:
a memory configured to store executable code for remotely accessing a console of a virtual machine (VM) running in a host; and a processor configured to execute the code to: (a) transmit images of virtual machines, including a first virtual machine, running in the cluster of hosts at a first point in time to the second data center for replication in the second data center; (b) generate difference data representing a difference in an image of the first virtual machine at a second point in time and the image of the first virtual machine at the first point in time; (c) transmit the difference data to the second data center; (d) sett the first virtual machine to be inactive in the first data center; and (e) communicate with a control plane in the second data center to set as active, and power on, a virtual machine in the second data center using the replicated image of the first virtual machine after updating the replicated image using the difference data.

11 . The computer system of claim 10 , wherein the cluster of hosts is not assigned a spare host in the first data center.

12 . The computer system of claim 10 , wherein the first data center is an on-premise data center serving one tenant and the second data center is a cloud data center serving a plurality of tenants.

13 . The computer system of claim 10 , wherein steps (b) through (e) are carried out upon detecting that one of the hosts in the cluster of hosts has failed and determining that no other hosts in the cluster of hosts has sufficient resources to run the first virtual machine therein.

14 . The computer system of claim 13 , wherein the processor is further configured to execute the code to:
after the first virtual machine is set to be inactive in the first data center, upon detecting that sufficient resources have been freed up in one of the hosts in the cluster of hosts to run the first virtual machine therein, notify the control plane in the second data center that the sufficient resources have been freed up.

15 . The computer system of claim 15 , wherein the processor is further configured to execute the code to:
update the image of the first virtual machine with data received from the second data center in response to said notifying; and set as active, and powering on, the first virtual machine using the updated image of the first virtual machine.

16 . The computer system of claim 10 , wherein steps (b) through (e) are carried out for all of the virtual machines running in one of the hosts in the cluster of hosts that has failed.

17 . The computer system of claim 10 , wherein the second data center is a disaster recovery data center and step (a) is repeated according to a recovery point objective that is set for the cluster of hosts.

18 . The computer system of claim 17 , wherein steps (b) through (e) are carried out for all of the virtual machines running in the cluster of hosts according to a recovery time objective that has been set for the cluster of hosts.

19 . A non-transitory computer-readable medium storing code for causing, when executed by a processor, restarting of a virtual machine running in a cluster of hosts in a first data center, to a second data center, the processor when executing the code performing the steps of:
(a) transmitting images of virtual machines, including a first virtual machine, running in the cluster of hosts at a first point in time to the second data center for replication in the second data center; (b) generating difference data representing a difference in an image of the first virtual machine at a second point in time and the image of the first virtual machine at the first point in time; (c) transmitting the difference data to the second data center; (d) setting the first virtual machine to be inactive in the first data center; and (e) communicating with a control plane in the second data center to set as active, and power on, a virtual machine in the second data center using the replicated image of the first virtual machine after updating the replicated image using the difference data.

20 . The non-transitory computer-readable medium of claim 19 , wherein the cluster of hosts is not assigned a spare host in the first data center.

Assignees

• Vmware Inc

Inventors

• Agarwal Anant
• Chandrasekaran Rahul
• Desai Aalap
• Nair Vikram
• Pan Zhelong

Classifications

• G06F11/1451

  by selection of backup contents · CPC title

• G06F11/1469

  Backup restoration techniques · CPC title

• G06F2201/815

  Virtual · CPC title

• G06F11/2028

  eliminating a faulty processor or activating a spare · CPC title

• G06F11/2025 Primary

  using centralised failover control functionality · CPC title