The server uses a back-end database to store system configurations, including policy profiles for each sensor and alerts.
The server supports two types of back-end database:
Database | Definition |
|---|---|
Internal backend database (evaluation only) | The server comes bundled with an in-process back-end database. The database is only supported in product evaluations and must store a maximum of 100,000 alerts between archive events. |
External backend database | The server can work with Oracle or MSSQL external databases. The use of an external database is required when the server is used in production and was designed to handle a large volume of alerts. Additionally, the use of an external database enables the use of standard DBMS tools to manage the database. |
Back up the internal database
The internal in-process database is file-based and stores its data in a set of files.
On Windows platforms, all data files reside in the hsqldb_data directory at:
<Root install dir>\webapps\ROOT\WEB-INF\hsqldb_data
To back up the internal database, all files in the specified hsqldb_data directory must be copied.
Back up the external database
When running the server with an external database (Oracle or MSSSQL), use your regular DBMS tools to perform backups.
Back up the schema according to the database types.
Database type | Definition |
|---|---|
Oracle | Back up the full schema of the users used by server to connect to Oracle. |
MSSQL | Back up the database, SNTRSRV. |