Dr.Web Enterprise Security Suite regularly backs up important data: database contents, Server license key, private encryption key, Server configuration key, and Dr.Web Control Center configuration key. The backup files are stored in the following folders (relatively to the Server installation folder):
◆for Windows OS: \var\Backup
◆for Linux OS: /var/opt/drwcs/backup
◆for FreeBSD and Solaris OS: /var/drwcs/backup
For that purpose a daily task is included to the Server schedule. If such task is missing, it is strongly recommended to create it.
The copies are stored in the .dz format unpackable with gzip and other archivers. After unpacking all the files, except for the database contents, are ready to use. To restore the data, the database contents can be imported from the backup to another database of the Server by means of the importdb switch (see p. Restoring the Database of Dr.Web Enterprise Security Suite).
It is also recommended to store copies of the following files on another PC: drwcsd.pri and drwcsd.pub encryption keys, enterprise.key and agent.key license keys, certificate.pem SSL certiifcate, private-key.pem RSA private key and regularly copy Server database contents backup database.dz, Server and Dr.Web Control Center configuration files drwcsd.conf and webmin.conf to another PC. Thus you will be able to avoid data loss should the PC, on which Enterprise Server is installed, be damaged, and to fully restore the data and the functionality of the Server. If license keys are lost they may be requested once again, as specified in p. Key Files.
To Restore a Dr.Web Enterprise Server for Windows OS
Install Enterprise Server software of the same version as the lost one on a working PC (see p. Installing the Dr.Web Enterprise Server for Windows OS). During the installation:
◆If there is a copy of the DB (internal or external) on another PC and it is not damaged, in the respective dialog boxes of the installer specify it along with the saved files of the Server license key, private encryption key and Server configuration.
◆If the Server DB (internal or external) was lost, but a backup of its contents database.dz is saved, then in the respective dialog boxes of the installer select creating a new database, specify the saved files of the Server and Agent license keys, private encryption key and Server configuration. After the installation import the DB contents from the backup (see p. Restoring the Database of Dr.Web Enterprise Security Suite).
To Restore a Dr.Web Enterprise Server for UNIX System-Based OS
1.Install Enterprise Server software of the same version as the lost one on a working PC (see p. Installing the Dr.Web Enterprise Server for UNIX system-based OS).
2.Put the saved files to:
◆for Linux OS: /var/opt/drwcs/etc, except for the public key. Put the latter to /opt/drwcs/Installer/
◆for FreeBSD OS: /var/drwcs/etc, except for the public key. Put the latter to /usr/local/drwcs/Installer/
◆for Solaris OS: /var/drwcs/etc, except for the public key. Put the latter to /opt/drwcs/Installer/
|
For all replaced files assign the same permissions as those set at the previous (lost) installation of the Server. |
3.Generate a new SSL certificate:
◆for Linux OS and Solaris OS:
/etc/init.d/drwcsd selfcert |
◆for FreeBSD OS:
/usr/local/etc/rc.d/drwcsd.sh selfcert |
◆for other supported versions:
/opt/drwcs/bin/drwcsd -var-root=/var/drwcs -log=/var/drwcs/log/drwcsd.log selfcert |
4.The next steps depend on the availability of the Server database:
a)If you have a working external DB, no further restoring procedures are needed, provided that you have the configuration file and the Server build is the same as the old one. Otherwise you will have to register the database in the configuration file and/or update the structure of the database with the upgradedb switch (see variant c below).
b)If you have a backup of internal or external DB contents (database.dz), start the Server, remove the internal DB created at the installation, initiate creating a new one and import the contents of the old DB from the backup copy (see p. Restoring the Database of Dr.Web Enterprise Security Suite).
c)If you have a saved copy of the internal DB, replace the new file with it:
for Linux OS: /var/opt/drwcs/dbinternal.dbs
for FreeBSD OS and Solaris OS: /var/drwcs/dbinternal.dbs
|
For all replaced files assign the same permissions as those set at the previous (lost) installation of the Server. |
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 |
for other supported versions:
/opt/drwcs/bin/drwcsd -var-root=/var/drwcs -log=/var/drwcs/log/drwcsd.log upgradedb update-db |
5.Launch Enterprise Server.
|
If some Agents were installed after the last backup had been made they will not be connected to the Server after the database has been restored from the backup. You should remotely reset them to the newbie mode. For that purpose, on Dr.Web Control Center Administration menu, select Configure Dr.Web Enterprise Server. A Dr.Web Enterprise Server configuration window will be opened. On the General tab, set the Reset unauthorized to newbie flag. |
