Virtual machine change block tracking

Patent metadata

Field	Value
Publication number	US-9823977-B2
Application number	US-201615394553-A
Country	US
Kind code	B2
Filing date	Dec 29, 2016
Priority date	Nov 20, 2014
Publication date	Nov 21, 2017
Grant date	Nov 21, 2017

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.

First claim

What is claimed is:

1. A method of backing up a virtual machine, the method comprising:
intercepting, by a first driver under the control of a first hypervisor which executes on a first 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 first 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;
with the first client computing device, accessing the change block bitmap file and modifying a first entry in the change block bitmap file to indicate that data in the first sector has changed;
performing a first migration of the VM to a second hypervisor which executes on a second client computing device, such that the VM is executed by the second hypervisor following said performing the first migration;
performing a second migration of the VM either back to the first hypervisor or to a third hypervisor executing on a third client computing device;
subsequent to said performing the second migration, receiving an instruction to begin an incremental backup of the VM; and
in response to the instruction to begin the incremental backup of the VM:
determining that changes made to the virtual machine hard disk file are not reflected in the change block bit map file, wherein the changes not reflected in the change block bit map file were made to the virtual machine hard disk file when the VM was executed by the second hypervisor,
invalidating the change block bit map file, and
performing a full backup of the VM.

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

3. The method of claim 1 , further comprising:
intercepting an open operation generated by the VM to open the virtual hard disk file; and
monitoring the virtual hard disk file in response to intercepting the open operation.

4. The method of claim 1 , wherein the first driver forms a part of the first hypervisor.

5. A system configured to backup a virtual machine, the system comprising:
one or more computing devices comprising computer hardware, wherein the one or more computing devices include:
a first hypervisor executed by a first client device of the one or more computing devices, the first hypervisor configured to:
execute a virtual machine (VM), wherein the VM comprises a virtual hard disk file and a change block file, wherein the virtual hard disk file stores data associated with a virtual hard disk;
intercept write operations generated by the VM to store data in the virtual hard disk file, and
modify the change block file to indicate sectors on the virtual hard disk that have changed as a result of the write operations; and

a data agent configured to receive an instruction to begin an incremental backup of the VM, and in response the instruction:
determine that changes made to the virtual machine hard disk are not reflected in the change block file, wherein the changes made to the virtual machine hard disk that are not reflected in the change block file were made to the virtual machine hard disk subsequent to migration of the VM to a second hypervisor executing on a second client computing device of the one or more computing devices, and prior to migration of the VM from the second hypervisor to a third hypervisor,
invalidate the change block bit map file, and
perform a full backup of the VM.

6. The system of claim 5 , wherein the third hypervisor is the same as the first hypervisor.

7. The system of claim 5 , wherein the third hypervisor is different than the first hypervisor and executes on a third client computing device different than the first client computing device and the second client computing device.

8. The system of claim 5 , wherein the first hypervisor comprises an I/O stack, and wherein the I/O stack comprises a driver that performs the intercept of the write operations.

9. The system of claim 5 , wherein the first hypervisor 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.

10. Non-transitory computer-readable memory comprising instructions, which when executed by one or more computers, cause the one or more computers to perform a method for backing up a virtual machine, the method comprising:
intercepting, by a first driver under the control of a first hypervisor which executes on a first 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 first 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;
with the first client computing device, accessing the change block bitmap file and modifying a first entry in the change block bitmap file to indicate that data in the first sector has changed;
performing a first migration of the VM to a second hypervisor which executes on a second client computing device, such that the VM is executed by the second hypervisor following said performing the first migration;
performing a second migration of the VM either back to the first hypervisor or to a third hypervisor executing on a third client computing device;
subsequent to said performing the second migration, receiving an instruction to begin an incremental backup of the VM; and
in response to the instruction to begin the incremental backup of the VM:
determining that changes made to the virtual machine hard disk file are not reflected in the change block bit map file,
invalidating the change block bit map file, and performing a full backup of the VM.

11. The non-transitory computer-readable memory of claim 10 , wherein the first hypervisor comprises an I/O stack, and wherein the I/O stack comprises the first driver.

12. The non-transitory computer-readable memory of claim 10 , wherein the method further comprises:
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.

Assignees

• Commvault Systems Inc

Inventors

• Dornemann Henry Wallace
• Pawar Rahul S

Classifications

• G06F11/1451 Primary

  by selection of backup contents · CPC title

• G06F11/1446

  Point-in-time backing up or restoration of persistent data · CPC title

• G06F11/1464

  for networked environments · CPC title

• G06F2009/4557

  Distribution of virtual machine instances; Migration and load balancing · CPC title

• G06F3/0619 Primary

  in relation to data integrity, e.g. data losses, bit errors · CPC title