A new feature has been introduced in ePO 5.10.0. A new Server Task is introduced to migrate data from an old database schema to the new database schema, post upgrade.
The Server task
Migrate Data to New Tables performs the migration activity over the default scheduled time on every Saturday at 12 p.m.
The data migrates the following:
- Threat Events
- Audit Logs
- Server Task Logs
How the data is migrated:
- During upgrade or a new installation, a new dedicated database instance is created for Threat Events.
- During the upgrade, the Migrate Data to New Tables server task runs for 30 minutes by default. The data is migrated based on 'last created first.'
- When the upgrade is completed successfully, you can schedule the server task Migrate Data to New Tables. The range can be set from 30 minutes to 12 hours.
- When rebuilding the index, there are two notifications:
- One notification when the internal task is started.
- Another notification when it's completed.
Example of the notifications:
- Upgrading from 5.1.x or 5.3.x to 5.10 causes the data migration to take more time to complete because the database tables are converted from INT to BIGINT format.
- Upgrading from 5.9.x to 5.10 causes the data migration to take less time because the database tables are already in BIGINT format.
IMPORTANT:
- Do not purge any of the following logs while the data migration task is running. Purging can affect the data migration task and slow down the task execution time:
- Threat Event Log
- Server Task Log
- Audit Log
- Do not restart the services while the task is executing the task.
