8.3. Setting the Dr.Web Enterprise Server Schedule

To schedule tasks for the Dr.Web Enterprise Server via the Dr.Web Control Center:

1.Select the Administration item in the main menu and click Dr.Web Enterprise Server Schedule in the control menu. The list with the current tasks of the Server will be opened.

2.To remove a task from the list, set the flag against it and click

Remove these settings in the toolbar.

3.To edit a task, select it in the list. This will bring up the Job editor window which is described below.

4.To add a new task to the list, click the

New job item in the toolbar. This will bring up the New job window where you should specify necessary parameters described below and click Save.

◆In the Name entry field assign a name to the task, which will be displayed in the schedule.

To disable the job, clear the flag. The job will remain on the list but will not be executed.

◆The Critical job flag instructs to perform the job at next Enterprise Server launch, if execution of this job is omitted (theEnterprise Server is switched off at the due time). If a task is omitted several times within a certain period of time, then it will be performed only once after the Enterprise Server has been launched.

2.On the Action tab, select the type of task in the Action drop-down list. The bottom part of the window containing the parameters of the selected task will change its look (the parameters of different types of tasks are described in Table below).

3.On the Time tab, select time intervals at which the task is to be launched and set the time accordingly (it is similar to scheduling tasks for a workstation, as described in p. Editing Scheduled Tasks on a Station above).

Type	Description
Run a procedure	For tasks of this type, you need to enter the procedure name in the Name filed. The name of the procedure must correspond to the name of the executable lua-script (with no extension), located at the var/extensions folder of the Server installation folder (see also scripts description at the Appendix M).
Shutdown and Restart	There are no additional parameters for tasks of this type. Use these tasks to stop and restart the Server.
Run	Specify the path to the executable file of the Server in the Path field, and the command line parameters at launch in the Arguments field. Set the Execute synchronously flag for the synchronization with Server - wait while task finishes before executing other tasks with Run type. If the Execute synchronously flag is cleared, the Server logging only the start of the program. If the Execute synchronously flag is set, the Server logging the start of the program, the returned code and the time of the program shutdown.
License expiration reminder	Select the period till the license expiration when to execute the task (licenses of Server and Agent either).
Update	See paragraph Updating Mobile Agents for details.
Log	Specify the message to be logged.
Backup critical server data	Use these tasks to create backups of the Server database, the license key file and private key. Specify the folder where to store the backup files (empty by default) and the maximum number of backup copies allowed (for unlimited number of copies, use 0). Appendix H5.5. for details.
Stations that nave not visited for a long time	Specify the absence period after which the station should be considered absent for too long. After this period, a reminder displays.
Purge unsent IS events	Specify the period after which the event should be purged. This task affects only the event which the secondary Servers fail to deliver to the main Server. If the secondary Server fails to send an event, the event is moved to the list of unsent events, which the Server tries to resend periodically. When you execute the Purge unsent IS events task, the events older than the specified period are purged.
Purge old stations	Specify the time period (90 days is by default). Stations, which do not visit the Server during specified period, will be considered outdated and deleted.
Purge old data	Specify number of days after which statistic data about workstations (but not stations themselves) should be considered outdated and be deleted. Periods for deleting statistics data for different types of records are set separately.