The single database is connected to the central protection Dr.Web Server and stores statistic data on anti-virus network events, settings of Dr.Web Server itself, parameters of protected stations and anti-virus components installed on protected stations.
You can use the following types of databases:
. The SQLite3 database that is embedded directly into the central protection Server is provided.
. Inbuilt drivers for connecting the following databases are provided:
•PostgreSQL (including Postgres Pro),
•ODBC driver to connect other databases such as Microsoft SQL Server/Microsoft SQL Server Express.
You can use any database that corresponds to your demands. Your choice should be based on the needs that must be satisfied by the data store, such as: capability to service the anti-virus network of corresponding size, features of database software maintenance, administration capabilities provided by the database itself and also requirements and standards which are accepted for use in your company.
Version of the database structure: 522.
To find the version of the database of your Dr.Web Server
1.Open the Control Center of your Dr.Web Server.
2.Go to the section.
3.Enter the following query:
All tables of Dr.Web Server database can be divided into the following subsystems:
Metadata that describe the database model (physical and partly logical model in the tables_refs table).
Existing notifications descriptions and variables used.
Settings for notification sending, assignation of notifications to administrators.
Web console notifications.
Administrators and administrator groups, their permissions.
Messages sent by administrators to stations and their templates.
License keys assigned at Dr.Web Server.
Propagation of licenses between stations, groups, policies, neighbor Dr.Web Servers.
License usage reports.
Catalogs of data frequently referenced by other tables.
Stations, groups, policies, Proxy servers, their attributes and hierarchy.
Interserver connections with neighbor Dr.Web Servers.
Generation of trusted applications of the Application Control component: settings, collected applications, intermediate data.
Application catalog data on process blocking and activity.
Dr.Web Server configuration.
Settings of stations and Proxy servers: component configurations, schedule, permissions, update restrictions.
Settings of station groups and Proxy server groups: component configuration, schedule, permissions, update restrictions.
Settings of policies: components configuration, schedule, permissions, updates restrictions.
Profiles of the Application Control component, their rules and user settings of components.
Events generated by Dr.Web Server:
•audit log, Task Scheduler, updates;
•messages sent by the administrator to stations;
•for Dr.Web AV-Desk: financial operations.
Events generated by stations:
•threat detection, errors and scan statistics;
•events of the Application Control component;
•installation and deinstallation of the Agent;
•log of the Task scheduler on stations;
•geolocation of stations.
Events generated by stations on neighbor Dr.Web Servers (similar to Stations Events).
Current state of the Dr.Web Server subsystems, including news, delayed updates of products.
Station states, including:
•abnormally terminated connections;
•installed components and their state (started/stopped), modules and virus databases;
•information on hardware and software, users of stations;
•registered connections of the Agent and Dr.Web Server;
•opened user sessions.
State of the neighbor Dr.Web Server stations, including information about hardware and software.
Other reference and operational data.