Running the Migration Assistant
- Note:
- We recommend logging in to the target system using the aiw user, as your RICOH ProcessDirector user ID probably does not exist on the new system yet.
- You can create a new administrator user to log in to the target system, but, if it exists on the source system, it is overwritten during migration.
- Log in to RICOH ProcessDirector on the target system as the aiw user.
- Click the Administration tab.
- In the left pane, click .
- Select IMPORT FROM ANOTHER SYSTEM.
- Log in to the source system with an administrator user name and password.
- On the Verify page, make sure all the information presented is correct and click Continue.
- On the Prepare page, review the suggested actions to reduce the migration failure possibilities.
For each step, you have the option to either complete or ignore it. Click Save and Continue to proceed with the migration.For example, in this step, you can make sure that the Product Update features are installed on both systems at the same level. In the Feature Manager, find the Product Update feature for both systems and compare the values in the Installed Version column.
- If the target system has a higher version, click the download button in the Migration Assistant to save the package to your system. Then you can install the Product Update using Import Package on the source system.
- If the source system has a higher version, find the most recent product update package
in:
/opt/infoprint/ippd/available
. The name of the package is:ProductUpdate-3.4.version_number.epk
. Download the package, then log in to the target system. Open Feature Manager, import the package, then install it.For more information, see Adding or upgrading a feature using Import Package.
- On the Features page, click CHECK FEATURES to compare the features installed on the systems. To proceed, make sure that both
the source and target systems have the same features installed.If any features are missing, click Save and Continue. Review the features to install and click OK. Feature Manager opens so you can install the missing features. After the features are installed, log in to your RICOH ProcessDirector target system again and return to the Migration Assistant. When both systems contain the same features, click Continue to proceed with the migration.
- Note:
- If you purchased one or more features for the first time, they exist on the target system only.
- If you worked with Ricoh's Advanced Solutions Practice to install additional functions on your source system, you must transfer those feature packages to your target system. Contact your Ricoh representative for assistance.
- On the Objects page, select to migrate all objects from your source system or specific objects.We recommend migrating all objects, but you can select which objects to migrate if you want to take this opportunity to remove some objects from your system. If you choose to selectively migrate objects, click the Select objects and choose the objects you want to migrate.
The Migrate options let you overwrite any identically named objects on the target system with the corresponding objects from the source system.
- On the Settings page, select which previously configured system settings to migrate. These settings are configured in the Settings section of the Administration page. Choose the settings to import and click Save and Continue.
- On the Files page, select which eligible files from the aiw/aiw1/ directory to migrate. Choose the files to import and click Save and Continue.
- Note:
- To easily identify all files that are eligible for migration on the target system, choose the Selected files option and then scroll through the list that appears.
- Files eligible for migration include customized files that you have added to the directory, such as control files, scripts, and AFP resources. In addition, files used by sample workflows and other sample objects are also eligible to migrate from the source system.
- Any files or folders with these special characters in their names: \ / : * ? " < > | are not visible in the list of eligible files to migrate and therefore cannot be selected for migration.
- Non-UTF-8 characters cause errors in migration, including failure to migrate files entirely. The Migration Assistant reports success, but the files are not moved to the target system.
- Not all files in the
/aiw/aiw1
directory are eligible for migration. For example, the spool files, hidden files, or symbolic link files cannot be migrated.
- Optional: On the Reports page, select how to manage the migration of the Reports PostgreSQL database configuration
and collected data.Choose the correct options for your installation based on your answers to the questions in Planning for Reports database migration.
- Note:
- If you choose to continue using the existing database, Migration Assistant migrates only the settings for the Reports database. Migration Assistant adjusts the host name value as needed. For example, if the host name value on the source system is localhost, the value is converted to the full host name of the source system when it is imported to the target system.
If you are not ready to migrate your Reports settings or data, skip this migration.
- Before proceeding with the migration process, review the configuration to import from the source system. If you need to change any choices, you can navigate to any step of setting up the migration elections by selecting Edit.
- When everything is confirmed, click START MIGRATION.The Migration Assistant starts to import objects and settings while displaying the progress. You can download the migration log file to review the details when any migration errors occur or the final version when the migration is complete.
During the migration, you can pause or cancel the import at any time.
If you cancel a data migration, the process stops after the cancellation request is processed. Upon cancellation, objects or files that were already migrated are reverted to their original versions from the target system. If the reverting process is unsuccessful, objects or files that were not successfully restored remain in their migrated state.
To manually return any objects or files on the target system to their original state, you can retrieve them from a snapshot or backup of the original system. Files on the target system are backed up before they are migrated. To restore files, you can find the backup versions in:
$AIWDATA/migrate/files-backup-<timestamp>.zip
- Download the ZIP file log if there are any errors that you need to review.
- After you download the ZIP file, click X button at the top of the page to exit the MIGRATION ASSISTANT.
- Note:
- You can click X in the upper right corner of the window followed by SAVE CHANGES to save the progress at anytime during migration. In this way, you can return to complete the migration process from where you left off.
- See Completing the upgrade process to complete the migration process.