Recreating the log database

If you have not backed up the SES Evolution log database and if a major incident occurs on the server hosting this database, the SES Evolution backends no longer start because no log database can be reached.

You must hence recreate the EsLogs log database. For this, you must have a SES Evolution Installation center EsInstaller.exe with the same version as your current installation.

NOTE
If you do not save the EsAdministration database and if this database is lost, the only way to recreate it is to reinstall the product.

The log database must be created on an existing SQL Server instance.

The EsAdministration and EsLogs databases were hosted in the same SQL Server instance:

  • If the EsAdministration database is still operational:

    1. Use or create a temporary SQL Server instance to create a new EsLogs database.

    2. Restore this database to the target instance.

  • If the EsAdministration database is no longer operational:

    1. Restore the EsAdministration database.

    2. Use or create a temporary SQL Server instance to create a new EsLogs database.

    3. Restore this database to the target instance.

If the EsLogs database was hosted on a separate SQL Server instance

  1. Set up a new SQL Server and a new SQL Server instance using the same machine name, IP address and DNS name as the instance hosting the lost EsLogs database.

New EsLogs databases are created with a SES Evolution Installation Centre EsInstaller.exe of the same version as your current installation.

This database is created on the "destination" instance, which is either a temporary instance, or directly the final target.

  1. Launch the SES Evolution Installation center.

  2. Choose to perform a new installation.

  3. Uncheck as many components as possible to leave only the mandatory components.

  4. Configure the installation:

    1. For the administration and log database, select the "destination" instance as target instance.

    2. Configure all the other parameters as for the original installation. The passwords entered in the Certificates section are of no use.

  5. Start the installation.

  6. Run the Stormshield_Database_Maintenance_Procedures.sql script on the "destination" instance.

  7. Run the following command on the "destination" instance to remove the EsAdministration database that was created during installation:

    EXECUTE master.dbo.Stormshield_DropDatabase @DatabaseName = 'EsAdministration';

    CAUTION
    Take care not to remove the real EsAdministration database.

  8. Run the following command on the "destination" instance to create the accesses for the Windows account used by the backends:

    EXECUTE master.dbo.Stormshield_CreateBackendAccess @BackendAccountName = 'DOMAIN_NAME\BACKEND_USER_NAME'

    where DOMAIN_NAME\BACKEND_USER_NAME corresponds to the Windows domain account entered during installation of the SES backends.

  9. If the "destination" instance is a temporary instance, move the newly created EsLogs database to the final target instance by running the Moving the SES Evolution databases procedure.