Transaction Log Backup Directory cleanup for Advanced Authentication
search cancel

Transaction Log Backup Directory cleanup for Advanced Authentication

book

Article ID: 250387

calendar_today

Updated On:

Products

CA Risk Authentication CA Advanced Authentication CA Advanced Authentication - Risk Authentication (RiskMinder / RiskFort)

Issue/Introduction

We are facing an issue in which it seems there is no cleanup of the log/backup directory.
In documentation they say 'When the maximum size is reached, older log information is moved to the backup file before the newer log information is saved' but they don't tell how to clean them or how to avoid the backup directory and just remove old logs.

How can we avoid the use of the backup directory (we have a log ingestion so old data is no longer required) and to avoid to fill up the Filesystem? (so, just a rollover policy on logs).

Environment

Release : 9.1

Component : Symantec Risk Authentication

Resolution

The parameters that control logging in these files can be configured either by using the relevant INI files (as is the case with the UDS and Advanced Authentication log files) or by using Advanced Authentication itself (as is the case with the Risk Authentication and Case Management Queuing Server log file.) The typical logging configuration options that you can change in these files include:

  • Specifying the log file name and path:

 Risk Authentication enables you to specify the directory for writing the log files and storing the backup log files. Specifying the diagnostic logging directory allows administrators to manage system and network resources.

  • Specifying the log file size: 

You can specify the maximum number of bytes that the log file can contain. When the log files reach this size, a new file with the specified name is created and the old file is moved to the backup directory.

  • Using log file archiving:

 As Risk Authentication components run and generate diagnostic messages, the size of the log files increases. If you allow the log files to keep increasing in size, then the administrator must monitor and clean up the log files manually. Risk Authentication enables you to specify configuration options that limit how much log file data is collected and saved. Risk Authentication allows you to specify the configuration option to control the size of diagnostic logging files. This helps you determine a maximum size for the log files. When the maximum size is reached, older log information is moved to the backup file before the newer log information is saved.

  • Setting logging levels:

 Risk Authentication also allows you to configure logging levels. By configuring logging levels, the number of messages saved to diagnostic log files can be reduced. For example, you can set the logging level so that the system only reports and saves critical messages. See "Supported Severity Levels" for more information on the supported log levels.

logs/backup directory contains all the roll over files and this is not used in real time so you can clean as per your Logs data retention policy, if you do not need the backup log files then you can simply delete the logs but if you need to keep it for certain time, then you can also copy to some other location or leave it at the system if enough space is available.

logs/backup directory is generally managed by customer as per their Logs data retention policy.