|
About the Database |
|
A unified database is connected to the Centralized Protection Dr.Web Server and stores statistical 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: An embedded SQLite3 database built into Dr.Web software. An external database. Dr.Web software comes with built-in drivers for the following databases: •MySQL, •Oracle, •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 meets your requirements, such as: scalability, database software maintenance, administrative capabilities provided by the database itself and also the standards adopted in your company. Database Version Version of the database structure: 542. How to find out which database version your Dr.Web Server is using: 1.Open the Control Center of your Dr.Web Server. 2.Go to the Administration → SQL console section. 3.Enter the following query:
4.Click Execute. Database Subsystems All tables of Dr.Web Server database can be divided into the following subsystems: Database Metadata Metadata that describe the database model (physical and, to some extent, logical model in the tables_refs table). Notifications Descriptions of existing notifications and their variables. Templates. Settings for sending notifications, assigning them to administrators. Web console notifications. Pending notifications. Administrators Administrators and administrator groups, their privileges. Messages sent by administrators to stations, and their templates. License Management License keys assigned at Dr.Web Server. Propagation of licenses between stations, groups, policies, neighboring Dr.Web Servers. License usage reports. Catalogs Catalogs of data frequently referenced by other tables. Stations and Anti-virus Network Tree Stations, groups, policies, Dr.Web Proxy Servers, their attributes and hierarchy. Neighborhood Interserver connections with neighboring Dr.Web Servers. Application Control 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 Dr.Web Server configuration. Station Configuration Settings of stations and Dr.Web Proxy Servers: component configurations, schedule, permissions, update restrictions. Group Configuration Settings of station groups and Dr.Web Proxy Server groups: component configuration, schedule, permissions, update restrictions. Policy Configuration Settings of policies: components configuration, schedule, permissions, updates restrictions. Other Object Configuration Profiles of the Application Control component, their rules and user-defined component settings. Dr.Web Server Events Events generated by Dr.Web Server: •audit log, Task Scheduler, updates; •messages sent by the administrator to stations. Station Events Events generated by stations: •threat detection, error and scan statistics; •Application Control component events; •device locking; •installation and uninstallation of Dr.Web Agent; •task scheduler log on stations; •station geolocation. Station Events from Neighbor Dr.Web Server Events generated by stations on neighboring Dr.Web Servers (similar to Station Events). Dr.Web Server Status Current state of the Dr.Web Server subsystems, including news, deferred product updates. Station Status Station states, including: •abnormally terminated connections; •installed components and their status (started/stopped), modules and virus databases; •information on hardware, software, and station users; •registered connections of the Dr.Web Agent and Dr.Web Server; •quarantine; •open user sessions. Station Status from Neighbor Dr.Web Servers Status of the neighboring Dr.Web Server stations, including information about hardware and software. Other Tables Other reference and operational data. |