How to move a database from one Remote SQL Server to another in a Distributed Environment

  • N°Id de l'article : 22468
  • Note :
  • 2 clients ont donné une note de 3.5 sur 6 à cet article
  • Mis à jour : 24 août 2015

In a distributed install environment, it may be necessary to move the database between remote database servers. This article details the steps necessary to perform this task.

  • If the existing installation resides on one server (i.e. not distributed) then following the migration instructions in article 28276.
  • If moving the database to a different drive on the same computer see article 114108.

Applies to the following Sophos product(s) and version(s)
Enterprise Console 5.3.1
Enterprise Console 5.3.0
Enterprise Console 5.2.2
Enterprise Console 5.2.1 R2
Enterprise Console 5.2.0
Enterprise Console 5.1.0
Enterprise Console 5.0.0
Enterprise Console 4.7.0
Enterprise Console 4.5.0

What To Do

  1. Backup the existing database(s) using backupdb.bat by following the instructions in article 110380 (As of SEC 5.2, this includes SOPHOSXX, SophosSecurity, SophosEncXX, and SophosPatchXX)
  2. On the new database host, create the new database by running the Sophos Enterprise Console installer and selecting only the database role for installation.
  3. Copy the database backup file from Step 1 to the new database host and restore it to the instance the database was installed to on Step 2 by using restoredb.bat as described in article 110380
  4. Stop the following services (If they exist):
    • Sophos Management Service
    • Sophos Management Host Service
    • Sophos Encryption Business Logic Service
    • Sophos Patch Server Communicator
  5. Warning: See warning about registry edits here,
  6. For all version of SEC, modify the following value:
    • 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\EE\Management Tools\DatabaseConnectionMS
    • 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Maangement Tools\DatabaseConnectionMS
    • This value is normally in the format: Provider=SQLOLEDB; Integrated Security=SSPI; Initial Catalog=SOPHOSXX; Data Source=[DatabaseServer\DatabaseInstanceName]
      • Edit the [DatabaseServer\DatabaseInstanceName] to point to the new server\instance.
      • If the username or password used to connect to the new SQL server is different than the previous one, you will also need to update the HKLM\Software\Sophos\EE\Management Tools\Database User registry keys with the new information. See article 13094 for instructions on how to obfuscate the username and password.
  7. For SEC 5.0 and above, you also need to modify the following value data for the new location of the patch database (This is the same for 64-bit and 32-bit systems) with the new DatabaseServer\DatabaseInstanceName
    • HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Patch\SophosPatchConnectionString
  8. For SEC 5.1 and above, the location must also be changed in the file
    • 64-bit: C:\Program Files (x86)\Sophos\Encryption\BLService.exe.config
    • 32-bit: C:\Program Files\Sophos\Encryption\BLService.exe.config
      • Search for "connectionString" and edit the value starting with "Data Source=" to use the new DatabaseServer\DatabaseInstanceName
  9. For SEC 5.2 and above, the below locations must also be changed for the Sophos Security database with the new DatabaseServer\DatabaseInstanceName (If 64-bit, both locations must be changed)
    • HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\ServerSecurity\DatabaseConnection
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\ServerSecurity\DatabaseConnection
  10. Start the following services on the Management Console server.
    • Sophos Management service (If the service fails to re-start see article 111898 for common causes.)
    • Sophos Management Host Service
    • Sophos Encryption Business Logic Service
    • Sophos Patch Server Communicator
  11. Open the Enterprise Console and confirm that the migration was a success.

Si vous avez besoin de plus d'informations ou d'instructions, veuillez contacter le support technique.

Évaluez cet article

Très mauvais Excellent