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

All actions must be performed under the root administrator account.

Upgrading the Server software of the previous version to version 10 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 saving the backup copy and install the 10 version based on the saved backup copy.

Upgrading the Server software within version 10 for the same package types is performed automatically.

Before removing the Server of previous version, please read the Upgrading Dr.Web Agent section.

Upgrading the Server within version 10 can be also performed via the Control Center. The procedure is described in the Administrator Manual, in the Updating Dr.Web Server and Restoring from the Backup section.

Not all Server updates within version 10 have the distribution kit file. Some of them can be installed via the Control Center only.

Saving Configuration Files

After the Server of version 6 has been removed, the following files are automatically saved:

File	Description	Default folder
agent.key (the name may vary)	Agent license key file	•for Linux OS and Solaris OS: /var/opt/drwcs/etc •for FreeBSD OS: /var/drwcs/etc
certificate.pem	SSL certificate
download.conf	network settings for generating of the Agent installation packages
drwcsd.conf (the name may vary)	Server configuration file
drwcsd.pri	private encryption key
enterprise.key (the name may vary)	Server license key file
private-key.pem	RSA private key
webmin.conf	Dr.Web Security Control Center configuration file
common.conf	configuration file (for some UNIX system-based OS)
local.conf	Server log settings
dbinternal.dbs	embedded database	•for Linux OS and Solaris OS: /var/opt/drwcs/ •for FreeBSD OS: /var/drwcs/
drwcsd.pub	public encryption key	•for Linux OS and Solaris OS: /opt/drwcs/Installer /opt/drwcs/webmin/install •for FreeBSD OS: /usr/local/drwcs/Installer /usr/local/drwcs/webmin/install

After the Server of version 10 has been removed, the following configuration files are automatically saved to the default backup folder:

File	Description	Default folder
agent.key (the name may vary)	Agent license key file	/var/tmp/drwcs/
certificate.pem	SSL certificate
download.conf	network settings for generating of the Agent installation packages
drwcsd.conf (the name may vary)	Server configuration file
drwcsd.pri	private encryption key
enterprise.key (the name may vary)	Server license key file. The file is saved if it presented after the upgrade from the previous versions. For the new Server 10 installation, the file is absent
frontdoor.conf	configuration file for the Server remote diagnostic utility
private-key.pem	RSA private key
webmin.conf	Dr.Web Security Control Center configuration file
common.conf	configuration file (for some UNIX system-based OS)
local.conf	Server log settings
dbexport.gz	database export
drwcsd.pub	public encryption key

After the automatic upgrade for Linux OS and Solaris OS, the following files are also saved:

For the Server of version 6:

File	Description	Default folder
auth-ldap.xml	configuration file for administrators external authorization via LDAP	/var/opt/drwcs/etc
auth-radius.xml	configuration file for administrators external authorization via RADIUS	/var/opt/drwcs/etc

For the Server of version 10:

File	Description	Default folder
auth-ldap.xml	configuration file for administrators external authorization via LDAP	/var/tmp/drwcs/
auth-pam.xml	configuration file for administrators external authorization via PAM
auth-radius.xml	configuration file for administrators external authorization via RADIUS

If you are planning to use configuration files from the previous version of the Server, please note:

1.Server license key is no longer supported (see Chapter 2: Licensing).

2.The embedded database is upgraded and configuration files of the Server is converted by the means of the installer. You cannot replace these files with a backup copies when upgrading to the Server 10.

Saving Database

Before upgrade Dr.Web Enterprise Security Suite software, it is recommended 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.

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

Automatic Upgrade

If you update the Server from 6 and later versions to the 10 version for Linux and Solaris OS, instead of deleting old version and installing new version of the Server, you can use the package update of the Server. For this, launch the installation of corresponding Server package.

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

Manual Upgrade

If using an embedded database:

1.Stop the 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 all contents of the repository.

4.Remove Dr.Web Server software (see Removing Dr.Web Server Software for UNIX® System-Based OS). You will be prompt to create backup copies of files. For this, specify a folder where to store the backup or accept the default folder.

5.Install Dr.Web Server of version 10 according to the general installation procedure (see Installing Dr.Web Server for UNIX® System-Based OS) based on the backup copy from the step 4. All saved configuration files and embedded database will be automatically converted for the Server of the 10 version. Without automatic conversion, database and some of Server configuration files from the previous version cannot be used.

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

For all backup files from the previous Server version (see step 6) assign the user, selected at the installation of the new Server version (drwcs by default), as files owner.

6.Launch the Server.

7.Set up repository upgrade and perform the upgrade.

8.Restart the Server.

If using an external database:

1.Stop Dr.Web Server.

3.Remove the contents of the repository.

4.Remove Dr.Web Server software (see the Removing Dr.Web 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 Dr.Web Server of version 10 (see p. Installing Dr.Web Server for UNIX® System-Based OS).

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

•for Linux OS:
public key: /opt/drwcs/Installer/ and to /opt/drwcs/webmin/install
other: /var/opt/drwcs/etc

•for FreeBSD OS:
public key: /usr/local/drwcs/Installer/ and to /usr/local/drwcs/webmin/install
other: /var/drwcs/etc

•for Solaris OS:
public key: /opt/drwcs/Installer/ and to /opt/drwcs/webmin/install
other: /var/drwcs/etc

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

For all backup files from the previous Server version (see step 6) assign the user, selected at the installation of the new Server version (drwcs by default), as files owner.

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 Dr.Web Server.

9.Set up repository upgrade and perform the upgrade.

10.Restart the Server.

After upgrade of anti-virus network Servers is completed, you must configure encryption and compression settings for the connected Servers (see the Administrator Manual, the Setting Connections between Several Dr.Web Servers section).