Moving the SES Evolution databases

You can move the SES Evolution databases to another SQL server or another SQL Server instance. For example, this enables you to migrate the databases from one SQL Server release to another release without risking an update on the production instance.

  • The Windows account used for the backend identity when installing SES Evolution must be a domain account.

  • Before moving a database, stop the administration console, the agent handlers, and the SES Evolution backend in this sequence. During the operation, the administration console is not available, but the agents continue to protect the workstations and store the logs generated locally. These logs are sent to the databases and/or to Syslog once the procedure is complete, when the agents reconnect.

If you move the two databases, first move EsAdministration and then EsLogs.

  1. Close all administration consoles to ensure no data are being edited.

  2. On each machine where an agent handler is installed, stop the "Stormshield Endpoint Security Server" Windows service:

    • Either via Windows services,

    • Or via the net stop EsrCoreSvc command.

  3. On each machine where a backend is installed, stop the IIS server:

    • Either via the "Internet Information Services (IIS) Manager",

    • Or via the iisreset/stop command.

  4. For each database to move:

    1. Check that the Stormshield_Database_Maintenance_Procedures.sql script has been run on the "destination" instance

    2. Create a full backup of the database to move:

      EXECUTE master.dbo.Stormshield_BackupDatabase
      @DatabaseName = 'EsXxx',
      @BackupDirectory = 'E:\Backups\EsXxx',
      @BackupType = 'full',
      @CopyOnly = 1;

      where Xxx is either Administration or Logs.

    3. Perform the Restoring a SES Evolution database procedure.

  5. On each machine where a backend is installed, restart the IIS server:

    • Either via the "Internet Information Services (IIS) Manager"

    • Or via the iisreset/start command.

  6. On each machine where an agent handler is installed, restart the "Stormshield Endpoint Security Server" Windows service:

    • Either via Windows services,

    • Or the net start EsrCoreSvc command.

  7. Delete the source databases once you have confirmed that SES Evolution is operational.

If the procedure fails, return to the initial status:

  1. Restore the web.config files you have saved in the restore procedure.

  2. Restart the backends and agent handlers.