Instruction on "moving" "DrWeb" Enterprise Server to another PC. — различия между версиями

Материал из wiki.drweb.com
Перейти к: навигация, поиск
м
 
м (wikify & spelling & style)
Строка 1: Строка 1:
== '''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.
 
+
Sometimes there is necessary to "move" working "DrWeb" Enterprise Server to another physical PC, for example because of the PC equipment failure or as a result of reorganisation the infrastructure of LAN.
+
  
 
How to do it ?
 
How to do it ?
  
1. Stop the "DrWeb" Enterprise Server service on the PC.
+
#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.)
2. Copy (backup) the next files from the server:
+
#*'''%ES%\var\repository\''' (this folder with all data that this folder contains)
(It is important to copy those files when server service is stopped.)
+
#*'''%ES%\var\dbinternal.dbs''' (the database file)
 
+
#*'''%ES%\etc\drwcsd.pri'''
''- %ES%\var\repository\''
+
#*'''%ES%\Installer\drwcsd.pub''' (files of private and public keys)
(this folder with all data that this folder contains)
+
#*'''%ES%\etc\drwcsd.conf''' (server configuration file)
 
+
#*'''%ES%''' (the program installation folder, default == "..\program files\drweb enterprise server\")
''- %ES%\var\dbinternal.dbs''
+
#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.)
(the database file)
+
#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.)
''- %ES%\etc\drwcsd.pri
+
#Check whether the server works correct.
- %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\")
+
 
+
3. Install "DrWeb" Enterprise Server product on the new PC with all default settings.
+
(Use the exact or higher version of "DrWeb" Enterprise Server distributive file, not lower one.)
+
 
+
4. Stop "DrWeb" Enterprise Server service on the new PC.
+
 
+
5. Copy the saved (backuped) files (chapter 2) up on the new server.
+
(It is important to copy theese files when "DrWeb" Enterprise Server is stopped.)
+
 
+
6. Check if the server works correct.
+
  
 
Other actions are not necessary if 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 - adress of the server during the installation of "DrWeb" ES agent.
+
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.)
  
(Client PC's may find "DrWeb" Enterprise Server using multicast- or broadcast- requests)
+
Otherwise it is necessary to reconfigure the client part agents according the new server address.
  
Otherwise it is necessary to reconfigure the client part agents on a new "DrWeb" Enteprise Suite adress.
+
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]].
 
+
You may also reconfigure IP - adress of "DrWeb" Enterprise Server for all agents that are in LAN in that moment through the "DrWeb" Enterprise Console.
+
  
 
It is necessary to reboot the client part PC's after all actions.
 
It is necessary to reboot the client part PC's after all actions.
  
It may be necessary to update the database to the currient version of it if the version of "DrWeb" Enterprise Suite installed on the new PC is higher than on the previous (old PC) one.
+
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.
 
The service will not work in that case.
Строка 54: Строка 32:
 
A new record like:
 
A new record like:
  
''"20061011.121813.14 FTL 001432/noname [DbMgr] Incompatible database version 49, expected 50"''
+
20061011.121813.14 FTL 001432/noname [DbMgr] Incompatible database version 49, expected 50
  
may appear in:
+
may appear in '''%ES%\var\drwcsd.log''' file.
  
''%ES%\var\drwcsd.log''
+
The procedure of updating the database can help in this situation. (The procedure of updating must be done with stopped service.)
  
file.
+
You may try the following command line for updating the database:
  
The procedure of updating the database may help in this situation.
+
"C:\Program Files\DrWeb Enterprise Server\bin\drwcsd.exe"
(The procedure of updating makes with stopped service.)
+
  "-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"
  
You may try the next command line for updating the database:
+
This command must be entered as a single line!
  
''"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-root=C:\Program Files\DrWeb Enterprise Server\var\." -verbosity=ALL upgradedb "C:\Program Files\DrWeb Enterprise Server\var\update-db\."''
+
After updating of the database the errors should disappear.
  
After the database updating the mistake may 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.
  
The second serious moment that may happen during "moving" "DrWeb" Enterprise Server on another PC is when the exact network interface on that "DrWeb" Enterprise Suite works was specified on the old server PC.
+
This data may be recorded in the end of the file '''%ES%\etc\drwcsd.conf'''
  
This data may be recorded in the end of the next file:
+
Transport "drwcs" '''"tcp/192.168.2.2:2371" "udp/192.168.2.2:2371"'''
  
''%ES%\etc\drwcsd.conf''
+
You should just edit these data and restart the server service.
 
+
Transport "drwcs" ''"tcp/192.168.2.2:2371" "udp/192.168.2.2:2371"''
+
 
+
You may just edit this data and reboot the PC after this action.
+
  
 
[[Перенос сервера Dr.Web® Enterprise Suite на другую машину|Original article]]
 
[[Перенос сервера Dr.Web® Enterprise Suite на другую машину|Original article]]
Строка 85: Строка 63:
 
Good wishes.
 
Good wishes.
  
You may follow the next link to download the manual on "DrWeb" Enterprise Suite to get more detail information about "DrWeb" Enterprise Suite product:
+
You may follow [ftp://ftp.drweb.com/pub/drweb/esuite/444/doc/drweb-es-444-en.pdf this link] to download [[Dr.Web® Enterprise Suite]] manual to get more detailed information about Dr.Web® Enterprise Suite product:
 
+
[ftp://ftp.drweb.com/pub/drweb/esuite/444/doc/drweb-es-444-en.pdf]
+

Версия 22:40, 18 марта 2009

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 ?

  1. Stop the server service on the PC.
  2. 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%\etc\drwcsd.pri
    • %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\")
  3. 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.)
  4. Stop the server service on the new PC.
  5. Copy the saved (backuped) files (chapter 2) to the new server. (It is important to copy these files when the server is not running.)
  6. 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.

Original article

Good wishes.

You may follow this link to download Dr.Web® Enterprise Suite manual to get more detailed information about Dr.Web® Enterprise Suite product: