Moving Dr.Web Server to Another Computer (Unix-like OS)

The procedure for moving Dr.Web Server described below requires that the same major version of Dr.Web Server as on the original computer will be installed on the computer it is moved to.

When moving Dr.Web Server to another computer, pay attention to the settings of the transport protocols and, if necessary, change them in 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, in the following subsections:

•Starting and Stopping Dr.Web Server for Windows OS,

•Starting and Stopping Dr.Web Server for Unix-like OSs.

The procedures for moving Dr.Web Server differ depending on the OS of the original computer:

After completing either of the procedures, check that the new Dr.Web Server is working properly and ensure that stations are connected to it.

To move Dr.Web Server from a computer running a Unix-like OS to another computer running a Unix-like OS

The instructions contain examples of commands for Linux OS. Note the difference in the paths in FreeBSD OS:

•/etc/init.d/ → /usr/local/etc/rc.d/

•/var/opt/drwcs/ → /var/drwcs/

•/opt/drwcs/ → /usr/local/drwcs/

1.Install a new Dr.Web Server (empty configuration, with a new database) 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 keep the old IP address of your Dr.Web Server, assign a temporary IP address to the new Dr.Web Server so that the stations can communicate with the old Dr.Web Server during the move.

2.In the web interface of the new Dr.Web Server, navigate to the Administration → License Manager section, add your valid agent.key license key, and propagate it to the Everyone group.

3.Open the Repository state section and make sure that the repository is updated correctly.
If there are any error messages in the product list table in the State column, please contact technical support. Attach the drwscd.log file to the request. Do not take any further action until you receive feedback on the request.

4.Open the 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 command:

6.To keep your user hooks, replace the contents of the /var/opt/drwcs/extensions/ folder on the new Dr.Web Server with the contents of the same folder on the old Dr.Web Server.

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

8.Replace the drwcsd.conf configuration file, drwcsd.pri private key file, and a copy of the drwcsd-certificate.pem certificate in the var/opt/drwcs/etc/ folder on the new Dr.Web Server with the corresponding files from the old Dr.Web Server.

9.Stop the old Dr.Web Server via the web interface or via the console using the command:

10.Verify the integrity of the database on the old Dr.Web Server using the command:

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

11.Export the database of the old Dr.Web Server to file using the command drwcsd modexecdb database-export. The full command line for database export looks as follows:

12.If you use the embedded database, replace the /var/opt/drwcs/database.sqlite database file on the new Dr.Web Server with the same file from the old Dr.Web Server.

13.Start the old Dr.Web Server so that it could keep servicing its clients via the console using the command:

14.Make the drwcs user the owner of the /var/opt/drwcs database folder and the /var/opt/drwcs/etc/drwcsd.pri, /var/opt/drwcs/etc/drwcsd.conf, and /var/opt/drwcs/etc/drwcsd-certificate.pem files on the new Dr.Web Server:

# chown -R drwcs:drwcs /var/opt/drwcs

# chown drwcs:drwcs /var/opt/drwcs/etc/drwcsd*

15.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

17.Log in to the web interface of the new Dr.Web Server using the same credentials as for the old Dr.Web Server.

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

icon and select the Action tab in the task editing window. Make sure that the path to the folder on the old 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 a folder on the new Dr.Web Server. Do the same for the Backup repository task, as well as for any other tasks with the Back up critical Dr.Web Server data and Back up repository actions (if such tasks are present).

If there are any tasks with the Run program action in the schedule, either edit them according to the software configuration of the new computer or remove them from the schedule.

Dr.Web Server will be unavailable for the duration of the move. To avoid an interruption in servicing the Dr.Web Server clients, it is recommended that you follow method 1.

The instructions contain examples of commands for Linux OS. Note the difference in the paths in FreeBSD OS:

/etc/init.d/ → /usr/local/etc/rc.d/

1.Stop the old Dr.Web Server via the web interface or via the console using the command:

2.Export the database of the old Dr.Web Server to file using the command drwcsd modexecdb database-export. The full command line for database export looks as follows:

3.Uninstall the old Dr.Web Server (see the Installation Manual, Removing Dr.Web Server for Unix-like OS). A backup copy of Dr.Web Server critical data will be created during the uninstallation (in the /var/tmp/drwcs/ folder by default).

4.Move the contents of the backup copy folder to the computer where the new Dr.Web Server will be installed.

5.Start the installation of Dr.Web Server of the same major version on the new computer (as described in the Installation Manual, Installing Dr.Web Server for Unix-like OS). When prompted to specify a backup source, enter the path to the backup copy folder. Wait until the installation is completed.

7.Log in to the web interface of the new Dr.Web Server using the same credentials as for the old Dr.Web Server.

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

If there are any tasks with the Run program action in the schedule, either edit them according to the software configuration of the new computer or remove them from the schedule.

To move Dr.Web Server from a computer running Windows OS to a computer running a Unix-like OS

The instructions contain examples of commands for Linux OS. Note the difference in the paths in FreeBSD OS:

•/etc/init.d/ → /usr/local/etc/rc.d/

•/var/opt/drwcs/ → /var/drwcs/

•/opt/drwcs/ → /usr/local/drwcs/

1.Install a new Dr.Web Server (empty configuration, with a new database) of the same major version 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 keep the old IP address of your Dr.Web Server, assign a temporary IP address to the new Dr.Web Server so that the stations can communicate with the old Dr.Web Server during the move.

2.In the web interface of the new Dr.Web Server, navigate to the Administration → License Manager section, add your valid agent.key license key, and propagate it to the Everyone group.

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

•drwcsd.conf configuration file, drwcsd.pri private key file, and a copy of the drwcsd-certificate.pem certificate:

# rm /var/opt/drwcs/etc/drwcsd.conf /var/opt/drwcs/etc/drwcsd.pri /var/opt/drwcs/etc/drwcsd-certificate.pem

7.Stop the old Dr.Web Server via the web interface or the Start → All programs → Dr.Web Server → Stop menu.

8.Verify the integrity of the database on the old Dr.Web Server using the command drwcsd modexecdb database-verify. The full command line for database verification looks as follows:

"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -verbosity=trace -log="C:\Program Files\DrWeb Server\var\verifydb.log" modexecdb database-verify

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

9.Export the database of the old Dr.Web Server to file using the command drwcsd modexecdb database-export. The full command line for database export looks as follows:

"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -verbosity=trace -log="C:\Program Files\DrWeb Server\var\exportdb.log" modexecdb database-export <full_file_name>

•the %programfiles%\DrWeb Server\var\extensions folder contents (user hooks) of the old Dr.Web Server to the /var/opt/drwcs/extensions/ folder of the new Dr.Web Server;

•the drwcsd.conf configuration file, drwcsd.pri private key, and drwcsd-certificate.pem certificate file from the %programfiles%\DrWeb Server\etc folder of the old Dr.Web to the /var/opt/drwcs/etc/ folder of the new Dr.Web Server.

Check if there are any Windows paths in the drwcsd.conf file. If so, fix them manually before moving the file.

11.If you use the embedded database, replace the database.sqlite database file in the /var/opt/drwcs/ folder on the new Dr.Web Server with the same file from the %programfiles%\DrWeb Server\var folder on the old Dr.Web Server.

12.Start the old Dr.Web Server so that it could keep servicing its clients using Windows OS service management tools or the Start → All programs → Dr.Web Server → Start menu.

13.Make the drwcs user the owner of the /var/opt/drwcs database folder and the /var/opt/drwcs/etc/drwcsd.pri, /var/opt/drwcs/etc/drwcsd.conf, and /var/opt/drwcs/etc/drwcsd-certificate.pem files on the new Dr.Web Server:

# chown -R drwcs:drwcs /var/opt/drwcs

# chown drwcs:drwcs /var/opt/drwcs/etc/drwcsd*

14.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

16.Log in to the web interface of the new Dr.Web Server using the same credentials as for the old Dr.Web Server.

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

If there are any tasks with the Run program action in the schedule, either edit them according to the software configuration of the new computer or remove them from the schedule.

1.Log in to the web interface of the new Dr.Web Server. Make sure that all Dr.Web Agents are displayed correctly in the anti-virus network list.

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

To allow those Dr.Web Agents to migrate for which the new Dr.Web Server address is set via the Control Center instead of the Dr.Web Agent settings on the station, keep both Dr.Web Servers operating until the procedure is completed.

It is recommended that you use the Dr.Web Server name in the FQDN format.

a)Specify the address of the new Dr.Web Server according to the procedure described in the Connecting Dr.Web Agent to Another Dr.Web Server section for all Dr.Web Agents serviced by the old Dr.Web Server.

The new Dr.Web Server IP address must be specified on both Dr.Web Servers in the Dr.Web Agent settings section for those Dr.Web Agents for which the new Dr.Web Server address was set via the Control Center instead of in the Dr.Web Agent settings on the station.

c)Restart the new Dr.Web Server for the changed network settings to take effect.