Back up and restore the reporting databases

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

The databases (Web Log Database, DLP Incident and Configuration Database, and Email Log Database) are supported on a number of versions of Microsoft SQL Server. Find the supported versions of Microsoft SQL Server for your product by selecting the appropriate link in this article.

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

• Upgrading in place 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.
• When migrating 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 the existing reporting databases. Because the backup process can be quite time consuming, the instructions in this document 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.

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