Abstract: A production host for hosting virtual machines includes a persistent storage and a production agent. The persistent storage stores virtual machine data associated with a virtual machine of the virtual machines and a virtual machine shadow copy associated with the virtual machine data. The production agent obtains a backup generation request for the virtual machine; in response to the backup generation request, generates the virtual machine shadow copy; makes a determination that the virtual machine shadow copy comprises an auto-recovery disk that comprises some data; in response to the determination, merges the virtual machine shadow copy using a parent block set storage template to obtain a backup of the virtual machine; and store the backup in backup storage. The parent block set storage template is not associated with the virtual machine shadow copy.

Abstract: A production host includes a persistent storage for storing backup policies and a production agent that obtains a backup generation request for a virtual machine of the virtual machines; in response to the backup generation request, performs a continuity chain verification of a continuity chain associated with the virtual machine to identify a continuity state of backups associated with the virtual machine; makes a first determination, based on the continuity state of the backups associated with the virtual machine, that the backups associated with the virtual machine are in a remediable state; and, in response to the first determination, performs a remediation of the continuity chain to change the backups associated with the virtual machine to be in a continuous state; and generates a backup of the virtual machine using the backup policies while the continuity state of the backups associated with the virtual machine are in the continuous state.

Abstract: A method and system for implementing data lossless synthetic full backups. Specifically, the method and system disclosed herein improves upon traditional synthetic full backup operations by considering all user-checkpoint branches, rather than just the active user-checkpoint branch, representing all chains of incremental changes to a virtual disk of a virtual machine. In considering all user-checkpoint branches, no data pertinent to users involved in the development of the non-active (or inactive) user-checkpoint branches is lost.