Virtual machine proxy server for hyper-V image backup and recovery

• US 10,417,027 B1
• Filed: 09/28/2012
• Issued: 09/17/2019
• Est. Priority Date: 03/30/2012
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Earl, Min-Chih Lu, Bishop, Brian, Gruszka, Jerzy, Buchman, Matthew D.
• Primary Examiner(s): An, Meng Ai T
• Assistant Examiner(s): Do, Steven M
• Application Number:
  US13/631,238
• Time in Patent Office: 2,545 Days
• Field of Search: 718 1
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455

Abstract

A snapshot of a remote virtual machine within a cluster of nodes is taken by using an image writer with a snapshot provider. A set of backup components is recorded by using a cluster interface. The remote virtual machine is reconstructed by using the snapshot and a framework with the set of backup components.

Claims

1. A method, comprising:

taking a snapshot of a remote virtual machine within a cluster of nodes by using an image writer with a snapshot provider, wherein;

the image writer is a part of Microsoft Windows Server 2012 infrastructure; and

the snapshot provider is a part of Microsoft Windows Server 2012 infrastructure;

determining whether the remote virtual machine is running on a node proxy;

selecting the image writer as a hypervisor volume shadow copy service (“

VSS”

) writer if the remote virtual machine is running on the node proxy, if the remote virtual machine is running on a node other than the node proxy select the image writer as a cluster shared volume VSS writer;

recording a set of backup components by using a cluster interface, wherein;

the cluster interface is a part of Microsoft Windows Server 2012 infrastructure; and

the set of backup components comprises metadata described in a backup session that contains the necessary information for local restore operations;

playing back the set of backup components taken from the snapshot of the remote virtual machine, to simulate a restore operation as if it were to be on a local machine;

reconstructing the remote virtual machine, by using both (1) the snapshot and (2) a windows management instrumentation (WMI) framework with the set of backup components based at least in part on the simulation of the local restore operation simulation, wherein the WMI framework is operable with Microsoft Windows Server 2012; and

using the WMI framework to enable the remote virtual machine as a cluster-wide virtual machine.

2. The method of claim 1, further comprising provisioning the node proxy from amongst the cluster of nodes to restore the remote virtual machine.

3. The method of claim 2, wherein the node proxy may be one or more of:

a physical node within the cluster of nodes;

a proxy virtual machine on a node within the cluster of nodes; and

a proxy virtual machine on a node on a different cluster.

4. The method of claim 2, wherein the cluster is a Microsoft Windows Server 2012 Cluster.

5. The method of claim 3, wherein the remote virtual machine does not have one or more of:

a restore agent;

a backup client; and

dedicated backup software.

6. The method of claim 5, where in the snapshot provider was originally configured to take a VM snapshot in order for a local node to restore the snapshot locally.

7. The method of claim 6, where in the snapshot is one or more of:

a copy-on-write snapshot;

a VM snapshot; and

a shadow snapshot.

8. The method of claim 7, where in the snapshot provider is a cluster shared volume (“

CSV”

) shadow copy provider.

9. The method of claim 8, further comprising deduplicating the snapshot using a deduplication engine.

10. The method of claim 9, wherein the set of backup components comprises virtual machine configuration metadata and data files.

11. The method of claim 10, wherein the cluster interface is one or more of:

a VSS cluster writer;

the WMI API; and

the WMI with a shell.

12. The method of claim 11, wherein the framework is the WMI management API.

13. The method of claim 12, wherein the snapshot is an incremental backup snapshot.

14. A system, comprising:

a processor configured to;

take a snapshot of a remote virtual machine within a cluster of nodes by using an image writer with a snapshot provider, wherein;

the image writer is a part of Microsoft Windows Server 2012 infrastructure; and

the snapshot provider is a part of Microsoft Windows Server 2012 infrastructure;

determining whether the remote virtual machine is running on a node proxy;

selecting the image writer as a hypervisor volume shadow copy service (“

VSS”

) writer if the remote virtual machine is running on the node proxy, if the remote virtual machine is running on a node other than the node proxy select the image writer as a cluster shared volume VSS writer;

record a set of backup components by using a cluster interface, wherein;

the cluster interface is a part of Microsoft Windows Server 2012 infrastructure; and

the set of backup components comprises metadata described in a backup session that contains the necessary information for local restore operations;

play back the set of backup components taken from the snapshot of the remote virtual machine, to simulate a restore operation as if it were to be on a local machine;

reconstruct the remote virtual machine by using both (1) the snapshot and (2) a windows management instrumentation (WMI) framework with the set of backup components based at least in part on the simulation of the local restore operation, wherein the WMI framework is operable with Microsoft Windows Server 2012; and

use the WMI framework to enable the remote virtual machine as a cluster-wide virtual machine and a memory coupled to the processor and configured to provide the processor with instructions.

15. The system recited in claim 14, wherein the remote virtual machine does not have one or more of:

a restore agent;

a backup client; and

dedicated backup software.

16. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

taking a snapshot of a remote virtual machine within a cluster of nodes by using an image writer with a snapshot provider, wherein;

the image writer is a part of Microsoft Windows Server 2012 infrastructure; and

the snapshot provider is a part of Microsoft Windows Server 2012 infrastructure;

determining whether the remote virtual machine is running on a node proxy;

selecting the image writer as a hypervisor volume shadow copy service (“

VSS”

) writer if the remote virtual machine is running on the node proxy, if the remote virtual machine is running on a node other than the node proxy select the image writer as a cluster shared volume VSS writer;

recording a set of backup components by using a cluster interface, wherein;

the cluster interface is a part of Microsoft Windows Server 2012 infrastructure; and

the set of backup components comprises metadata described in a backup session that contains the necessary information for local restore operations;

playing back the set of backup components taken from the snapshot of the remote virtual machine, to simulate a restore operation as if it were to be on a local machine; and

reconstructing the remote virtual machine, by using both (1) the snapshot and (2) a windows management instrumentation (WMI) framework with the set of backup components based at least in part on the simulation of the local restore operation simulation, wherein the WMI framework is operable with Microsoft Windows Server 2012; and

using the WMI framework to enable the remote virtual machine as a cluster-wide virtual machine.

17. The computer program product recited in claim 16, wherein the remote virtual machine does not have one or more of:

a restore agent;

a backup client; and

dedicated backup software.