Restoring from Dr.Web Server Backup

Top  Previous  Next

During the operation, Dr.Web Server regularly stores backup copies of important information: license keys, database contents, encryption private key, 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 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 the Server using the upimportdb command, thus restore the data.

info

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). But, at this, a backup copy is saved in the xml format, and for the import you must use the xmlupimportdb command.

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 the Server. If license keys are lost, they may be requested once again, as specified in Administrator Manual, p. Licensing.

If after the Server failure, the backup is available, perform the following procedure:

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 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 Server installation.

4.Update repository of the installed 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 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 Server versions list, click the current version of the Server or click the Versions list button. This opens the Dr.Web Server Updates section with the list of available updates and backups of the Server.

c)To update the Server software, set the option next to the last version in the All versions list. Click Save.

d)Wait for the completion of the Server update process.

6.Stop the Server.

7.To get a public encryption key from the private key backup, use the drwsign utility from the \bin subfolder of the Server installation folder:

drwsign extract [-private-key=<private_key>] <public_key>

As the <private_key> and <public_key>, specify the corresponding paths to find the private key and to place the creating public key.

8.Replace the Server critical data with the saved ones from the backup:

Operating system

Public encryption key

Configuration files

Windows

webmin\install in the Server installation folder

etc in the Server installation folder

Linux

/opt/drwcs/webmin/install

/var/opt/drwcs/etc

FreeBSD

/usr/local/drwcs/webmin/install

/var/drwcs/etc

9.Configure the database.

a)External database:

No more actions to connect the database to the Server are required (as long as the Server configuration file has been saved).

If the version of the Server installed from the last updates is newer than the version of the lost Server, update the external database via the upgradedb command:

for Windows OS:

"C:\Program Files\DrWeb Server\bin\drwcsd.exe" upgradedb

for Linux OS:

/etc/init.d/drwcsd upgradedb

for FreeBSD OS:

/usr/local/etc/rc.d/drwcsd upgradedb

b)Backup of external or embedded database:

For the external database, preliminary clean it up via the cleandb command (see Appendix H4.3).

Import the database content from the corresponding backup file with database format updating to the installed Server version using the upimportdb 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 upimportdb "<path_to_the_backup_file>\database.gz"

for Linux OS:

/etc/init.d/drwcsd upimportdb "<path_to_the_backup_file>/database.gz"

for FreeBSD OS:

/usr/local/etc/rc.d/drwcsd upimportdb "<path_to_the_backup_file>/database.gz"

warning

For all replaced files assign the same permissions as those set at the previous (lost) installation of the Server.

For UNIX system-based OS: rw for drwcs:drwcs.

10.Start the Server.

11.Make sure that data from the database backup is save and actual: the Agent settings, anti-virus network tree state and etc.

12.Restore the Server accessibility for the Agents according to the Server isolation way selected on step 1.

info

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. 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 the Server.

After all stations will be successfully connected to the new Server, change these Server settings to the settings adopted according to the policy of your company.