Home
Altair Monitor Administrator Guide
Database
Monitor stores historical information about jobs in a relational database. As of version 2015.09, the database is fully integrated and managed as part of Monitor. This section provides an overview of the components that run and manage the database.
Database Backup
There are two ways to do direct backups of the database: automatic and manual. In addition, the original source data files may be saved.

Welcome
What's New
View new features for Monitor 2025.1.0.
Monitor Overview
A real time software license monitoring and management tool.
Monitor Tutorials
Currently there are no Monitor tutorials available.
Getting Started Guide
This manual describes the web user interface and provides instructions on common uses and best practices for users. It also provides the basic setup, installation and management practices for administrators. For both administrators and users, it functions as a getting started guide.
Altair Monitor User Guide
Altair Monitor is a software license tracking tool that reports current and historical license utilization. The license managers that Monitor supports includes FlexNet Publisher, Reprise, LUM, and many others. The primary user interface for accessing Monitor is a web interface.
Altair Monitor Administrator Guide
- Altair Monitor Overview
  This document describes how to configure and manage Altair Monitor.
- Enable CLI Access on UNIX
  This section explains how to set up a UNIX user's shell environment to have a proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- Enable CLI Access on Windows
  This section explains how to set up a Window user's command prompt environment to have the proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- Use Monitor Help
  Monitor documentation is available in HTML and PDF format.
- Server Operation
- Failover Server Candidates
  If a server crashes suddenly, VOV has the capability to start a replacement server on a pre-selected host. This capability requires that the pre-selected host is configured as a failover server.
- Daemon Operation
  Although the Monitor daemons are started automatically upon startup, there may be times where a daemon should be restarted. This section describes how to control the Monitor daemons.
- Daemon Manager Utility
  Although the Monitor daemons are started automatically upon startup, there may be times where a daemon should be restarted. This section describes how to control the daemons from the command line (CLI).
- Database
  Monitor stores historical information about jobs in a relational database. As of version 2015.09, the database is fully integrated and managed as part of Monitor. This section provides an overview of the components that run and manage the database.
  - Daemon
  - Tasker
  - Set Up
  - Configure the Database from the Command Line
    The command line utility vovdb_util can be used to configure most aspects of the Monitor database. You must have ADMIN privileges on the Monitor server to configure and control the database.
  - Database Engine Versions and Upgrades
    Monitor includes version 14.4 of the PostgreSQL database engine that is used by the VOV database daemon vovdb. This section describes how to determine if a database upgrade will be needed when upgrading the Accelerator product software.
  - Load Data
    This section details the methods that Monitor uses to load data into the database, and the configuration options available to control which data is loaded.
  - Export Data
    One function of the utility vovdb_util is to export the database into jobs data files. The exported files are saved in the vnc.swd/data/dump directory.
  - Database Backup
    There are two ways to do direct backups of the database: automatic and manual. In addition, the original source data files may be saved.
  - Tag Administration
    The Tag Administration page, found in the Admin tab, provides an interface to managing tags. A tag is defined as a unique identifier for a license server being monitored. Tags are chosen by the Monitor administrator. The actions that are available in the tag administration page are listed below.
  - Manage Data from Different Origins
    In FlexNet Publisher monitoring, checkout data can be obtained from two different data sources.
  - License Violation Effects and Actions
    Monitor requires a license in order to store and report on historical license utilization information. If at any point a license is not available while the server is running, the server enters a licensing "grace period" of five days and the system will continue to operate as normal.
  - Database Schema
    The SQL schema used by this version of Monitor is visualized in the following entity-relationship diagram.
- Configuring Monitoring
- License Server Management
- Other Configurations
- Command Line Operations
- Reference

View All Altair Accelerator Help

Database Backup

There are two ways to do direct backups of the database: automatic and manual. In addition, the original source data files may be saved.

Automatic Backups

Automatic backups are configured through the administration web UI. When enabled, the backups are generated in subdirectories of the configured Backup Location named for the time of backup.

If the backup location is configured as:

/data/rtda/db_backup/licmon

The backup started on August 21st, 2023 at 1:00AM will be located in:

/data/rtda/db_backup/licmon/20230821_010000

Manual Backups

Manual backups are generated by running the vovdb_util utility. Backups are generated directly in the directory specified; it is recommended to specify the time of backup in the directory name for future reference. Example:

% vovdb_util backup /data/backup/licmon/2023Aug22_10AM

Source Data Backups

In addition to backing up the database directly, the source data files used to populate the database can be saved. The source files are located in licmon.swd/data and can be used to rebuild a database from scratch. No utility is provided to save these files.

Restore a Database from Backups

The procedure to restore from backup is the same whether the backup was generated automatically or manually.

Ensure the current database is stopped, either through the web UI or via the command line.
Delete or move the existing database.
For example, if the database is located at /data/rtda/db/licmon, it can be moved with:
```
 % mv /data/rtda/db/licmon /data/rtda/db/vnclicmon.bad 
```

Copy or move the backup to the original database location.

# Using the example of an automatic backup from above.
% mv /data/rtda/db_backup/licmon/20160821_010000 /data/rtda/db/vnclicmon

# Using the example of a manual backup from above.
% mv /data/backup/licmon/2016Aug22_10AM /data/rtda/db/vnclicmon

Restart the database.

Rebuild a Database from Source Data Files

Ensure the current database is stopped, either through the web UI or via the command line.
Delete or move the existing database.
For example, if the database is located at /data/rtda/db/licmon, it can be moved with:
```
% mv /data/rtda/db/licmon /data/rtda/db/vnclicmon.bad
```

Reload the source data files.

% vovproject enable licmon

% lmmgr loaddb