Restoring a Dr.Web Server Cluster Node |
If one of the Dr.Web Servers in a cluster stops working, Dr.Web Agents that lost the connection to it will connect to another cluster node. In case of a fatal Dr.Web Server failure, you need to restore it: install Dr.Web Server software and add the Dr.Web Server to the cluster again. Installing a Dr.Web Server to be added to a cluster
If you have a backup copy of the failed Dr.Web Server, you can use it to facilitate the cluster node restoration process. A backup copy contains repository settings, configuration files, encryption keys, certificates, and the embedded database backup. When installing a Dr.Web Server to replace a cluster node, follow the directions below. Installing Dr.Web Server for Unix-like OS Follow the instructions from the , section Installing Dr.Web Server for Unix-like OS . You can install a new Dr.Web Server or use a backup copy of the Dr.Web Server that was part of the cluster and failed. By default, backup copies are stored in the following folders: •for Dr.Web Server under Linux—/var/opt/drwcs/backup, •for Dr.Web Server under FreeBSD—/var/drwcs/backup. A Dr.Web Server that was installed from a backup copy will use the common database accessed by the cluster nodes. A Dr.Web Server installed without a backup copy will use the embedded database. Once the installation process is finished, the Dr.Web Server must be switched to the common database used by the cluster. Installing Dr.Web Server for Windows OS You can install a new Dr.Web Server or use a backup copy of the Dr.Web Server that was part of the cluster and failed. By default, backup copies are stored in the <installation_drive>:\DrWeb Backup folder. Follow the instructions from the , section Installing Dr.Web Server for Windows OS, taking note of the following points: •It is inadvisable to connect Dr.Web Server to an external database during the installation process due to the risk of database data loss once the Dr.Web Server is connected to the cluster. •When installing from a backup copy, set the following configuration parameters: ▫: select the option. It is not recommended to proceed with the external database as it can lead to data loss once Dr.Web Server connects to the cluster. Dr.Web Server needs to be reconnected to the external database used within the cluster only after the Dr.Web Server installation is finished. ▫: set the and values. If the flag is not set, set it to allow Dr.Web Server to communicate with the other cluster nodes via a multicast group. Specify the parameters of the multicast group used by Dr.Web Servers in the cluster below. The values of the other parameters can be specified according to the section. •When installing a new Dr.Web Server, specify the following configuration parameters: ▫: specify the paths to the drwcsd.conf configuration file and the private encryption key used by the Dr.Web Server that failed, if you have them. Otherwise, leave the fileds empty to create new encryption keys, certificate, and configuration file with the default settings. The values of these parameters must be changed after the Dr.Web Server installation. ▫: select the option. The Dr.Web Server needs to be connected to the external database used within the cluster only after the Dr.Web Server installation is finished. ▫: specify the and values. Set the flag to allow the Dr.Web Server to communicate with other cluster nodes via a multicast group. Specify the multicast group parameters to be used by Dr.Web Servers in the cluster. The values of other parameters can be set as described in the section. Adding a Dr.Web Server to a cluster To add the installed Dr.Web Server to a cluster, follow the instructions from the , section Dr.Web Server Cluster . |