How to migrate NoSpamProxy version 12.x or 13.x

NOTE: This information only refers to versions 12.x and 13.x. Instructions for migrating versions 14.x can be found under How to migrate NoSpamProxy version 14.x.

To migrate version 12.x or 13.x to another server, proceed as follows

1. Export and delete any existing DKIM keys on the source server (only available with Protection module).
2. Copy your own stored logo image files to the target server.
3. From the directory C:\ProgramData\Net at Work Mail Gateway\Configuration copy the files Intranet Role.config and license.xml to the target server.
4. On the target server, create the directory C:\ProgramData\Net at Work Mail Gateway\Configuration and copy Intranet Role.config and license.xml into it.
5. Adjust the file Intranet Role.config.
6. Install the SQL server.
7. Stop the Intranet Role.
8. Perform one of the following two steps:
   • Back up the database files and restore them to the target SQL server.

   • Move the database files to the new directory and mount them on the SQL server.

9. Execute the NoSpamProxy setup on the target server.
10. Connect the Intranet Role to the Gateway Role.
11. Then check all previously set passwords and certificates and reassign the connectors.
12. Import the DKIM keys exported in step 1 on the target server.

The steps in detail

1. On the source server, in the NoSpamProxy Management Console, go to People and Identities > DKIM Keys.
2. Export existing DKIM keys there and delete them afterwards.
3. Copy your own stored logo image files to the new server. The deposited logo image file can be found under the name Logo.png on the intranet roll in the directory C:\ProgramData\Net at Work Mail Gateway\Intranet\Theme\. Create this directory on the new server in exactly the same way and place the file Logo.png there.
4. Stop all NoSpamProxy services on the source server and then stop the SQL database instance. You will find these under the Windows services usually under the name SQL Server (NOSPAMPROXY).
5. Create the directory C:\ProgramData\Net at Work Mail Gateway\Configuration on the target server.
6. Copy the files Intranet Role.config and license.xml from the directory C:\ProgramData\Net at Work Mail Gateway\Configuration on the source server to the directory you just created on the target server.
   

   NOTE: Copy only the mentioned files from the directories, otherwise there might be problems during the installation.

7. Adjust the configuration file Intranet Role.config as follows:

   Search for the following entry
   <connectionStrings configProtectionProvider="DataProtectionConfigurationProvider">
   <EncryptedData>
   <CipherData>
   <CipherValue>AQAAANCMnd...==</CipherValue>
   </CipherData>
   </EncryptedData>
   </connectionStrings>
   Change it so that it looks like this at the end:
   <connectionStrings>
   </connectionStrings>
   Search the whole file for
   encryptedPassword=
   and change the occurrences that look something like
   encryptedPassword="AQAAANCM...W9b17"
   to
   encryptedPassword=""
   Proceed analogously for all occurrences of
   tlsCertificatePin="AQAAANCM...W9b17"
   and
   tlsCertificateThumbprint="AQAAANCM...W9b17"
   and
   password="AQAAANCM...W9b17"
   .
   If De-Mail was configured, please search for
   certificatePin="AQKLM....D87W"<mtlingo type="" prevChar="" nextChar="
   " /><mtlingo type="" prevChar="" nextChar="" />and change the entry to
   certifcatePin=""<mtlingo type="" prevChar="" nextChar="
   " /><mtlingo type="" prevChar="" nextChar="" />.
   Finally, search for any DKIM keys that may be existent. To do this, search for the following entry:
   <dkimKeys>
   <key domain="example.com" selector="key1" privateKey="AAAAcVARJk3pG0SsnJkmR2FK..." />
   </dkimKeys>
   Change the entry so that it looks like this:
   <dkimKeys>
   
   </dkimKeys>

8. Save the file.
9. Install the Microsoft SQL Server in the version you require from SQL Server 2012.
10. Install the administration tools including the SQL Management Studio.
11. Stop the Intranet Role via the NoSpamProxy console or via Windows Services to exclude access to the database and entries in the Intranet Role database.
12. Perform one of the following two steps:
    • Back up the database files and restore them to the target SQL server:
      1. Create a backup of the SQL database NoSpamProxyAddressSynchronization on the source server using SQL Management Studio. To do this, right-click the database NoSpamProxyAddressSynchronization.
      2. Select Task / Backup. A dialogue opens.
      3. Leave the settings shown unchanged and only add a "Disk" and the corresponding path of the backup file in the lower section.
      4. Start the backup.
      5. Copy the resulting backup file to the destination server.
      6. Perform a recovery. To do this, right-click on Databases in the SQL Management Studio of the target server and select Restore Database. A dialogue opens.
      7. Select Device and add a new File in the dialogue that appears. This file is the backup file that was just copied.
      8. Start the recovery.
    • Move the database files to the new directory and mount them on the SQL server. The SQL database files are usually located at C:\Program Files (x86)\Microsoft SQL Server\MSSQL.XXXX\MSSQL\Data or C:\Program Files\Microsoft SQL Server\MSSQL.XXXX\MSSQL\Data. You can recognise it by the fact that the name begins with NoSpamProxy.
      1. Copy the files NoSpamProxyAddressSynchronization.mdf and NoSpamProxyAddressSynchronization.ldf to the target server.
      2. Move the database files to the desired directory. This does not necessarily have to be the default directory of the SQL server.
      3. Open the SQL Management Studio.
      4. Log on to the server, right click on databases and select Attach/Attach.
      5. In the following dialog, add the first database file from the desired directory. The corresponding log file is automatically recognized.
      6. Run the NoSpamProxy setup.
      7. Start the NoSpamProxy setup in the same version that is installed on the source server.
         

         NOTE: Make sure you select the Advanced Installation.

      8. When asked which SQL server is used, select that an SQL server is already installed and set the corresponding connection parameters. The setup then recognises all other configuration files and adjusts them.
      9. Connect the Intranet Role to the Gateway Role.

      10. As soon as the setup has been completed successfully, reconnect the Intranet Role to the Gateway Role and, if necessary, to the Web Portal under Gateway Components. To do this, delete the existing connections, then restart the Intranet Role and reconnect it.

      11. Then check all previously set passwords and certificates and reassign the connectors.
      12. In the interface, set the sensitive data protection password again to restore access.
          

          NOTE: With the changeover, the device-dependent encrypted passwords were deleted or can no longer be decrypted. This applies in particular to the sensitive data protection password, which is used to protect the private S/MIME and PGP keys.

      13. Check all passwords and SSL certificates configured in the receiving connector that were previously stored and set them again.
      14. Re-assign the send and receive connectors to the corresponding Gateway Roles.
      15. Import the DKIM keys exported in step 1 to the target server.

Migrating the NoSpamProxy Web Portal

If the NoSpamProxy Web Portal is in use and is to be migrated to another server, there are two different ways to do this, which are described below:

Migration by installing another Web Portal

1. Install the NoSpamProxy Web Portal on the new server including a new database and set it up according to the installation instructions.
2. Integrate the new Web Portal in parallel to the existing Web Portal in the NoSpamProxy Management Console at Configuration > NoSpamProxy Components > Web Portal.
3. Change the accessibility of the Web Portal from outside so that the default link points to the new Web pPrtal and it can only be accessed from outside/from the Gateway Role. As a result, all files are exchanged between the Web Portals via the service NoSpamProxy - FileSynchronizationService.
4. Switch off the old Web Portal after the set storage time has expired at Configuration > NoSpamProxy Components > Web Portal > Web Portal Settings > Edit" on the tab Large Files.

NOTE: If you switch off the system with the old Web Portal, also remove it at Configuration > NoSpamProxy Components > Web Portal. The Intranet Role will otherwise continue to try to communicate with the Web Portal, which can fill up the database.

Migration by moving the data

1. Install the SQL server in the version you want from SQL Server 2012.
2. Install the administration tools including the SQL Management Studio.
3. Stop the service NoSpamProxy - FileSynchronizationService via the computer administration of Windows (Windows Services) and the Internet Information Service (IIS) via the command line command CMD> iisreset /stop, in order to exclude access to the database and entries in the database of the Web Portal
4. Perform one of the following two steps:
   • Back up the database files and restore them to the target SQL server:
     1. Create a backup of the SQL database enQsigPortal on the source server using the SQL Management Studio. To do this, click on the database enQsigPortal with the right mouse button.
     2. Select Task / Backup. A dialogue opens.
     3. Leave the settings shown unchanged and only add a "Disk" and the corresponding path of the backup file in the lower section.
     4. Start the backup.
     5. Copy the resulting backup file to the destination server.
     6. Perform a recovery. To do this, right-click on Databases in the SQL Management Studio of the target server and select Restore Database. A dialogue opens.

     7. Select Device and add a new "File" in the appearing dialogue. This file is the backup file that was just copied.

     8. Start the recovery.
   • Move the database files to the new directory and mount them on the SQL server. The SQL database files are usually located in the path "C:\Program Files (x86)\Microsoft SQL Server\MSSQL.XXXX\MSSQL\Data" or "C:\Program Files\Microsoft SQL Server\MSSQL.XXXX\MSSQL\Data". You will recognise it by the name "enQsigPortal".
     1. Copy the files enQsigPortal.mdf and enQsigPortal.ldf to the target server.
     2. Move the database files to the desired directory. This does not necessarily have to be the default directory of the SQL server.
     3. Open the SQL Management Studio.
     4. Log on to the server, right click on databases and select Attach/Attach.
     5. In the following dialog, add the first database file from the desired directory. The corresponding log file is automatically recognized.
     6. Copy the storage folder of the files from the source server to the destination server. You can view the location of the files on the source server in the NoSpamProxy Management Console at Configuration > NoSpamProxy Components > Web Portal in the integrated Web Portal. Please note the folder structure and place the files on the target server where they are to be stored in the future.

     7. Install the Web Portal on the target server and set up access in IIS according to your environment.
        

        NOTE: Make sure that you select the already existing instance of SQL Server and do not install a new instance.

     8. Remove the old Web Portal from the Intranet Role and add the new Web Portal at Configuration > NoSpamProxy Components > Web Portal.
        

        NOTE: After inserting, make sure that you adjust the storage location accordingly.

     9. Check that access to the new Web Portal works and that your users can download the files.
     10. Check in the NoSpamProxy Management Console under Monitoring > Emails on holdwhether emails have accumulated there in the meantime that are still waiting to be processed by the content filter. If yes, start the processing again.

Notes