Who is this article for?

IT Administrators responsible for managing system upgrades.

Services app and Server access are required.

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

It is occasionally necessary to roll back an upgraded system to its previous version.  If Retain is also in use, then the Retain database should be restored to the same point in time, and both systems should go back online together in order to stay in sync.

This article summarises the required steps.  It is assumed that this is being done immediately following an upgrade, and that no live data has been added.

1. Rolling back upgrade

1.1. Stop the services

First it is necessary to make sure that nobody is accessing the system and that no files are locked:

1. Stop the Ideagen Internal Audit (Aura) robot service.
2. Stop the application pools for Ideagen Internal Audit (Aura).

1.2. Purge the message queue

As the database is going to be restored, any pending MSMQ messages must be purged.

1.3. Restore the Database(s)

Restore the pre-upgrade backup of the PentanaAudit database.

1.4. Restore the application folders

During the upgrade process, the App Manager creates a backup for each of the service applications.  Each backup is in the form of a zip file, named Application_Backup_DateTime.zip.  The IIS service backups are in the root of the application instance path, and the Robot backup is at the path to the robot application, so:

In inetpub\wwwroot\[Instance Name]:

1. Unzip FBA_Backup_DateTime.zip, overwriting the content of \FBA.
2. Unzip Service_Backup_DateTime.zip, overwriting the content of \Service.
3. Unzip WebService_Backup_DateTime.zip, overwriting the content of \WebService.
4. Unzip WebUI_Backup_DateTime.zip, overwriting the content of \WebUI.

In \Program Files (x86)\Pentana\ServerRobot\[Instance Name]:

1. Unzip [InstanceName]_Backup_DateTime.zip, overwriting the content of \[Instance Name].

1.5. Restoring the SAML2 application

If you are using SAML2 for SSO in the main application AND you took a manual backup of inetpub\wwwroot\[Instance Name]\SamlMvc prior to the upgrade, then overwrite the SamlMvc folder with your backup.

If you do not have a manual backup of this folder, then you should overwrite \SamlMvc with the folder from the install set for the correct version, but keep the following:

• \saml.config
• \Certificates\*.*

1.6. Restore the client

If you are using ClickOnce AND you took a manual backup of the wwwroot\[Instance Name]\Client folder:

1. Overwrite the Client folder with your backup.
2. Any users who have updated their local ClickOnce installs from the server since the upgrade will need to uninstall the Internal Audit client and then reinstall.

If you are using ClickOnce and you did not take a manual backup of the wwwroot\[Instance Name]\Client folder:

1. Go to the folder wwwroot\[Instance Name]\Client.
2. It will contain at least two folders named Vision_x_x_x_x/
3. Locate the newest folder in the sequence.
4. Delete that folder.
5. Any users who have updated their local ClickOnce installs from the server since the upgrade will need to uninstall their Internal Audit client and then reinstall.

1.7. Restart

1. Start the application pools for Ideagen Internal Audit (Aura).
2. Start the Ideagen Internal Audit (Aura) robot service.

1.8. Verify

Check:

• User, particularly one who accessed the desktop client before the rollback, can run the Internal Audit desktop client without error.
• User can access the Web application.
• Robot service starts without error.