Moving the TRITON Reporting Databases

Moving the TRITON reporting databases | Web, Data, and Email Solutions | v8.3.x | 15-Dec-2016

If you need to move your Microsoft SQL Server database to a new location (directory, drive, or machine), this article describes procedures you can use to move your TRITON reporting databases to minimize risk of data corruption or loss. Consult your database administrator to determine whether either of these procedures is appropriate for your organization.

(Recommended) You can back up your TRITON AP-WEB, TRITON AP-DATA, and TRITON AP-EMAIL databases in their current location, and restore them to the new location. See Backup and restore the TRITON reporting databases.

You can detach your TRITON AP-WEB, TRITON AP-DATA, and TRITON AP-EMAIL 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 TRITON AP-DATA databases

If you are performing this procedure while upgrading to a newer software version, be sure to upgrade your TRITON software first.

For web and email protection solutions, regardless of which procedure you choose, once the databases are in their new location, you must:

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.

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 (Start > All Programs > Microsoft SQL Server 2008 | 2012 | 2016 > 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.