Implementation Guide › Configuring Services › Configuring the Event Log Store › Event Log Store Settings in the Basic Environment

Event Log Store Settings in the Basic Environment

In an environment with separate CA User Activity Reporting Module servers performing roles of collection server and reporting server, you should configure the event log stores individually as local configurations. If you also choose to use the reporting server to handle failover traffic, you may want to set a higher value for the Maximum Rows field than that which is shown in the table. If you use your management server as a reporting server, consider that the management server does generate some event information itself in the form of self-monitoring events.

Note: You must configure each pair of servers that participate in auto archiving for non-interactive authentication for the auto archive configuration to operate properly.

The following table is an example, illustrating certain basic settings. The collection CA User Activity Reporting Module server is named CollSrvr-1. The reporting CA User Activity Reporting Module server named RptSrvr-1. For the example, there exists a remote storage server named RemoteStore-1 to store cold database files, and that the cold files are located in the directory, /CA-ELM_cold_storage.

The auto archive options in this example move archive files (warm database files) on the collection server to the reporting server every hour. This keeps disk space available for incoming events. Both servers use an incremental backup to avoid having to move large volumes of data at any one time. After a warm database is moved to the reporting server, it is automatically deleted from the collection server.

Note: The 0 value for the Start Time does not have any effect when the backup Frequency is set to Hourly.

For EEM User and EEM Password, you specify the credentials of a CA User Activity Reporting Module user assigned either the predefined role of Administrator or a custom role associated with a custom policy that grants the ability to perform the edit action on the database resource.

For the reporting server, specify /opt/CA/LogManager for the Remote Location and caelmservice as the Remote User if auto archiving from the reporting server to the remote storage server. You create this path and this user when you configure non-interactive authentication between these servers.

The auto archive options in this example move archive files on the reporting server to the remote storage server daily starting at 11:00 pm. After a database is moved to cold storage on the remote server, it is retained on the reporting server for Max Archive Days.

If auto-archive is not enabled, warm databases are retained based on thresholds configured for Max Archive Days and Archive Disk Space, whichever occurs first. Archived databases would be retained on the reporting server for 30 days before being deleted unless the disk space drops below 10%. In that case, the reporting server generates a self-monitoring event and deletes the oldest databases until available disk space is above 10%. You can create an alert to notify you by email or RSS feed when this occurs.

When a database is restored from a remote storage server to its original reporting server, it is kept for 3 days (72 hours).

More information about each of these fields and their values is available in the online help.

More information:

Example: Auto-Archiving Across Three Servers