Who is this article for?

IT Administrators moving the Internal Audit (and Retain) database to a different server.

IIS Manager, Services, and App Manager access is required.

Ideagen no longer provides guidance on use or configuration of the Retain applications. Please contact support at Retain International for further detail.

This article describes the reconfiguration required in the application when its database is moved from one SQL Server to another.

Where a change to Retain impacts Internal Audit this is noted in the article. Internal Audit and Retain must be treated as a 'matched pair' of databases, and should both be online or offline at the same time. 

1. Assumptions

You may need to move the application's database from one SQL Server to another.  This article describes actions required within the application environment, it does not cover use of SQL Server.

It is assumed that your starting point is:

• A running Internal Audit system (with or without Retain).
• That you have a working knowledge of App Manager.
• You have a configured App Manager instance.
• You have admin rights for your application server.

Users with checked out audits or reserved files will not be affected by this change, because the client application is unaware of the database server, it connects only to the application server.

2. Migrating the database

The process can be summarised as follows:

1. Stop the application services.
2. Backup and move the database(s) to the new server.
3. Restore the database and grant the relevant database user access.
4. Update the application configuration.
5. Start the application services.
6. Test access.

Each step is covered in more detail in its own subsection below.

2.1. Stopping application services

1. Stop the Pentana Robot service.
2. Stop the Ideagen Internal Audit (Aura) application pools.

2.2. Backing up and migrating the database

Once the services are stopped, the database for Internal Audit can be backed up.

Once the backup is completed, consider taking the database offline to ensure data is not added inadvertently.

2.3. Restoring database and granting access

After copying the backup to the new server and restoring, it is necessary to create/grant access to the SQL Server login required by the application. 

2.4. Updating application configuration

1. Open App Manager.
2. Connect to the correct application Instance.
3. Go to the Config tab.

This brings up a view into each of the Internal Audit configuration files. 

1. Click the Service tab.
2. Scroll down to the <Pentana.Tng.Data> section.  Update the Data Source for the new server/instance.
3. Scroll down to the <connectionStrings> section (note:  If Forms authentication is not used then there might not be a <connectionStrings> section in this file).
4. Update the Data Source for the new server/instance.
5. When done, click the Save icon.
6. Click on the FBA tab (if present).
7. Scroll down to the <connectionStrings>  section.  Update the Data Source for the new server/instance.
8. Click Save.
9. Click on the Web UI tab (if present).
10. If Forms-based authentication is used then there will be a <connectionStrings> section, if present (if FBA is not used then there will be no connection string).
11. Update the Data Source for the new server/instance.
12. Click Save.
13. If Retain is used, click on the Server Robot tab.
14. Locate the add key="RetainProviderString" line, and update the Data Source for the new server/instance.
15. Click Save.

2.5. Starting application services

1. Start the Ideagen Internal Audit (Aura) application pools.
2. Start the Pentana Robot service.

2.6. Testing access

After the services are started, ensure that a user is able to access the Internal Audit client.

3. Changing database user

This section is applicable ONLY if you are also wanting to change the type of authentication used for the database, or change Windows accounts used by the app pools and services where Windows authentication is used.

If you are wanting to change the connection so that a SQL account is used instead of Windows authentication (or vice versa), the connection strings shown above must be changed.

We supply Windows authentication connection strings as standard, but these can be changed to SQL authentication strings in the following format:

Internal Audit:  Password=password;Persist Security Info=True;User ID=username;Initial Catalog=databasename;Data Source=servername

If you use Windows authentication and want to change the Windows users that are used for the app pool identities and the Robot service, then assuming that these users already exist and have been configured in SQL Server:

1. Open IIS Manager.
2. Update the Identity for each of the Internal Audit application pools with the new user details.
3. Open Services.
4. Update the Log On As property of the Robot service with the new user details.
5. Open App Manager.
6. Go to the Tasks tab.
7. Click Manage System Identities.
8. Update the Identity values so that the correct Windows accounts are named.
9. Click Apply.