Upgrading of Dr.Web Server from version 6, 10 or 11 to version 13 and within version 13 is performed automatically by the means of the installer.
Upgrading Dr.Web Server from versions 11.X to version 13.0 is also available via the Control Center. The procedure is described in the Administrator Manual, in the Updating Dr.Web Server and Restoring from the Backup section.
|
Before upgrading Dr.Web Server, please read the Upgrading Dr.Web Agent section. |
|
Upgrading Dr.Web Server within version 13 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 Dr.Web Server updates within version 13 have the distribution kit file. Some of them can be installed via the Control Center only. |
Saving Configuration Files
When upgrading Dr.Web Server to the 13 version by the installer means, the configuration files are saved into the folder specified for the back up:
•When upgrading from version 6: to the <installation_drive>:\DrWeb Backup.
•When upgrading from versions 10, 11, and within version 13: to the folder that is specified in the Back up Dr.Web Server critical data option during the upgrade (<installation_drive>:\DrWeb Backup by default).
When upgrading Dr.Web Server of version 6, the following files are saved:
File |
Description |
|---|---|
agent.key (the name may vary) |
Agent license key file |
auth-ads.xml |
configuration file for administrators external authorization via Active Directory |
auth-ldap.xml |
configuration file for administrators external authorization via LDAP |
auth-radius.xml |
configuration file for administrators external authorization via RADIUS |
drwcsd.conf (name may vary) |
Dr.Web Server configuration file |
dbinternal.dbs |
embedded database |
drwcsd.pri |
private encryption key |
drwcsd.pub (name may vary) |
public encryption key |
enterprise.key (the name may vary) |
Dr.Web Server license key file |
webmin.conf |
Dr.Web Security Control Center configuration file |
When upgrading Dr.Web Server of version 10, the following files are saved:
File |
Description |
|---|---|
agent.key (the name may vary) |
Agent license key file |
auth-ads.xml |
configuration file for administrators external authorization via Active Directory |
auth-ldap.xml |
configuration file for administrators external authorization via LDAP |
auth-radius.xml |
configuration file for administrators external authorization via RADIUS |
enterprise.key (name may vary) |
Dr.Web Server license key file. The file is saved if it presented after the upgrade from the previous versions. For the new Dr.Web Server 13.0 installation, the file is absent |
drwcsd.conf (name may vary) |
Dr.Web Server configuration file |
drwcsd.conf.distr |
Dr.Web Server configuration file template with default parameters |
drwcsd.pri |
private encryption key |
drwcsd.pub (name may vary) |
public encryption key |
download.conf |
network settings for generating of the Agent installation packages |
frontdoor.conf |
configuration file for the Dr.Web Server remote diagnostic utility |
webmin.conf |
Control Center configuration file |
openssl.cnf |
Dr.Web Server certificate for HTTPS |
At upgrading of Dr.Web Server from version 11 and within version 13, the following files are saved:
File |
Description |
|---|---|
agent.key (the name may vary) |
Agent license key file |
auth-ads.conf |
configuration file for administrators external authorization via Active Directory |
auth-radius.conf |
configuration file for administrators external authorization via RADIUS |
auth-ldap.conf |
configuration file for administrators external authorization via LDAP |
auth-ldap-rfc4515.conf |
configuration file for administrators external authorization via LDAP using the simplified scheme |
auth-ldap-rfc4515-check-group.conf |
configuration file template for administrators external authorization via LDAP using the simplified scheme with verification of belonging to an Active Directory group |
auth-ldap-rfc4515-check-group-novar.conf |
configuration file template for administrators external authorization via LDAP using the simplified scheme with verification of belonging to an Active Directory group and using variables |
auth-ldap-rfc4515-simple-login.conf |
configuration file template for administrators external authorization via LDAP using the simplified scheme |
auth-pam.conf |
configuration file for administrators external authorization via PAM |
enterprise.key (name may vary) |
Dr.Web Server license key file. The file is saved if it presented after the upgrade from the previous versions. For the new Dr.Web Server 13.0 installation, the file is absent |
drwcsd-certificate.pem |
Dr.Web Server certificate |
download.conf |
network settings for generating of the Agent installation packages |
drwcsd.conf (name may vary) |
Dr.Web Server configuration file |
drwcsd.conf.distr |
Dr.Web Server configuration file template with default parameters |
drwcsd.pri |
private encryption key |
dbexport.gz |
database export |
drwcsd.pub (name may vary) |
public encryption key |
frontdoor.conf |
configuration file for the Dr.Web Server remote diagnostic utility |
openssl.cnf |
Dr.Web Server certificate for HTTPS |
webmin.conf |
Dr.Web Security Control Center configuration file |
yalocator.apikey |
API key for the Yandex.Locator extension |
|
If you are planning to use configuration files from the version 6 of Dr.Web Server, please note: 1.Dr.Web Server license key is no longer supported (see Licensing). 2.The embedded database is upgraded and configuration files of Dr.Web Server are converted by the means of the installer. You cannot replace these files with a backup copies when upgrading from Dr.Web Server of version 6. |
If necessary, copy other critical files you want to preserve to another folder, other than the Dr.Web Server installation folder. For instance, report templates which are stored in the \var\templates folder.
Saving Database
|
The MS SQL CE database starting from the 10 version of Dr.Web Server is no longer supported. During automatic Dr.Web Server upgrade by the means of the installer, the MS SQL CE database is automatically converted to the SQLite embedded database. |
|
Before upgrading, make sure that Microsoft SQL DBMS has case-sensitive (_CS) and accent-sensitive (_AS) collation suffixes specified. Otherwise, automatic update will be impossible.
Before upgrading, also make sure that the DBMS you use is supported by Dr.Web Server version 13. Otherwise, automatic update will be impossible. A list of supported DBMS's is available in Appendices, Appendix B. The Description of the DBMS Settings. The Parameters of the DBMS Driver. |
Before upgrading Dr.Web Enterprise Security Suite software, it is recommended that you backup the database first.
To backup database
1.Stop Dr.Web Server.
2.Export the database to the file:
•for Dr.Web Server prior to version 13
"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -home="C:\Program Files\DrWeb Server" -var-root="C:\Program Files\DrWeb Server\var" -verbosity=all exportdb <backup_folder>\esbase.es |
•for Dr.Web Server version 13 and later
"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -home="C:\Program Files\DrWeb Server" -var-root="C:\Program Files\DrWeb Server\var" -verbosity=all modexecdb database-export <backup_folder>\esbase.es |
For Dr.Web Servers with external database, it is recommended to use standard tools supplied with the database.
|
Make sure, that Dr.Web Enterprise Security Suite database export completed successfully. If the database backup copy is not available, Dr.Web Server could not be restored in emergency case. |
Upgrading Dr.Web Server
To upgrade Dr.Web Server, run the distribution file.The following procedure depends on the version you are upgrading from.
|
By default, installer uses the language of the operating system. If necessary, you can change the installation language on any step by selecting the corresponding option in the right upper part of the installer window.
For the external Dr.Web Server database, also select Use existing database during upgrade. |
|
If you are going to use the Oracle DB as an external database via the ODBC connection, then during installation (upgrading) of Dr.Web Server, in the installer settings, disable the installation of embedded client for Oracle DBMS (in the Database support → Oracle database driver section). Otherwise, interaction with the Oracle DB via ODBC will fail because of the libraries conflict. |
Upgrade from the Version 6
1.The window opens, which notifies you on the previous Dr.Web Server version installed and brief description of the upgrade process to a new version. To start configuring upgrade procedure, click Upgrade.
2.The next window contains the information on the product and the link to the license agreement text. When you read the agreement, to continue the installation, select I accept the terms of the license agreement and click Next.
3.On the following steps, the upgrading Dr.Web Server is configured as at the Installing Dr.Web Server process based on the configuration files from the previous installation. The installation wizard automatically locates the Dr.Web Server installation folder, configuration files and embedded DB location from the previous installation. If necessary, you can change locations of the files which were found automatically by the installer.
4.To uninstall Dr.Web Server of the previous version and launch the installation process of the 13.0 version of Dr.Web Server, click Install.
During the Dr.Web Server uninstallation, the configuration files are automatically saved to the <installation_drive>:\DrWeb Backup folder.
Upgrade from the Version 10.0
1.The window opens, which notifies you on the previous Dr.Web Server version installed and brief description of the upgrade process to a new version. To start configuring upgrade procedure, click Upgrade.
2.The next window contains the information on the product and the link to the license agreement text. When you read the agreement, to continue the installation, select I accept the terms of the license agreement and click Next.
3.On the following steps, the upgrading Dr.Web Server is configured as at the Installing Dr.Web Server process based on the configuration files from the previous installation. The installation wizard automatically locates the Dr.Web Server installation folder, configuration files and embedded DB location from the previous installation. If necessary, you can change locations of the files which were found automatically by the installer.
4.To uninstall Dr.Web Server of the previous version and launch the installation process of the 13.0 version of Dr.Web Server, click Install.
5.During the update, the window opens that contains the critical data backup settings before uninstalling Dr.Web Server of the previous version. It is recommended to set the Back up Dr.Web Server critical data flag. If necessary, you can change the default backup folder (<installation_drive>:\DrWeb Backup).
Upgrade from the Version 10.0.1, 10.1, 11, and within version 13
1.The window opens, which notifies you on the previous Dr.Web Server version installed and brief description of the upgrade process to a new version. To start configuring upgrade procedure, click Upgrade.
2.The next window contains the critical data backup settings before uninstalling Dr.Web Server of the previous version. It is recommended to set the Back up Dr.Web Server critical data flag. If necessary, you can change the default backup folder (<installation_drive>:\DrWeb Backup). Click Uninstall to start the uninstalling of Dr.Web Server of previous version.
3.After the previous version is uninstalled, the new version of Dr.Web Server starts the installation. The next window contains the information on the product and the link to the license agreement text. When you read the agreement, to continue the installation, select I accept the terms of the license agreement and click Next.
4.In the following steps, upgrading Dr.Web Server is configured using an existing database (as at the Installing Dr.Web Server process based on the configuration files from the previous installation). The installation wizard automatically locates the Dr.Web Server installation folder, configuration files and embedded DB location from the previous installation. If necessary, you can change locations of the files which were found automatically by the installer.
5.To start the installation of Dr.Web Server of version 13.0, click Install.
|
After upgrade of anti-virus network Dr.Web Servers is completed, you must do the following: 1.Configure encryption and compression settings for the connected Dr.Web Servers (see the Administrator Manual, the Setting Connections between Several Dr.Web Servers section). 2.Clear the cache of the Web browser that is used to connect to Dr.Web Security Control Center. |