Migrating Data on a Single-tier Installation on Linux

After you install the version
16.0.2
Enforce Server, you use the Migration Utility to migrate data to the new instance. The Migration Utility migrates Enforce Server data in the following two phases:
  1. Runs a report to confirm the status of the file system
    The report lists information to confirm that the file system is ready for migration and identifies issues. The report lists saved customizations. Saved customizations includes certificates, keystores, plugins, FlexResponse scripts, and configuration file settings.
    The first phase of the migration also moves data files, document profiles, property files, plugins, and keystores to the
    16.0.2
    instance.
  2. Performs pre-checks before DLP services are taken down during the migration
    The second phase of the migration moves incidents, indexes, services, and the database.
Before you start the migration, use the Upgrade Readiness tool to confirm that the Oracle database is ready for migration. See Checking the database update readiness.
You can migrate data silently or using interactive mode.
The process to migrate data does not move all plug-ins. See Migrating plug-ins.
Before you run the Migration Utility, you must switch to
root
user.

Migrate silently

  1. Open the command prompt window.
  2. Switch to root user:
    su root
    .
  3. Go to the following directory:
    /opt/Symantec/DataLossPrevention/SingleTierServer/
    16.0.20000
    /Protect/Migrator
  4. Run the following command as root to complete the migration using silent mode:
    ./migrateSingleTierServer.sh -silent -sourceVersion="
    <previous version>
    " -jreDirectory="
    /opt/AdoptOpenJRE/jdk8u
    <version>
    -jre
    "
    Where
    <previous version>
    is the previous version number and
    /opt/AdoptOpenJRE/jdk8u
    <version>
    -jre/
    points to the current JRE location.

Migrate using interactive mode

  1. Open the command prompt window.
  2. Switch to root user:
    su root
    .
  3. Go to the following directory:
    /opt/Symantec/DataLossPrevention/SingleTierServer/
    16.0.20000
    /Protect/Migrator
  4. Run the Migration Utility using the following command:
    ./migrateSingleTierServer.sh
  5. Confirm that OpenJRE is installed and that the directory is correct, then enter
    Y
    .
  6. Press
    Enter
    .
    If no JRE displays, you must install it before proceeding.
    A list of the migration phases appears.
  7. Enter
    Y
    and press
    Enter
    to start phase 1.
    After phase 1 completes, a message provides a path to where you can access the phase 1 report. The report lists details about the data files, document profiles, property files, plugins, and keystores that were migrated. Resolve any errors listed on this page before proceeding to phase 2.
  8. Select the active
    Symantec Data Loss Prevention
    version to migrate and press
    Enter
    .
    The previous version continues to run, including the services and the database, after phase 1 completes. You can exit the migration process and continue to phase 2 at a later time.
  9. Enter
    Y
    and press
    Enter
    to start phase 2.
    A message indicates when the migration completes.
    If the upgrade fails because of DatabaseProcessCheck, see Stop all Symantec Data Loss Prevention database sessions.
  10. If the migration fails, review the Enforce Server migration logs in
    MigrationUtility.log
    at
    /var/log/Symantec/DataLossPrevention/EnforceServer/
    16.0.20000
    /debug/
    for more details.