Instruction on "moving" "DrWeb" Enterprise Server to another PC.
Sometimes it is necessary to "move" working Dr.Web® Enterprise Server to another physical PC, for example because of the PC equipment failure or as a result of reorganization of the infrastructure of LAN.
How to do it ?
- Stop the server service on the PC.
- Copy (backup) the following files from the server: (It is important to copy those files when server service is stopped.)
- %ES%\var\repository\ (this folder with all data that this folder contains)
- %ES%\var\dbinternal.dbs (the database file)
- %ES%\Installer\drwcsd.pub (files of private and public keys)
- %ES%\etc\drwcsd.conf (server configuration file)
- %ES% (the program installation folder, default == "..\program files\drweb enterprise server\")
- Install the server on the new PC with all default settings. (Use the exact or higher version of the server distributive file, not lower one.)
- Stop the server service on the new PC.
- Copy the saved (backuped) files (chapter 2) to the new server. (It is important to copy these files when the server is not running.)
- Check whether the server works correct.
Other actions are not necessary if server works correct.
It is not necessary to reconfigure client part PC's without the specification of IP - address of the server during the installation of Dr.Web® Enterprise Agent. (Client PC's may use multicast or broadcast requests to search for the server.)
Otherwise it is necessary to reconfigure the client part agents according the new server address.
You may also reconfigure IP address of the server for all agents that are in LAN in that moment through the [[Dr.Web&rep; Enterprise Console]].
It is necessary to reboot the client part PC's after all actions.
It may be necessary to update the database up to the current version of it if the version of the server installed on the new PC is higher than on the previous (old PC) one.
The service will not work in that case.
A new record like:
20061011.121813.14 FTL 001432/noname [DbMgr] Incompatible database version 49, expected 50
may appear in %ES%\var\drwcsd.log file.
The procedure of updating the database can help in this situation. (The procedure of updating must be done with stopped service.)
You may try the following command line for updating the database:
"C:\Program Files\DrWeb Enterprise Server\bin\drwcsd.exe" "-home=C:\Program Files\DrWeb Enterprise Server" "-exe-root=C:\Program Files\DrWeb Enterprise Server" "-var-oot=C:\Program Files\DrWeb Enterprise Server\var" -verbosity=ALL upgradedb "C:\Program Files\DrWeb Enterprise Server\var\update-db"
This command must be entered as a single line!
After updating of the database the errors should disappear.
The second important moment that may happen during "moving" the server to another PC is when the exact network interface on that server works was specified on the old server PC.
This data may be recorded in the end of the file %ES%\etc\drwcsd.conf
Transport "drwcs" "tcp/192.168.2.2:2371" "udp/192.168.2.2:2371"
You should just edit these data and restart the server service.