Database Management

The Database management section allows to perform direct maintenance of the database with which Dr.Web Server is operated.

The General section contains the following parameters:

•The Last DB maintenance field—the date of last execution of the database maintenance commands from this section.

•The list of commands to maintain the database which includes:

▫Commands similar to the tasks from Dr.Web Server schedule. The names of commands correspond to the names of tasks in the Action section of the Server schedule (description of corresponding schedule tasks is given in the Tasks types and their parameters table).

▫The Analyse database command. It is designed to optimise the Server database using the analyze command.

▫The Purge non-activated stations command. It is designed to delete accounts of stations that were created in the anti-virus network but have never been connected to the Server. Specify the period after which the unused station accounts should be purged.
You can view the list of unused station accounts in the hierarchical list of the anti-virus network, in the Status → New group.

To execute database maintenance commands

1.In the commands list, set the flags for the commands you want to execute.

If necessary, change the time periods for the database purging commands, after which stored information is confirmed outdated and should be removed from the Server.

2.Click Apply now. All selected commands will be executed immediately.

For postponed or/and periodic automatic execution of these commands (except Analyse database), use Server Task Scheduler.

To manage database use the following buttons on the toolbar:

Import,

Export.

Database Export

To save the database information into a file, perform the following actions:

1.Click Export on the toolbar.

2.In the export settings configuration window, select one of the following variants:

•Export entire database to save all information from the database into a gz archive. Exported XML file is similar to the database export file which is obtained when running the Server executable file from the command line with the xmlexportdb switch. This export file can be imported when running the Server executable file from the command line with the xmlimportdb switch.
These commands are described in details in the Appendices documents, in the H4.3. Database Commands section).

•Export information on stations and groups to save information about the objects of the anti-virus network into a zip archive. In the result of this command execution, all information on groups of stations and stations accounts of the anti-virus network served by this Servers, is save into the file of a specific format. Export file contains the following information about stations: properties, components configuration, permissions, update restrictions settings, schedule, installing components list, statistics, information on deleted stations; about groups: properties, components configuration, permissions, update restrictions settings, schedule, installing components list, parent group ID.
Further, export file can be imported via the Database management section.

▫In the Anti-virus network tree, you can select one or several user groups. In this case, export will contain information only on selected groups and on stations for which the selected groups are primary. If no group is selected, export will contain information on all stations and user groups of the anti-virus network.

3.Click Export.

4.Specify the path to save the archive with the database according to the web browser settings in which the Control Center is opened.

Database Import

You can use the import procedure of the database containing information on the objects of anti-virus network, to transfer the information either on the new Server or on the Server which is already operating into anti-virus network, particularly to merge the lists of served stations of two Servers.

To load the database from a file, perform the following actions:

1.Click Import on the toolbar.

2.In the import window, specify the zip archive with the database file. To select the file, you can use the button.

You can import only those zip archives that have been obtained during the export of the database for the Export information on stations and groups option.

3.Click Import to start the import process.

4.If during import, there are stations or/and groups with the same identifiers which are included both into imported data and into current Server database, the Collisions section opens to configure actions on duplicated objects.

Groups and stations lists are presented in separated tables.

For corresponding objects table, in the Groups import mode or Stations import mode drop-down list, select one of the collision resolving option:

•Save import data for all—delete all information on duplicated objects from the current Server database and overwrite it with the information from the imported database. The action is applied simultaneously to all duplicated objects in this table.

•Save current data for all—save all information on duplicated objects from the current Server database. Information on duplicated objects from the imported database will be ignored. The action is applied simultaneously to all duplicated objects in this table.

•Select manually—specify the action for each duplicated objects manually. In this mode, the list of duplicated objects become editable. Set the options for those objects, which will be saved.

Click Save.