|
Upgrading of the Server from the 6 version to the 10 version and within version 10 is performed automatically by the means of the installer.
|
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 6 version has been removed, the following files are automatically saved:
File
|
Description
|
Default folder
|
agent.key (name may vary)
|
Agent license key file
|
etc
|
certificate.pem
|
SSL certificate
|
drwcsd.conf (name may vary)
|
Server configuration file
|
drwcsd.pri
|
private encryption key
|
enterprise.key (name may vary)
|
Server license key file
|
private-key.pem
|
RSA private key
|
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
|
dbinternal.dbs
|
embedded database
|
var
|
drwcsd.pub
|
public encryption key
|
•Installer •webmin\install |
After the Server of 10 version has been removed, the following files are saved:
File
|
Description
|
Default folder
|
agent.key (name may vary)
|
Agent license key file
|
etc
|
enterprise.key (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 of version 10 installation, the file is absent
|
frontdoor.conf
|
configuration file for the Server remote diagnostic utility
|
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
|
download.conf
|
network settings for generating of the Agent installation packages
|
drwcsd.conf (name may vary)
|
Server configuration file
|
drwcsd.conf.distr
|
Server configuration file template with default parameters
|
drwcsd.pri
|
private encryption key
|
openssl.cnf
|
Server certificate for HTTPS
|
webmin.conf
|
Dr.Web Security Control Center configuration file
|
dbexport.gz
|
database export
|
<backup> folder
|
drwcsd.pub
|
public encryption key
|
•Installer •webmin\install |
|
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 of version 10. |
If necessary, copy other critical files you want to preserve to another folder, other than 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 Server upgrade by the means of the installer, the MS SQL CE database is automatically converted to the IntDB embedded 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:
"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 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.
|
Upgrading Dr.Web Server
To upgrade Dr.Web Server
1.Run the distribution file.
|
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.
|
2.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. 3.A window with information on the product and the link to the license agreement text will be opened. When you read the agreement, to continue the installation, select I accept the terms of the license agreement and click Next. 4.On the following steps of the installation wizard, the upgrading Server is configured as at the Installing Dr.Web Server process based on the configuration files from the previous installation (see above). The installation wizard automatically locates the 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.
|
For the external Server database, also select Use existing database during upgrade.
|
|
If you are going to use the Oracle or PostgreSQL DB as an external database via the ODBC connection, then during upgrading of the Server, in the installer settings, disable the installation of embedded client for PostgreSQL DBMS (in the Database support section).
Otherwise, interaction with the Oracle DB via ODBC will fail because of the libraries conflict.
|
5.To remove the Server of the previous version and launch the installation process of the 10 version of the Server, click Install.
After upgrading of Dr.Web Server to 10 version perform the following to ensure normal operation of Dr.Web Security Control Center:
1.Clear cache of the Web browser that is used to connect to Dr.Web Security Control Center. 2.Upgrade Dr.Web Security Control Center Extension.
|
