IBM System Dashboard for Enterprise Content Management, Version 5.0.0.2

IBM License Metric Tool database backup

Back up the current IBM® License Metric Tool installation files, configuration files, and database directory on a regular schedule.

The usage data that the IlmtReporter script file requires to generate reports is stored in the database directory. Back up this directory on a regular schedule. It is also important to back up the IBM System Dashboard for Enterprise Content Management installation directory where any configuration files are kept. The current installation files, configuration files, and database directory are all required to fully restore an operational system if a disaster recovery is required.

To perform an offline backup of a Derby database, use operating system commands to copy the database directory. The database must be shut down prior to performing an offline backup.

Maintaining database integrity

The IlmtCollector and IlmtReporter script files use Derby for their internal database.

Derby must be able to synchronize to the disk. Some server, disk, or operating system settings can prevent a correct synchronization and cause unrecoverable database corruption in the event of a power failure, system crash, or software crash. To avoid database corruption, you can take the following precautions:

Do not enable disk write caching on the hard disk drive that holds the database. If disk write caching is enabled, disable it. (It is enabled by default on many Windows systems.) Disk write caching can increase operating system performance. However, it can also result in the loss of information if a power failure, equipment failure, or software failure occurs. For information about disabling disk write caching, see your operating system support documentation.
Run Derby on a local drive rather than on an NFS-mounted, SMB-mounted, or other network-mounted disk.
Disable any other settings or options that might prevent a correct synchronization to disk when Derby is writing its transaction logs or other data.

Corruption issues can occur because of improper backups or restores. Take steps to back up your database in a way that prevents it from becoming corrupted.

For an offline backup, make sure that the database is shut down before you use the operating system commands to back it up.
Always back up the database to a new backup location rather than overwriting any existing backups.