Moving Dr.Web Server to Another Computer (Windows 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 Windows to another computer running Windows

1.Install a new Dr.Web Server (empty configuration, with a new database) of the same major version on the target computer (detailed instructions are given in the Installation Manual, section Installing Dr.Web Server for Windows 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 using Windows OS service management tools, Dr.Web Security Control Center, or the Start → All programs → Dr.Web Server → Stop menu.

7.Verify the integrity of the database of 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.

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

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

10.Replace the contents of the %programfiles%\DrWeb Server\etc and %programfiles%\DrWeb Server\var\extensions folders on the new Dr.Web Server with the contents of the same folders on the old Dr.Web Server.

11.Replace the drwcsd-certificate.pem certificate file in the %programfiles%\DrWeb Server\webmin\install\windows folder on the new Dr.Web Server with the same file from the old Dr.Web Server.

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

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

15.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 %programfiles%\DrWeb Server\var\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.

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

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/

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 using Windows OS service management tools, Dr.Web Security Control Center, or the Start → All programs → Dr.Web Server → Stop menu.

6.Replace the following files on the new Dr.Web Server with their equivalents from the old Dr.Web Server:

•drwcsd-certificate.pem certificate file in the %programfiles%\DrWeb Server\webmin\install\windows folder on the new Dr.Web Server with the corresponding file from the /opt/drwcs/webmin/install/windows folder on the old Dr.Web Server;

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

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

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

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

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:

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

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

12.Start the new Dr.Web Server using Windows OS service management tools or the Start → All programs → Dr.Web Server → Start menu.

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

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