Abstract: Techniques described herein relate to a method for generating synthetic full backups. The method may include obtaining a snapshot associated with a previous backup stored in a data domain; obtaining a second snapshot associated with a current state of the source data; generating a snapshot difference report using the first snapshot and the second snapshot and including a delete list, a rename list, and a copy list; storing a copy of the previous backup in the data domain; performing a delete operation on the copy based on the delete list; performing a rename operation on the copy based on the rename list; and performing a copy operation based on the copy list. In one or more embodiments, performing the delete operation, the rename operation, and the copy operation on the copy of the previous backup generates a first synthetic full backup of the source data.

Abstract: A method for data consolidation and preservation during backups of data stored in a source device from the source device to a target device is provided. The method is executed by the source device and includes: obtaining a first snapshot of the data and a second snapshot of the data; generating, in response to the obtaining, a first snapshot difference report using the first snapshot and the second snapshot; transmitting, in response to generating the first snapshot difference report, the first snapshot difference report to the target device to be stored with a backup copy of the data; and deleting, in response to transmitting the first snapshot difference report, the first snapshot.

Abstract: In general, embodiments relate to a method for performing rename operations, the method comprising: obtaining a rename list from a snapshot difference report, sorting the rename list to obtain an ordered rename list, making a determination using the ordered rename list that circular rename entries exist in the ordered rename list, based on the determination, creating a plurality of temporary target paths based on the circular rename entries, generating a temporary rename list of the rename operations, generating a circular rename list of the rename operations, performing rename operations in the temporary rename list, and after completing operations in the temporary rename list, performing rename operations in the circular rename list.

Abstract: In general, embodiments relate to a method for generating synthetic full backups, the method comprising: performing a verification that a previous backup of source data stored in a data domain is a failed synthetic full backup, obtaining based on the verification a latest snapshot of the source data, obtaining based on the verification a prior snapshot of the source data making a determination, using a copy list that a first portion of the data items in the copy list exists in the previous backup and a second portion of the data items does not exist in the previous backup, and performing based on the determination a copy operation to copy the second portion of the data items to the data domain to obtain a synthetic full backup.

Abstract: A method for data consolidation and preservation during backups of data stored in a source device from the source device to a target device is provided. The method is executed by the source device and includes: obtaining a first snapshot of the data and a second snapshot of the data; generating, in response to the obtaining, a first snapshot difference report using the first snapshot and the second snapshot; transmitting, in response to generating the first snapshot difference report, the first snapshot difference report to the target device to be stored with a backup copy of the data; and deleting, in response to transmitting the first snapshot difference report, the first snapshot.

Abstract: Techniques described herein relate to a method for generating synthetic full backups. The method may include obtaining a snapshot associated with a previous backup stored in a data domain; obtaining a second snapshot associated with a current state of the source data; generating a snapshot difference report using the first snapshot and the second snapshot and including a delete list, a rename list, and a copy list; storing a copy of the previous backup in the data domain; performing a delete operation on the copy based on the delete list; performing a rename operation on the copy based on the rename list; and performing a copy operation based on the copy list. In one or more embodiments, performing the delete operation, the rename operation, and the copy operation on the copy of the previous backup generates a first synthetic full backup of the source data.

Abstract: A method for managing data includes obtaining, by a backup agent, a migration request, wherein the migration request specifies a plurality of users, and in response to the migration request: identifying a set of source-format data sets in a backup storage system, mounting the set of source-format data sets from the backup storage system, performing data mining on the set of source-format data sets in response to the mounting to obtain a hierarchical structure, generating a cloud-based service user account for each user of the plurality of users, wherein the cloud-based service user accounts are associated with a cloud-based service, obtaining source-format data sets associated with each user of the plurality of users using the hierarchical structure, and initiating a migration of the source-format data sets to the cloud-based service.

Abstract: A method for managing data includes obtaining, by a backup agent, a migration request, wherein the migration request specifies a plurality of users, and in response to the migration request: identifying a set of source-format data sets in a backup storage system, mounting the set of source-format data sets from the backup storage system, performing data mining on the set of source-format data sets in response to the mounting to obtain a hierarchical structure, generating a cloud-based service user account for each user of the plurality of users, wherein the cloud-based service user accounts are associated with a cloud-based service, obtaining source-format data sets associated with each user of the plurality of users using the hierarchical structure, and initiating a migration of the source-format data sets to the cloud-based service.

Abstract: A method for performing a backup operation includes obtaining a restoration request, and in response to the restoration request: identifying a first set of backups, wherein each backup in the first set of backups is associated with requested data, mounting the first set of backups from the backup storage system, performing data mining on the first set of backups to obtain a hierarchical structure, providing a set of options to a client based on the hierarchical structure, obtaining a selection from the client, wherein the selection is a portion of the set of options, obtaining selected content based on the selection, wherein the selected content is in a source format, converting the selected content from a source format to a target format to obtain target formatted user-specified content, and initiating a transfer of the target-formatted user-specified content to a cloud-based service.

Abstract: A method for performing a backup operation includes obtaining a restoration request, and in response to the restoration request: identifying a first set of backups, wherein each backup in the first set of backups is associated with requested data, mounting the first set of backups from the backup storage system, performing data mining on the first set of backups to obtain a hierarchical structure, providing a set of options to a client based on the hierarchical structure, obtaining a selection from the client, wherein the selection is a portion of the set of options, obtaining selected content based on the selection, wherein the selected content is in a source format, converting the selected content from a source format to a target format to obtain target formatted user-specified content, and initiating a transfer of the target-formatted user-specified content to a cloud-based service.

Abstract: A backup agent for generating backups includes a persistent storage and a backup manager. The persistent storage stores backup/restoration policies. The backup manager obtains production host computing resource characteristics associated with production hosts; performs a computing resource analysis of the production host computing resource characteristics to obtain resource profiles for each of the production hosts; performs an availability analysis of the obtained resource profiles to determine an application-level computing resources distribution for generating the backups; coordinates generating the backups using the application-level computing resource distribution and the backup/restoration policies to obtain the backups; and stores the obtained backups in backup storage.

Abstract: A backup agent for generating backups includes a persistent storage and a backup manager. The persistent storage stores backup/restoration policies. The backup manager obtains production host computing resource characteristics associated with production hosts; performs a computing resource analysis of the production host computing resource characteristics to obtain resource profiles for each of the production hosts; performs an availability analysis of the obtained resource profiles to determine an application-level computing resources distribution for generating the backups; coordinates generating the backups using the application-level computing resource distribution and the backup/restoration policies to obtain the backups; and stores the obtained backups in backup storage.

Abstract: A decoupled backup solution for distributed databases across a failover cluster. Specifically, a method and system disclosed herein improve upon a limitation of existing backup mechanisms involving distributed databases across a failover cluster. The limitation entails restraining backup agents, responsible for executing database backup processes across the failover cluster, from immediately initiating these aforementioned processes upon receipt of instructions. Rather, due to this limitation, these backup agents must wait until all backup agents, across the failover cluster, receive their respective instructions before being permitted to initiate the creation of backup copies of their relative distributed database. Subsequently, the limitation imposes an initiation delay on the backup processes, which the disclosed method and system omit, thereby granting any particular backup agent the capability to immediately (i.e., without delay) initiate those backup processes.