Configuring the database update schedule and settings

26 April 2024

ID 91221

To configure the database update schedule and settings:

  1. In the application web interface window, select the SettingsExternal servicesDatabase update section.
  2. Select the Update settings tab.
  3. In the Source drop-down list, select one of the following update sources:
    • Kaspersky servers (secure connection).
    • Kaspersky servers (insecure connection).
    • Custom.

    By default, the value is set to Kaspersky servers (secure connection).

  4. If you selected Custom at the previous step, in the Custom source field, specify the address of the custom source from which you want to receive upgrade packages. You can specify the following sources:
    • URL of the update server

      For servers that use HTTPS, the update will proceed only if the Kaspersky server is specified.

    • Local directory

      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.

    • A network folder, that is, a directory on a remote computer mounted over SMB or NFS.

    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.

  5. In the Schedule drop-down list, select one of the options and do the following to configure the schedule:
    • Manually.
    • Once. In the field that opens, specify the date and time to start a database update.
    • Daily. In the field that opens, specify the time to start a daily database update.
    • Weekly. In the fields that open, specify the day of the week and time to start a database update.

      For example, if the values are set to Mon and 15:00, the database update runs every Monday at 3 p.m.

    • Monthly. In the fields that open, specify the day of the month and time to start a database update.

      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.

    • Run every. In the fields that open, specify the frequency for starting a database update (in minutes, hours, or days).

      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.

  6. In the Maximum duration (min) field, specify the maximum duration of a database update (in minutes), after which the database update should be stopped.

    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.

  7. Set the Run skipped tasks toggle switch to Enabled if you want to run skipped database update tasks the next time the application starts.

    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.

  8. Click Save.

Database update schedule and settings are configured.

See also

Database update for Kaspersky Secure Mail Gateway

Updating databases manually

Monitoring application database status

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.