Abstract: In general, embodiments relate to a method for backing up databases, the method includes receiving a backup request, wherein the backup request specifies a role of primary and an asset group identifier for an asset group, identifying, based on the backup request, a database in the asset group, and issuing the backup request for the database.

Abstract: In general, embodiments relate to a method for managing logs on databases, the method comprising determining that a backup request has been completed for an asset group, wherein the asset group comprises a plurality of databases, and triggering, in response to the determining, deletion of logs on the databases in the asset group.

Abstract: In general, embodiments relate to a method for backing up databases, the method includes receiving a first backup request, wherein the first backup request specifies a role and an asset group identifier for an asset group, identifying, based on the first backup request, a database in the asset group with the role, determining that the role of the database has changed since a last backup of the asset group, and in response to the determining, issuing a second backup request for the database, wherein the second backup request is for a full backup.

Abstract: In general, the technology relates to a method for managing databases, the method includes receiving, by a data manager, an asset notification comprising a first database identifier (DID) for a database and a second DID for the database, and performing, using the asset notification, an asset records update operation, wherein the data manager is configured to perform data protection on the database.

Abstract: In general, the technology relates to A method for managing databases, the method includes receiving a database identifier (DID) for a database, generating, using the DID, a unique identifier (UID) for the database, making a first determination that the UID does not exist in any agent service records, based on the first determination, making a second determination that at least one backup copy of the database exists, based on the second determination: creating an agent service record that comprises the UID and a tag, wherein a value of the tag is DIRTY, initiating copy discovery of the database, and receiving a notification that the copy discovery has been completed, wherein after the notification, requests from a data manager comprising the UID are permitted to be provided to an agent, wherein the request a backup request or request for copy discovery.

Abstract: In general, the technology relates to a method for managing database copies, the method includes receiving a request to perform copy discovery on a database, wherein the database is associated with a unique identifier (UID), identifying, using an agent operatively connected to the database, entries corresponding to copies of the database specified in a catalog that are associated with the UID, wherein the catalog is associated with the database, and providing, by the agent, information about the identified copies to a data manager, wherein a data manager applies a retention policy to the identified copies.

Abstract: In general, in one aspect, the technology relates to a method for backing up assets, the method comprising obtaining a group identifier (ID) associated with an asset, associating the asset with an asset group using the group ID, wherein all assets in the asset group are associated with the group ID, and protecting the asset in the asset group using a backup strategy associated with the asset group.

Abstract: In general, embodiments relate to a method for backing up databases, the method includes receiving a backup request, wherein the backup request specifies a role of standby and an asset group identifier for an asset group, identifying, based on the backup request, a database in the asset group, and issuing the backup request for the database.

Abstract: In general, embodiments relate to a method for backing up databases, the method includes receiving a backup request, wherein the backup request specifies a role of primary and an asset group identifier for an asset group, identifying, based on the backup request, a database in the asset group, and issuing the backup request for the database.

Abstract: In general, the technology relates to a method for managing databases, the method includes receiving a database identifier (DID) for a database, generating, using the DID, a unique identifier (UID) for the database, determining, after the generating, that the database is associated with a data protection policy, and permitting backup operations specifying the UID to be serviced by an agent operatively connected to the database.

Abstract: In general, in one aspect, the technology relates to a method for backing up assets, the method comprising: making a first determination about an asset type of an asset, based on the first determination, associating the asset with an asset group, wherein all assets in the asset group are of the asset type, and protecting the asset in the asset group using a backup strategy associated with the asset group.

Abstract: Described is a system for management of specialized files used for a backup restore. The system may allow for an automated recovery to be performed without having to manually identify critical information required to perform a restore of a particular backup within a backup chain. This information may include a control file and a parameter file. A backup agent may store such information within specialized objects that are stored as part of metadata managed by a backup agent to provide an additional layer of recover capability and efficiency. This information may then be leveraged for retrieval during a restore operation, for example, in a disaster recovery scenario.

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: Described is a system for management of specialized files used for a backup restore. The system may allow for an automated recovery to be performed without having to manually identify critical information required to perform a restore of a particular backup within a backup chain. This information may include a control file and a parameter file. A backup agent may store such information within specialized objects that are stored as part of metadata managed by a backup agent to provide an additional layer of recover capability and efficiency. This information may then be leveraged for retrieval during a restore operation, for example, in a disaster recovery scenario.

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: 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: 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: 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.