Back up and restore the Log Database

Moving the Web Security Log Database : Back up and restore the Log Database

Topic 50531 | Web Security Solutions | Version 7.7.x, 7.8.x | Updated 22-Oct-2013

Before upgrading an existing installation of Microsoft SQL Server to a new version or migrating to a new machine, back up your Websense 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.

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 and catalog database for your Web or Email Security solution.

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

Step 1: Perform a full backup

1.	Open SQL Server Management Studio (Start > All Programs > Microsoft SQL Server 2005 or 2008 > SQL Server Management Studio) and log on to the SQL Server instance that hosts your Websense TRITON reporting databases.

2.	In the Object Explorer, under Databases, locate your Websense Web Security databases.

The default database names are: wslogdb70_n and wslogdb70_amt_1 (partition databases) and wslogdb70 (the catalog database)

In these examples, "n" is the partition number. The higher the number, the newer the partition.

3.	Right-click each database (for example, wslogdb70_1), expand the Tasks menu, and select Back Up.

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

5.	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, as well as recent backups of the catalog database and the active partition to which new log records are currently being added. Continue to the next section when you are ready to temporarily stop database processing.

Step 2: Back up the catalog database and active partition

1.	Stop all Websense Log Server instances in your deployment.

2.	Disable the Web Security database jobs.

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

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

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

Continue with one of the following:

Step 3a: Upgrade in place

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

Step 3a: Upgrade in place

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

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

2.	Once installation is complete, enable the Websense SQL Server Agent jobs.

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

b.	Click Jobs, and enable each of the Websense jobs by right-clicking the job and selecting Enable.

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

3.	Start all Websense Log Server or instances in your deployment.

Log Server resumes sending data to the Log Database, and the ETL job begins processing the Web Security records into the active partition.

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

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

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

2.	Restore the reporting databases from their backup location:

a.	In Object Explorer, right-click Databases and select Restore Database.

b.	Enter the database name in the To database field.

c.	Select From device, then click the browse (...) button.

d.	With File selected (the default), click Add and browse to the backup location.

e.	Select the databases you want to restore from the Select the backup sets to restore list.

f.	Select the Options page of the restore window, then verify that the Restore As column shows the correct location for the destination (restored) partition.

g.	Repeat steps a through f until all databases have been restored.

3.	Recreate the Web Security database jobs on the new SQL Server installation.

a.	Open the Query window and point to the Websense catalog database (default name wslogdb70).

b.	Execute the following stored procedures:

exec dbo.usp_update_views;

exec dbo.usp_create_background_jobs;

Continue with Update the Log Server connection.

Moving the Web Security Log Database : Back up and restore the Log Database

Support

Search

Article Rating:

Related Articles

Quick Links

Service Requests

How are we doing?