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: Methods and systems for data backup are described. According to some embodiments, the method includes in response to receiving a request for database instance discovery, retrieving backup history information. The method further includes filtering the backup history information to obtain selected backup information. The method further includes sending an instance discovery response that includes the selected backup information. The method further includes generating one or more protection policies based on the selected backup information.

Abstract: First, second, and third threshold limits are configured. The first threshold limit corresponds to a data change at which a backup of a client should be triggered. The second threshold limit corresponds to a maximum time interval at which the backup should be triggered. The third threshold limit corresponds to a utilization of resources at the client above which the backup should not be triggered. An amount of data change since a last backup, an elapsed time, and level of resource utilization at the client is monitored. A determination is made that at least one of the amount of data change has reached the first threshold limit or the elapsed time has reached the second threshold limit. The backup of the client is prevented from occurring because the level of resource utilization at the client is above the third threshold limit.

Abstract: Enabling point-in-time recovery for databases which change transaction log recovery models is described. If a database is associated with a recovery model that creates independent backups of the database's transaction log, a system identifies most recent backup information and a current transaction log sequence number. If the most recent backup information includes a transaction log sequence number and the current transaction log sequence number is a reset value, the system creates a full backup of the database, without first creating any independent backup of the transaction log. The system creates an independent backup of the transaction log when the independent backup of the transaction log is scheduled next, subsequent to creating the full backup of the database.

Abstract: Methods and systems for data backup are described. According to some embodiments, the method includes in response to receiving a request for database instance discovery, retrieving backup history information. The method further includes filtering the backup history information to obtain selected backup information. The method further includes sending an instance discovery response that includes the selected backup information. The method further includes generating one or more protection policies based on the selected backup information.

Abstract: Federated restore of availability group database replicas is described. A system receives a restore request associated with an availability group, and identifies a primary node in a cluster of nodes, the primary node storing a primary database replica associated with the availability group. The system identifies a secondary node in the cluster of nodes, the secondary node storing a secondary database replica associated with the availability group. The system removes the primary database replica and the secondary database replica from the availability group. The system simultaneously restores a backup database replica, associated with the availability group, as the primary database replica in the primary node and the secondary database replica in the secondary node. The system adds the restored primary database replica and the restored secondary database replica to the availability group.

Abstract: A production host for hosting a multi-instanced application includes a persistent storage and a resource manager. The persistent storage stores a resource registration associated with a plurality of instances of the multi-instanced application and a resource backup registration associated with backups, of the multi-instance application, that are stored in backup storage.

Abstract: First, second, and third threshold limits are configured. The first threshold limit corresponds to a data change at which a backup of a client should be triggered. The second threshold limit corresponds to a maximum time interval at which the backup should be triggered. The third threshold limit corresponds to a utilization of resources at the client above which the backup should not be triggered. An amount of data change since a last backup, an elapsed time, and level of resource utilization at the client is monitored. A determination is made that at least one of the amount of data change has reached the first threshold limit or the elapsed time has reached the second threshold limit. The backup of the client is prevented from occurring because the level of resource utilization at the client is above the third threshold limit.

Abstract: A first threshold corresponds to a data change at which a backup is triggered. A second threshold corresponds to a time interval at which the backup is triggered. A client is polled to obtain a first value indicating an amount of data changed since a last backup. A second value is tracked indicating an amount of time elapsed since the last backup. A determination is made as to whether to trigger the backup based on at least one of the first value exceeding the first threshold or the second value exceeding the second threshold. When the backup is not triggered because neither the first value exceeds the first threshold nor the second value exceeds the second threshold, the backup is triggered regardless based on a degree to which the first threshold has been reached, a degree to which the second threshold has been reached, and current usage of resources.

Abstract: A production host for hosting a multi-instanced application includes a persistent storage and a resource manager. The persistent storage stores a resource registration associated with a plurality of instances of the multi-instanced application and a resource backup registration associated with backups, of the multi-instance application, that are stored in backup storage.

Abstract: A first threshold corresponds to a data change at which a backup is triggered. A second threshold corresponds to a time interval at which the backup is triggered. A client is polled to obtain a first value indicating an amount of data changed since a last backup. A second value is tracked indicating an amount of time elapsed since the last backup. A determination is made as to whether to trigger the backup based on at least one of the first value exceeding the first threshold or the second value exceeding the second threshold. When the backup is not triggered because neither the first value exceeds the first threshold nor the second value exceeds the second threshold, the backup is triggered regardless based on a degree to which the first threshold has been reached, a degree to which the second threshold has been reached, and current usage of resources.