Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Migrating web solutions to a new operating system > Moving web policy components to a new machine
Moving web policy components to a new machine
Deployment and Installation Center | Web Protection Solutions
 
When you move the same web protection software version to a new machine, first perform a new installation of the components on the new machine. Once the components are running successfully on the new machine, use the following procedure to preserve your policies and system configuration.
1.
*
*
*
*
2.
PgSetup --save backup.policydb
This command backs up only data stored in the Policy Database. It does not back up custom block pages or customized configuration files. To preserve customized configuration files or block pages, back those up separately.
3.
4.
*
Windows: Navigate to the Websense\Web Security directory and enter the following command:
WebsenseAdmin stop
*
Linux: Use the /opt/Websense/WebsenseAdmin stop command.
5.
PgSetup --restore backup.policydb --no-clobber
The "no-clobber" parameter eliminates the need to update the token value in the config.xml file (a step included in migration procedures prior to 7.7).
6.
*
Windows: Navigate to the Websense\Web Security directory and enter the following command:
WebsenseAdmin start
*
Linux: Use the /opt/Websense/WebsenseAdmin start command.
Once the new machine has successfully replaced the original machine in your deployment, and you have verified that your policy information is correct, you are ready to begin the upgrade process.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Migrating web solutions to a new operating system > Moving web policy components to a new machine
Copyright 2018 Forcepoint. All rights reserved.