US-12625847-B2 - Deletion of audit trail files based on a database

US12625847B2US 12625847 B2US12625847 B2US 12625847B2US-12625847-B2

Abstract

In general, certain embodiments described herein relate to a method for managing and deletion of audit trail files on a database created by a backup system. The method includes setting up a retention policy for backup system audit trail files. The audit trail files include the backup system audit trail files and other audit trail files. After setting up the retention policy, the method includes making a first determination that a first audit trail file is a backup system audit trail file, making a second determination, based on the first determination, that an age of the first audit trail file is passed a time period specified in the retention policy, and making a third determination, based on the second determination, that no retention policy exclusion applies to the first audit trail file. Finally based on the third determination, the first audit trail file is deleted from the database.

Inventors

Shivaraj Abbigeri
Ban Wang
Harini H S
Elango Chockalingam
Navneet Upadhyay

Assignees

DELL PRODUCTS L.P.

Dates

Publication Date: 20260512
Application Date: 20241024

Claims (17)

1 . A method for managing audit trail files on a database, comprising: setting up a retention policy for backup system audit trail files in a backup system connected to the database, wherein the audit trail files comprise the backup system audit trail files and other audit trail files; after setting up the retention policy: making a first determination that a first audit trail file is a backup system audit trail file; based on the first determination, making a second determination that an age of the first audit trail file is passed a time period specified in the retention policy; based on the second determination, making a third determination that no retention policy exclusion applies to the first audit trail file, wherein the retention policy specifies at least one retention policy exclusion; based on the third determination, deleting the first audit trail file from the database; making, after deleting the first audit trail file, a fourth determination that a second audit trail file is a second backup system audit trail file; based on the fourth determination, making a fifth determination that a second age of the second audit trail file has exceeded the time period specified in the retention policy; based on the fifth determination, making a sixth determination that a retention policy exclusion applies to the second audit trail file; based on the sixth determination, maintaining the second audit trail file on the database; and monitoring, after maintaining the second audit trail file, a memory usage of the database for adjustments to the retention policy by a program of the backup system.
2 . The method of claim 1 , wherein the first audit trail file is generated based on an interaction between a backup system and the database.
3 . The method of claim 2 , wherein at least one of the other audit trail files is generated based on an interaction between a production host and the database, wherein an application is executing on the production host and the database stores application data generated by the application.
4 . The method of claim 1 , wherein the retention policy exclusion specifies that the second audit trail file is not to be deleted when the second audit trail file is associated with an ongoing operation of the database.
5 . The method of claim 1 , wherein the retention policy exclusion specifies that the second audit trail file is not to be deleted when the second audit trail file is associated with a failed backup on a backup system.
6 . The method of claim 1 , wherein the time period is determined by a user of the database and a backup system.
7 . The method of claim 1 , making the first determination that the first audit trail file is the backup system audit trail file comprises determining that the first audit trail file comprises a unique signature.
8 . 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 audit trail files on a database, the method comprising: setting up a retention policy for backup system audit trail files in a backup system connected to the database, wherein the audit trail files comprise the backup system audit trail files and other audit trail files; after setting up the retention policy: making a first determination that a first audit trail file is a backup system audit trail file; based on the first determination, making a second determination that an age of the first audit trail file is passed a time period specified in the retention policy; based on the second determination, making a third determination that no retention policy exclusion applies to the first audit trail file, wherein the retention policy specifies at least one retention policy exclusion; based on the third determination, deleting the first audit trail file from the database; making, after deleting the first audit trail file, a fourth determination that a second audit trail file is a second backup system audit trail file; based on the fourth determination, making a fifth determination that a second age of the second audit trail file has exceeded the time period specified in the retention policy; based on the fifth determination, making a sixth determination that a retention policy exclusion applies to the second audit trail file; based on the sixth determination, maintaining the second audit trail file on the database; and monitoring, after maintaining the second audit trail file, a memory usage of the database for adjustments to the retention policy by a program of the backup system.
9 . The non-transitory computer readable medium of claim 8 , wherein the first audit trail file is generated based on an interaction between a backup system and the database.
10 . The non-transitory computer readable medium of claim 9 , wherein at least one of the other audit trail files is generated based on an interaction between a production host and the database, wherein an application is executing on the production host and the database stores application data generated by the application.
11 . The non-transitory computer readable medium of claim 8 , wherein the retention policy exclusion specifies that the second audit trail file is not to be deleted when the second audit trail file is associated with an ongoing operation of the database.
12 . The non-transitory computer readable medium of claim 8 , wherein the retention policy exclusion specifies that the second audit trail file is not to be deleted when the second audit trail file is associated with a failed backup on a backup system.
13 . The non-transitory computer readable medium of claim 8 , wherein the time period is determined by a user of the database and a backup system.
14 . The non-transitory computer readable medium of claim 8 , making the first determination that the first audit trail file is the backup system audit trail file comprises determining that the first audit trail file comprises a unique signature.
15 . A system for managing audit trail files, comprising: a database; and a backup system connected to the database and comprising a processor and a memory, the processor programmed to complete the following steps stored on the memory: set up a retention policy for backup system audit trail files, wherein the audit trail files comprise the backup system audit trail files and other audit trail files; after setting up the retention policy: make a first determination that a first audit trail file is a backup system audit trail file; based on the first determination, make a second determination that an age of the first audit trail file is passed a time period specified in the retention policy; based on the second determination, make a third determination that no retention policy exclusion applies to the first audit trail file, wherein the retention policy specifies at least one retention policy exclusion; based on the third determination, delete the first audit trail file from the database; make, after deleting the first audit trail file, a fourth determination that a second audit trail file is a second backup system audit trail file; based on the fourth determination, make a fifth determination that a second age of the second audit trail file has exceeded the time period specified in the retention policy; based on the fifth determination, make a sixth determination that a retention policy exclusion applies to the second audit trail file; based on the sixth determination, maintain the second audit trail file on the database; and monitor, after maintaining the second audit trail file, a memory usage of the database for adjustments to the retention policy by a program of the backup system.
16 . The system of claim 15 , wherein the first audit trail file is generated based on an interaction between the backup system and the database.
17 . The system of claim 16 , wherein at least one of the other audit trail files is generated based on an interaction between a production host and the database, wherein an application is executing on the production host and the database stores application data generated by the application.

Description

BACKGROUND Applications may be executed to run tasks on databases creating data. The data generated by the applications may be backed up to a secondary system. The backup of data on databases creates audit trail files logging a backup systems interactions with the database. These audit trail files are stored on the database and can significantly inflate the database memory usage over time. This leads to inefficient memory utilization, which is typically manifested as a performance impairment of the databases. BRIEF DESCRIPTION OF DRAWINGS Certain embodiments of the invention will be described with reference to the accompanying drawings. However, the accompanying drawings illustrate only certain aspects or implementations of the invention by way of example and are not meant to limit the scope of the claims. FIG. 1 shows a system in accordance with one or more embodiments of the invention. FIG. 2 shows a flowchart of a method for managing audit trail files in accordance with one or more embodiments of the invention. FIG. 3 shows a diagram of a computing device in accordance with one or more embodiments of the invention. DETAILED DESCRIPTION The backup system is used by a user of a database to assist in operation of the database. The backup system of the database may provide software defined data protection, automated discovery, and deduplication in creating backups. The backup service supports compliance service level objectives of the database including backups of application data, file system data, virtual machines, hypervisors etc. In addition, the backup system generates audit trail files on the database in the course of its operation. The audit trail files are generated at commencement of a session of the backup system on the database and at the closure of the session. The audit trail files are critical for monitoring actions taken on the database and database operations. Traditionally, the database does not manage the audit trail files created by the sessions with the backup system. Said another way, the audit trail files are not automatically deleted from, or archived off, the database. Accumulation of these audit trail files can lead to decreased performance, reduced efficiency, and system instability on the database. As the number of audit trail files grows the system memory of the database, usage increases. Each audit trail file occupies a certain amount of memory space in the database. When the system memory is filled with the audit trail files, the database must work harder to manage the data, leading to slower response times and decreased performance. The efficiency of the database is decreased causing backup operations may take longer. Further, increase in the amount of data on the database, causes an increase in time for the backup operation. Similarly, database scans or searches may be slower because of all the extra files to sift. If the memory usage becomes too high, the database will experience system instability or even crashes. This is because the database might run out of memory resources, causing it to behave unpredictably or stop working altogether. To address one or more of the aforementioned issues, embodiments of the invention relate to a method for managing and deletion of audit trail files created by a backup system on a database. The method optimizes memory usage and bolsters system performance. In addition, the method operates in tandem with functions of the database, offering a seamless integration that minimizes disruption to ongoing operations. The database may be continuously monitored for the generation of new audit trail files. Upon detection, the backup system identifies backup system created audit trail files using a unique signature and deletes them based on a set retention period. This approach provides efficient memory utilization, enhancing the overall system performance while maintaining the integrity of the auditing process. This approach ensures seamless database operations while minimizing disruptions. Accordingly, in accordance with one or more embodiments of the invention, the method of managing and deletion of the audit trail files reduces the issues caused by the audit trail files. The method may lead to increased performance, increased efficiency, and a minimization of system instability on the database. By implementing one or embodiments disclosed here, the backup system manages the accumulation of audit trail files, optimizing system memory usage, enhancing system performance, and improving the overall efficiency of database operations. This approach strikes a balance between maintaining necessary audit trails for a reasonable period and preventing undue strain on system resources. The following describes one or more embodiments. FIG. 1 shows a system in accordance with one or more embodiments of the invention. The system may include a backup system (100), a database (110), a production host (120), and a client (130). Each component may be operatively conn