Preparing the Log Database for upgrade

Before you begin

Applies to:
  • Forcepoint Web Security, v8.5.x
  • Forcepoint URL Filtering, v8.5.x

It is important that you back up your current web protection reporting databases, stop Log Server, and stop all Log Database jobs.

Warning:
  • If database operations are active during upgrade, the Log Database may be left in an inconsistent state, rendering it unusable.
  • When this occurs, it can be difficult to fix.
  • Make sure to stop Log Server and the database jobs, as described below, before upgrading the database.

Steps

  1. Back up the databases and stop Log Server.
    1. Back up the reporting databases for your web protection solution.
      Refer to Microsoft documentation for instructions on backing up databases. The web protection databases are named wslogdb70 (the catalog database), wslogdb70_amt_1 (the threats partition), and wslogdb70_1, wslogdb70_2, and so on (the standard logging partition databases).
    2. On the Log Server machine, use the Windows Services tool to stop Websense Log Server.
  2. Make sure no database jobs are running.
    It is best to stop all Log Database jobs prior to starting the upgrade, but, before it upgrades the Log Database, the upgrade process will attempt to stop any Log Database jobs not already stopped. If the jobs cannot be stopped, you will need to stop them manually. However, you do not need to exit the installer to do that.
    Stop the Log Database jobs using these steps:
    • If you have a full version of Microsoft SQL Server:
      1. Log in to the Microsoft SQL Server Management Studio and expand SQL Server Agent > Jobs (in Object Explorer).
      2. To disable all currently active SQL Server Agent jobs, right-click each of the following jobs and select Disable:
        • Websense_ETL_Job_wslogdb70
        • Websense_AMT_ETL_wslogdb70
        • Websense_IBT_DRIVER_wslogdb70
        • Websense_Trend_DRIVER_wslogdb70
        • Websense_Maintenance_Job_wslogdb70

        Disabling the jobs prevents them from executing at the next scheduled time, but does not stop them if a job is in process.

        Make sure all jobs have completed any current operation before proceeding with upgrade.

      3. After upgrade, verify that the jobs have been to enabled.

        Enable any that were not automatically enabled by the upgrade process. Normal database operations will then resume.

    • If you have SQL Server Express:
      1. Log in to the Microsoft SQL Server Management Studio.
      2. Expand the Databases tree to locate the catalog database (wslogdb70, by default), then expand the catalog database node.
      3. Expand Service Broker > Queues.
      4. Right click dbo.wse_scheduled_job_queue and select Disable Queue.
      5. The upgrade process will re-enable the job queue. After upgrade, verify that the Queue has been enabled.

        Enable it, if necessary, by repeating the process, this time ultimately selecting Enable Queue to resume normal database operations.