System and method for incremental virtual machine backup using storage system functionality

• US 9,104,331 B2
• Filed: 09/28/2012
• Issued: 08/11/2015
• Est. Priority Date: 09/28/2012
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Hsu, Windsor W., Xing, Jian
• Primary Examiner(s): Elmore, Reba I
• Application Number:
  US13/631,794
• Publication Number:
  US 20140095817A1
• Time in Patent Office: 1,047 Days
• Field of Search: 711/156, 711/161, 711/166, 711/162, 711/165, 711/206, 711/209, 707/633, 707/638, 707/639, 707/646, 707/659, 707/667, 710/28, 710/308, 709/212, 709/232
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1479 Generic software techniques for error detection or fault masking
• CPC Class Codes: G06F 12/08 in hierarchically structured memory systems, e.g. virtual memory systems
• CPC Class Codes: G06F 12/12 Replacement control
• CPC Class Codes: G06F 12/121 using replacement algorithms
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Techniques for virtual machine incremental backup are described herein. According to one embodiment, a request for an incremental backing up a virtual machine (VM) is received at a storage system, the request identifying a requested VM disk image associated with a consistent state of the VM. The storage system determines a difference between the requested VM disk image and a previous VM disk image representing a previous VM backup. The changes between the requested VM disk image and a previous VM disk image are then transmitted to a target backup storage system.

Claims

1. A computer-implemented method, comprising:

receiving at a storage system a virtual machine (VM) snapshot from a host system, the snapshot representing a consistent state of a VM hosted by the host system, wherein the storage system is communicatively coupled to the host system over a storage network, wherein the VM snapshot was captured by a virtual machine monitor (VM) in response to a first request received from a backup application server via a VMM application programming interface (API) over a network, and wherein the VMM manages a plurality of VMs within the host system;

storing the VM snapshot in a persistent storage device of the storage system as a VM disk image file;

receiving a second request at the storage system for an incremental backup of the VM from the backup application server over the network, the second request including a VM identifier identifying a requested VM disk image associated with a consistent state of the VM;

in response to the second request, identifying by backup logic of the storage system the VM disk image file corresponding to the requested VM disk image from the persistent storage device based on the VM identifier;

determining, by a disk change tracker of the storage system, a difference between the requested VM disk image and a previous VM disk image representing a previous VM backup; and

transmitting, by the backup logic of the storage system, changes between the requested VM disk image and the previous VM disk image to a target backup storage system directly without going through the backup application server, wherein the backup application server is a separate server for managing backup of a plurality of storage systems over the network.

2. The method of claim 1, wherein the VM disk image includes one or more disk snapshots created at the storage system based on a VM snapshot created at the VMM.

3. The method of claim 2, further comprising deleting the one or more disk snapshots after the changes has been transmitted to the target backup storage system.

4. The method of claim 3, wherein deletion of the one more disk snapshots is performed by erasing a VM snapshot initiated by the VMM.

5. The method of claim 2, wherein the difference between the disk snapshot and the previous disk snapshot is determined based on disk change tracking by the storage system.

6. The method of claim 1, further comprising creating at the target backup storage system the requested VM disk image based on the transmitted changes and the previous VM disk image.

7. The method of claim 1, wherein the storage system is a deduplicating storage system.

8. The method of claim 1, wherein the target backup storage system is a deduplicating storage system.

9. The method of claim 1, wherein the target backup storage system is a proxy server.

10. A non-transitory computer-readable storage medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations, the operations comprising:

receiving at a storage system a virtual machine (VM) snapshot from a host system, the snapshot representing a consistent state of a VM hosted by the host system, wherein the storage system is communicatively coupled to the host system over a storage network, wherein the VM snapshot was captured by a virtual machine monitor (VM) in response to a first request received from a backup application server via a VMM application programming interface (API) over a network, and wherein the VMM manages a plurality of VMs within the host system;

storing the VM snapshot in a persistent storage device of the storage system as a VM disk image file;

receiving a second request at the storage system for an incremental backup of the VM from the backup application server over the network network, the second request including a VM identifier identifying a requested VM disk image associated with a consistent state of the VM;

in response to the second request, identifying by backup logic of the storage system the VM disk image file corresponding to the requested VM disk image from the persistent storage device based on the VM identifier;

determining, by a disk change tracker of the storage system, a difference between the requested VM disk image and a previous VM disk image representing a previous VM backup; and

transmitting, by the backup logic of the storage system, changes between the requested VM disk image and the previous VM disk image to a target backup storage system directly without going through the backup application server, wherein the backup application server is a separate server for managing backup of a plurality of storage systems over the network.

11. The non-transitory computer-readable storage medium of claim 10, wherein the VM disk image includes one or more disk snapshots created at the storage system based on a VM snapshot created at the VMM.

12. The non-transitory computer-readable storage medium of claim 11, wherein the operations further comprise deleting the one or more disk snapshots after the changes has been transmitted to the target backup storage system.

13. The non-transitory computer-readable storage medium of claim 12, wherein deletion of the one more disk snapshots is performed by erasing a VM snapshot initiated by the VMM.

14. The non-transitory computer-readable storage medium of claim 10, wherein the difference between the disk snapshot and the previous disk snapshot is determined based on disk change tracking by the storage system.

15. The non-transitory computer-readable storage medium of claim 10, wherein the operations further comprise creating at the target backup storage system the requested VM disk image based on the transmitted changes and the previous VM disk image.

16. The non-transitory computer-readable storage medium of claim 10, wherein the storage system is a deduplicating storage system.

17. The non-transitory computer-readable storage medium of claim 10, wherein the target backup storage system is a deduplicating storage system.

18. A storage system, comprising:

a processor;

a persistent storage device;

a backup logic executed by the processor configured to

receive a virtual machine (VM) snapshot front a host system, the snapshot representing a consistent state of a VM hosted by the host system, wherein the storage system is communicatively coupled to the host system over a storage network, wherein the VM snapshot was captured by a virtual machine monitor (VMM) in response to a first request received from a backup application server via a VMM application programming interface (API) over a network, and wherein the VMM manages a plurality of VMs within the host system,

store the VM snapshot in a persistent storage device of the storage system as a VM disk image file,

receive a second request for an incremental backup of the VM from the backup application server over the network, the second request including a VM identifier identifying a requested VM disk image associated with a consistent state of the VM; and

in response to the second request, identify by the VM disk image file corresponding to the requested VM disk image from the persistent storage device based on the VM identifier; and

a disk tracker executed by the processor to determine a difference between the requested VM disk image and a previous VM disk image representing a previous VM backup; and

wherein the backup logic is to transmit changes between the requested VM disk image and the previous VM disk image to a target backup storage system directly without going through the backup application server. wherein the backup application server is a separate server for managing backup of a plurality of storage systems over the network.

19. The storage system of claim 18, wherein the VM disk image includes one or more disk snapshots created at the storage system based on a VM snapshot created at the VMM.

20. The storage system of claim 19, wherein the backup logic is further configured to delete the one or more disk snapshots after the changes has been transmitted to the target backup storage system.

21. The storage system of claim 20, wherein the further deletion of the backup is to be triggered by erasing of a VM snapshot initiated by the VMM.

22. The storage system of claim 18, wherein the difference between the disk snapshot and the previous disk snapshot is to be determined based on disk change tracking by the storage system.

23. The storage system of claim 18 is a deduplicating storage system.