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: Systems and methods for deleting backup pieces associated with an application such as a database application. Backup pieces are identified and deleted from the database records and from the backup application.

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: A backup manager for managing backup services includes persistent storage and a backup analyzer. The persistent storage includes a backup data repository and protection policies. The backup analyzer identifies a new backup stored in backup storage; performs a backup compatibility analysis on the new backup to determine inter-backup compatibility of the identified new backup; updates the backup data repository based on the inter-backup compatibility to obtain an updated backup data repository; and modifies a backup schedule using the updated backup data repository to meet a requirement of a protection policy of the protection policies.

Abstract: A method and system for live-mounting database backups. Specifically, disclosed method and system entail recovering database data—in entirety or at any granular level—without needing to provision storage resources for point-in-time database copies (i.e., backup database data), or without needing to wait for large amounts of data, representative of the point-in-time database copies, to traverse a network from backup storage to a target device. Substantively, through live-mounting, the physical point-in-time database data, as well as the associated structural metadata, may be retained on backup storage while a pointer-based snapshot, mapping to the physical point-in-time database data and structural metadata, may be generated thereon. Thereafter, a file system—mapping to the pointer-based snapshot on the backup storage—may be mounted on the target device, which exposes an interface through which the backup database data may be accessed and/or manipulated using a distributed file system protocol.

Abstract: A method and system for auto live-mounting database golden copies. Specifically, the disclosed method and system entail reactively auto live-mounting golden copy databases on hosts or proxy hosts based on the operational state of one or more database hosts and/or one or more assets (or databases) residing on the database host(s). Should a database host prove to be unresponsive, through periodic monitoring, databases residing on the database host may be brought back online on a proxy database host using stored golden copies respective of the aforementioned databases. Alternatively, should a given database on any database host exhibit an operational abnormality (e.g., an error, failure, etc.), the given database may be brought back online on the database host or a proxy database host using a stored golden copy respective of the given database. Accordingly, through the disclosed method and system, database outages may be minimized.

Abstract: In general, the invention relates to a method for performing backup operations. The method includes generating a backup on backup storage system, locking the backup for a retention span, generating a backup archive log image using archive log files for the backup, and locking the backup archive log image for a second retention span.

Abstract: In general, the invention relates to a method for backing up data. The method includes receiving a backup instruction from a client device, wherein the backup instruction comprises a backup tag corresponding to a backup operation for a user asset, making a first determination that the backup tag matches a second backup tag specified in a tag file, and in response to the first determination, identifying a checkpoint of a backup associated with the second backup tag, and resuming the backup operation at the checkpoint for the user asset.

Abstract: System extracts metadata of system committed change numbers, system change numbers for backup copies. System generates start system change numbers as minimums of committed change numbers, end system change numbers as maximums of change numbers, and identifiers for archive log backup copies. System identifies dependent system change numbers from start number to end number for backup copy. System identifies backed-up system change numbers, from start numbers to end numbers for log backup copies, which are in dependent numbers. If backed-up numbers don't include all dependent numbers, system outputs missing system change numbers. System generates start numbers, end numbers, and identifiers for new archive log backup copies, identifies new backed-up system change numbers, from start numbers to end numbers for new log backup copies, which are in missing numbers. If new backed-up numbers include all missing numbers, system stores backup copy with each log backup copy corresponding to any backed-up numbers.

Abstract: In general, the invention relates to a method for performing operations. The method includes protecting a database includes detecting a first trigger event for a first backup operation targeting an user asset of a client device of client devices, wherein the first trigger event specifies first metadata associated with the first backup operation, acquiring a first byte-range lock associated with a backup type specified in the first metadata in an asset lock file associated with the user asset, acquiring a second byte-range lock of the asset lock file that is associated with a storage mounting operation, after acquiring the first byte-range lock and the second byte-range lock, mounting a backup storage to the client device using the first metadata, unlocking the second byte-range lock, and performing, after unlocking the second byte-range lock, the first backup operation on the user asset.

Abstract: System extracts backup metadata, comprising committed change numbers, system change numbers, types, database version identifiers, and details, for backup copies. System generates data structure, comprising start system change numbers, based on minimums of system committed change numbers, end system change numbers and maximums of system change numbers, database version identifiers, and identifiers including details, for the backup copies. System identifies at least first type of backup copies as candidate dependent backup copies and at least second type of backup copies as candidate preceding backup copies.

Abstract: A system for providing data protection services for data generated by host components hosted by hosts includes persistent storage for storing data and a local data protection manager. The local data protection manager identifies a data protection trigger event associated with a host component hosted by the host, identifies an add-on library associated with the host component, identifies a data protection agent associated with the host component, and initiates performance of data protection services by the data protection agent using the add-on library.

Abstract: A system for providing data protection services for data generated by host components hosted by hosts includes persistent storage for storing data and a local data protection manager. The local data protection manager identifies a data protection trigger event associated with a host component hosted by the host, identifies an add-on library associated with the host component, identifies a data protection agent associated with the host component, and initiates performance of data protection services by the data protection agent using the add-on library.

Abstract: In general, the invention relates to a method for performing backup operations. The method includes generating a full backup of a user asset at a first point in time, generating an incremental backup after the full backup is generated, applying the incremental backup to the full backup to generate a second full backup, obtaining a distinct data files subset associated with the second full backup, and deleting the distinct data files subset from the second full backup to obtain a third full backup.

Abstract: Systems and methods for deleting backup pieces associated with an application such as a database application. Backup pieces are identified and deleted from the database records and from the backup application.

Abstract: System extracts metadata of system committed change numbers, system change numbers for backup copies. System generates start system change numbers as minimums of committed change numbers, end system change numbers as maximums of change numbers, and identifiers for archive log backup copies. System identifies dependent system change numbers from start number to end number for backup copy. System identifies backed-up system change numbers, from start numbers to end numbers for log backup copies, which are in dependent numbers. If backed-up numbers don't include all dependent numbers, system outputs missing system change numbers. System generates start numbers, end numbers, and identifiers for new archive log backup copies, identifies new backed-up system change numbers, from start numbers to end numbers for new log backup copies, which are in missing numbers. If new backed-up numbers include all missing numbers, system stores backup copy with each log backup copy corresponding to any backed-up numbers.

Abstract: System extracts backup metadata, comprising system committed change numbers, system change numbers, types, and database version identifiers, for backup copies. System generates data structure, comprising start system change numbers, based on minimums of system committed change numbers, end system change numbers, based on maximums of system change numbers, database version identifiers, and identifiers for archive log backup copies. System identifies dependent system change numbers, based on start system change number to end system change number for backup copy corresponding to database version identifier. System identifies, in data structure, backed-up system change numbers, based on start system change numbers to end system change numbers for archive log backup copies corresponding to database version identifier, which are included in dependent system change numbers.

Abstract: System extracts backup metadata, comprising committed change numbers, system change numbers, types, database version identifiers, and details, for backup copies. System generates data structure, comprising start system change numbers, based on minimums of system committed change numbers, end system change numbers and maximums of system change numbers, database version identifiers, and identifiers including details, for the backup copies. System identifies at least first type of backup copies as candidate dependent backup copies and at least second type of backup copies as candidate preceding backup copies.