About Database |
The single database is connected to the central protection Server and stores statistic data on anti-virus network events, settings of the 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 into the central protection Server directly is provided. . Inbuilt drivers for connecting the following databases are provided: •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 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. Database Version Version of the database structure: 473. To find the version of the database of your Server 1.Open the Control Center of your Server. 2.Go to the section. 3.Enter the following query:
4.Click . Database Subsystems All tables of Dr.Web Server database can be divided on 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. Templates. Notifications send configuration, assigning them to administrators. Web console notifications. Notifications of all types that are waiting to be sent. Administrators and groups pf administrators, their permissions. Messages sent by administrators to stations and their templates. License keys assigned at the Server. Propagations of licences between stations, groups, policies, neighbor Servers. Licenses usage reports. Catalogs with frequently repeated data on which other tables are refer. Stations, groups, policies, Proxy servers, their attributes and hierarchy. Interserver connections with neighbor Servers. Infrastructure of trusted applications generating for the Application Control component: settings, collected applications, intermediate data. Data of applications catalog received by collecting processes blockings and activity. Dr.Web Server Configuration Settings of stations and Proxy servers: components configuration, schedule, permissions, updates restrictions. Settings of station groups and Proxy server groups: components configuration, schedule, permissions, updates 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 the Server: •audit log, Task Scheduler, updates; •messages sent by the administrator to stations; •for Dr.Web AV-Desk: financial operations. Events generated by stations: •threats detection, errors and scan statistics; •events of the Application Control component; •devices blockings; •the Agent installation and deinstallation; •log of the Task scheduler on stations; •stations geolocation. Events generated by stations on neighbor Servers (similarly). Current state of the Server subsystems, including news, delayed updates of products. Stations state, 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 the Server; •quarantine; •opened user sessions. State of the neighbor Server stations, including information about hardware and software. Other reference and operational data. |