UNIFIED RCT BACKUP FOR DIFFERENT HYPERVISOR CONFIGURATIONS

• US 20190317867A1
• Filed: 04/17/2018
• Published: 10/17/2019
• Est. Priority Date: 04/17/2018
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Yadav, Sunil, Bansal, Aaditya R., Acharya, Soumen, Tokuri, Suman C., Hebsur, Sudha V.
• Granted Patent: US 10,719,413 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0712 in a virtual computing platform, e.g. logically partitioned systems
• CPC Class Codes: G06F 11/1407 Checkpointing the instruction stream
• 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/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/815 Virtual
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

A unified backup workflow process for different hypervisor configurations of virtual machines on different storage of a cluster leverages RCT-based backup functionality so that backup operations can be performed by a single host of the cluster. The process enables backing up together virtual machines that are local, as well as part of CSV or SMB storage using virtual machine level snapshots as checkpoints rather than volume level snapshots that were traditionally used. Backup data is sent to a backup server as a data stream rather than a file, which avoids the necessity of maintaining chains or structures that identify parent-child disks on the server.

Claims

1. A method of unified backup for different hypervisor configurations of virtual machines on different storage of a cluster having a plurality of hosts, the method being performed by a single host, comprising:

determining information for targets of all of said virtual machines that span over one or more of said hosts;

accessing said targets of virtual machines that span over one or more of said hosts and creating individual virtual machine-level checkpoints for said targets;

identifying cluster hosts for a backup rollover of the targets of said individual virtual machines, and balancing the backup data load of said virtual machine targets among said identified hosts;

backing up the data of said virtual machines targets using said identified hosts; and

creating a reference point for said backed up data to track data changes following said backing up.

2. The method of claim 1 further comprising validating said data backup and creating a snap-view of metadata of the backup process for performing recovery or a next incremental backup of the virtual machine target.

3. The method of claim 1, wherein said accessing comprises querying said hosts to gather virtual machine data points the targets of virtual machines that span said hosts.

4. The method of claim 3, wherein said accessing comprises accessing together virtual machines based on cluster shared column storage and on server message block storage.

5. The method of claim 1, wherein said creating individual machine-level checkpoints comprises creating a machine-level snapshot of each target of a virtual machine.

6. The method of claim 5, wherein said creating snapshots comprises creating snapshots of individual target virtual machines instead of creating snapshots of storage volumes.

7. The method of claim 1, wherein said backing up comprises sending a copy of underlying disks for a full back up as a data stream to a backup server.

8. The method of claim 7, wherein said sending comprises streaming copies of said underlying disks in parallel to the backup server.

9. The method of claim 1, wherein said backing up comprises sending, for an incremental backup, metadata identifying extent locations, lengths and offsets on a backup server of chunks of data that changed since the last backup, and streaming to the backup server the changes to said chunks of data for merging with the previously stored data.

10. The method of claim 1, wherein creating a reference point comprises using a checkpoint created for a virtual machine and a resilient change tracking identifier that tracks changes to a target subsequent to backup.

11. A non-transitory computer readable medium for storing executable instructions for controlling the operations of a processor to perform a method of unified backup of different hypervisor configurations of virtual machines on different storage of a cluster having a plurality of hosts, comprising:

determining information for targets of all of said virtual machines that span over one or more of said hosts;

accessing said targets of virtual machines that span over one or more of said hosts and creating individual virtual machine-level checkpoints for said targets;

identifying cluster hosts for a backup rollover of the targets of said individual virtual machines, and balancing the backup data load of said virtual machine targets among said identified hosts;

backing up the data of said virtual machines targets using said identified hosts; and

creating a reference point for said backed up data to track data changes following said backing up.

12. The non-transitory computer readable medium of claim 11 further comprising validating said data backup and creating a snap-view of metadata of the backup process for performing recovery or a next incremental backup of the virtual machine target.

13. The non-transitory computer readable medium of claim 11, wherein said accessing comprises querying said hosts to gather virtual machine data points the targets of virtual machines that span said hosts.

14. The non-transitory computer readable medium of claim 13, wherein said accessing comprises accessing together virtual machines based on cluster shared column storage and on server message block storage.

15. The non-transitory computer readable medium of claim 11, wherein said creating individual machine-level checkpoints comprises creating a machine-level snapshot of each target of a virtual machine.

16. The non-transitory computer readable medium of claim 15, wherein said creating snapshots comprises creating snapshots of individual target virtual machines instead of creating snapshots of storage volumes.

17. The non-transitory computer readable medium of claim 11, wherein said backing up comprises sending a copy of underlying disks for a full back up as a data stream to a backup server.

18. The non-transitory computer readable medium of claim 17, wherein said sending comprises streaming copies of said underlying disks in parallel to the backup server.

19. The non-transitory computer readable medium of claim 11, wherein said backing up comprises sending, for an incremental backup, metadata identifying extent locations, lengths and offsets on a backup server of chunks of data that changed since the last backup, and streaming to the backup server the changes to said chunks of data for merging with the previously stored data.

20. The non-transitory computer readable medium of claim 11, wherein creating a reference point comprises using a checkpoint created for a virtual machine and a resilient change tracking identifier that tracks changes to a target subsequent to backup.