Rolling back the last update of Kaspersky Security databases and application modules

After Kaspersky Security databases and application modules are updated for the first time, the ability to roll back databases and application modules to their previous versions becomes available.

Every time a database update is started on the Protection Server, Kaspersky Security creates a backup copy of the existing databases and application modules and only then proceeds to update them. This makes it possible to return to the previous version of databases and application modules if necessary. The ability to roll back an update is useful if, for example, the new version of the application database contains an invalid signature that causes Kaspersky Security to block a safe application.

A rollback of the last update of Kaspersky Security databases and application modules is performed as follows:

1. The Protection Server component rolls back the last update of Kaspersky Security databases and application modules on SVMs. You can roll back the last update of databases and application modules on one or more SVMs:
   • The latest database update on the SVM is rolled back using the Database update rollback task for the Protection Server. The task is started from Kaspersky Security Center and is performed on the SVM.
   • A script is used to roll back an application module update on SVMs.

   When rolling back the latest update of databases and application modules on the SVM, the Protection Server also rolls back updates of Light Agent databases, which are located in a folder on the SVM. The Protection Server sends Light Agents an event indicating that an update is required.

2. After an update of databases and application modules has been rolled back on an SVM, a special local Update task for Kaspersky Endpoint Security for Linux is automatically launched on Light Agents connected to this SVM. In this task, a folder on the SVM is specified as the update source.

   The update task causes the Light Agent to switch to using the previous set of Kaspersky Security databases.

In this section: Creating a Database update rollback task Rolling back an application module update on an SVM

Page top