Moving Dr.Web Server to Another Computer (under Linux OS)

After migrating Dr.Web Server to another computer, pay attention to the settings of the transport protocols and, if necessary, change them in the the Transport tab of the Administration → Dr.Web Server configuration section.

The procedure for starting and stopping Dr.Web Server is described in the Administrator Manual, section Starting and Stopping Dr.Web Server.

Migrating Dr.Web Server (when installing the same version of Dr.Web Server) under Linux OS

1.Install a new Dr.Web Server (empty configuration, with a new DB) on the target computer according to the instructions in the Installation Manual, section Installing Dr.Web Server for Unix-like OS.

If you plan to migrate the previous Dr.Web Server while keeping its IP address, assign a temporary IP address to the new Dr.Web Server so that the stations can communicate with the previous Dr.Web Server during the migration.

2.Add your valid license key Agent.key to the License Manager of the new Dr.Web Server and propagate it to the Everyone group.

3.Open the Repository state section in the web interface of the new Dr.Web Server and make sure that the repository is updated correctly.

4.Open the Administration → Dr.Web Server section and make sure that the date displayed in this section matches the date of the current Dr.Web Server revision in the Repository state section. If the date does not match and there is a message about the availability of updates, click the View list of versions button and update Dr.Web Server to the latest version.

5.Stop the new Dr.Web Server via the web interface or via the console using the following command:

# /etc/init.d/drwcsd stop

6.Replace the /var/opt/drwcs/etc/drwcsd.conf file on the new Dr.Web Server with a similar one from the previous Dr.Web Server.

If you are going to use a different OS, you should check if there are any Windows paths in the drwcsd.conf file. If so, fix them manually before switching an OS.

Please note that the paths for FreeBSD OS are different:

•/var/opt/drwcs/ -> /var/drwcs/

•/opt/drwcs/ -> /usr/local/drwcs/

7.Remove the drwcsd-certificate.pem certificate file from the /opt/drwcs/webmin/install/windows folder on a new Dr.Web Server.

# rm /opt/drwcs/webmin/install/windows/drwcsd-certificate.pem

8.Delete the drwcsd.pri private key and the second copy of the drwcsd-certificate.pem certificate from the /var/opt/drwcs/etc/ folder on the new Dr.Web Server .

9.Delete the database file from the /var/opt/drwcs/ folder on the new Dr.Web Server.

10.If the previous Dr.Web Server is running on Windows OS, copy the drwcsd.pri private key and the drwcsd-certificate.pem certificate from the %programfiles%\DrWeb Server\etc folder on the previous Dr.Web Server to the /var/opt/drwcs/etc directory/ folder on the new Dr.Web Server. If the previous Dr.Web Server is running on a Linux OS, copy these files from the var/opt/drwcs/etc/ folder on the previous Server to the same folder on the new server.

11.Stop the previous Dr.Web Server via the web interface (Start → All programs → Dr.Web Server → Dr.Web Server management) or (if Linux OS is installed) via the console:

# /etc/init.d/drwcsd stop

# /etc/init.d/drwcsd modexecdb database-verify

If an error message appears in the drwscd.log file after running this command, please, contact technical support.

13.Back up the database using the SQL server tools (when using the embedded DB, just back up the database.sqlite file). Copy the database file from the %programfiles%\DrWeb Server\var folder of the previous Dr.Web Server (from the /var/opt/drwcs/ folder if Linux OS was installed) to the /var/opt/drwcs/ folder of the new Dr.Web Server.

14.Start the previous Dr.Web Server (to continue offering service to Dr.Web Agents) via the web interface or via the console using the following command:

# /etc/init.d/drwcsd start

15.On the new Dr.Web Server make the drwcs user the owner of the /var/opt/drwcs/database.sqlite folder and the owner of the /var/opt/drwcs/etc/drwcsd.pri and /var/opt/drwcs/etc/drwcsd-certificate.pem files:

# chown -R drwcs /var/opt/drwcs/database.sqlite

# chown drwcs /var/opt/drwcs/etc/drwcsd.pri

# chown drwcs /var/opt/drwcs/etc/drwcsd-certificate.pem

16.Copy the drwcsd-certificate.pem certificate to the /opt/drwcs/webmin/install/windows folder.

# cp /var/opt/drwcs/etc/drwcsd?certificate.pem /opt/drwcs/webmin/install/windows

# /etc/init.d/drwcsd start

18.Log in to the web interface of the new Dr.Web Server using the same credentials as for the previous Dr.Web Server. Make sure that all Dr.Web Agents are displayed correctly in the anti-virus network list.

19.Open the Administration → Repository state section and make sure that the repository on the new Dr.Web Server is updated without errors. If there are any error messages in the product list table in the "Repository status" column, please, contact technical support. Attach the drwscd.log file to the request. Do not take any further actions until you receive feedback on the request.

20.Open the Administration → Dr.Web Server Task Scheduler section and select the Backup sensitive data task. Click on the

icon and select the Action tab in the task editing window. Make sure that the path to the folder on the previous Dr.Web Server is not specified in the Path field. Either clear this field and leave it empty (in this case, the default /var/opt/drwcs/backup folder will be used to store backup copies) or specify the path to the folder on the new Dr.Web Server.

21.On the new Dr.Web Server open the Anti-virus network → Everyone → Connection settings section and specify the new Dr.Web Server address in the Server field.

If you need to keep the previous IP address for the new Dr.Web Server (see step 1), stop the previous Dr.Web Server and assign its IP address to the new Dr.Web Server. Restart the new Dr.Web Server for the changed network settings to take effect.

1.Log in to the web interface of the previous Dr.Web Server and select a station or a group of stations you want to reconnect.

2.Open the Connection settings section and specify the new Dr.Web Server address for the selected objects. Make sure that all stations are disconnected from the previous Dr.Web Server and connected to the new Dr.Web Server. For more information, see Connecting Dr.Web Agent to Another Dr.Web Server.