Before migrating data

Last Updated : Feb 17, 2021 |

The following items should be read and understood before migrating data:

Caution:

Attempting to migrate Agent and Call Center Administration data more than once might cause serious errors from which recovery is difficult. Performing the migration of this data a second time can result in the corruption of the password tables. To do a second migration of ACD administration data, do a second setup of the CMS software.

  • To migrate System Administration data or Agent and Call Center Administration data, CMS must be in single-user mode.

  • Migrations of system administration data cannot be done in phases. Migrating some user IDs at one time and others at a later time result in two separate sets of data. Only one set of data can be used and cannot be migrated into another set.

  • When migrating or restoring a non-LDAP user from a maintenance backup, and the logid (logon ID) for a user does not exist in /etc/passwd, the user is created as a new logid. That logid requires password administration just as if the user was created as described in User administration.

    When this happens, the migration and restore logs contain messages similar to the following examples:

    • /cms/maint/r3mig/mig.log

      INFO: New UNIX user normusr1: name, room and telephone will not be migrated.

    • /cms/maint/restore/rest.log

      Created UNIX login 'normusr1'.

      Warning: Name, Telephone, and Room will not be restored for normusr1.