Hyper-V virtual machine synthetic full backup where user and recovery snapshots coexist

Description

BACKGROUND OF THE INVENTION

No provisions are provided by Microsoft for taking incremental backups of Hyper-V virtual machines when user and recovery snapshots coexist.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

FIG. 1 is a high level block diagram illustrating an embodiment of a network environment in which a synthetic full backup of a virtual machine is performed.

FIG. 2 is a flow chart illustrating an embodiment of a virtual machine backup process.

FIG. 3 is a flow chart illustrating an embodiment of a process for restoring a backup of a virtual machine.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims, and the invention encompasses numerous alternatives, modifications, and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example, and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.

A hypervisor manages the generation and execution of virtual machines on a host machine. An example of a hypervisor is Hyper-V, which is a native hypervisor for Microsoft Windows systems.

A backup operation may comprise a full or incremental backup. In a full backup of a virtual machine, all data corresponding to the virtual machine is stored. In an incremental backup of a virtual machine, only data that has changed since the last backup of the virtual machine is stored. When feasible, incremental backups may be preferred to achieve reduced storage consumption, network traffic, and backup time. In a synthetic full backup of a virtual machine, an incremental backup is performed and subsequently applied to the last synthetic full backup of the virtual machine to generate a current synthetic full backup of the virtual machine.

Incremental backups of Hyper-V virtual machines are supported by Windows Server 2012 and subsequently released Windows operating systems. Specifically, incremental backups leverage a special Hyper-V snapshot known as a recovery snapshot. Moreover, Hyper-V provides an option for a user to create a snapshot of a virtual machine known as a user snapshot, which provides a quick and easy way for the user to revert the virtual machine to a previous state.

A virtual machine snapshot captures the state, data, and hardware configuration of the virtual machine at the time the snapshot is generated. The snapshot creates a child virtual hard disk, i.e., a differencing virtual hard disk (AVHD), that points to its corresponding parent virtual hard disk. When a snapshot is created, all virtual machine operating system files, application data, and data changes made during the execution of the virtual machine are stored in an associated differencing virtual hard disk. Snapshots and differencing virtual disks create a chain or tree of child and parent virtual hard disks up to the top parent.

Techniques for generating a synthetic full backup of a Hyper-V virtual machine when recovery and user snapshots coexist are disclosed herein. As described in further detail below, in some embodiments, current and previous virtual hard disk trees are compared to identify new differencing virtual hard disks, i.e., those differencing virtual hard disks that have not been previously backed up. Such identified incremental backup data is applied to the last synthetic full backup of the virtual machine to generate a new or current synthetic full backup. Although many of the given examples are described with respect to Microsoft's Hyper-V hypervisor, the disclosed techniques may be similarly employed with respect to any other hypervisor platform that provisions for a plurality of types of snapshots that may need to be consolidated during a backup.

FIG. 1 is a high level block diagram illustrating an embodiment of a network environment in which a synthetic full backup of a virtual machine is performed. In network environment 100, host 102 comprises a physical machine running Hyper-V. Hyper-V manages the generation and execution of virtual machine (VM) 104 on host 102. Although a single virtual machine is depicted for the purpose of example, Hyper-V may generate and manage any number of virtual machines on host 102.

Various types of data are associated with virtual machine 104. For example, virtual machine 104 is associated with state data such as a configuration XML file, saved state file, memory .bin file, etc. Furthermore, virtual machine 104 comprises virtual hard disk data as well as child and parent relationships thereof (e.g., a pointer is created for each child or differencing virtual hard disk that points to its corresponding parent virtual hard disk). Moreover, virtual machine 104 comprises snapshot data that captures the state, data, and hardware configuration of the virtual machine for each point in time a snapshot is created. In the context of a Hyper-V virtual machine, for example, snapshot data may comprise user snapshot data and/or recovery snapshot data. A user snapshot may be manually created by a user at a desired time while a recovery snapshot may be created by an automatic backup process.

Backup of various Microsoft applications including Hyper-V is facilitated at host 102 by EMC Corporation's Networker Module for Microsoft (NMM) 106. As depicted, NMM 106 interfaces with Microsoft's Hyper-V Virtual Machine Management Service 108 and Volume Shadow Copy Service (VSS) 110 resident on host 102. NMM 106 communicates with these services during a backup of virtual machine 104.

A synthetic full backup of virtual machine 104 may be performed as desired and/or routinely. For example, an administrator may manually initiate a synthetic full backup and/or configure a backup policy that automatically schedules and initiates synthetic full backups at prescribed times or time intervals. In network environment 100, a synthetic full backup of virtual machine 104 is initiated by backup server 112. For example, backup server 112 may comprise EMC Corporation's NetWorker server.

A backup request from backup server 112 is received by NMM 106 at host 102. In response to receiving the backup request, NMM 106 communicates with Hyper-V Virtual Machine Management Service 108 and Volume Shadow Copy Service 110 to obtain a file list associated with virtual machine 104. The file list specifies the various virtual hard disks associated with virtual machine 104. By sorting the list to generate a current tree of virtual hard disks associated with virtual machine 104 and comparing with a previous tree of virtual hard disks associated with virtual machine 104 from the last backup, NMM 106 identifies the differencing virtual hard disks that have not previously been backed up, i.e., the incremental backup data.

To facilitate the backup, NMM 106 sends the differencing virtual hard disks containing incremental data from the previous backup to storage node 114. Moreover, NMM 106 sends configuration files associated with the virtual machine to storage node 114 for backup. In some cases, NMM 106 may appropriately edit various configuration files associated with virtual machine 104 (e.g., the virtual machine configuration XML file and the VSS writer's BCD (Backup Component Document) XML file) prior to backup.

A new synthetic full backup of virtual machine 104 is generated at storage node 114 by merging the incremental backup data provided by NMM 106 with the last synthetic full backup previously stored at storage node 114. Moreover, a tree of virtual hard disks associated with the virtual machine maintained at storage node 114 with the synthetic full backup is updated to include links (e.g., pointers) associated with the newly added differencing virtual hard disks.

FIG. 2 is a flow chart illustrating an embodiment of a virtual machine backup process. In some embodiments, process 200 is employed by NMM 106 of FIG. 1, for example, when a request to backup virtual machine 104 is received from backup server 112. Process 200 starts at step 202 at which a snapshot of the virtual machine is created. For example, the VSS framework may be employed to create a snapshot of the virtual machine at step 202. The snapshot created at step 202 generates a list of virtual hard disks and differencing virtual hard disks of all user snapshots and recovery snapshots associated with the virtual machine.

At step 204, the list of virtual hard disks and differencing virtual hard disks associated with the virtual machine obtained via the snapshot of step 202 is traversed to identify relationships of the various virtual hard disks and differencing virtual hard disks. In some such cases, the list of virtual hard disks and differencing virtual hard disks is sorted and organized into a chain or tree structure comprising parent and child nodes with child nodes pointing to their corresponding parent nodes.

In the case of a full backup, all virtual hard disks and differencing virtual hard disks associated with the virtual machine are backed up at step 206. Moreover, the tree specifying the relationships of the virtual hard disks and differencing virtual hard disks is backed up at step 206. More specifically, step 206 comprises providing full backup data to a storage node at which the backup data is to be stored. A full backup is performed at step 206 when a previous synthetic full backup of the virtual machine does not exist at the storage node at which the current backup is to be stored. This may occur, for example, the first instance the virtual machine is backed up or when the virtual machine is backed up to a new or different storage node, for instance, because a previous storage node at which the virtual machine data was formerly being backed up has become full or has insufficient remaining capacity.

In the case of an incremental backup, differencing virtual hard disks not present in the previous backup of the virtual machine are identified and backed up. At step 208, a previous tree or list of sorted virtual hard disks and differencing virtual hard disks associated with the virtual machine from the last backup of the virtual machine is retrieved, for example, from the storage node at which the last backup of the virtual machine is stored. At step 210, the current tree generated at step 204 is compared with respect to the previous tree retrieved at step 208 to identify the differencing virtual hard disks comprising the incremental backup data, i.e., the differencing virtual hard disks not present in the previous backup. At step 212, the incremental data identified at step 210 is backed up. That is, the incremental data is provided to the backup storage node at which the incremental data is merged with the last synthetic full backup to generate a current synthetic full backup and the previous tree is updated to mirror the current tree.

In addition to the full or incremental backup of the virtual hard disks and differencing virtual hard disks of the virtual machine at steps 206 or 212, configuration data associated with the virtual machine is backed up at step 214. That is, a container for backing up configuration files (e.g., .xml, .bin, transfer files, etc.) is generated and linked with other backup containers of the virtual machine and provided to the corresponding storage node at step 214.

As described, backup process 200 takes into consideration both recovery and user snapshots in the event that the two types of snapshots coexist. An incremental backup is performed that consolidates both recovery and user snapshots and is subsequently employed to generate a synthetic full backup.

FIG. 3 is a flow chart illustrating an embodiment of a process for restoring a backup of a virtual machine. In some embodiments, process 300 is employed by NMM 106 of FIG. 1, for example, when a request to restore a synthetic full backup of virtual machine 104 is received. Process 300 starts at step 302 at which a backup container is mounted. At step 304, the virtual hard disk and differencing virtual hard disk files as well as the configuration files comprising the synthetic full backup of the virtual machine are copied to a local folder from the storage node at which the backup is stored. At step 306, the standard VSS restore workflow is employed to restore the virtual machine.

Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.