9.1.1. Upgrading Dr.Web Enterprise Server for Windows® OS

Two modes of upgrading the Server to 6.0.4 version are available:

1.Automatic. Upgrading the Server of 5.0 and 6.0.0 versions can be done automatically by using the installer.

 

Automatic upgrade is supported for Servers with the same bitness only.

In other cases, it is necessary to delete the old Server and install the new Server manually.

 

2.Manual. To upgrade Server software of 4.XX, 6.0.2 and later versions, delete Server software of current versions and install the new Server.

Saving Configuration Files

During deleting of the Server manually or upgrading by using the installer, the following files will be backed up automatically:

File

Description

Default folder

dbinternal.dbs

internal database

var

drwcsd.conf (the name may vary)

Server configuration file

etc

drwcsd.pri

private encryption key

drwcsd.pub

public encryption key

Installer

webmin\install

enterprise.key (the name may vary)

Server  license key file

etc

agent.key (the name may vary)

Agent license key file

certificate.pem

SSL certificate

private-key.pem

RSA private key

If necessary, copy other critical files you want to preserve to another folder, other than Server installation folder. For instance, copy the Dr.Web Control Center configuration file (webmin.conf) and report templates which are stored in the \var\templates folder.

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:
"C:\Program Files\DrWeb Enterprise Server\bin\drwcsd.exe" -home="C:\Program Files\DrWeb Enterprise Server" -var-root="C:\Program Files\DrWeb Enterprise Server\var" -verbosity=all exportdb <backup_folder>\esbase.es

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

 

Make sure, that Dr.Web ESS DB export completed successfully. If DB backup copy is not  available, the Server could not be restored in emergency case.

 

Important Notes

 

Starting from version 5.0 anti-virus package includes SpIDer Gate and Office Control components. For using this components, they must be included in you license (Antivirus+Antispam). If you license does not include this components, it is recommended to perform the actions described below.

 

If the Agent with an active self-protection is installed on Sever computer, the wizard prompts you to disable Dr.Web SelfPROtect during update process. Disable self-protection in the Agent settings to continue updating the Server.

 

If you are using the ODBC for Oracle as an external database, select the Custom option and in the opened window disable the installation of Oracle client in the Database support - Oracle database driver section in the installer settings during the Server upgrading (or reinstallation).

Otherwise, Oracle DB functioning will fail because of the libraries conflict.

 

Automatic Upgrading Dr.Web Enterprise Server from 5.0 and 6.0.0 Versions

Dr.Web Enterprise Server can be upgraded from 5.0 and 6.0.0 versions to version 6.0.4 automatically by using the installation wizard.

To upgrade the Dr.Web Enterprise Server to version 6.0.4 run the installation file and follow instructions of the Wizard

1.The Dr.Web Enterprise Server Upgrade Notes window displays, which notifies you on the previous Enterprise Server version installed. The installation wizard locates the Server installation folder automatically.

2.On the following steps, the wizard displays locations of the preserved files (see above) which will be used during installation of the 6.0.4 Server. You can change locations if necessary.

For the external Server database, also select Use existing database during upgrade. After subsequent selection of existing Server configuration file and private encryption key, a further update will be proceeded automatically.

3.To remove the previous version and launch the installation process, click Install.

 

During upgrade of the Server software, contents of the repository are removed and new version is installed.

If after Server upgrade from the 5.0 and earlier versions, the repository has not been removed, it is necessary to remove its contents and renew it manually.

 

For a network with several Severs, from the main Server with 6.0.4 version to child Servers with 5.0 and earlier versions, only virus bases are transmitted.

To transmit all software and Agent updates, upgrade child Servers to 6.0.4 version (for repositories  compatibility).

 

After upgrading of Dr.Web Enterprise Server to 6.0.4 version:

Do the following to ensure normal operation of Dr.Web Control Center:

1.Clear cache of the Web browser that is used to connect to Dr.Web Control Center.

2.Upgrade the Dr.Web Browser-Plugin.

Manual Upgrading Dr.Web Enterprise Server from 4.XX, 6.0.2 and Later Versions

Dr.Web Enterprise Server does not support upgrade from 4.XX versions or 6.0.2 and later versions to 6.0.4 version automatically. To upgrade Server, delete the current Server software and install the new Server.

 

In case of upgrade from 4.XX version, if your licence on anti-virus software of 6.0.4 version does not include SpIDer Gate and Office Control components (Antivirus+Antispam), it is recommended to perform the actions described below.

 

To upgrade the Dr.Web Enterprise Server, do the following

1.Stop the Server (see Start and Stop the Dr.Web Enterprise Server).

2.In case of using external DB, save DB via SQL server loots.

3.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.

4.Remove the Enterprise Server software.

5.Install new Server (see p. Installing the Dr.Web Enterprise Server for Windows® OS).

In case of using external DB, specify to create a new DB.

In case of using internal DB, specify saved dbinternal.dbs file.

6.Stop the Server (see Start and Stop the Dr.Web Enterprise Server).

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

8.In case of using external DB, restore the DB on the new Server and specify the path to this DB in the configuration file drwcsd.conf.

Run the drwcsd.exe with upgradedb switch for DB upgrading. The command line will look as follows:

"C:\Program Files\DrWeb Enterprise Server\bin\drwcsd.exe" upgradedb "C:\Program Files\DrWeb Enterprise Server\update-db"

9.Start the Server (see Start and Stop the Dr.Web Enterprise Server).

In upgrading procedure of Dr.Web Enterprise Server from 4.XX version to 6.0.4 version, 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.

 

After the Server upgrading from the 4.XX version to 6.0.4 version, the transport parameter must be present in the drwcsd.conf configuration file of the Server:

Transport "drwcs" "tcp/0.0.0.0:2193" "udp/231.0.0.1:2193"

where the drwcs is a Server name.

If this parameter is not specified, add it manually and restart the Server.