Planning for migration

Migration covers a number of scenarios.

  • Upgrading versions. When you upgrade from a prior release, the installation and startup process will handle migrating any configuration or data that may have changed between versions. See Installing the IBM Traveler server for more information on upgrading a server.
  • Moving to a new server. It is possible to move the server data from one physical machine to another.
  • Integrating stand alone IBM Traveler servers into a high availability pool. In this process, the local data from each servers is transferred to the shared enterprise database of the High Availability (HA) pool.

Upgrading versions

Existing IBM Traveler servers can be upgraded to this release. The installation and start up process will handle the migration of configuration information and the upgrading of existing internal databases. It is recommended to upgrade the Domino® server at the same time you upgrade the IBM Traveler server. See Upgrade considerations for more information.

If you are upgrading servers in an HA environment, it is recommended that you upgrade one server at a time. Doing this ensures continued service for any IBM Traveler users. For more information, refer to Upgrade considerations for a Highly Available environment.

As of release 8.5.3 Upgrade Pack 1 and later, configuration information from a number of files and locations has been consolidated to only use notes.ini parameters. As a result, parameter names have been changed. The installation process will migrate supported configuration settings to notes.ini settings. There are some configuration settings, such as trace settings, that are not migrated. See Configuring IBM Traveler server for more information on the updated configuration settings for this release.

As of release 8.5.3 Upgrade Pack 1 and later, some of the properties in notes.ini have been renamed to make the naming more consistent and easier to understand. See Notes.ini settings for more information.

For standalone servers, the upgrade process does not require an enterprise database. Upon startup, the server automatically upgrades the existing internal database, retaining any existing data. Note that the service is unavailable during this upgrade process. If you are upgrading from a version earlier than 8.5.3 upgrade pack 1 (, due to extensive changes made to sync meta-data to improve performance, the upgrade can take an extended period of time, on the order of 2 to 3 times the amount of time it takes to run a defragmentation (load traveler -defrag). In this case, depending on the number of users and the quality of your hardware, a multi-hour maintenance window may be required to perform this upgrade. When upgrading standalone servers running 8.5.3 upgrade pack 1 ( and higher, the upgrade process requires approximately the same time as a defragmentation. Note that the upgrade process automatically runs the defragmentation process when upgrading releases. After the upgrade, a server can then be configured as part of an HA pool, if desired. See Integrating IBM Traveler servers into a High Availability (HA) pool for more information.