How to migrate the databases

You can keep the default options that are pre-set in the Database Migration Wizard. Changing them is recommended only in special cases.

The migration process goes through the following steps:

1. Connect to the main database

   The first step is to perform a connection test to the main DriveLock database, reading the connection data from the registry.

   In case you want to change the default settings, click the Advanced Mode button (see 3.).

2. Analyze the databases

   After testing the connection, the wizard analyzes the data in the databases.

   Then, it determines the connection parameters to the event databases and, if available, the tenant databases from the main DriveLock database.

   The wizard checks the connection to and version of each database. The databases must be up to date to support migration.

   If the version of a database is not up to date, please use the Database Installation Wizard to update the database and start the migration again.

3. Configure data migration settings

   This step is only displayed in Advanced Mode. Migration is configured on a per-client basis and provides the following customization options:

   • Prepare databases

     This option runs the database maintenance (index maintenance) on both databases and automatically prepares the event data to ensure a more efficient migration.

   • Migrate event data

     This option migrates the events as they can be evaluated in the reports in DCC / DOC.

     • Reprocess events after migration

       This option is necessary to create the links from the events to the other data such as computers, users, drives, devices, etc. These are displayed in DCC Forensics and DOC related entities.

       The processing of this data may take some time for larger amounts of data. When the DriveLock Enterprise Server is running, this will happen in the background.

     • Check for existing events

       Use this setting to check whether the data in the target database has already existed before the migration. This may be the case if you migrate the data at a later point in time. This option can be turned off to speed up the migration. If errors occur, we recommend repeating the migration and checking the data. In case an error occurs, no data will be lost.

   • Migrate security awareness session data

   • Migrate EDR categories

   • Migrate EDR alerts data

   • Processing batch sizes

4. Database migration processing

   • The databases are migrated one after the other, depending on the tenant. You can stop the migration and start it again. The output shows the progress of the migration.

   • Migrated data is deleted from the source database (here the event database).

   • After successful migration, the DriveLock Enterprise Service is started again.

     When the migration is finished, the event databases are no longer needed and can be archived or deleted.