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, 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, 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, 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, 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, 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, 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, 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, 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, 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: A backup data analysis system includes a data generation subsystem that generates primary data, a primary data storage subsystem that stores the primary data, and a backup data storage subsystem that stores backup data that has a backup file format and that is a backup of the primary data. At least one backup data conversion/analytics data provisioning subsystem is coupled to a data analytics subsystem, an analytics data storage subsystem, and the backup data storage subsystem, and retrieves the backup data from the backup data storage subsystem, converts the backup data from the backup file format to an open file format to provide analytics data, and stores the analytics data in the analytics data storage subsystem. When the backup data conversion/analytics data provisioning subsystem(s) receive an analytics data request from the data analytics subsystem, they provide the analytics data to the analytics data subsystem for use in analytics operation(s).

Abstract: A backup data analysis system includes a data generation subsystem that generates primary data, a primary data storage subsystem that stores the primary data, and a backup data storage subsystem that stores backup data that has a backup file format and that is a backup of the primary data. At least one backup data conversion/analytics data provisioning subsystem is coupled to a data analytics subsystem, an analytics data storage subsystem, and the backup data storage subsystem, and retrieves the backup data from the backup data storage subsystem, converts the backup data from the backup file format to an open file format to provide analytics data, and stores the analytics data in the analytics data storage subsystem. When the backup data conversion/analytics data provisioning subsystem(s) receive an analytics data request from the data analytics subsystem, they provide the analytics data to the analytics data subsystem for use in analytics operation(s).

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: 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 and system for maintaining live database data across hybrid storage. Specifically, the disclosed method and system entail accessing live backup database data in part residing on local storage and in part residing on remote storage. That is, on occasion, available local storage capacity may fall short of the required free storage space to accommodate the full restoration or recovery of a given database. Accordingly, to overcome this shortfall, the disclosed method and system detect and cycle the recovery of frequently accessed asset (or database) data files, of the given database, from remote storage onto local storage.

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