Migrating the databases

When updating from DriveLock 2020.1 (or older) to 2020.2, the two DriveLock databases are merged. The data from the DriveLock-DATA database will be migrated to the DriveLock database.

As of version 2020.2, the DriveLock-DATA database is no longer used and can be archived or deleted after migration. This applies both to the main "root" databases and to the tenant databases, if used.

If necessary, custom SQL jobs created for maintenance and backup need to be adjusted. This also applies to any queries and tools you may have created that use the DriveLock DATA.

Database Migration Wizard

The wizard is automatically started by the Database Installation Wizard after a successful update.

Make sure to back up all DriveLock databases before database migration.

• The Database Migration Wizard analyzes all DriveLock databases and checks whether data should be migrated and how much data needs to be migrated. Based on the data found, it proposes how to configure the migration.

  It is possible to interrupt and resume the migration process at any time. No data is lost.

• The following data is migrated from the DriveLock-DATA database to the DriveLock database:

  • EDR categories

  • EDR alerts

  • Event data

  • Security Awareness Sessions

    Any EDR categories you have created will need to be migrated to ensure EDR functionality after the update. Events, EDR alerts and Security Awareness Sessions can also be migrated later. We recommend that you migrate only the important data first and schedule the migration of bulk data at a time when activity is low.