Abstract: A backup manager for providing backup services includes persistent storage and a backup orchestrator. The persistent storage includes protection policies. The backup orchestrator identifies a last backup generation time for a client in response to a protection policy of the protection policies triggering a backup generation for the client; obtains system metadata for the client; identifies a portion of client data that has been modified since the last backup generation time using the system metadata; generates an incremental backup based on the identified portion of the client data; and stores the incremental backup in backup storage.

Abstract: Techniques described herein relate to a method for generating backups of assets. The method may include identifying, by a backup agent, a backup generation event associated with an asset; in response to identifying the backup generation event: obtaining change information associated with the asset, and the change information includes at least one change list; generating an asset backup using the at least one change list, in which the asset backup includes asset backup data, asset backup metadata, and historical metadata; and storing the asset backup in a backup storage.

Abstract: Techniques described herein relate to a method for generating backups of virtual machines. The method may include, in response to identifying a backup generation event associated with virtual machines: obtaining, by a backup agent, virtual machine metadata associated with the virtual machines; identifying groups of virtual machines based on the virtual machine metadata; provisioning resources to generate backups of the virtual machines based on the groups of virtual machines; and generating a backup of the virtual machines based on the groups of virtual machines using the provisioned resources associated with the groups of virtual machines.

Abstract: Techniques described herein relate to a method for performing data protection services for data stored in a shared storage. The method may include identifying, by a primary data node, a protection policy event initiating performance of data protection services for data stored in the shared storage used by the primary data node and secondary data nodes; in response to identifying the protection policy event: obtaining primary data node monitoring information associated with the primary data node; obtaining secondary data node monitoring information associated with the secondary data nodes; assigning at least one resource limit to the primary data node and the secondary data nodes based on the primary data node monitoring information and the secondary data node monitoring information; and initiating performance of the data protection services by the primary data node and the secondary data nodes based on the assigned at least one resource limit.

Abstract: Embodiments for managing metadata in a high density network attached storage system. A change file list is obtained though external or internal crawler processes. A slicer creates multiple slices of the entire fileshare to enable parallel backup of the slices. A backup engine creates a separate backup containers and separate metadata files for each slice. The individual metadata files are combined into a single consolidated metadata file, and the individual metadata files are then deleted. The consolidated metadata file contains all of the elements comprising the entire fileshare, and a corresponding container ID is also added to each entry of the file. Another table contains details of the sub-assets and their backup properties. A backup agent obtains the backup IDs for the individual sub-assets, using a job ID field for a backup query operating on the single consolidated metadata file.

Abstract: A backup storage for providing backup services includes storage and a compliance manager. The storage includes backups. The compliance manager obtains a compliance request for data; makes a determination, in response to obtaining the compliance request, that the data is stored as part of a backup of the backups; in response to making the determination: deletes linking data that associates a portion of a compliance sensitive data portion stored in backup metadata of the backup with a portion of modified backup data of the backup to make the linking data unavailable; and removes the modified backup data using garbage collection.

Abstract: A method that is performed for backing up data. The method includes obtaining a backup request; and in response to the backup request: obtaining an asset and an asset entry from a file system metadata repository associated with the backup request; identifying asset components of the asset using the asset entry; assigning asset components to backup threads to be backed up as pseudo-assets based on the asset entry; executing the backup threads to generate pseudo-asset backups; storing the pseudo-asset backups on backup storages; and updating asset backup metadata based on the pseudo-asset backups.

Abstract: A method that is performed for backing up data. The method includes obtaining an incremental backup request; and in response to the incremental backup request: obtaining an asset and an asset entry associated with the incremental backup request; dividing the asset into pseudo-assets based on the asset entry; storing the pseudo-assets across backup storages to generate incremental pseudo-asset backups; initiating the merging of the incremental pseudo-asset backups to generate an incremental asset backup; and initiating the merging of the incremental asset backup with a previously generated full asset backup associated with the incremental backup request to generate a first synthetic full asset backup.

Abstract: Embodiments described herein relate to a technique for performing an enhanced backup and restore for a computing device. The method may include: receiving, at a backup management device, a request to perform an enhanced backup operation; creating, by the backup management device, an enhanced recovery asset including computing device data items and stored on a backup storage device; performing a backup operation of a volume of the computing device to obtain a first backup container; performing a backup operation of system state information associated with the computing device to obtain a second backup container; associating the first backup container and the second backup container with the enhanced recovery asset; receiving, by the backup management device, a second request to perform a recovery operation; and performing, based on the second request, the recovery operation using at least a portion of the enhanced recovery asset.

Abstract: Backup operations may save a full backup and subsequent checkpoints. Systems and methods for handling backup and restore operations when checkpoints are deleted. Checkpoints can be merged during a restore operation to account for deleted checkpoints. Also, the backup can continue to leverage existing backups even though checkpoints have been deleted.

Abstract: A method for verifying data includes obtaining, by a backup agent, a backup verification trigger for a backup stored in a backup storage system, in response to the backup verification trigger, obtaining backup metadata associated with the backup, performing a hierarchical structure data mapping based on the backup metadata to obtain a hierarchical structure associated with the backup, performing, using the hierarchical structure, a backup verification to generate a backup health state of the backup, after the backup verification is generated: making a determination, based on the backup verification, that the backup health state is not in a healthy state, and in response to the determination, performing a remediation of the backup policies.

Abstract: Techniques described herein relate to a methods and systems for asset classification, which may include: identifying, in a backup domain, a first asset and a second asset; performing a first analysis of the first asset to determine a set of first asset characteristics; performing a second analysis of the second asset to determine a set of second asset characteristics; creating a first asset group based on the first analysis and the second analysis, the first asset group comprising the first asset and the second asset; and assigning a first backup policy to the first asset group.

Abstract: Backup operations may save a full backup and subsequent checkpoints. Systems and methods for handling backup and restore operations when checkpoints are deleted. Checkpoints can be merged during a restore operation to account for deleted checkpoints. Also, the backup can continue to leverage existing backups even though checkpoints have been deleted.

Abstract: A method for managing a persistent storage system includes obtaining, by a first node in a node cluster, a write request, wherein the node cluster comprises the first node and a second node, processing the write request, storing data associated with the write request in a persistent storage system, updating a block-based change list based on the storing, making a first determination that a synchronization schedule is triggered, and in response to the first determination: initiating a block-based change list synchronization to the second node.

Abstract: A method and system for backup processes that includes identifying a target volume and identifying a number of available threads to back up the target volume. The elements in the target volume are distributed among the available threads based on a currently pending size of data in the threads. The elements are stored from each thread into a backup container, and merged from each of the backup containers into a backup volume.

Abstract: A method and system for hybrid incremental file-based backup that includes receiving a list of desired elements for incremental backup and determining the elements on the list of desired elements that have changed since a previous backup, and storing the elements on the list of desired elements that have changed since the previous backup in a backup container. The method and system determines a list of unchanged elements from the previous backup and storing the unchanged elements on the list of unchanged elements in the backup container to obtain an updated backup.

Abstract: A method of performing data recovery of a first virtual machine (VM) hosted on a first hypervisor to a second hypervisor that is different from the first hypervisor is provided. The method identifies information indicating format of a first virtual disk in a backup of the first VM, and creates a second virtual disk using the information indicating format of the first virtual disk. The method also accesses information indicating configuration of the first VM and metadata of the first virtual disk, and creates a second VM hosted on the second hypervisor using the information indicating configuration of the first VM and the metadata of the first virtual disk. The method further attaches the second virtual disk to the second VM.

Abstract: Embodiments described herein relate to a technique for performing an enhanced backup and restore for a computing device. The method may include: receiving, at a backup management device, a request to perform an enhanced backup operation; creating, by the backup management device, an enhanced recovery asset including computing device data items and stored on a backup storage device; performing a backup operation of a volume of the computing device to obtain a first backup container; performing a backup operation of system state information associated with the computing device to obtain a second backup container; associating the first backup container and the second backup container with the enhanced recovery asset; receiving, by the backup management device, a second request to perform a recovery operation; and performing, based on the second request, the recovery operation using at least a portion of the enhanced recovery asset.

Abstract: A method for verifying data includes obtaining, by a backup agent, a backup verification trigger for a backup stored in a backup storage system, in response to the backup verification trigger, obtaining backup metadata associated with the backup, performing a hierarchical structure data mapping based on the backup metadata to obtain a hierarchical structure associated with the backup, performing, using the hierarchical structure, a backup verification to generate a backup health state of the backup, after the backup verification is generated: making a determination, based on the backup verification, that the backup health state is not in a healthy state, and in response to the determination, performing a remediation of the backup policies.

Abstract: A method that is performed for backing up data. The method includes obtaining an asset backup request; and in response to the asset backup request: obtaining an asset and an asset entry associated with the asset backup request; dividing the asset into pseudo-assets using the asset entry; storing the pseudo-assets across backup storages to generate pseudo-asset backups; initiating the merging of the pseudo-asset backups to generate an asset backup; and updating asset backup metadata based on the asset backup.