Installing CA Enterprise Log Manager - CA Technologies

Configuring the Event Log StoreAbout the Event Log Store ServiceThe event log store service handles database interactions such as the following:■■■■■■■■Inserting new events into the current (hot) databaseRetrieving events from local and remote federated databases for queries andreportsCreating new databases when the current database is fullCreating new archive files and deleting old archive filesManaging the archive query cacheApplying selected summarization and suppression rulesApplying selected event forwarding rulesDefining CA Enterprise Log Manager servers that act as federated children tothis CA Enterprise Log Manager serverAbout Archive FilesThe CA Enterprise Log Manager server automatically creates warm databasefiles, called archive files, when a hot database reaches the Maximum Rowssetting you specify in the event log store service. Hot database files are notcompressed.When you configure auto archiving from a collection server to a reporting server,the warm databases on the collection server are deleted after the databases arecopied to the reporting server. The Max Archive Days does not apply here.When you configure auto archiving from a reporting server to a remote storageserver, the warm databases on the reporting server are not deleted after beingcopied to the remote storage server. Rather, these warm databases are retainedon the reporting server until the Max Archive Days value is reached. Then, theyare deleted. However, a record of these deleted, cold databases is retained soyou can query the archive database for details, should you ever need thisinformation for performing a restore.When determining how to set Max Archive Days, consider your available diskspace on the reporting server. You configuration for Archive Disk Space sets thethreshold. If available disk space falls below the set percentage, event log data isdeleted to make more room even when the Max Archive Days for that data hasnot elapsed.Chapter 5: Configuring Services 117