Updating databases and application modules

Updating the databases and application modules of Kaspersky Security ensures up-to-date protection of virtual machines. New viruses and other types of malware appear worldwide on a daily basis. Kaspersky Security databases contain information about threats and ways of neutralizing them. To enable Kaspersky Security to detect threats in a timely manner, you need to update the databases and application modules regularly.

If application databases have not been updated for a long time, a notification indicating this fact will appear in the Events window of the SVM's properties.

Database and application module updates may change certain Kaspersky Security settings, for example, heuristic analysis settings that improve the effectiveness of protection and scans.

Application database and module updates require a current license to use the application.

An update source is a resource which contains updates for databases and application software modules of Kaspersky Lab applications. The Kaspersky Security Center Administration Server repository is the source of updates for Kaspersky Security for Virtualization 5.1 Light Agent.

Kaspersky Security application database and module updates are performed as follows:

  1. The Protection Server component downloads the update package from the Administration Server storage to a folder on the SVM.

    By default, the update package includes updates of application databases required for operation of Protection Server and Light Agent. You can also update the modules of the Light Agent for Windows, Light Agent for Linux, and Protection Server components. To do so, you must include application module updates in the update package.

    The update package is downloaded using update tasks on the Protection Server component. The task is started from Kaspersky Security Center and is performed on the SVM.

    To download an update package from the Administration Server storage successfully, an SVM needs to have access to the Kaspersky Security Center Administration Server.

    If databases and application modules have not been updated for a long time, the size of the update package may be large. Downloading this update package may generate additional network traffic (up to several dozen megabytes).

  2. Database updates are installed from a folder located on the SVM:
    • After the update package has been downloaded, the Protection Server component automatically installs on the SVM the database updates needed for the operation of Protection Server.
    • The Light Agent component checks the availability of an update package in the folder on the SVM to which it is connected.

      To receive updates for Light Agent modules and databases on a virtual machine, Light Agent must interact with an SVM over the HTTP protocol.

      If an update package is available, Light Agent installs the application database updates required for the operation of Light Agent on the protected virtual machine. Light Agent databases are updated using the update task on the protected virtual machine. The SVM update task is started according to the schedule. The automatic task launch mode is selected by default. The task is started once every two hours.

      On a virtual machine with the Light Agent for Windows component installed, you can configure the update task run schedule in the local interface or start the update task manually, if these functions are not denied by the policy for all protected virtual machines of the administration group. If it is not possible to run the update task for some reason (for example, the virtual machine is powered off at that time), you can configure the skipped update task to be started automatically as soon as it becomes possible.

      On a virtual machine with the Light Agent for Linux component installed, you can manually start the update task from the command line.

  3. Application module updates are installed from a folder on SVMs (if they have been included into the update package):
    • Updates for Light Agent for Windows and Light Agent for Linux modules are installed automatically when the update task is run on the protected virtual machine.

      You can view a list of installed module updates for Light Agent for Windows in one of the following ways:

      • In the local interface of Light Agent for Windows in the Support window.
      • In the command line (for more details, please refer to the Knowledge Base).
      • Through Kaspersky Security Center in the properties of Kaspersky Security installed on the virtual machine with Light Agent for Windows (General section, Installed updates field).

      You can view a list of installed module updates for Light Agent for Linux in one of the following ways:

      • By running the command line script named patch_list.pl located in the /opt/kaspersky/lightagent/patching/ folder.
      • Using the command lightagent productinfo.
      • Through Kaspersky Security Center in the properties of Kaspersky Security installed on the virtual machine with Light Agent for Linux (General section, Installed updates field).
    • Installation of application module updates on SVMs is performed using the SVM application module update task.

      On SVMs, you can view a list of installed application module updates by using the command line script named patch_list.pl located in the /opt/kaspersky/la/patching/ folder.

    After application module updates are installed, the performance of Kaspersky Security is checked on each SVM and protected virtual machine. If problems are detected, the application module update is automatically rolled back.

    If application errors occur after you update modules, you can manually roll back an application module update on SVMs and protected virtual machines.

    When application module updates are being installed, protection of virtual machines and running tasks are paused.

To ensure up-to-date protection of temporary virtual machines, you are advised to regularly update Light Agent databases and modules on the virtual machine template from which temporary protected virtual machines have been deployed.

If you selected the Installation on the template for temporary VDI pools check box while installing Light Agent on the virtual machine template, updates that require restarting the protected virtual machine are not installed on temporary virtual machines. On receiving updates that require restarting the protected virtual machine, Light Agent installed on a temporary virtual machine sends a message to Kaspersky Security Center informing it that the protected virtual machine template needs to be updated.

In this Help section

Enabling and disabling application module updates

Automatically downloading the application module and database update package to SVMs

Creating a Protection Server database update task

Creating an SVM application module update task

Configuring the update task run mode in the local interface

Updating Light Agent for Windows databases and modules on a virtual machine template

Rolling back the last update of databases and application modules

Page top