Abstract: A method for managing data protection operations includes obtaining, by a computing node of the database system and from a data protection system, a data protection request for an incremental merge operation, and in response to obtaining the data protection request: identifying a selection of computing nodes in the database system for performing the data protection operation, initiating, for each computing node in the selection, a mounting operation for mounting a full backup, performing the data protection operation using a subset of the selection that successfully mounted the full backup based on a set of backup streams assigned to each of the subset to perform the incremental merge operation of a database managed by the database system, initiating, after the data protection operation, an unmounting on the subset of the selection.

Abstract: A method for managing data protection operations includes obtaining, by a computing node of the database system and from a data protection system, a data protection request for an incremental merge operation, and in response to obtaining the data protection request: identifying a selection of computing nodes in the database system for performing the data protection operation, initiating, for each computing node in the selection, a mounting operation for mounting a full backup,, performing the data protection operation using a subset of the selection that successfully mounted the full backup based on a set of backup streams assigned to each of the subset to perform the incremental merge operation of a database managed by the database system, initiating, after the data protection operation, an unmounting on the subset of the selection.

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