VIRTUAL MACHINE CHANGE BLOCK TRACKING

• US 20160147607A1
• Filed: 11/20/2014
• Published: 05/26/2016
• Est. Priority Date: 11/20/2014
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Dornemann, Henry Wallace, Pawar, Rahul S.
• Granted Patent: US 9,983,936 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/00 Error detection; Error correction; Monitoring error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00
• CPC Class Codes: G06F 11/1435 using file system or storage system metadata
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• 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/1464 for networked environments
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• 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/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/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

According to certain aspects, a system includes a client device that includes a virtual machine (VM) executed by a hypervisor, a driver located within the hypervisor, and a data agent. The VM may include a virtual hard disk file and a change block bitmap file. The driver may intercept a first write operation generated by the VM to store data in a first sector, determine an identity of the first sector based on the intercepted write operation, determine an entry in the change block bitmap file that corresponds with the first sector, and modify the entry in the change block bitmap file to indicate that data in the first sector has changed. The data agent may generate an incremental backup of the VM based on the change block bitmap file in response to an instruction from a storage manager, where the incremental backup includes the data in the first sector.

Claims

1. A system configured to backup a virtual machine, the system comprising:

a client device comprising computer hardware, wherein the client device includes;

a virtual machine (VM) executed by a hypervisor, wherein the VM comprises a virtual hard disk file and a change block bitmap file, wherein the virtual hard disk file stores data associated with a virtual hard disk;

a driver module under control of the hypervisor, wherein the driver module is configured to;

intercept a first write operation generated by the VM to store data in a first sector,

determine an identity of the first sector based on the intercepted write operation,

determine an entry in the change block bitmap file that corresponds with the first sector, and

modify the entry in the change block bitmap file to indicate that data in the first sector has changed; and

a data agent configured to gather data for use in performance of an incremental backup of the VM based on the change block bitmap file in response to an instruction from a storage manager, wherein the incremental backup comprises the data in the first sector.

2. The system of claim 1, wherein the hypervisor comprises an I/O stack, and wherein the I/O stack comprises the driver module.

3. The system of claim 1, wherein the data agent is further configured to:

parse the change block bitmap file;

identify each entry in the change block bitmap file that indicates that data in a sector associated with the respective entry has changed;

for each identified entry, determine an associated sector and read data from the associated sector in the virtual hard disk file; and

for each identified entry, include the read data in the incremental backup.

4. The system of claim 1, wherein the driver is further configured to modify the entry in the change block bitmap file from a logical 0 to a logical 1 to indicate that data in the first sector has changed.

5. The system of claim 1, wherein the virtual hard disk file and the change block bitmap file are stored in a volume of the VM.

6. The system of claim 1, wherein the driver is further configured to:

intercept an open operation generated by the VM to open the virtual hard disk file; and

begin monitoring the virtual hard disk file in response to intercepting the open operation.

7. The system of claim 1, wherein the change block bitmap file is associated with a first period of time.

8. The system of claim 7, wherein the driver is further configured to generate a second change block bitmap file associated with a second period of time after the first period of time and store the second change block bitmap file in the VM.

9. The system of claim 8, wherein the driver is configured to generate the second change block bitmap file after the data agent performs the incremental backup based on the change block bitmap file.

10. The system of claim 9, wherein the data agent is further configured to gather data for use in performance of a second incremental backup at a time after the incremental backup based on the second change block bitmap file.

11. A method of backing up a virtual machine, the method comprising:

intercepting, by a driver under the control of a hypervisor which executes on a client computing device, a first write operation generated by a virtual machine (VM) to store data in a first sector of a virtual hard disk, wherein the VM is executed by the hypervisor, wherein the VM comprises a virtual hard disk file and a change block bitmap file, and wherein the virtual hard disk file stores data associated with the virtual hard disk; and

with the client computing device,

determining an identity of the first sector based on the intercepted write operation;

determining an entry in the change block bitmap file that corresponds with the first sector; and

modifying the entry in the change block bitmap file to indicate that data in the first sector has changed.

12. The method of claim 11, further comprising:

receiving an instruction from a storage manager to begin a backup of the VM; and

gathering data for use in performance of an incremental backup of the VM based on the change block bitmap file in response to the received instruction, wherein the incremental backup comprises the data in the first sector.

13. The method of claim 12, further comprising:

parsing the change block bitmap file;

identifying each entry in the change block bitmap file that indicates that data in a sector associated with the respective entry has changed;

for each identified entry, determining an associated sector and read data from the associated sector in the virtual hard disk file; and

for each identified entry, including the read data in the incremental backup.

14. The method of claim 11, wherein the hypervisor comprises an I/O stack, and wherein the I/O stack comprises the driver module.

15. The method of claim 11, further comprising modifying the entry in the change block bitmap file from a logical 0 to a logical 1 to indicate that data in the first sector has changed.

16. The method of claim 11, wherein the virtual hard disk file and the change block bitmap file are stored in a volume of the VM.

17. The method of claim 11, further comprising:

intercepting an open operation generated by the VM to open the virtual hard disk file; and

begin monitoring the virtual hard disk file in response to intercepting the open operation.

18. The method of claim 11, wherein the change block bitmap file is associated with a first period of time.

19. The method of claim 18, further comprising:

generating a second change block bitmap file associated with a second period of time after the first period of time and store the second change block bitmap file in the VM, wherein the second change block bitmap file is generated after a first incremental backup based on the change block bitmap file is performed.

20. The method of claim 19, further comprising gathering data for use in performance of a second incremental backup at a time after the first incremental backup based on the second change block bitmap file.

21. (canceled)