Moving the Reporting Databases

Moving the Reporting Databases | Web, Data, and Email Solutions | 8-June-2020

Applies to:

Forcepoint Web Security and Forcepoint URL Filtering, v8.5.x

Forcepoint DLP, v8.5.1, v8.6.x, v8.7.x

Forcepoint Email Security, v8.5.x

Forcepoint appliances, v8.5.x

This article describes two procedures that can be used to move a Forcepoint reporting database hosted on Microsoft SQL Server to a new location (directory, drive, or machine).

The procedures outlined here are intended to minimize risk of data corruption or loss. Consult a database administrator to determine whether to use either of these procedures.

(Recommended) Back up the Forcepoint Web Security, Forcepoint DLP, and Forcepoint Email Security databases in their current location, then restore them to the new location. See Back up and restore the reporting databases.

Detach the Forcepoint Web Security, Forcepoint DLP, and Forcepoint Email Security databases from their current location and reattach them in a new location. See:

Detach and reattach the Web or Email Log Database

Detach and reattach the Forcepoint DLP databases

Warning

Before beginning, make sure that the destination SQL Server instance's collation setting matches that of the source SQL Server instance.

To check:

Log onto the SQL Server Management Studio.

Right-click the SQL server instance name and select Properties.

Under the General tab, check the Server Collation value.

Only move the SQL Server databases if the collation values match.

Those upgrading to a newer software version should upgrade the Forcepoint software first, then migrate the databases.

Regardless of which procedure is used, for web and email protection solutions, once the databases are in their new location:

Recreate the Forcepoint SQL Server Agent jobs.

Update the Log Server connection to the Log Database and configure the Log Database to create new database partitions in the correct (new) location. See Update Log Server and Log Database settings.