Rolling back the last update of databases and application modules

After the databases and application modules are updated for the first time, the function of rolling back the databases and application modules to their previous versions becomes available.

Every time an update is started on an SVM, Kaspersky Security creates a backup copy of the existing application databases and modules and only then proceeds to update them. This lets you roll back the databases and application modules to their previous versions when necessary. The update rollback feature is useful if the new application database version contains an invalid signature that causes Kaspersky Security to block a safe application.

Kaspersky Security application database and module updates are rolled back in the following order:

1. Rolling back the last update of databases and application modules on the SVM. You can roll back the last application database and module update on one or several SVMs:
   • Rollback of the last database update on an SVM is performed using the database update rollback task on the Protection Server. The task is started from Kaspersky Security Center and is performed on the SVM.
   • Rollback of application module updates on SVMs is performed by a script.
2. Rolling back the last database update on protected virtual machines. After a database update has been rolled back on an SVM, the last database update is automatically rolled back on all protected virtual machines connected to this SVM. If a protected virtual machine is disabled or paused, the last database update on this machine will be performed after it is enabled according to the Light Agent update task start schedule. The automatic task launch mode is selected by default. The task is started once every two hours.

   On a protected 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.

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

3. Rollback of an application module update on protected virtual machines.

To roll back the last application database and module update:

1. Create a Protection Server database update rollback task for SVMs on which you want to roll back the database update.
2. Start the Protection Server database update rollback task.
3. If necessary, perform a rollback of an application module update on SVMs and protected virtual machines.

In this section: Creating a Protection Server database update rollback task Rolling back application module updates on SVMs and virtual machines

Page top