Kaspersky Security 9.x for Microsoft Exchange Servers

Backup and statistics database

April 2, 2024

ID 134320

The application stores Backup data and application statistics in a special database deployed on a Microsoft SQL Server, the so-called the Backup and statistics database (hereinafter also database).

During installation, the application can create a new database or use an existing database. When the application is removed, the database can be saved on an SQL server for future use.

The Backup and statistics database can be stored locally on one computer with the Security Server or on a remote computer on the corporate LAN.

Kaspersky Security does not encrypt data transmitted between the Security Server and the database. When the database is hosted on a remote computer, you have to manually encrypt data transmitted via communication channels if such encryption is required by the information security policy of your company.

Some part of the application configuration data are stored in the database. The application does not control unauthorized modification of those data nor their integrity. You will have to take your own steps in order to protect the data against unauthorized access and control the data integrity.

When creating an SQL database, the server uses local collation rules. Take the Collation parameter into account when installing the application to avoid register-dependent behavior and errors when connecting to the database.

Database settings

The Backup and statistics database settings are stored in the following configuration file:

<application setup folder>\Configuration\BackendDatabaseConfiguration2.config

It is an editable XML file. It contains the following settings:

  • AdditionalConnectionParameters – additional settings of the SQL server connection. The value of this setting is automatically defined by the application based on the information provided by the administrator during installation of the application.
  • SqlServerName : name of the SQL server. It is specified by the application automatically as <SQL server name>\<copy> based on information provided by the administration during installation of the application.
  • DatabaseName – name of the main database. It is specified by the application automatically based on information provided by the administration during installation of the application.
  • FailoverPartner: settings (SQL server and instance) of the database mirror. They are specified by the application automatically as <SQL server name>\<copy>.

In the Additional connection parameters field, it is not recommended to define the SqlServerName and DatabaseName settings because they are already defined in the Name of SQL server and Database name fields.

Database mirroring

The application supports the Database Mirroring technology. If this technology is used in the configuration of your SQL server, the application will use it automatically. In other words, if the main Backup and statistics database fails or is disabled, the application automatically switched to using a database mirror. The application automatically switches back to the primary database as soon as it has been restored.

If the application is installed with or works with an SQL database configured with AlwaysOn technology, you must synchronize the rights between all servers that belong to the database mirroring group.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.