Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Manually move the ScanMail for Exchange (SMEX) database from one SQL Server to another

    • Updated:
    • 24 Oct 2018
    • Product/Version:
    • ScanMail for Exchange 12.0
    • ScanMail for Exchange 12.5
    • Platform:
    • N/A N/A
Summary

If a ScanMail database was installed on a remote SQL Server, it is possible to move it to another remote SQL Server. Consider these two scenarios:

  • Scenario 1: Upgraded from SMEX 11.0 (three separate databases)
  • Scenario 2: Fresh installed SMEX 12.x. (single database)

The database created by the fresh install will have one database: ScanMail_GUID.

single

The database created by the upgrade install from SMEX11.0 SP1 will have three databases: Conf_Servername_GUID, Log_Servername_GUID, and Report_Servername_GUID.

multiple

Details
Public

Do the following procedures to move ScanMail database(s) from one SQL Server to another SQL Server. The first scenario above will be used to demonstrate this task.

  1. Stop the following services:
    • ScanMail for Microsoft Exchange Remote Configuration Server
    • ScanMail for Microsoft Exchange Master Service
    • ScanMail for Microsoft Exchange System Watcher
  2. Move the ScanMail databases by using SQL Server Management Studio:
    1. Detach the SMEX database from the source SQL Server:

      detach

    2. Copy the SMEX database files from source SQL Server to target SQL Server. The folder is usually C:\Program Files\Microsoft SQL Server\MSSQL**.***\MSSQL\DATA. Make sure to copy the Primary Data file as well as the Transaction Log files:

      verify

    3. Attach the SMEX database to the target SQL Server:

      attach

    If you don’t install SQL Server Management Studio, use Transact-SQL to finish this task. Check the following Microsoft articles for detailed information on how to move a database using Detach and Attach in MSDN:

    Detach a Database
    Attach a Database
    Move a Database Using Detach and Attach (Transact-SQL)

  3. Go to the ScanMail erver and modify the SMEX database profiles located: \%SCANMAIL_INSTALL_PATH%\config
  4. Make sure to backup/modify these files correctly to reflect the new remote SQL:

    dbcfg_DatabaseInstance.txt
    dbcfg_IsSeperateSQLServer.txt
    dbcfg_ConfDBName
    dbcfg_LogDBName
    dbcfg_ReportDBName
    dbcfg_ServerName.txt
    dbcfg_SQLUserId.txt
    dbcfg_SQLPassword.txt
    dbcfg_SecurityString.txt

    Take note of the following:

    • The dbcfg_DatabaseInstance.txt should be the remote SQL instance where you attached the ScanMail database(s) in the Step 2.
    • The value in dbcfg_IsSeperateSQLServer.txt should be 1.
    • “Dbcfg_ConfDBName”, "dbcfg_LogDBName" and "dbcfg_ReportDBName" should be the ScanMail database name, if you choose not to change the GUID (not necessary to change it).
    • Dbcfg_ServerName.txt should match the ScanMail server name, if you prefer not to change the GUID (not necessary to change it).
    • If you select SQL Server authentication to connect to SQL Server during ScanMail installation, make sure that the SQL account and password are stored in "dbcfg_SQLUserId.txt" and dbcfg_SQLPassword.txt" separately. To generate the encrypted password for "dbcfg_SQLPassword.txt":
      1. Go to the \%SCANMAIL_INSTALL_PATH%\SMEX folder via the Command prompt.
      2. Type toolChangeRemoteDBPWD.exe –p %SCANMAIL_INSTALL_PATH%\config\ -c Current SQL Password
      3. You may type toolChangeRemoteDBPWD.exe /? for usage info.
      4. Verify that the new dbcfg_SQLPassword.txt file generated the encrypted password.

        toolChangeRemoteDBPWD

      If you select Windows authentication to connect to SQL Server during ScanMail installation, make sure the ScanMail service account has DBO privileges on ScanMail’s databases in the new SQL Servers.
    • Make sure dbcfg_SecurityString.txt uses the following string: Integrated Security=SSPI;Persist Security Info=FALSE;
  5. Start the following services:
    • ScanMail for Microsoft Exchange Remote Configuration Server
    • ScanMail for Microsoft Exchange Master Service
    • ScanMail for Microsoft Exchange System Watcher
  6. Once the procedure above is implemented, log on to the ScanMail console and verify all the configuration. Check as well for any error on the console.
Premium
Internal
Rating:
Category:
Configure
Solution Id:
1120943
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.