Upgrading to a Newer Version

Introductory Remarks

The upgrade procedure for Dr.Web Security Space of earlier versions to a newer version is supported. Migrate to the newer version of Dr.Web Security Space in the same way the earlier version of Dr.Web Security Space was installed:

If the current Dr.Web Security Space version was installed from the repository, an upgrade requires updating program packages from the repository.

If the current Dr.Web Security Space version was installed from the universal package, to upgrade the product, you need to install another universal package that contains a newer version.

To identify how the version of Dr.Web Security Space was installed, check whether the Dr.Web Security Space executable directory contains uninst.sh program uninstallation script. If so, the current version of Dr.Web Security Space was installed from the universal package; otherwise it was installed from the repository.

If you cannot update Dr.Web Security Space the same way you installed it initially, uninstall your current version, and then install a new version using any convenient method. Installation and uninstallation procedures for previous versions of Dr.Web Security Space are the same as installation and uninstallation methods described in the current manual. For additional information, refer to the User manual for your current version of Dr.Web Security Space.

Upgrading of Dr.Web Security Space from version 6.0.2 and earlier to a newer version can be performed only by uninstalling the outdated version of Dr.Web Security Space and installing the newer version.

 

If the version of Dr.Web Security Space to be updated is controlled by a centralized protection server, it is recommended that you save the address of this server. For example, to determine the address of the centralized protection server to which Dr.Web Security Space of the version later than 6.0.2 is connected, use the following command:

$ drweb-ctl appinfo

in the output provided by this command, from the line like

ESAgent; <PID>; RUNNING 1; Connected <address>, on-line

save the <address> part (which can look like tcp://<IP address>:<port>, for example: tcp://10.20.30.40:1234). In addition, it is recommended that you save the server certificate file.

In case of any difficulties with finding out the parameters of the current connection, refer to the Administrator Manual for the installed version of Dr.Web Security Space and to the administrator of your anti-virus network.

Upgrading Version 9.0 and Newer

Installing Universal Package as an Upgrade

Install Dr.Web Security Space from the universal package. If necessary, during the installation you will be prompted to automatically uninstall installed components of the older version of Dr.Web Security Space.

Upgrading from the Repository

To upgrade your current version of Dr.Web Security Space that was installed from the Doctor Web repository, do one of the following, depending on the required package type:

In case of using RPM packages (yum):

1.Change the repository in use (switch from the package repository of your current version to the package repository of the new version).

You can find the name of the repository storing the packages of the new version in the Installing from the Repository section. For details on how to switch between repositories, refer to help guides of your distribution.

2.Install the new version of Dr.Web Security Space from the repository using the following command:

# yum update

or, if the dnf manager is used (such as on Fedora 22 and later):

# dnf update

If an error has occurred while updating the packages, uninstall and reinstall Dr.Web Security Space. If necessary, see sections Uninstallation of Dr.Web Security Space Installed from the Repository and Installing from the Repository (paragraphs related to your OS and package manager).

In case of using DEB packages (apt-get):

1.Change the repository in use (switch from the package repository of your current version to the package repository of the new version).

2.Update the packages of Dr.Web Security Space with the following commands:

# apt-get update
# apt-get dist-upgrade

Key File Transfer

Regardless of the selected method to update Dr.Web Security Space, your license key file is installed to the appropriate location automatically to be used by the newer version of Dr.Web Security Space.

If any issue occurs during automatic installation of the key file, you can install it manually. The license key file of Dr.Web Security Space version 9.0 and newer is stored in the /etc/opt/drweb.com directory. If the valid license key file is lost, contact the Doctor Web technical support.

Restoring Connection to the Centralized Protection Server

If possible, your connection to a centralized protection server will be restored automatically after the upgrade (if the version to be upgraded was connected to the centralized protection server). In case the connection has not been automatically restored, to re-establish the connection of the upgraded version of Dr.Web Security Space to the anti-virus network, use one of the following methods:

Select the check box on the Mode tab of the Dr.Web Security Space settings window.

Use the command:

$ drweb-ctl esconnect <address> --Certificate <path to the server certificate file>

These actions require providing an address and a server public key file stored in advance.

In case of any difficulties with the connection process, contact the administrator of your anti-virus network.

Aspects of Upgrading Procedure

If your current version of Dr.Web Security Space is active while upgrading the product from the repository, after installing the packages of the newer version of Dr.Web Security Space, the processes of the earlier version of Dr.Web Security Space remain running until the user logs off the system. At that, if Dr.Web Security Space is operating in graphical mode, the icon of the earlier version can be displayed in the notification area.

While upgrading Dr.Web Security Space, SpIDer Gate settings can be reset to default values.

In case of an active mail client (such as Mozilla Thunderbird) that uses the IMAP protocol to receive email messages, restart this client after the update is complete to ensure scanning of incoming email messages.

Upgrading Version 6.0.2 and Earlier

Upgrading of Dr.Web Security Space from version 6.0.2 and earlier to a newer version can be performed only by uninstalling the outdated version of Dr.Web Security Space and installing version the newer version. For additional information about uninstalling an earlier version of Dr.Web Security Space, refer to the User manual for your version of Dr.Web Security Space.

Key File Transfer

The license key file of the earlier version of Dr.Web Security Space is not installed automatically to be used by the newer version, but you can install this key file manually. The license key file of Dr.Web Security Space 6.0.2 and earlier is stored in the /home/<user>/.drweb directory which is marked as hidden. If the valid license key file is lost, contact the Doctor Web technical support.

Dr.Web Security Space of the up-to-date version does not manage the quarantine of Dr.Web Security Space 9.0 and earlier. If any isolated files remain in the quarantine of the earlier version, you can retrieve or delete these files manually. Dr.Web Security Space 6.0.2 (and earlier) uses the following directories for quarantine:

/var/drweb/infected—system quarantine;

/home/<user>/.drweb/quarantine—user quarantine (where <user> is a user name).

To simplify processing of quarantined files, it is recommended to revise them using the earlier version of Dr.Web Security Space before starting an upgrade.