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 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: 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: A method and system for minimizing rolling database recovery downtime. Specifically, the disclosed method and system entail migrating and recovering database data from backup storage to local host storage while enabling database access operations through live mounts mapped to the database data on the backup storage. Database downtime may subsequently be reduced through the rapid switching of file system references between database data stored on backup storage and database data copies recovered on local storage.

Abstract: In general, in one aspect, the invention relates to a method for accessing backup data includes receiving a live mount connection request from a client device, in response to the live mount connection request: generating a directory, populating the directory with a backup control file image and a plurality of pointers to backup data file images in a second directory, wherein the backup control file image is obtained from the second directory, restoring at least a portion of the backup data file images in the directory using the backup control file image and at least a portion of the backup data file images in the second directory, and providing after the restoring, a handle to the directory to the client device.

Abstract: Creating vendor-neutral data protection operations for vendors' application resources is described. Capabilities specified for data protection operations by a vendor of an application are input from a host of the application. Any capabilities specified for the data protection operations are used to create a vendor-neutral version of a data protection operation for a resource of the application. The vendor-neutral version of the data protection operation for the application resource is output to the host. A result of performing the vendor-neutral version of the data protection operation on the application resource is input from the host.

Abstract: A backup storage for managing backups of clients includes persistent storage and a backup analyzer. The persistent storage includes the backups, protection policies, and an early deletion schedule. The backup analyzer obtains a request to analyze a protection policy of the protection policies; in response to obtaining the request: obtains backup data information associated with the protection policy; makes a determination, based on the backup data information and the protection policy, that a portion of the backups associated with the protection policies overprotect a client of the clients associated with the protection policy; and modifies the early deletion schedule based on the determination to obtain a modified early deletion schedule.

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: In general, the invention relates to a method for performing backing operations. The method includes receiving a user instruction to perform a backup operation on a user asset on a client device, determining that a prior backup operation on the user asset was interrupted, in response to the determination, generating a data file difference subset using a control file and a recovery catalog, wherein the control file is associated with the user asset and the recovery catalog is associated with at least the prior backup operation, and initiating the backup operation using the data file difference subset.

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: In general, in one aspect, the invention relates to a method for accessing backup data includes receiving a live mount connection request from a client device, in response to the live mount connection request: generating a directory, populating the directory with a backup control file image and a plurality of pointers to backup data file images in a second directory, wherein the backup control file image is obtained from the second directory, restoring at least a portion of the backup data file images in the directory using the backup control file image and at least a portion of the backup data file images in the second directory, and providing after the restoring, a handle to the directory to the client device.

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: 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: A backup storage for managing backups of clients includes persistent storage and a backup analyzer. The persistent storage includes the backups, protection policies, and an early deletion schedule. The backup analyzer obtains a request to analyze a protection policy of the protection policies; in response to obtaining the request: obtains backup data information associated with the protection policy; makes a determination, based on the backup data information and the protection policy, that a portion of the backups associated with the protection policies overprotect a client of the clients associated with the protection policy; and modifies the early deletion schedule based on the determination to obtain a modified early deletion schedule.

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 summary change log indexed by inode number is disclosed. An indication is received that a file system object associated with a corresponding file system index node (inode) has been modified. A summary change record is stored for the corresponding inode, including by: locating or creating an entry for the inode in an inode translation file; storing data associated with the modification in a summary change record located within a summary change file at an offset indicated in the entry; and using the summary change record to perform a backup.

Abstract: A method for managing virtual machines includes obtaining a restoration request via a first pane of a graphical user interface generated by a graphical user interface manager; in response to obtaining the restoration request: predicting a restoration load for performing the restoration of a virtual machine of the virtual machines; performing a resource availability analysis of the production hosts using the restoration load to obtain a list of production hosts for performing a restoration of the virtual machine; making a first determination that the list specifies at least one production host of the production hosts; and, in response to the first determination: modifying a second pane of the graphical user interface based on the list to obtain a modified second pane; obtaining a user selection of a restoration option displayed in the modified second pane; and restoring the virtual machine using the restoration option and backup/restoration policies.

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: A computing device for backing up virtual machine data includes a persistent storage and a backup initiator. The persistent storage stores virtual machine priority groupings and backup policies associated with the virtual machine priority groupings. The backup initiator obtains write rates of virtual machines; divides the virtual machines into priority groups based on the obtained write rates; updates the virtual machine priority groupings based on the priority groups; and performs a backup of the virtual machine data based on the backup policies using the updated virtual machine priority groupings.