To configure the database update schedule and settings:
By default, the value is set to Kaspersky servers (secure connection).
For servers that use HTTPS, the update will proceed only if the Kaspersky server is specified.
Specify the full path to an update directory that exists on all cluster nodes. If the directory with the specified path is missing on the Control node, a notification is displayed. If the specified directory is missing on a Secondary node, database update for that node is performed with old settings.
You can also select the If inaccessible, use Kaspersky servers check box if you want to receive upgrade packages from Kaspersky update servers whenever the custom update source is unavailable. This check box is cleared by default.
For example, if the values are set to Mon and 15:00, the database update runs every Monday at 3 p.m.
For example, if the values are set to 20 and 15:00, the database update runs on the 20th day of the month at 15:00.
If the specified value exceeds the number of days in a given month, the database update in that month will take place on the last day. For example, if the value is 31, in 30-day months, the database update will take place on the 30th of the month.
For example, if the frequency value is 30 and Minutes frequency is selected, database update is run every half hour.
The first database update starts immediately after the changes are saved.
By default, database update runs every 15 minutes.
If the database update task does not complete in the allotted time, it runs again at the next scheduled opportunity.
By default, the value is set to 180.
The update could fail to run at the scheduled time, for example, if the computer was turned off or the application was not running.
If running skipped tasks is disabled, skipped database update tasks will not be started the next time the application starts. The next database update will be started according to the schedule.
By default, the running of skipped tasks is enabled.
Database update schedule and settings are configured.