9.1.2. Upgrading Dr.Web Enterprise Server for UNIX® System-Based OS

Top  Previous  Next

Upgrading the Server software over the previous version is possible not for all UNIX system-based OS. Thus, under UNIX system-based OS, in which upgrading is not supported, it is recommended to delete the Server software of previous versions and install the 6.0.4 version.

Saving Configuration Files

After the Server has been removed, the following files will remain:

Saving Database

Before upgrade Dr.Web Enterprise Security Suite software, it is recommender to backup database.

To backup database:

1.Stop the Server.

2.Export DB to the file:

◆For FreeBSD OS:
# /usr/local/etc/rc.d/drwcsd.sh exportdb /var/drwcs/etc/esbase.es

◆For Linux OS:
# /etc/init.d/drwcsd exportdb /var/opt/drwcs/etc/esbase.es

◆For Solaris OS:
# /etc/init.d/drwcsd exportdb /var/drwcs/etc/esbase.es

For Servers with external DB, it is recommended to use standard tools supplied with the database.

Important Notes

Automatic Upgrade

If you update the Server from 5.XX version to 6.0.4 version for Linux OS, instead of deleting old version and installing new version of the Server, you can use the following commands to update the Server:

◆for rpm: rpm -U <package_name>

◆for dpkg: dpkg -i <package_name>
for upgrading deb packages, the /root/drwcs catalog must be empty or absent.

All automatically saved files will be stored in corresponding directories and manual replacement is not required.

During upgrade of package for rpm distribution kits of 5.0 or 6.0 Server, if before Server upgrade, the webmin.conf Control Center configuration file had been changed, the webmin.conf file is saved form the old version, and the new file is created with the webmin.conf.rpmnew name.

If you want to use functional, provided by changed parameters of configuration file (and also, the Agent installer could be available at http://<server_name>:9080/install page, see Installation Files), copy all changed settings from the old file to the new file and rename the webmin.conf.rpmnew new file to the webmin.conf with replace.

Manual Upgrade

If using an internal database:

1.Stop the Enterprise Server.

2.If you plan to use any files (besides files which are copied automatically during Server uninstall at step 4), backup these files manually. For instance, copy the report templates to a backup folder.

3.Remove the contents of the repository.

4.Remove Enterprise Server software (see Uninstalling the Dr.Web Enterprise Server Software for UNIX system-based OS). You will be prompt to create backup copies, for this specify a folder where to store the backup or accept the default folder.

5.Install Enterprise Server version 6.0.4 (see Installing the Dr.Web Enterprise Server for UNIX system-based OS).

6.After new install, you can replace automatically created files with the backup copies from the previous installation. In case of automatic backup, replace the files in the following folders:

In case of manual backup, replace the files in the same folders from which you copied the files before new install.

7.To upgrade the databases, execute the following commands:

◆for Linux OS and Solaris OS: /etc/init.d/drwcsd upgradedb

◆for FreeBSD OS: /usr/local/etc/rc.d/drwcsd.sh upgradedb

8.Launch Enterprise Server.

9.Set up repository upgrade and perform the upgrade.

10.Restart the Server.

If using an external database:

1.Stop Enterprise Server.

2.If you plan to use any files (besides files which are copied automatically during Server uninstall at step 4), backup these files manually. For instance, copy the report templates to a backup folder.

3.Remove the contents of the repository.

4.Remove Enterprise Server software (see the Uninstalling the Dr.Web Enterprise Server Software for UNIX system-based OS section). You will be prompt to create backup copies, for this, specify a folder where to store the backup or accept the default folder.

5.Install Enterprise Server version 6.0.4 (see p. Installing the Dr.Web Enterprise Server for UNIX system-based OS).

6.Move the automatic saved files (see above) to:

◆for Linux OS: to /var/opt/drwcs/etc, except for the public key. The latter must be saved to /opt/drwcs/Installer/ and to /opt/drwcs/webmin/install

◆for FreeBSD OS: to /var/drwcs/etc, except for the public key. The latter must be saved to /usr/local/drwcs/Installer/ and to/usr/local /drwcs/webmin/install

◆for Solaris OS: to /var/drwcs/etc, except for the public key. The latter must be saved to /opt/drwcs/Installer/ and to /opt/drwcs/webmin/install

In case of manual backup, replace the files in the same folders from which you copied the files before new install.

7.To upgrade the databases, execute the following commands:

•for Linux OS and Solaris OS:

/etc/init.d/drwcsd upgradedb

•for FreeBSD OS:

/usr/local/etc/rc.d/drwcsd.sh upgradedb

8.Launch Enterprise Server.

9.Set up repository upgrade and perform the upgrade.

10.Restart the Server.

In upgrading procedure of the Dr.Web Enterprise Server to version 6.0.4, it is recommend to do the following:

1.Before upgrading disable the use of communication protocols with Enterprise Agent and the Network installer. To do this, select the Administration item in the main menu and click Configure Dr.Web Enterprise Server  in the control menu, go to the Modules tab and clear the Protocol Dr.Web Enterprise Agent and the Protocol Dr.Web Network Installer flags. Click Save. A request to restart the Server will be opened. Click Yes.

2.Upgrade the Server to version 6.0.4 as described above (using preserved Server configuration file).

3.After upgrading the Server, configure the set of components installed at the workstations (see p. Anti-Virus Package Composition), in particular if you do not have Antispam license, the cannot option for the SpIDer Gate and Office Control components must be set.

4.Update the components of Dr.Web ESS. To do this, select the Administration item in the main menu and click Repository state in the control menu. In the opened window click Check for updates. Beforehand configure the proxy servers settings for GUS updating if necessary.

5.If necessary, configure ports that is using by the Agents for communication with the Server. To do this, use the Administration → Configure Dr.Web Enterprise Server → Transport tab.

6.Enable the use of communication protocols with Enterprise Agent and the Network installer, disabled at step 1.

7.Upgrade the workstations software.

The upgraded anti-virus program is ready for operation.