How to transition Enforce from one OS to another

book

Article ID: 159877

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

Moving the Enforce Server from a machine on one version of an OS (Operating System) to another.  For example, moving from 32 bit to 64 bit OS.

Resolution

The process to transition Enforce from one OS to another depends on whether the database is located on the Enforce server as well. We will address both scenarios:

1. Enforce with database NOT on same system - To do this process you simply backup the Vontu directory (as well as your krb5.ini or conf if you are setup for AD authentication). Then wipe the OS and install your new one. Then install Enforce with the correct platform installer (64-bit vs 32-bit), telling it to NOT initialize the database to connect to the existing one. (Note: Must use the same Administrator password when reinstalling). Then you can restore your krb5.ini to where it was previously, as well as use the backup of the Vontu directory to restore any Lookup Plugins you have configured.

 

*** If your current version is greater than 11.1, in addition to these steps you will need the Cryptomasterkey.properties file because when you connect to a existing database it will prompt you for that file. It can be found in Vontu\Protect\config***

2. Enforce with database on same system - In order to do this, you first must backup a cold backup copy of your database. Also backup the Vontu directory(as well as your krb5.ini or conf if you are setup for AD authentication). Noting the version of Oracle currently being used you can then wipe the OS, and install the new one. Next you will need to install Oracle being sure to use the correct installer based on architecture (32-bit vs 64-bit). Then you would create a blank database. Once that is done you must stop all Oracle services and replace the database datafiles with your backup. Then you can start Oracle. Then install Enforce with the correct platform installer (64-bit vs 32-bit), telling it to NOT initialize the database to connect to the existing one. (Note: Must use the same Administrator password when reinstalling). Then you can restore your krb5.ini to where it was previously, as well as use the backup of the Vontu directory to restore any Lookup Plugins you have configured.

 

*** If your current version is greater than 11.1, in addition to these steps you will need the Cryptomasterkey.properties file because when you connect to a existing database it will prompt you for that file. It can be found in Vontu\Protect\config***

 

Some modification of these steps may be necessary in special circumstances.