Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
Policy Manager's database is very large in size. How can the size be reduced?
Last updated
Issue:
Policy Manager's H2DB has grown very large in size. how can the size be reduced?
Resolution:
In most cases the growth of the H2DB is due to old alerts and Scanning reports. This can be resolved 2 ways either from the user interface or using the Database recovery tool.
Interface:
To reduce the size open the Policy Manager Console:
- Log in to the Policy Manager Console
- Select Root from the domain tree
- Go to the Alerts tab
- Click Select all from the right side of the table and then click Delete
- Go to the Scanning reports tab
- Click Select all from the right side of the table and then click Delete
- Restart the Policy Manager Server services by running: net stop wspms and net start wspms. Restarting the services will force the database to recompact itself immediately.
Database Recovery Tool:
Policy Manager includes a database maintenance tool that optimizes and checks the integrity of your database.
Database maintenance is automatically started as part of any Policy Manager upgrade or re-installation to ensure that the database structure is compatible with the latest version.
The maintenance tool creates a backup of your database, after which it verifies the database integrity and then applies the updated schema to the contents of the database. It also cleans up any invalid data to optimize the size and performance of the database.
To run the database maintenance tool manually:
- 1. Stop the Policy Manager service.
- 2. Start the maintenance tool.
- On Windows, run C:\Program Files\WithSecure\Policy Manager Server\bin\fspms-db-maintenance-tool.exe. When the maintenance tool opens, click Start maintenance.
- On Linux, run the /opt/f-secure/fspms/bin/fspms-db-maintenance-tool script.
The progress and details of the maintenance steps are shown.
- 3. On Windows, after the maintenance steps have run, click Close.
- 4. Restart the Policy Manager Server service
If the maintenance is not successful, no changes are applied to the database and Policy Manager Server is not started.