Scenario

In certain cases one may need to move an SQL database that stores KSE operational data to another SQL server/instance. The following procedure can be used to achieve that:

Step-by-step guide

1. Change the startup type of KSE services to Manual.
2. Stop the KSE services which use this database (may be located on several hosts in case of DAG, for example).
3. Create a backup of the KSE database using MS SQL tools.
4. Restore the database on a new SQL server/instance using MS SQL tools.

5. Assign the required rights for this database according to this article.

6. Manually edit the file BackendDatabaseConfiguration*.config on every KSE server that will use this database. See this article for instructions. 

7. In the scenario when KSE doesn't use the DB default port, we must edit the BackendDatabaseConfiguration*.config file properly, here is an example when custom port is 1435:

   <SqlServerName>sqlag02ls,1435</SqlServerName>

8. Manually change the values of BackendDatabaseName and BackendSqlServerName with the new ones in the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Kaspersky Lab\Kaspersky Security for Microsoft Exchange Server" on every KSE server that will use this new database.

9. Return the startup type for the KSE services back to original values.
10. Start the KSE services.
11. Verify that there are no errors in event logs after the service will be started.