The issue can be caused by a third-party monitoring solution that acts as a watchdog.

Deep Security installer starts a stored procedure named RunBatchTableMigration, which works to migrate the data. After a while, the procedure suddenly stopped causing the migration task to be terminated. Based on the server0.log, Deep Security Manager service starts or restarts at the same moment.

This happens because there is a third-party solution that monitors the Deep Security process, and starts the process if it is not there. It can disturb the installer and the upgrade process.

To resolve the issue, disable the third-party application and try to upgrade the Deep Security again.