During its 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 backup, a daily task is included in the Dr.Web Server schedule. If such a 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 backup copy of the database is stored in the .gz format compatible with gzip and other archivers. The contents of the database can be imported from the backup copy to another Dr.Web Server database using the modexecdb database-import-and-upgrade command. Thus the data can be fully restored.
|
To restore the database you can also use a backup created by the administrator manually 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 the Administrator Manual, section Licensing.
Restoring Dr.Web Server after a failure if a backup is available
1.Select a computer to install the new Dr.Web Server. Isolate this computer from the online Dr.Web Agents: disconnect it from the network where Dr.Web Agents are installed or temporarily change its IP address, or use any other method you prefer.
2.Install the new Dr.Web Server.
3.In the Administration → License manager section, add the license key from the previous Dr.Web Server installation and propagate it to the appropriate groups, particularly to the Everyone group. This step is mandatory if the license key was not set during Dr.Web Server installation.
4.Update the repository of the installed Dr.Web Server from the GUS:
a)Open the Administration → Repository state section of the Control Center.
b)Click the Check for updates button to check whether updates for all of products are available on the GUS servers and download them, if necessary.
5.If new versions of the Dr.Web Server software are available, perform the update to the latest version:
a)Open Administration → Dr.Web Server section of the Control Center.
b)To open the Dr.Web Server version list, click on the current version of Dr.Web Server or click the List of versions button. This will open the Dr.Web Server Updates section with the list of available Dr.Web Server updates and backups.
c)To update the Dr.Web Server software, set the flag next to the last version in the All versions list. Click Apply.
d)Wait for the Dr.Web Server update process to complete.
6.Stop Dr.Web Server.
7.Replace the critical Dr.Web Server data with the saved data 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 further actions are required to connect the database to Dr.Web Server (as long as the Dr.Web Server configuration file was saved).
If the version of Dr.Web Server installed using the latest updates is greater than the version of the faulty Dr.Web Server, update the external database using the modexecdb database-upgrade command:
•for Windows OS:
"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -verbosity=all -log="C:\Program Files\DrWeb Server\var\upgradedb.log" modexecdb database-upgrade |
•for Linux OS:
/etc/init.d/drwcsd modexecdb database-upgrade |
•for FreeBSD OS:
/usr/local/etc/rc.d/drwcsd modexecdb database-upgrade |
b)Backup of external or embedded database:
If you are using the external database, first clean it up using the modexecdb database-clean command (see Appendix G3.3. Database Commands).
Import the database contents from the corresponding backup file and simultaneously update the database format to comply with 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=trace -log="C:\Program Files\DrWeb Server\var\importupgradedb.log" modexecdb database-import-and-upgrade "<path_to_the_backup_file>\database.gz" |
•for Linux OS:
/etc/init.d/drwcsd modexecdb database-import-and-upgrade "<path_to_the_backup_file>/database.gz" |
•for FreeBSD OS:
/usr/local/etc/rc.d/drwcsd modexecdb database-import-and-upgrade "<path_to_the_backup_file>/database.gz" |
|
Assign the same permissions to all replaced files as in the previous (corrupted) installation of Dr.Web Server. For Unix-like OS: rw for drwcs:drwcs. |
9.Start Dr.Web Server.
10.Make sure that the data from the database backup is safe and up-to-date: the Dr.Web Agent settings, anti-virus network tree state and etc.
11.Restore the access to Dr.Web Server for Dr.Web Agents according to the Dr.Web Server isolation method selected in step 1.
|
If some Dr.Web Agents were installed after the last backup had been made, they will not connect to Dr.Web Server after the database is restored from the backup. You should remotely reset them to Newbie mode. In the Administration → 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 have successfully connected to the new Dr.Web Server, change these Dr.Web Server settings to the settings adopted by your company policy. |