Backup and Restore the ELM Configuration Data

Depending on your backup and recovery needs, some or all of the components described below should be backed up. Except where noted, all data described is found on the computer running the ELM Server service.

In general, restoring the ELM configuration for a system recovery involves reinstalling ELM components, stopping ELM and replacing default components with backed up components. More detailed instructions are below.

ELM Server .dat and .bak Files

The ELM Server stores the majority of its configuration data in the ELM installation directory. The default installation directory is:

c:\Program Files\ELM Enterprise Manager

The important configuration files are:

EEMSVR.dat
EEMSVR.bak
appSettings.xml
databaseSettings.xml

These files can all be found in the ELM install directory specified during setup.

The ELM Server is notified internally when its configuration changes. If no more changes occur for a fifteen second period, then the ELM Server writes the changes to its current configuration in the .dat file. The configuration can also be manually written by right clicking on the ELM Server and selecting All Tasks | Save Configuration. When the ELM Server is started, it loads the configuration in the server .dat file. If this loads successfully, the ELM Server then makes a .bak copy of the configuration. Stopping the ELM Server service and backing up both the .dat and .bak files provides a copy of the current configuration and the prior configuration.

We recommend backing up at least the .bak file to backup media. If many changes have been made since the last time the ELM Server service was started, then we recommend making a backup of the .dat without restarting the ELM Server service.

The ELM Console snap-in security settings are also stored in the .dat file. Before changing ELM Console security, we recommend making a backup and securing a copy of the .dat file to allow restoring the prior security configuration.

Restoring ELM Server Configuration

To restore the ELM Server configuration file from a .BAK file:

1.Stop the ELM Server service.

2.Rename the existing .DAT file to .OLD (e.g., EEMSVR.OLD).

3.Copy the .BAK file to .DAT (e.g., copy EEMSVR.BAK to EEMSVR.DAT).

4.Start the ELM Server service.

appSettings.xml

The appSettings.xml file stores settings for ELM reports and the ELM Server database connection. ELM administrator updates to this file are made primarily by the ELM database wizard. Otherwise, updates are relatively infrequent and do not use the internal notification mechanism like with the .dat file. Therefore the ELM Server service does not need to be stopped to backup this file, but all ELM Wizards should be closed.

Restoring appSettings.xml

To restore appSettings from a backup:

1.Close all ELM Wizards.

2.Rename the existing appSettings.xml to appSettings.old.

3.Copy the backup of appSettings.xml to the ELM install folder.

TNT Software Registry Keys

Important
Before modifying the Windows registry, be certain you understand how to backup and restore it if a problem occurs. See KB256986 for further information on the registry.

ELM Server

ELM stores a small amount of data in the Windows registry. This includes both software-specific settings and COM component registration information. The main registry key with ELM Server configuration data is HKEY_LOCAL_MACHINE \ SOFTWARE \ TNT Software. Other ELM registry entries under HKEY_CLASSES_ROOT and under SERVICES can be recreated by reinstalling ELM.

ELM Console

On computers running the ELM Console, the main registry keys are HKEY_CURRENT_USER \ Software \ TNT Software and HKEY_USERS \ .Default \ Software \ TNT Software.

TNT Agent

On computers running a Service Agent (TNTAgent.exe), the main registry key is at the same location as the ELM Server: i.e. HKEY_LOCAL_MACHINE \ SOFTWARE \ TNT Software.

If you have made use of custom ELM registry settings, you may wish to make regular backups of your registry. In all supported versions of Windows, the registry and COM registration database are backed up as part of the System State Data.

Restoring TNT Registry Keys

If the registry back up was created with the ntbackup Backup Wizard, it can be restored using the companion Restore Wizard. If regedit was used to export registry configuration, it can also be used to import configuration. Please see the appropriate Microsoft Knowledge Base article for detailed steps.

ELM Databases

The ELM databases can reside on the ELM Server or on a remote server. One place the configured ELM databases can be viewed, is through the properties of the ELM Server service, on the Database tab. We also recommend regular backups of your ELM Server database, as it contains all of the data collected from Agents. Regular backups also help keep the SQL transaction log from growing unchecked. During install, ELM creates a SQL Maintenance Job that can be scheduled and will backup the primary ELM database and rebuild table indexes.

Restoring ELM Databases

Restoring an ELM Database can be done through SQL Management Studio. Please see Backing Up and Restoring Databases in SQL Books Online for more details.

Reports Folder and Sub-folders

Below the ELM install folder is a WebSite \ Reports folder. This folder and one or more of its sub-folders may need to be backed up depending on your system recovery requirements.

The default location for generated reports is below the Reports folder. If historical reports should be recoverable, then these generated reports should be backed up.

Below the Reports folder is a ReportDefinitions sub-folder. This folder contains .xml files for each report which include the Categories of Agents collecting data for the report. If configured reports should be recoverable, then these .xml files should be backed up.

Restoring ELM Reports

Generated reports and report definitions can be restored by replacing files in the Reports folder and sub-folders with the backup copy of the same file. Please stop the ELM Server Service and the ELM Reports Scheduler Service before replacing report files.

ELM Advisor .dat File

The ELM Advisor "username".dat file is created for each user where the ELM Console is installed. This file is located the user's Windows profile, in the TNT Software, Inc. \ ELM Advisor sub-folder, and is updated when the ELM Advisor exits. The "username".dat file contains the following configuration details:

•Servers -The list of ELM Servers registered to the local ELM Advisor for this user. Servers can be added through the ELM Advisor UI.

•Responses -The configured actions taken by the ELM Advisor for the 5 different types of events. Responses can be configured through the ELM Advisor UI.

•Notifications -These records are the event details plus any additional ELM Advisor Notification messages that have been sent to the ELM Advisor. These notification records are independent of events stored in the ELM databases. Deleting them will not delete records from the ELM database. Notifications are configured through the ELM Advisor Notification Methods in the ELM Console.

To save the current ELM Advisor configuration, right-click on the ELM Advisor icon in the Windows notification area and select Exit from the context menu. Then backup the .dat file to backup media.

Restoring ELM Advisor

To restore the ELM Advisor configuration, right-click on the ELM Advisor icon in the Windows notification area and select Exit from the context menu. Then replace the existing .dat file the backup copy of the same file. Restart the ELM Advisor.