Migrating the Insolvency database to another server

Here are notes on migrating Insol 6 database to a new on premise server.

1. Do you have Creditors' Portal or Bankfeeds: see below for steps to be performed before any SQL Server changes are made.
2. Install SQL Server on the new database server. 
   
   

   Note

   Ensure SQL is configured for mixed mode authentication.
   
   
3. On the original server take a backup of the insolvency database.
   
   Ensure the old database is set to offline or is renamed.
   
   
4. Move the backup file to the new server
   
   
5. Restore the back up
   
   Restore the backup created in step 2. A restore script is available restore.sql.
   
   

   Notes

   1. Amend the database file paths as required.
      
      
   2. The mdf file logical name will be restored as ims_Data and the ldf logical file will be restored as ims_Log.
      
      
6. Reconfigure the SQL logins
   
   To ensure that the SQL login is correctly mapped see: Reconfigure the database login
7. Ensure that the TCP/IP protocol is enabled on the new server.
   
   
8. File system folders
   
   If the file system locations of job folders and documents has changed then a script may need to be run on the database and the application setting folder locations re-entered.
   
   
9. Insol Data Sync Service
   
   The insol data sync service manages DMS integration, banking integration and creditors portal. This service needs to be installed on a applicaiotn service and configured with encrypted details for the banking and portal API queue. This requires windows AD credentials.
   
   

   Note

   The Insol Data Sync service needs to be removed from the old production server.
   
   
10. SMTP Setup
    
    Test to ensure that the software may still send emails from the new server location.
    
    
11. Windows task scheduler
    
    Email alerts are sent from a scheduled tasks on an application server. There is a procedure to implement task scheduling on a new server.
    
    This requires windows AD credentials.
    
    
12. Once the new server is online, workstation connections will need to be updated. 
    See how to configure a database connection
    
    

Automating distribution of connections

If you users are not skilled dealing with entering a server and database name, you have option of shipping a text file called connect.txt to the application directory on each machine (%program files%\Insol6\Insolvency).  This file should contain a single line of text in the format servername;database name.  A sample connect.txt is attached.  This file will be used to automatically connect to the new server.

Do you have Creditors' Portal or Bankfeeds features?

Please contact Insol6 helpdesk and request a consultant assist in the migration.

The InsolDataSync windows service has a stored encrypted connection string to the current SQL Server and Database. If you are decommissioning the server that hosts InsolDataSync, then steps must be taken to ensure there are not 2 active copies of the service. If the SQL server or database names are changing, then the Svc will need to be reinstalled.

After the SQL database is restored, the security objects (roles/users/schemas) required by the InsolDataSync connection will need to be removed and recreated. Note, that although they have the same names the server instance of those objects will have different hidden Unique Identifiers.