3b: Migrate the database to a new SQL Server host
Steps
-
Install the SQL Server on the new machine.
Note:
During installation, select the collation that the wbsn- data-security database uses. The SQL Server collation must match the incident and reporting database collation exactly.
To determine a database collation, use the Microsoft SQL Server Management Studio. Right-click the server name and select Properties, then right-click the database name and do the same. The collation is listed in the Maintenance section.
- Open SQL Server Management Studio and log on to the SQL Server instance that will host the reporting databases.
-
To restore the reporting databases from their backup location:
- In Object Explorer, right-click Databases and select Restore Database.
- Enter the database name in the To database (or Database) field.
- Select From device (or Device) then click the browse (...) button.
- With File selected (the default), click Add and browse to the backup location.
- Select the databases you want to restore from the Select the backup sets to restore list.
- Select the Options page of the restore window, then verify that the Restore As column shows the correct location for the destination (restored) partition.
- Repeat steps a through f until all databases have been restored.
-
Recreate the web or email database jobs on the new SQL Server installation.
- Open the Query window and point to your catalog database (default name wslogdb70 or esglogdb76).
- Run the following stored procedures:
exec dbo.usp_update_views;
go
exec dbo.usp_create_background_jobs;
go
- Direct the Forcepoint DLP management components to the new database server. To do this, run the Forcepoint Security Setup program, and select Modify.
- Direct Forcepoint Email Security to the new database server by navigating to the Settings > Reporting > Log Database page and changing the configuration.