Take the following notes during restoring.
Make a restore in an environment where Systemwalker Operation Manager is operating normally.
If you have backed up the data using backup commands or tools in an earlier version/level, you cannot restore it using the restore commands or tools in the current version/level.
The backup data in a different product (OS type/supported architecture type) cannot be restored.
The backup data in a different installation drive or directory cannot be restored.
The Systemwalker Operation Manager services or daemons are stopped automatically during restoring. Automatic start up of the Systemwalker Operation Manager services or daemons when restore is complete differs according to the restore method, as noted below:
If you restore using the Operation Environment Maintenance Wizard, the services or daemons are started up automatically when restore is complete.
If you restore using the mprso command, the services or daemons are not started up automatically when restore is complete.
To make the settings of Job Execution Control valid after restoring, you must restart the system in the Initialization mode. For startup in the Initialization mode, refer to the Systemwalker Operation Manager Reference Guide.
If the Extended User Management function is used in the UNIX version, the data is restored differently according to the enable or disable setup of Extended User Management function.
If the Extended User Management function was enabled during the backup, this function is made enable regardless of whether it was enabled or not. Both the Operation Manager user information and the access rights information to the Operation Manager user projects will be restored.
If the Extended User Management function was disabled during backup, the Extended User Management function remains disabled regardless of whether it is enabled or disabled during restoring, and the privilege information on the OS user's project access is restored.
Ensure that the following conditions are the same for both the backup source and the restoration destination:
The user names, passwords and user group names that have been registered with the operating system
The destination Systemwalker authentication repository (if a Systemwalker authentication repository is being used)
The user ID specified as the project owner in the backup source server or the user ID that has been given access privileges to the project must be registered on the restoration destination server. Refer to "mplstacluser Command" in the Systemwalker Operation Manager Reference Guide for details on how to check user IDs for which access privileges to the project have been set.
If Systemwalker Operation Manager is linked to Systemwalker Centric Manager and Systemwalker Centric Manager is being operated as a cluster system, use the windows indicated below (depending on the cluster system being used) to make the group for Systemwalker Centric Manager offline before restoring:
Microsoft(R) Failover Clustering
Failover Cluster Manager
