# US 12,602,293 B2 · Management of logs in asset groups > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,293 B2 - Document ID: US12602293B2 - Status: Granted - Kind: B2 - Application number: 18/496,127 - Filed: 2023-10-27 - Published: 2025-05-01 - Granted: 2026-04-14 - Earliest claimed: 2023-10-27 - Assignees: Dell Products L.P. - Applicants: Dell Products L.P. - Inventors: Navneet Upadhyay; Rejith Mohan M; Ban Wang; Shivaraj Abbigeri; Elango Chockalingam - Web page: https://patentgrep.com/patent/US12602293B2 ## CPC - G06F 11/1458: {Management of the backup or restore process} - G06F 11/1464: {for networked environments} - G06F 11/1451: {by selection of backup contents} - G06F 16/162: {Delete operations (erasing in storage systems G06F3/0652)} - G06F 2201/80: Database-specific techniques - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## 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. ## Claims ### Claim 1 A method for managing logs on databases, the method comprising: issuing a backup request at a backup frequency that is specified in a data protection strategy associated with an asset group, wherein: the asset group comprises at least two databases; one database of the at least two databases is configured as a primary storage location of data for the asset group; a remaining number of databases of the at least two databases are configured as either physical standby databases or logical standby databases, wherein physical standby databases are identical copies of the one database, wherein logical standby databases have the same content as the one database but differ in organization of the same content; and the data protection strategy further specifies a type of backup that needs to be obtained for each database of the asset group; receiving, in response to the backup request, information about a successful backup of at least one database of the asset group; determining, based on the information, that the backup request has been completed for the asset group; triggering, in response to the determining, deletion of logs on the databases in the asset group; and synchronizing, after the backup request is completed, logs stored on the at least one database with a recovery catalog, wherein the recovery catalog is a backup log generated from the backup request. ### Claim 2 (depends on 1) The method of claim 1, wherein the backup request backs up all databases of the asset group. ### Claim 3 (depends on 1) The method of claim 1, wherein the backup request identifies databases of the asset group based on load levels, and selects the identified databases for backup, wherein the identified databases is a number of databases less than a total number of databases associated with the asset group. ### Claim 4 (depends on 1) The method of claim 1, wherein the databases of the asset group are configured in a high-availability configuration, and wherein determining that the backup request has been completed for the asset group comprises determining that a backup for a database in the asset group has been completed. ### Claim 5 (depends on 4) The method of claim 4, wherein triggering the deletion of logs on the databases in the asset group comprises: identifying a plurality of databases within the at least two databases in the asset group, and initiating deletion of logs on the plurality of databases, wherein the plurality of databases does not include the one database configured as the primary storage location. ### Claim 6 (depends on 5) The method of claim 5, wherein the logs are redo logs, wherein the redo logs are generated on one the database configured as the primary storage location and provided to the plurality of databases, wherein a redo log stores, in a temporal order, changes made to a database during a predetermined period of time. ### Claim 7 A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for managing logs on databases, the method comprising: issuing a backup request at a backup frequency that is specified in a data protection strategy associated with an asset group, wherein: the asset group comprises at least two databases; one database of the at least two databases is configured as a primary storage location of data for the asset group; a remaining number of databases of the at least two databases are configured as either physical standby databases or logical standby databases, wherein physical standby databases are identical copies of the one database, wherein logical standby databases have the same content as the one database but differ in organization of the same content; and the data protection strategy further specifies a type of backup that needs to be obtained for each database of the asset group; receiving, in response to the backup request, information about a successful backup of at least one database of the asset group; determining, based on the information, that the backup request has been completed for the asset group; triggering, in response to the determining, deletion of logs on the databases in the asset group; and synchronizing, after the backup request is completed, logs stored on the at least one database with a recovery catalog, wherein the recovery catalog is a backup log generated from the backup request. ### Claim 8 (depends on 7) The non-transitory computer readable medium of claim 7, wherein the backup request backs up all databases of the asset group. ### Claim 9 (depends on 7) The non-transitory computer readable medium of claim 7, wherein the backup request identifies databases of the asset group based on load levels, and selects the identified databases for backup, wherein the identified databases is a number of databases less than a total number of databases associated with the asset group. ### Claim 10 (depends on 7) The non-transitory computer readable medium of claim 7, wherein the databases of the asset group are configured in a high-availability configuration, and wherein determining that the backup request has been completed for the asset group comprises determining that a backup for a database in the asset group has been completed. ### Claim 11 (depends on 10) The non-transitory computer readable medium of claim 10, wherein triggering the deletion of logs on the databases in the asset group comprises: identifying a plurality of databases within the at least two databases in the asset group, and initiating deletion of logs on the plurality of databases, wherein the plurality of databases does not include the one database configured as the primary storage location. ### Claim 12 (depends on 11) The non-transitory computer readable medium of claim 11, wherein the logs are redo logs, wherein the redo logs are generated on the one database configured as the primary storage location and provided to the plurality of databases, wherein a redo log stores, in a temporal order, changes made to a database during a predetermined period of time. ### Claim 13 A system, comprising: a processor of a data manager configured to: issue a backup request at a backup frequency that is specified in a data protection strategy associated with an asset group, wherein: the asset group comprises at least two databases; one database of the at least two databases is configured as a primary storage location of data for the asset group; a remaining number of databases of the at least two databases are configured as either physical standby databases or logical standby databases, wherein physical standby databases are identical copies of the one database, wherein logical standby databases have the same content as the one database but differ in organization of the same content; and the data protection strategy further specifies a type of backup that needs to be obtained for each database of the asset group; receive, in response to the backup request, information about a successful backup of at least one database of the asset group; determine, based on the information, that the backup request has been completed for the asset group; send a deletion request for deletion of logs on the databases in the asset group to a first physical component of a computing device; and synchronizing, after the backup request is completed, logs stored on the at least one database with a recovery catalog, wherein the recovery catalog is a backup log generated from the backup request; the first physical component configured to: receive the deletion request; and provide the deletion request to a second physical component of the computing device; and the second physical component, executing on a host, configured to: interact with the databases in the asset group to service the request, wherein servicing the deletion request results in deletion of logs on databases in the asset group. ### Claim 14 (depends on 13) The system of claim 13, wherein the backup request backs up all databases in the asset group. ### Claim 15 (depends on 13) The system of claim 13, wherein the databases in the asset group are configured in a high-availability configuration. ### Claim 16 (depends on 13) The system of claim 13, wherein determining that the backup request has been completed for the asset group comprises determining that a backup for a database in the asset group has been completed. ### Claim 17 (depends on 16) The system of claim 16, wherein triggering the deletion of logs on the databases in the asset group comprises: identifying a plurality of databases within the at least two databases in the asset group and initiating deletion of logs on the plurality of databases, wherein the plurality of databases does not include the one database configured as the primary storage location. ### Claim 18 (depends on 17) The system of claim 17, wherein the logs are redo logs, wherein the redo logs are generated on the one database configured as the primary storage location and provided to the plurality of database, wherein a redo log stores, in a temporal order, changes made to a database during a predetermined period of time. ### Claim 19 (depends on 1) The method of claim 1, wherein the triggering deletes logs on all databases in the asset group except for the database that was most recently backed up.