Data must be backed up before it can be restored. To ensure the safety of your data, you should frequently back up your system.
Consider the following before restoring data:
Ensure that the data collection and CMS states are set as follows:
Data backup type |
Data collection (on or off) |
CMS state (user mode) |
Local system administration data |
Turn off |
Single-user mode |
CMS system administration data |
On or off |
Single-user mode |
ACD system administration data |
On or off |
Single-user mode |
Historical data |
On or off |
Single-user mode or multi-user mode |
Non-CMS data |
Specific tables |
The restore process is run in the background. The Restore Data page shows the status of the restore process as it is performed.
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.