Pre-migration tasks
The migration process includes manual and automated steps. These tasks are part of the IRC and CM migration:
- Back up database, application, configuration files, report server database and the Report Encryption key from Source System.
Note: The 'Appendix C: Backing up the database' section in the Planning & Deployment Guide lists one of the methods of database back-up. For more information, refer to http://msdn.microsoft.com/en-us/library/ms187510.aspx. For information on backing up the report server database, refer to http://msdn.microsoft.com/en-us/library/ms155814.aspx.
- Install the new instance of Application and Database server on Target System in line with the installation sequence followed while installing the Application and Database server on Source System.
- Restore the database in the Target System.
- Back up the Approva folder([InstallPath]\Approva) of the Target System.
- Back up the registry settings ([InstallPath]\HKEY_LOCAL_MACHINE\SOFTWARE\Approva) of the Target System by taking a back-up of the entire path.
- Share the Approva folder of the Source System, located at [InstallPath]. This file share is used by the migration utility to copy the configuration settings to the new deployment of the Target System. The folder must be shared with full control permissions with 'Everyone' or with the user account performing the migration activity.
Note: It is recommended that the IRC/CM service account is used to perform the installation.
- If report scheduling inbox files and archived analysis files must be copied over to the Target System, the default path must be manually configured in the IRC/CM User Interface on the Configurations page of the menu before migration.
- If Insights are present on the Source System but are not present on Target System setup, the migration utility searches for the Insights and displays an error message when not found. Such Insights must be commented out in the file Migration.xml located at [InstallPath]\ BRPublisher\bin\ before beginning migration.