Virtual machine cluster backup in a multi-node environment

• US 9,411,628 B2
• Filed: 11/13/2014
• Issued: 08/09/2016
• Est. Priority Date: 11/13/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Bezbaruah, Angshuman, Reuther, Lars, Brown, Taylor O'Neil
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US14/540,640
• Publication Number:
  US 20160139943A1
• Time in Patent Office: 635 Days
• Field of Search: 718/1, 718100-109
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1484 involving virtual machines
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Embodiments are directed to backing up a virtual machine cluster and to determining virtual machine node ownership prior to backing up a virtual machine cluster. In one scenario, a computer system determines which virtual machines nodes are part of the virtual machine cluster, determines which shared storage resources are part of the virtual machine cluster and determines which virtual machine nodes own the shared storage resources. The computer system then indicates to the virtual machine node owners that at least one specified application is to be quiesced over the nodes of the virtual machine cluster, such that a consistent, cluster-wide checkpoint can be created. The computer system further creates a cluster-wide checkpoint which includes a checkpoint for each virtual machine in the virtual machine cluster.

Claims

1. At a computer system including at least one processor, a computer-implemented method for backing up a virtual machine cluster, the method comprising:

determining a plurality of virtual machine nodes that are part of the virtual machine cluster;

determining one or more shared storage resources that are part of the virtual machine cluster;

determining which of the virtual machine nodes owns each of the shared storage resources;

indicating to each of the virtual machine nodes that is an owner of a shared storage resource that at least one specified application is to be quiesced over the nodes of the virtual machine cluster, such that a consistent, cluster-wide checkpoint can be created; and

initiating the creation of a cluster-wide checkpoint which includes a checkpoint for each virtual machine node in the virtual machine cluster, wherein the cluster-wide checkpoint includes at least one instance of each shared storage resource in the virtual machine cluster.

2. The method of claim 1, wherein a virtualization agent is instantiated on each virtual machine.

3. The method of claim 2, wherein the virtualization agent determines current ownership of shared storage resources within the virtual machine cluster.

4. The method of claim 2, wherein the virtualization agent communicates with a host operating system using a secure, private guest-host communication channel.

5. The method of claim 1, wherein upon failover due to node failure, ownership of a shared storage resource is moved to another virtual machine node within the virtual machine cluster.

6. The method of claim 1, wherein the owning virtual machine node of a shared storage resource quiesces one or more applications running on the shared storage resource and creates a checkpoint for that shared storage resource.

7. The method of claim 6, wherein the owning virtual machine node owns a plurality of shared storage resources, and creates checkpoints for each of the plurality of shared storage resources that it owns.

8. The method of claim 1, wherein at least one of the virtual machine nodes has its own private, non-shared storage resource, and wherein the at least one virtual machine node having its own private, non-shared storage resource creates a checkpoint for its private, non-shared storage.

9. The method of claim 1, wherein a non-owning virtual machine node that does not own a specified shared storage resource communicates with the shared storage resource'"'"'s owner to quiesce a given application.

10. The method of claim 1, wherein a shared storage resource owner implements hard disk reservations to maintain consistent state on a shared hard disk.

11. At a computer system including at least one processor, a computer-implemented method for determining virtual machine node ownership prior to backing up a virtual machine cluster, the method comprising:

determining that ownership has changed for at least one shared storage resource within a virtual machine cluster;

identifying at least one potential new owner of the at least one shared storage resource;

determining which of the one or more virtual machine nodes owns each shared storage resource within the virtual machine cluster;

indicating to each of the virtual machine nodes that is an owner of a shared storage resource that at least one specified application is to be quiesced over the nodes of the virtual machine cluster, such that a consistent, cluster-wide checkpoint can be created; and

initiating the creation of the cluster-wide virtual machine checkpoint which includes checkpoints for each shared storage resource in the virtual machine cluster, wherein the cluster-wide checkpoint includes at least one instance of each shared storage resource in the virtual machine cluster.

12. The method of claim 11, wherein the change in ownership results from failover due to failure of a previous shared storage resource owner.

13. The method of claim 11, wherein the shared storage resource owner has exclusive access to the shared storage resource, or has shared access to the shared storage resource wherein access is regulated according to an access policy.

14. The method of claim 11, wherein the shared storage resource is part of a host computing node or is accessed through the host computing node.

15. The method of claim 11, wherein a virtualization agent is instantiated on each virtual machine, the virtualization agent being configured to determine shared storage resource ownership and ensure consistency among checkpoints.

16. The method of claim 11, wherein a non-owning virtual machine node determines the current owner for a given shared storage resource and allows the current owner to quiesce one or more applications running on the non-owning virtual machine node.

17. A computer system comprising the following:

one or more processors; and

one or more computer-readable storage media having stored thereon computer-executable instructions that are executable by the one or more processors to cause the computer system to back up a virtual machine cluster, the computer-executable instructions including instructions that are executable by the one or more processors to cause the computer system to perform at least the following;

determine a plurality of virtual machine nodes that are part of the virtual machine cluster;

determine one or more shared storage resources that are part of the virtual machine cluster;

determine which of the virtual machine nodes owns each of the shared storage resources;

indicate to each of the virtual machine nodes that is an owner of a shared storage resource that at least one specified application is to be quiesced over the nodes of the virtual machine cluster, such that a consistent, cluster-wide checkpoint can be created; and

initiate the creation of the cluster-wide checkpoint which includes a checkpoint for each virtual machine in the virtual machine cluster, wherein the cluster-wide checkpoint includes at least one single instance of each shared storage resource in the virtual machine cluster.

18. The computer system of claim 17, wherein a virtual machine node'"'"'s guest operating system initiates the creation of a checkpoint for the virtual machine node.

19. The computer system of claim 18, the computer-executable instructions also including instructions that are executable by the one or more processors to cause the computer system to analyze one or more virtual machine nodes in the virtual machine cluster to determine whether the virtual machine nodes have experienced failure and, upon determining that at least one virtual machine node has failed, initiate an analysis to determine whether the virtual machine node'"'"'s failure has affected shared storage node ownership within the virtual machine cluster.