Virtual machine backup with efficient checkpoint handling based on a consistent state of the virtual machine of history data and a backup type of a current consistent state of the virtual machine
According to one embodiment, a system in response to a request to back up a virtual machine (VM) to a backup storage system, retrieves history data from the backup storage system. The history data has been previously backed up in the backup storage system during a previous backup operation of the VM. The history data includes a change tracking identifier (ID) associated with a consistent state of a VM disk attached to the VM at the point-in-time of the previous backup operation. The system validates the history data against a current configuration of the VM. The current configuration includes information of one or more current consistent states of the VM disk. The system determines a backup type for each of the current consistent states based on the validated history data. The system backs up each of the current consistent states based on the backup type.
1. A computer-implemented method to back up virtual machines, the method comprising:
in response to a request to back up a virtual machine (VM) to a backup storage system, retrieving history data from the backup storage system, wherein the history data has been previously backed up in the backup storage system during a previous backup operation of the VM, wherein the history data includes a change tracking identifier (ID) associated with a consistent state of a VM disk attached to the VM at a point-in-time of the previous backup operation;
validating the history data against a current configuration of the VM, wherein the current configuration includes information of one or more current consistent states of the VM disk;
determining a backup type for each of the current consistent states based on the validated history data; and
backing up each of the current consistent states based on the backup type.
2. The method of claim 1 , wherein determining a backup type for each of the current consistent states comprises:
determining whether the change tracking ID within the history data is associated with the current consistent state,
determining that the backup type is an incremental backup in response to determining that the change tracking ID is associated with the current consistent state, and
otherwise, determining that the backup type is a full backup in response to determining that the change tracking ID is not associated with the current consistent state.
3. The method of claim 2 , wherein backing up each of the current consistent states comprises:
using the change tracking ID to query change-tracking data associated with the current consistent state in response to determining that the tracking ID is associated with the current consistent state, and
storing the change-tracking data on the backup storage system.
4. The method of claim 1 ,
wherein validating the history data against a current configuration of the VM comprises identifying a new VM disk is attached to the VM, and
further comprising performing a full backup of the new VM disk onto the backup storage system.
5. The method of claim 1 , wherein the backup type is an incremental backup or a full backup.
6. The method of claim 1 , wherein the VM disk and the one or more current consistent states are within a disk chain.
7. The method of claim 2 , further comprising:
communicating merge information to the backup storage system to merge backup data from a deleted intervening consistent state with its parent backup.
8. A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations, the operations comprising:
in response to a request to back up a virtual machine (VM) to a backup storage system, retrieving history data from the backup storage system, wherein the history data has been previously backed up in the backup storage system during a previous backup operation of the VM, wherein the history data includes a change tracking identifier (ID) associated with a consistent state of a VM disk attached to the VM at a point-in-time of the previous backup operation;
validating the history data against a current configuration of the VM, wherein the current configuration includes information of one or more current consistent states of the VM disk;
determining a backup type for each of the current consistent states based on the validated history data; and
backing up each of the current consistent states based on the backup type.
9. The non-transitory machine-readable medium of claim 8 , wherein determining a backup type for each of the current consistent states comprises:
determining whether the change tracking ID within the history data is associated with the current consistent state,
determining that the backup type is an incremental backup in response to determining that the change tracking ID is associated with the current consistent state, and
otherwise, determining that the backup type is a full backup in response to determining that the change tracking ID is not associated with the current consistent state.
10. The non-transitory machine-readable medium of claim 9 , wherein backing up each of the current consistent states comprises:
using the change tracking ID to query change-tracking data associated with the current consistent state in response to determining that the tracking ID is associated with the current consistent state, and
storing the change-tracking data on the backup storage system.
11. The non-transitory machine-readable medium of claim 8 ,
wherein validating the history data against a current configuration of the VM comprises identifying a new VM disk is attached to the VM, and
wherein the operations further comprise performing a full backup of the new VM disk onto the backup storage system.
12. The non-transitory machine-readable medium of claim 8 , wherein the backup type is an incremental backup or a full backup.
13. The non-transitory machine-readable medium of claim 8 , wherein the VM disk and the one or more current consistent states are within a disk chain.
14. The non-transitory machine-readable medium of claim 9 , wherein the operations further comprise:
communicating merge information to the backup storage system to merge backup data from a deleted intervening consistent state with its parent backup.
15. A data processing system, comprising:
a processor; and
a memory coupled to the processor to store instructions, which when executed by the processor, cause the processor to perform operations, the operations including:
in response to a request to back up a virtual machine (VM) to a backup storage system, retrieving history data from the backup storage system, wherein the history data has been previously backed up in the backup storage system during a previous backup operation of the VM, wherein the history data includes a change tracking identifier (ID) associated with a consistent state of a VM disk attached to the VM at a point-in-time of the previous backup operation;
validating the history data against a current configuration of the VM, wherein the current configuration includes information of one or more current consistent states of the VM disk;
determining a backup type for each of the current consistent states based on the validated history data; and
backing up each of the current consistent states based on the backup type.
16. The data processing system of claim 15 , wherein determining a backup type for each of the current consistent states comprises:
determining whether the change tracking ID within the history data is associated with the current consistent state,
determining that the backup type is an incremental backup in response to determining that the change tracking ID is associated with the current consistent state, and
otherwise, determining that the backup type is a full backup in response to determining that the change tracking ID is not associated with the current consistent state.
17. The data processing system of claim 16 , wherein backing up each of the current consistent states comprises:
using the change tracking ID to query change-tracking data associated with the current consistent state in response to determining that the tracking ID is associated with the current consistent state, and
storing the change-tracking data on the backup storage system.
18. The data processing system of claim 15 ,
wherein validating the history data against a current configuration of the VM comprises identifying a new VM disk is attached to the VM, and
wherein the operations further include performing a full backup of the new VM disk onto the backup storage system.
19. The data processing system of claim 15 , wherein the VM disk and the one or more current consistent states are within a disk chain.
20. The data processing system of claim 16 , wherein the operations further include:
communicating merge information to the backup storage system to merge backup data from a deleted intervening consistent state with its parent backup.