In this section
•Upgrading by Installing a Universal Package
•Upgrading from the Repository
•Restoring Connection to a Centralized Protection Server
|
Before you upgrade to a new version, make sure that your server meets the system requirements of a new version and dependencies are installed. |
Your version of Dr.Web Server Security Suite must be upgraded in the same way Dr.Web Server Security Suite was installed.
•If the version of Dr.Web Server Security Suite to be updated was installed from the repository, upgrading to a new version must be done from the repository.
•If the version of Dr.Web Server Security Suite to be updated was installed from a universal package, you should install another universal package that contains a new version of Dr.Web Server Security Suite.
|
To determine how the version of Dr.Web Server Security Suite to be updated was installed, check whether the Dr.Web Server Security Suite executable directory contains the uninst.sh program uninstallation script. If so, the current version of Dr.Web Server Security Suite was installed from the universal package; otherwise, it was installed from the repository.
Dr.Web Server Security Suite сan be installed on FreeBSD only from a universal package. |
If you cannot update Dr.Web Server Security Suite the way you installed it initially, uninstall your current version and then install a new version of Dr.Web Server Security Suite using any convenient method. Installation and uninstallation procedures for previous Dr.Web Server Security Suite versions are the same as the installation and uninstallation procedures described in this manual. For additional information, refer to the Administrator Manual for your current version of Dr.Web Server Security Suite.
If the version of Dr.Web Server Security Suite to be updated operates in centralized protection mode, it is recommended that you save the address of the centralized protection server to which Dr.Web Server Security Suite is connected. For example, to determine the address of the centralized protection server to which Dr.Web Server Security Suite of the version later than 6.0.2 is connected, use the following command:
$ drweb-ctl appinfo |
In the output of this command, from the line of the form:
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 Server Security Suite and to the administrator of your anti-virus network.
Upgrading by Installing a Universal Package
Install Dr.Web Server Security Suite of a new version from a universal package. If an automatic update is impossible, during the installation of the new version you will be prompted to automatically remove the installed components of the old version of Dr.Web Server Security Suite.
|
If you need to remove the installed version of Dr.Web Server Security Suite during the update process, and there are multiple Dr.Web server products installed on your server (for example, Dr.Web Server Security Suite, Dr.Web Mail Security Suite and Dr.Web Gateway Security Suite), you need to mark for removal only the packages listed below in order to keep products that are not to be updated functional (Dr.Web Mail Security Suite and Dr.Web Gateway Security Suite): •drweb-file-servers-doc, •drweb-smbspider. |
|
You cannot upgrade Dr.Web for UNIX File Servers 6.0.2 to a new version from the repository if multiple Dr.Web server products of version 6.0.2 are installed on your server (for example, products for file servers, for mail servers and for internet gateways). In this case, install the new version of Dr.Web Server Security Suite on another machine. |
To upgrade your current version of Dr.Web Server Security Suite installed from the repository of Doctor Web
Depending on the type of packages in use, do the following:
•RPM packages (yum, dnf)
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 operating system distribution. |
2.Install the new version of Dr.Web Server Security Suite 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 Server Security Suite. If necessary, see sections Uninstallation of Dr.Web Server Security Suite Installed from the Repository and Installing from the Repository (paragraphs related to your OS and package manager). |
•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 Server Security Suite with the following commands:
# apt-get update |
Regardless of the selected method to upgrade Dr.Web Server Security Suite, your current key file will be automatically transferred to a proper location required for the new version.
|
If any issue occurs during the automatic installation of the key file, you can install it manually. |
If the valid license key file was lost, contact the technical support.
Restoring Connection to a Centralized Protection Server
If possible, your connection to a centralized protection server will be restored automatically after the upgrade (if Dr.Web Server Security Suite to be upgraded was connected to the centralized protection server). In case the connection has not been automatically restored, to reestablish the connection of the upgraded version of Dr.Web Server Security Suite to the anti-virus network, run the command:
$ drweb-ctl esconnect <address> --Certificate <path to a certificate file> |
In case of any issues with the connection process, contact the administrator of your anti-virus network.