Upgrading to a Newer Version

Top  Previous  Next

Introductory Remarks

Please note that your version of Dr.Web for UNIX Internet Gateways must be upgraded in the same way that was used to install the product:

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

If the current version was installed from the universal package, then to upgrade the product, you need to install another universal package that contains a newer version of the product.

To identify how the product version, which requires an update, has been installed, check whether the directory with the product’s executables contains a program removal script uninst.sh. If it does contain this script, then the current version was installed from the universal package; otherwise, it was installed from the repository.

 

Note that for the FreeBSD and Solaris operating systems, the product can be installed only from the universal package.

If you cannot update the product the way you installed it initially, uninstall your current version of Dr.Web for UNIX Internet Gateways, and then install a new version using any convenient method. Installation and uninstallation procedures for previous Dr.Web for UNIX Internet Gateways versions are the same as installation and uninstallation described in the current manual for version 11.0. For additional information, see Administrator manual for your current version of Dr.Web for UNIX Internet Gateways.

If the current version of the product is operating in the central protection mode, it is recommended that you record the address of the used central protection server. For example, to determine the address to which Dr.Web for UNIX Internet Gateways of the version higher than 6.0.2, you can use the following command:

$ drweb-ctl appinfo

In the output provided by this command, from the line that looks 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 public key file.

In case there are any problems with finding out the parameters of the connection that you are currently using, refer to the Administrator’s Manual for the product version that you are currently using and to the administrator of your anti-virus network.

Installing Universal Package for an Upgrade

Install Dr.Web for UNIX Internet Gateways 11.0 from the universal package. If an automatic update of the installed product is impossible, during the installation of the new version, you will get an offer to automatically remove the components of the older version of the product installed on your computer.

If during the update process you need to remove the installed product version, and there are multiple Dr.Web’s server products are installed together on your server (for example, products for file servers, for mail servers, and for Internet gateways), you need to select only the packages listed below for removal, in order to keep other server products—that will not be upgraded—fully functional (i.e. to keep the products for file servers and for mail servers intact):

drweb-internet-gateways-doc

drweb-icapd-web

drweb-icapd  

Upgrading from the Repository

Note that you cannot upgrade Dr.Web for UNIX Internet Gateways 6.0.2 to version 11.0 from the repository if several Dr.Web’s version 6.0.2 server products are installed together on your server (for example, if the product for file servers, the product for mail servers, and the product for Internet gateways are installed). In this case, install the new version of Dr.Web for UNIX Internet Gateways on a separate machine.

To upgrade your current version of Dr.Web for UNIX Internet Gateways that was installed from the Doctor Web’s repository, do one of the following, depending on the required type of packages:

RPM packages (yum, dnf).

1.Change the used repository (from the package repository of your current version to the package repository 11.0).

You can find the name of the repository that stores 11.0 packets in the Installing from the Repository section. For details on how to change repositories, refer to help guides of the used operating system distribution.

2.Install the new version using the following command:

# yum update

or, if the manager dnf is used (similar to the Fedora OS of the version 22 and earlier):

# dnf update

If during the update of packages there is an error, uninstall and repeat the installation of the product. If necessary, see sections Uninstalling the Product Installed from the Repository and Installing from the Repository (items for the OS and the package manager that you are using).

DEB packages (apt-get).

1.Change the used repository (from the package repository of your current version to the package repository 11.0).

2.Update the product using the following commands:

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

Please note that for the Ubuntu 14.04 (64-bit version) OS, the apt-get dist-upgrade command may fail. In this case use the aptitude package manager (to upgrade the product, issue the aptitude dist-upgrade command).

 

Key File Transfer

Regardless of the selected method to upgrade the product, the license key file which you already have (if you have one) will be automatically transferred and installed to the correct location required for the new version of the product.

If any problem occurs during the automatic installation of the key file, you can install it manually.

If a valid license key file was lost, contact the technical support.

Restoring Connection to the Central Protection Server

If it is possible, your connection to the central protection server will be restored automatically after the upgrade (if the product had been connected to a central protection server before the upgrade). In case the connection has not been automatically restored, then to reestablish the connection of the upgraded Dr.Web for UNIX Internet Gateways to the anti-virus network, execute the following command:

$ drweb-ctl esconnect <address> --Key <path to a file of the server public key>

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