On the Database tab, you can configure the DB required for Dr.Web Server operation.
|
Dr.Web Server database structure is available in the form of a separate manual of the same name. The document can be opened from the Support section in Dr.Web Security Control Center. |
To specify parameters for working with the database
1.In the Number of connections field, specify the maximum number of Dr.Web Server connections with the database.
Do not change the default value when using the embedded database. The use of an external database may require a higher value. Recommendations on determining the optimal value are given in Appendices, in the Dr.Web Server Load and Recommended Configuration Parameters section.
|
The embedded DB is intended for use in networks where about 400–600 stations are connected to Dr.Web Server. If the hardware configuration of the computer on which Dr.Web Server is installed and the load level of other executing tasks permit, between 1000 and 1500 stations can be connected. Otherwise, you must use an external DB. Depending on the configuration and the load level of the computer running Dr.Web Server, the external DB may be used on the same or on a dedicated computer. If you use an external DB in an anti-virus network with more than 10 000 stations, it is recommended that you follow these minimal system and hardware requirements: •3 GHz processor CPU, •at least 6 CPU cores, •at least 4 GB RAM for Dr.Web Server and at least 8 GB RAM for the DB server, •Unix-like OS. |
When working in an anti-virus network with a large number of client connections to Dr.Web Server, it is recommended that you consult with the Doctor Web technical support team before changing the value.
2.Set the Automatically purge the database after maintenance procedures flag to automatically perform delayed purging of the database after its initialization, upgrade, and import. If the flag is cleared, automatic purging is not performed. In this case it is recommended to configure the Purge database task in the Dr.Web Server schedule or purge the database manually in the Database Management section.
To perform automatic purging, a hidden task is created in the Dr.Web Server schedule. The task is executed the next night after the designated maintenance procedures, at 01:17 local time of Dr.Web Server. The task is executed only if the Dr.Web Server schedule does not contain another Purge database task within the next 24 hours relative to the maintenance procedures.
3.Select the database type in the Database drop-down list:
•MySQL—external DB,
•ODBC—to use an external DB via an ODBC connection (for Microsoft SQL Server/Microsoft SQL Server Express),
|
If warnings or errors occur while Dr.Web Server interacts with the Microsoft SQL Server DBMS via the ODBC, please make sure that you are using the latest available DBMS version for this edition. You can learn how to determine whether an update is available on the following Microsoft company page: https://learn.microsoft.com/troubleshoot/sql/general/determine-version-edition-update-level. |
•Oracle—external DB for all platforms except FreeBSD,
|
If you use an Oracle external DBMS via an ODBC connection, install the latest version of the ODBC driver delivered with the DBMS. It is strongly recommended not to use the Oracle ODBC driver supplied by Microsoft. |
•PostgreSQL—external DB,
•SQLite3—embedded DB (a component of Dr.Web Server).
4.Set the necessary settings for working with the DB:
•For the embedded DB, if necessary, enter the full path to the database file in the File name field and specify the cache size and the flush mode.
•The parameters of an external DB are described in detail in the Appendices document, Appendix A. The Description of the DBMS Settings. The Parameters of the DBMS Driver.
5.Click Save to apply the specified settings.
|
The Dr.Web Server distribution kit contains embedded clients for the supported DBMS, so note the following: •If you plan to use the embedded DBMS clients supported within Dr.Web Server, then during installation (upgrading) of Dr.Web Server make sure that installation of the corresponding embedded DBMS client is enabled in the Database support section of the installer settings. •If you plan to use the Oracle DB via an ODBC connection as your external database, then during installation (upgrading) of Dr.Web Server, in the installer settings, disable installation of the Oracle DBMS embedded client (in the Database support → Oracle database driver section). Otherwise you will be unable to work with the Oracle DB via ODBC because of a library conflict.
The Dr.Web Server installer supports product modification mode. To add or remove separate components, for instance, database management drivers, run the Dr.Web Server installer and select the Change option. |
The embedded DB is intended for use by default. This mode considerably increases the load on Dr.Web Server. It is recommended to use an external DBMS in large anti-virus networks. The procedure for changing the DB type is described in the Appendices, document, the Changing the Type of the DB for Dr.Web Enterprise Security Suite section.
|
It is possible to perform operations related to purging the database used by Dr.Web Server, in particular: deleting records of events, as well as information about workstations that have not visited Dr.Web Server for a certain period of time. To purge the database, open the Setting Dr.Web Server Schedule and create an appropriate task. |