Database Settings
Previous
Next
Database Settings |
Previous
Next
|
|
During installation, ELM requires two databases, a primary and a failover database. These databases can be in any combination of: •Microsoft SQL 2008 R2/Standard/Enterprise, Microsoft SQL 2012 Standard/Enterprise, Microsoft SQL 2014, or a local SQL database installed with the Server component. •the same instance or separate instances •local to the ELM Server computer or on a computer available on the network •default instances or named instances ELM will need write permissions so that it can create the databases. Given an instance and permissions, ELM will create the database, tables, indices, and constraints required. To open Database Settings, right click on the ELM Server computer name and select Database Settings from the menu. Database Settings is used to configure:Connections - Setup the connections to the ELM Primary, ELM Failover, and Archive databases. Retention Policy - Data management, area to configure when to delete/archive data. Archive - Database archive management, when to rollover archive databases. Properties - A summary of the Database Settings in an easy to read format.
Primary DatabaseThe primary database is the database used by ELM for storing data gathered from monitored systems. Types of data collected include: •Windows event log entries •Events generated by the ELM Server and Agents •SNMP Traps •SNMP Values •Syslog Data •Performance Data Maintenance Microsoft SQL jobAn optional database maintenance plan is enabled by default for the ELM primary database to run at midnight every night. The plan runs in the ELM server process and will perform integrity checks on the database, rebuild indexes to optimize the database, and backup the database. These settings are located in the databaseSettings.xml file. Failover Database The ELM Server has built-in database failover protection to minimize data loss in the event the ELM Server's primary database is unavailable. When the ELM Server detects a connectivity problem with its primary database, ELM will log the following event: Event Type: Warning Event Source: EEMSVR Event Category: None Event ID: 5214 Date: 4/26/2010 Time: 1:15:02 PM User: N/A Computer: ELMSERVERCOMPUTER Description: A critical database failure occurred and the temporary database ELM_FAILOVER on SQLSERVER\INSTANCENAME has been enabled. Data in this temporary database will be merged with the configured database when it becomes available. Error: 0x80004005, Microsoft OLE DB Provider for SQL Server, [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. SQL Error: 0x00000011, 08001
When this happens, ELM begins using the configured failover database and stores data in matching table names. When connectivity to the primary database is restored, the following event will be logged: Event Type: Information Event Source: EEMSVR Event Category: None Event ID: 5216 Date: 4/26/2010 Time: 1:22:22 PM User: N/A Computer: ELMSERVERCOMPUTER Description: The configured database has returned on-line. Temporary data written to ELM_FAILOVER on SQLSERVER\INSTANCENAME is now being merged with the database.
When ELM has completed merging data back into the primary database, most tables in the failover database will be deleted and event 5217 will be logged, as in the following example: Event Type: Information Event Source: EEMSVR Event Category: None Event ID: 5217 Date: 4/26/2010 Time: 1:22:26 PM User: N/A Computer: ELMSERVERCOMPUTER Description: Success, recovery attempt completed for the database. Merging data from (Failover database name) to (Primary database name). Data: Event Status: Success Rows processed: 508 Processing Time: 0h:0m:2s
Data: Perf Status: Success Rows processed: 442 Processing Time: 0h:0m:4s
Data: Disk Status: Success Rows processed: 60 Processing Time: 0h:0m:5s
Data: Memory Status: Success Rows processed: 300 Processing Time: 0h:0m:3s
Data: Network Status: Success Rows processed: 60 Processing Time: 0h:0m:4s
Data: Processor Status: Success Rows processed: 745 Processing Time: 0h:0m:3s
Table: DATA.Correlation Status: Success, Rows processed: 7
Table: DATA.SV_AgentStatus Status: Success, Rows processed: 8
Total Processing Time: 0h:0m:35s
All data written to the failover database will be automatically merged into the primary database. During database failover, it is possible for Events to appear in the ELM Console that are stored only in the ELM Server's primary database, and not in the temporary database. An attempt to open one of these items will fail because the record will not be in the database currently in use. When the database has failed back to the primary database, all Events will be accessible. Archive DatabaseThe Archive database is an optional database that can be used to minimize the size of the ELM primary database, improving the responsiveness of the ELM Console. It is not required that the database be created in SQL ahead of time; ELM can create the database and tables if it has adequate permissions to SQL. To connect an Archive database, right click the Viewing and Notifying container -> Connect Archive Database.
|