Restoring the Database of Dr.Web Enterprise Security Suite

During the operation, Dr.Web Server regularly stores backup copies of important information: license keys, database contents, encryption private key, Server configuration and Control Center configuration.

The backup files are stored in the following folders:

•for Windows OS: \var\Backup (relatively to the Server installation folder)

•for Linux OS and Solaris OS: /var/opt/drwcs/backup

•for FreeBSD: /var/drwcs/backup

To perform the back up, a daily task is included into the Server schedule. If such task is missing in the schedule, it is recommended to create it.

All files in the backup except the database contents, are ready to use. The database backup copy is stored in the .gz format compatible with gzip and other archivers. The database contents can be imported from the backup copy to another database of the Server using the importdb command, thus restore the data.

To restore the database you can also use a backup created manually by administrator via the Control Center in the Administration → Database management → Export (for the Export entire database mode only). But, at this, a backup copy is saved in the xml format, and for the import you must use the xmlimportdb command.

Restoring the DB for Different Versions of Dr.Web Server

You can restore the DB from the backup copy only if it had been created via the Server of the same major version as the version of the Server which you use for restoring.

For example:

•You can restore DB from the backup created via the Server of 10 version using the Server of 10 version only.

•You cannot restore DB from the backup created via the Server of 5 or 6 version using the Server of 10 version.

If DB has been corrupted for some reasons during Server upgrade from previous versions to 10 version, do the following:

1.Remove the Server software of the 10 version. Backup copies of files, used by the Server, will be stored automatically.

2.Install the Server of version, which had been installed before upgrading and had been used to create backup copy.

According to the general upgrade procedure, you should use all stored Server files except the DB file.

Create a new DB during the Server installation.

3.Restore DB from the backup according to general rules (see procedures below).

4.Disable the Agent, the Server and the Network Installer protocols in the Server settings. To do this, select the Administration item in the main menu and click Dr.Web Server configuration in the control menu, go to the Modules tab and clear corresponding flags.

5.Upgrade the Server to the 10 version according to general rules (see Administrator Manual, p. Updating Dr.Web Enterprise Security Suite Software and Its Components).

6.Enable the Agent, the Server and the Network Installer protocols, disabled at the step 4.

For Windows OS

Procedure of how to start and stop Dr.Web Server is described in the Administrator Manual, p. Start and Stop Dr.Web Server.

To restore DB from backup

1.Stop Dr.Web Server if it is running.

2.Import the content of the database from the correspondent backup file. The command line will look as follows:

"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -home="C:\Program Files\DrWeb Server" -var-root="C:\Program Files\DrWeb Server\var" -verbosity=all importdb "<path_to_the_backup_file>\database.gz"

The command must be entered in a single line. It is presumed that Dr.Web Server is installed to the C:\Program Files\DrWeb Server folder.

3.Start Dr.Web Server.

To restore DB from backup in case of changing Dr.Web Server version or corruption of the previous DB version

1.Stop Dr.Web Server if it is running.

2.Remove the current DB. To do this:

2.1. For the embedded DB:

a)Remove database.sqlite file.

b)Initialize a new database. In Windows the command line will look as follows:

"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -home="C:\Program Files\DrWeb Server" -var-root="C:\Program Files\DrWeb Server\var" -verbosity=all initdb D:\Keys\agent.key - - <password>

The command must be entered in a single line (see also drwcsd command format with the initdb switch at the Appendix H4.3). It is presumed that Dr.Web Server is installed to the C:\Program Files\DrWeb Server folder and agent.key license key is located in D:\Keys.

c)Once this command is executed, a new database.sqlite will be generated in the var subfolder of Dr.Web Server installation folder.

2.2. For the external DB: clean up the DB via the clean.sql script, located in the etc subfolder of the Server installation folder.

3.Import the content of the database from the correspondent backup file. The command line will look as follows:

"C:\Program Files\DrWeb Server\bin\drwcsd.exe" -home="C:\Program Files\DrWeb Server" -var-root="C:\Program Files\DrWeb Server\var" -verbosity=all importdb "<path_to_the_backup_file>\database.gz"

The command must be entered in a single line. It is presumed that Server is installed to the C:\Program Files\DrWeb Server folder.

4.Start Dr.Web Server.

For UNIX OS

1.Stop Dr.Web Server.

•for Linux OS and Solaris OS:

/etc/init.d/drwcsd stop

•for FreeBSD OS:

/usr/local/etc/rc.d/drwcsd.sh stop

2.Remove database.sqlite from the following subfolder of Dr.Web Server installation folder:

•for Linux OS and Solaris OS: /var/opt/drwcs/

•for FreeBSD OS: /var/drwcs/

To clean an external DB, use the clean.sql script, located at:

•/var/opt/drwcs/etc for Linux OS and Solaris OS,

•/var/drwcs/etc for FreeBSD OS.

3.Initialize the Server database. The command will look as follows:

•for Linux OS and Solaris OS:

/etc/init.d/drwcsd initdb

•for FreeBSD OS:

/usr/local/etc/rc.d/drwcsd.sh initdb

4.Once this command is executed, a new database.sqlite database will be generated in the var subfolder of Dr.Web Server installation folder.

5.Import the content of the database from the correspondent backup file. The command line will look as follows:

•for Linux OS and Solaris OS:

/etc/init.d/drwcsd importdb "<path_to_the_backup_file>/database.gz"

•for FreeBSD OS:

/usr/local/etc/rc.d/drwcsd.sh importdb "<path_to_the_backup_file>/database.gz"

6.Start Dr.Web Server:

•for Linux OS and Solaris OS:

/etc/init.d/drwcsd start

•for FreeBSD OS:

/usr/local/etc/rc.d/drwcsd.sh start

If you want to run the script with parameters (e.g., set Server installation directory and etc.), you must make all changes in the start script:

•for FreeBSD OS: /usr/local/etc/rc.d/drwcsd.sh

•for Linux and Solaris OS: /etc/init.d/drwcsd

If you need to change the log level of detail of the Server, use the local.conf file:

•for Linux and Solaris OS: /var/opt/drwcs/etc/local.conf;

•for FreeBSD OS: /var/drwcs/etc/local.conf.

If some Agents were installed after the last backup had been made, they will not be connected to the Server after the database has been restored from the backup. You should remotely reset them to the newbie mode. In the Administrating → Dr.Web Server configuration on the General tab, set the Reset unauthorized to newbie flag and in the Newbies registration mode drop-down list, select Allow access automatically. Click Save and restart the Server.

After all stations will be successfully connected to the new Server, change these Server settings to the settings adopted according to the policy of your company.

As soon as the database is restored from the backup it is recommended to connect Dr.Web Security Control Center to the Server. On the Administration menu, select Dr.Web Server Task Scheduler and check that the Back up critical server data task is on the list. If this task is absent, add it to the list.