During the operation, Dr.Web Server regularly stores backup copies of important information: license keys, database contents, encryption private key, Dr.Web Server configuration and Control Center configuration.
The backup files are stored in the following folders:
•for Windows OS: <installation_drive>:\DrWeb Backup
•for Linux OS: /var/opt/drwcs/backup
•for FreeBSD OS: /var/drwcs/backup
To perform the back up, a daily task is included into the Dr.Web Server schedule. If such task is missing in the schedule, it is recommended to create it.
All files in the backup except the database contents, are ready to use. The database backup copy is stored in the .gz format compatible with gzip and other archivers. The database contents can be imported from the backup copy to another database of Dr.Web Server using the modexecdb database-import-and-upgrade command, thus restore the data.
|
To restore the database you can also use a backup created manually by administrator via the Control Center in the Administration → Database management → Export (for the Export entire database mode only). |
It is also recommended to store copies of created backups and other important files on another computer. Thus, you will be able to avoid data loss should the computer, on which Dr.Web Server is installed, be damaged, and to fully restore the data and the functionality of Dr.Web Server. If license keys are lost, they may be requested once again, as specified in Administrator Manual, p. Licensing.
To restore Dr.Web Server after the failure if the backup is available
1.Choose a computer to install the new Dr.Web Server. Isolate this computer from operating Agents: disconnect it from the network in which the Agents are installed or temporarily change its IP address, or use any other method you mostly prefer.
2.Install the new Dr.Web Server.
3.In the Administrating → License manager section, add the license key from the previous Dr.Web Server installation and propagate it on corresponding groups, particularly on the Everyone group. The step is obligatory if the license key was not set during the Dr.Web Server installation.
4.Update repository of the installed Dr.Web Server from the GUS:
a)Open the Administrating → Repository state section of the Control Center.
b)Click the Check for updates button to check whether updates to all of the products are available on the GUS servers and download updates, if any.
5.If new versions of the Dr.Web Server software are available, perform the update to the latest version:
a)Open Administrating → Dr.Web Server section of the Control Center.
b)To open the Dr.Web Server versions list, click the current version of Dr.Web Server or click the Versions list button. This opens the Dr.Web Server Updates section with the list of available updates and backups of Dr.Web Server.
c)To update the Dr.Web Server software, set the option next to the last version in the All versions list. Click Save.
d)Wait for the completion of the Dr.Web Server update process.
6.Stop Dr.Web Server.
7.Replace the Dr.Web Server critical data with the saved ones from the backup:
Operating system |
Configuration files |
|---|---|
Windows |
etc in the Dr.Web Server installation folder |
Linux |
/var/opt/drwcs/etc |
FreeBSD |
/var/drwcs/etc |
8.Configure the database.
a)External database:
No more actions to connect the database to Dr.Web Server are required (as long as the Dr.Web Server configuration file has been saved).
If the version of Dr.Web Server installed from the last updates is later than the version of the lost Dr.Web Server, update the external database via the modexecdb database-upgrade command:
•for Windows OS:
"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -log=drwcsd.log modexecdb database-upgrade |
•for Linux OS:
/etc/init.d/drwcsd -log=drwcsd.log modexecdb database-upgrade |
•for FreeBSD OS:
/usr/local/etc/rc.d/drwcsd -log=drwcsd.log modexecdb database-upgrade |
b)Backup of external or embedded database:
For the external database, preliminary clean it up via the modexecdb database-clean command (see Appendix H3.3. Database Commands).
Import the database content from the corresponding backup file with database format updating to the installed Dr.Web Server version using the modexecdb database-import-and-upgrade command:
•for Windows OS:
"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -home="C:\Program Files\DrWeb Server" -var-root="C:\Program Files\DrWeb Server\var" -verbosity=all -log=drwcsd.log modexecdb database-import-and-upgrade "<path_to_the_backup_file>\database.gz" |
•for Linux OS:
/etc/init.d/drwcsd -log=drwcsd.log modexecdb database-import-and-upgrade "<path_to_the_backup_file>/database.gz" |
•for FreeBSD OS:
/usr/local/etc/rc.d/drwcsd -log=drwcsd.log modexecdb database-import-and-upgrade "<path_to_the_backup_file>/database.gz" |
|
For all replaced files assign the same permissions as those set at the previous (lost) installation of Dr.Web Server. For UNIX system-based OS: rw for drwcs:drwcs. |
9.Start Dr.Web Server.
10.Make sure that data from the database backup is save and actual: the Agent settings, anti-virus network tree state and etc.
11.Restore the Dr.Web Server accessibility for the Agents according to the Dr.Web Server isolation way selected on step 1.
|
If some Agents were installed after the last backup had been made, they will not be connected to Dr.Web Server after the database has been restored from the backup. You should remotely reset them to the newbie mode. In the Administrating → Dr.Web Server configuration on the General tab, set the Reset unauthorized to newbie flag and in the Newbies registration mode drop-down list, select Allow access automatically. Click Save and restart Dr.Web Server. After all stations will be successfully connected to the new Dr.Web Server, change these Dr.Web Server settings to the settings adopted according to the policy of your company. |