Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Moving the Reporting Databases : Detach and reattach the Web or Email Log Database
Detach and reattach the Web or Email Log Database
Moving the Reporting Databases | Web, Data, and Email Solutions | April 2022
 
Applies to:                                         
*
Forcepoint Web Security and Forcepoint URL Filtering, v8.5.x
*
Forcepoint DLP, v8.5.1, v8.6.x, v8.7.x, v8.8.x, v8.9.x
*
Forcepoint Email Security, v8.5.x
*
Forcepoint appliances, v8.5.x
To move the Log Database by detaching it, manually moving files, and then reattaching the files in a new location, use the following procedure.
1: Detach the Log Database
To prepare to move the Web or Email Log Database, stop all of the SQL Server Agent jobs and wait for them to stop, then detach the database from its current SQL Server location.
1.
On the Log Server machine, use the Windows Services tool to stop the following services:
*
Websense Log Server
*
Websense Email Log Server
2.
On the SQL Server machine, open Microsoft SQL Server Management Studio.
3.
Log into the SQL Server instance that hosts the Log Database.
4.
Disable all web or email protection SQL Server Agent Jobs as follows:
a.
In the left navigation pane, click the SQL Server Agent folder for the instance hosting the Log Database.
b.
Click Jobs, and disable each of the Forcepoint jobs by right-clicking the job and selecting Disable.
The job names are in the format "Websense_xxx_<catalog database name>" where xxx is the type of job and <catalog database name> is the actual name of your catalog database (by default, wslogdb70 or esglogdb76).
Make sure that all of the jobs are completed before continuing. This could take several minutes or a few hours, depending on the details of your installation. Contact your database administrator if you need assistance determining whether the jobs are completed.
5.
Use T-SQL commands or a SQL Server backup tool to create a backup of the database.
Before continuing, verify that the backup files are valid.
6.
To simply copy the database files to a new directory or disk, and then reattach them, continue to step 7.
To move the database to a new instance of SQL Server, first delete the web or email protection SQL Server Agent jobs after disabling them. To do this:
a.
In SQL Server Management Studio, connect to the old instance and expand the SQL Server Agent > Jobs tree.
b.
Right-click each job associated with wslogdb70 or esglogdb76 and select Delete. (The number of jobs depends on product version.)
7.
In SQL Server Management Studio, use the following steps to detach the catalog database (default name wslogdb70 or esglogdb76), each standard logging partition database (wslogdb70_x or esglogdb76_x) and the web protection threats (AMT) partition database (wslogdb_amt_1):
a.
Expand the Databases folder.
b.
Right-click one of the databases, and then select Tasks > Detach.
c.
Repeat this process for each database until the catalog database and all partition databases have been detached. The order does not matter because the Forcepoint SQL Server Agent Jobs are disabled (not running).
The web or email protection Log Database has now been detached from its original location.
2: Move the Log Database
Once the Log Database has been detached from its original location, move it to the new location, reattach it to SQL Server, and recreate the SQL Server Agent jobs.
1.
Navigate to the directory selected for the Log Database during Log Server installation.
2.
Move all database files ending in .mdf and .ldf to the new location.
There should be an mdf file and an ldf file for each database detached in the previous procedure.
3.
On the SQL Server machine, open Microsoft SQL Server Management Studio for the new SQL Server instance, then attach each standard logging (wslogdb70_x or esglogdb76_x) and the web protection threats (AMT) partition database (wslogdb_amt_1) as follows:
a.
Expand the nodes in the left navigation pane until the Databases folder is displayed, then right-click that folder.
b.
Select Attach, then click Add.
c.
Navigate to the location of the Log Database mdf and ldf files, then select a partition database mdf file.
d.
Repeat this process for each standard logging and threats partition database.
e.
Click OK when all partition databases have been selected.
4.
Use the same procedure to attach the catalog database (by default, wslogdb70 or esglogdb76).
5.
To create the SQL Server Agent jobs:
a.
Open the Query window and point to the catalog database (default name wslogdb70 or esglogdb76).
b.
Execute the following stored procedure:
exec dbo.usp_update_views;
go
exec dbo.usp_create_background_jobs;
go
If a Web or Email Log Database is being migrated, continue with Update Log Server and Log Database settings.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Moving the Reporting Databases : Detach and reattach the Web or Email Log Database
Copyright 2022 Forcepoint. All rights reserved.