Migrating the Data Security manager from server A to server B

Topic 50622 | Management Server Location Change | Data Security Solutions | Version 7.8.x

Complete these instructions to migrate the Data Security manager from one server to another.

Back up Data Security

Navigate to the Backup page in the Data Security manager (Settings > System > Backup).

Fill all required fields on the page, then click OK to save your changes.

These fields will be used at the backup process. (Make sure you include the forensics.)

Use the Windows Task Scheduler tool to Enable DSS Backup task.

After the task is enabled, right-click it and run it.

Once the DSS Backup task is finished, you can see the backup contents in the directory you chose on the Backup page in the Data Security manager.

Keep the backup folder in a convenient location. The folder will be used to restore your settings once you have finished installing Data Security.

For more detailed backup instructions, see the Backup and Restore FAQ in the Websense Technical Library.

Restore Data Security settings on the new machine

Copy the contents of the DSS backup folder from the old Windows Server 2008 R2 machine to a temporary directory on the new Data Security Windows Server 2012 machine.

When the process is complete, you should have a directory that contains an MngDB folder and a subscription.xml file, as well as policies_backup and certs folders.

Open the Windows Control Panel and select Programs and Features. (Depending on your setup, you may first need to select Programs to see the Programs and Features option).

Select Websense Data Security, and then click Uninstall/Change.

When prompted, select Modify, then click Next until you reach the "Restore Data from Backup" screen.

Mark the Use backup data box and browse to the backup folder location. Click Next until the restore process begins.

For more detailed restore instructions, see the Backup and Restore FAQ in the Websense Technical Library.

The new server has a new IP address and host name. You must separately re-register every TRITON management component installed on the new server with the new server address.