Upgrade the database

If you're planning on upgrading Deep Security Manager, you may also need to upgrade the Deep Security database. Check this list of currently-supported databases, and then, if required, migrate to a new database following the instructions below.

The upgrade path

The upgrade path for the database is as follows:

1. Upgrade the database software first.
2. Upgrade Deep Security Manager.

The database you choose must be supported by both the new and currently-installed version of Deep Security Manager. See these lists:

• Databases supported by the current release of the manager.
• Databases supported by previous versions of the manager. (The adjacent link takes you to a page that provides access to the documentation for previous releases. You can drill down into the documentation to find database support.)

Upgrade the database

To upgrade the database, follow these instructions:

To prevent data loss, complete the database migration before upgrading the Deep Security Manager software.

1. Stop the Deep Security Manager service. Deep Security Agents continue with their current protection policies while the manager is stopped.
2. Back up the database(s).
3. Back up the database connection settings file: [Deep Security install directory]/webclient/webapps/ROOT/WEB-INF/dsm.properties
4. Migrate to the new database server. For specific requirements, see Database requirements.
5. If the migration did not preserve existing databases, load the database backup(s) into the new database engine.
6. If required, edit dsm.properties to use the migrated database.
7. Restart the Deep Security Manager service.