How do I backup and restore the Policy Manager Server database?

Issue:

How to backup and restore Policy Manager Server database ?

Resolution:

Read the following instructions completely before you start working on the server.

If you want to keep the DNS name, just move h2db to the new host, stop the old host and start the new one.

If you change the DNS name of the server, you must follow the instructions below.

Create a backup of the Policy Manager Server:

Stop the Policy Manager Server service:
- Policy Manager 15: net stop fsms
- Policy Manager 16: net stop wspms
Back up the directory:
- Policy Manager 15: <F-Secure Installation Folder> \ Management Server 5 \ data \ h2db>
- Policy Manager 16: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data
Note: Please copy the database to a different location than the one Policy Manager is installed in
Restart the Policy Manager Server service:
- Policy Manager 15: net start fsms
- Policy Manager 16: net start wspms

Now perform the installation on the new server. The current installation file can be found here

Note: To avoid the communication issues, use exactly the same ports by the installation like for the old WithSecure Policy Manager Server.

To restore secured Policy Manager data:

Stop the Policy Manager Server service:
- Policy Manager 15: net stop fsms
- Policy Manager 16: net stop wspms
Copy the backup to the correct location:
- Policy Manager 15: <F-Secure Installation Folder>\Management Server 5\data\h2db\
- Policy Manager 16: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\
Restart the Policy Manager Server service:
- Policy Manager 15: net start fsms
- Policy Manager 16: net start wspms

After the installation is complete, the new Policy Manager Server has the complete domain structure, including the settings.

After logging into the old server using the Policy Manager Console, enter the address of the new Policy Manager Server in the Settings > Windows > Centralized management > Policy Manager Server host communication settings and distribute the policies for all your policy domain. Note that the policy setting needs to be locked down to ensure that it's not getting overwritten by locally defined settings.

Now all clients will connect the new server. Once all clients are connected without errors with the new Policy Manager Server, you can turn off the old one.

You may also find additional instructions in this community article.