An upgrade of Dr.Web Server up to version 13 can be performed in the following ways:
•Upgrading Dr.Web Server of version 11 or later for the same package types is performed automatically for all Unix-like OSs. If needed, you can also perform the upgrade manually.
•Upgrading Dr.Web Server of version 12 or later 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. |
|
Updating 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 uninstalling and automatically upgrading Dr.Web Server to version 13, the configuration files are saved to the default backup directory: /var/tmp/drwcs/.
When uninstalling Dr.Web Server, the following files are automatically saved:
File |
Description |
|---|---|
agent.key (the name may vary) |
Dr.Web Agent license key file |
auth-ldap.conf |
configuration file for external authorization of administrators via LDAP |
auth-ldap-rfc4515.conf |
configuration file for simple external authorization of administrators via LDAP |
auth-pam.conf |
configuration file for external authorization of administrators via PAM |
auth-radius.conf |
configuration file for external authorization of administrators via RADIUS |
certificate.pem |
SSL certificate |
common.conf |
configuration file (for some Unix-like OSs) |
dbexport.gz |
database export (created during the Dr.Web Server uninstallation using the command drwcs.sh xmlexportdb) |
download.conf |
network settings for generating Dr.Web Agent installation packages |
drwcsd-certificate.pem |
Dr.Web Server certificate |
drwcsd.conf (the name may vary) |
Dr.Web Server configuration file |
drwcsd.pri |
private encryption key |
drwcsd.pub (name may vary) |
public encryption key |
enterprise.key (name may vary) |
Dr.Web Server license key file. The file is saved if it was present after the upgrade from the previous versions. The file is missing when installing a new Dr.Web Server |
frontdoor.conf |
configuration file for the Dr.Web Server remote diagnostic utility |
local.conf |
Dr.Web Server log settings |
private-key.pem |
RSA private key |
webmin.conf |
Dr.Web Security Control Center configuration file |
yalocator.apikey |
API key for the Yandex.Locator extension |
During an automatic upgrade, the following files are saved to the backup directory:
File |
Description |
|---|---|
auth-ldap.conf |
configuration file for external authorization of administrators via LDAP |
auth-ldap-rfc4515.conf |
configuration file for simple external authorization of administrators via LDAP |
auth-pam.conf |
configuration file for external authorization of administrators via PAM |
auth-radius.conf |
configuration file for external authorization of administrators via RADIUS |
db.backup.gz |
database export (created during the Dr.Web Server upgrade using the command drwcs.sh exportdb) |
Saving the database
Before upgrading the Dr.Web Enterprise Security Suite software, it is recommended that you back up the database first.
To back up database
1.Stop Dr.Web Server.
2.Export the database to file:
•For FreeBSD:
•for Dr.Web Server prior to version 13
# /usr/local/etc/rc.d/drwcsd exportdb /var/tmp/esbase.es |
•for Dr.Web Server version 13 and later
# /usr/local/etc/rc.d/drwcsd modexecdb database-export /var/tmp/esbase.es |
•For Linux OS:
•for Dr.Web Server prior to version 13
# /etc/init.d/drwcsd exportdb /var/tmp/esbase.es |
•for Dr.Web Server version 13 and later
# /etc/init.d/drwcsd modexecdb database-export /var/tmp/esbase.es |
For Dr.Web Servers with an external database, use the standard tools supplied with the database.
|
Make sure that the Dr.Web Enterprise Security Suite database export completed successfully. If a database backup copy is not available, Dr.Web Server cannot be restored in an emergency case. |
Upgrading Dr.Web Server version 11 or later for the same package types is automatic for all Unix-like OSs.
The configuration files will be automatically converted and placed in the corresponding directories. Some configuration files are also stored in the backup directory.
If you cannot upgrade Dr.Web Server from version 11 or later over the installed package, uninstall the Dr.Web Server software of the previous versions saving a backup copy, and then install the software of version 13 using the saved backup copy.
1.Stop Dr.Web Server.
2.If you plan to use any files later (besides the files which are copied automatically during uninstallation of Dr.Web Server at step 3), back up these files (for example, the report templates, etc) manually.
3.Uninstall the Dr.Web Server software (see Removing Dr.Web Server for Unix-like OS). You will be prompted to create backup copies of the files. To do this, specify the path to store the backup or accept the default path.
4.Install the new Dr.Web Server version 13 according to the general installation procedure (see Installing Dr.Web Server for Unix-like OS) using the backup copy from step 3. All saved configuration files and the embedded database (if you use the embedded database) will be automatically converted to be used by Dr.Web Server version 13. Without the automatic conversion the database (if you use the embedded database) and some of the Dr.Web Server configuration files from the previous version cannot be used.
If you saved some files manually, move them to the same directories where they were located in the previous version.
|
Set the user selected at the installation of the new Dr.Web Server version (drwcs by default) as the file owner for all backup files from the previous Dr.Web Server version (see step 4). |
5.Launch Dr.Web Server.
6.Set up a repository upgrade and perform the full upgrade.
|
Once the upgrade of Dr.Web Servers within the anti-virus network is completed, configure encryption and compression settings for connected Dr.Web Servers (see the Administrator Manual, the Setting Connections between Several Dr.Web Servers section). |