Restoring from Dr.Web Server Backup |
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 OS: \var\Backup (relatively to the Server installation folder) •for OS and OS: /var/opt/drwcs/backup •for : /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.
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 , 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 section, add the license key from the previous Server installation and propagate it on corresponding groups, particularly on the 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 section of the Control Center. b)Click the 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 section of the Control Center. b)To open the Server versions list, click the current version of the Server or click the button. This opens the 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 list. Click . 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:
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:
▫for Linux OS and Solaris OS:
▫for FreeBSD OS:
b)Backup of external or embedded database: For the external database, preliminary clean it up via the clean.sql script located in the etc subfolder of the Server installation folder. 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:
•for Linux OS and Solaris OS:
•for FreeBSD OS:
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.
|