Archiving lets you manage the size of your incident database and optimize performance. Backup lets you safeguard your policies, forensics, configuration, data, fingerprints,
encryption keys, and more.
If you do not plan to archive incidents or perform system backup and restore, you do not need to fill out this screen.
Before proceeding, create a folder in a location that both the database and management server can access. (The folder must exist before you click Next.)
On average, this folder will hold 10 GB of data, so choose a location that can accommodate this.
On the Temporary Folder Location screen, complete the fields as follows:
- Enable incident archiving and system backup: Check this box if you plan to archive old or aging incidents and perform system backup or restore. This
box does not appear when you run the installer in Modify mode and perform a disaster recovery restore operation.
- From SQL Server: Enter the path that the SQL Server should use to access the temporary folder. For best practice, it should be a remote UNC path, but
local and shared network paths are supported. For example: c:\folder or \\10.2.1.1.\folder. Make sure the account used to run SQL has write access to this folder.
- From Management Server: Enter the UNC path the management server should use to access the temporary folder. For example: \\10.2.1.1.\folder. Enter a
user name and password for a user who is authorized to access this location.
To grant this permission, issue the following T-SQL commands on the SQL Server instance:
USE master
GRANT BACKUP DATABASE TO <user>
GO
After installation of Forcepoint DLP components, you can revoke this permission:
USE master
REVOKE BACKUP DATABASE TO <user>
GO