Backup and restore the TRITON reporting databases

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

TRITON reporting databases (Web Log Database, Data Security Incident and Configuration Database, and Email Log Database) are supported on the latest service packs of:

Microsoft SQL 2008 R2 Express

Microsoft SQL Server 2008

Microsoft SQL Server 2008 R2

Microsoft SQL Server 2012

Microsoft SQL Server 2014

Microsoft SQL Server 2016

Before upgrading an existing installation of Microsoft SQL Server to a new version or migrating to a new machine, back up your TRITON reporting databases to a safe location.

If you are upgrading in place, the upgrade process should not affect the reporting databases, but it is a best practice to make a backup copy to safeguard against corrupted data or other data loss.

If you plan to migrate your databases to a new Microsoft SQL Server installation on another machine, to minimize downtime, start by installing and configuring SQL Server in the new location.

The upgrade or migration process begins with a backup of your existing reporting databases. Because the backup process can be quite time consuming, the instructions in this document ask you to perform the backup in 2 stages.

For web and email solutions:

The initial backup can be performed while the Log Database is online, processing data.

The second, incremental backup is performed on just the active partition (the partition currently receiving new records) and catalog database for your web or email solution.

The intent is to minimize the database downtime required for the upgrade or database migration.

1: Perform a full database backup

Open SQL Server Management Studio (Start > All Programs > Microsoft SQL Server 2008 | 2012 | 2016 > SQL Server Management Studio) and log onto the SQL Server instance that hosts your TRITON reporting databases.

In the Object Explorer, under Databases, locate your TRITON databases. The default database names are:

For web solutions, wslogdb70_n and wslogdb70_amt_1 (partition databases) and wslogdb70 (the catalog database)

For email solutions, esglogdb76_n (partition databases) and esglogdb76 (the catalog database)

For data solutions, wbsn-data-security and wbsn-data-security-temp-archive

In the web and email examples, "n" is the partition number. The higher the number, the newer the partition.

Right-click each database, expand the Tasks menu, and select Back Up.

Make sure the Backup type is "Full."

In the Back Up Database window, you can either accept the default backup Destination, or click Add and specify a new path or name for the backup file. Save the file as *.BAK. When you are finished, click OK to run the backup.

Repeat steps 3 and 4 to back up each of the remaining databases.

At the end of this process, you have full backups of all of your older partition databases, and recent backups of your active partition (the one that new log records are being added to) and catalog databases. Continue to the next section when you are ready to temporarily stop database processing.

2: Back up the catalog database and active partition (Web and Email)

Stop all Web Log Server or Email Log Server instances in your deployment.

Disable the web or email protection database jobs.

In the left navigation pane, click the SQL Server Agent folder for the instance hosting the Log Database.

Click Jobs, and disable each of the web or email protection 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.

Perform a differential backup of the catalog database (wslogdb70 or esglogdb76). This will back up anything that has changed since the initial backup performed in Part 1 of this procedure.

Perform a differential backup of the active database partition (the one that is still receiving new log records). Its name is something like wsglogdb70_10 or esglogdb76_5).

3a: Upgrade in place

If the machine hosting your database engine is adequate to host an upgraded version of SQL Server:

Stop the TRITON AP-DATA server. The Web and Email Log Servers are already stopped. Change the server startup type to Disabled.

Upgrade your Microsoft SQL Server installation, following the instructions in your Microsoft documentation.


	Note During upgrade, select the collation that the wbsn-data-security database uses. The SQL Server collation must match the Data Security 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. You will see the collation listed in the Maintenance section.

Once installation is complete, enable the Forcepoint SQL Server Agent jobs:

In the left navigation pane, click the SQL Server Agent folder for the instance hosting the Log Database.

Click Jobs, and enable each of the web or email protection jobs by right-clicking the job and selecting Enable.

Start all Web Log Server or Email Log Server instances in your deployment.

Start the TRITON AP-DATA server.

Log Server resumes sending data to the Log Database, and the ETL job begins processing the web or email records into the active partition.

3b: Migrate the database to a new SQL Server host

If you are moving the reporting database to SQL Server on another machine:

Install the desired version of 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 Data Security 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. You will see the collation listed in the Maintenance section.

Open SQL Server Management Studio (Start > All Programs > Microsoft SQL Server 2008 | 2012 | 2016 > SQL Server Management Studio) and log on to the SQL Server instance that will host your TRITON reporting databases.

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).

Execute the following stored procedures:

exec dbo.usp_update_views;

exec dbo.usp_create_background_jobs;

If you are migrating a Web or Email Log Database, continue with Update Log Server and Log Database settings.

Direct the TRITON AP-DATA management components to the new database server. To do this, run the TRITON Setup installer, and select Modify.

Direct TRITON AP-EMAIL to the new database server by navigating to Settings > Reporting > Log Database and changing the configuration.