Previous Topic: Log Collection Planning

Next Topic: About the CA EEM Server

Disk Space Planning

When you plan your environment, ensure that you have sufficient disk space to support high event volumes. For the collection server, this means enough disk space for each collection server to accommodate its share of peak loads as well as standard event volumes. For a reporting server, disk space is calculated based on event volume and the required online retention period.

Hot databases are not compressed. Warm databases are compressed. Both the hot and warm databases are considered to be online. You can search or report on their data. You would typically have at most between 30 and 90 day's worth of data ready for reporting and immediate search at any one time. Records older than that are stored on a remote server. You can restore them for search and reporting as needed.

Collection servers support both hot and warm databases. Since the retention period for a collection server is very short, from one to 23 hours, long term storage is not a factor.

A hot database exists on a management server for inserting self monitoring event messages.

Reporting servers support smaller hot databases and a large number of warm databases. Reporting servers must also have enough additional space to support restored files for some term. When you use direct attached storage, the partitions are automatically extended to allow for greater storage capacity.

More information:

Manually Backing Up Archived Databases

Manually Restoring Archives to the Original Event Log Store

Manually Restoring Archives to a New Event Log Store

LMArchiveā€“Backup/Restore Tracking