Take the following notes during backup.
Make a backup in an environment where Systemwalker Operation Manager is operating normally.
When you start a backup, the Systemwalker Operation Manager services or daemons are stopped automatically. The stopped services or daemons are started up automatically when the backup has completed.
We recommend to make a backup in the time period when job, job net and group are not executed. If you make a backup when a job, job net or group is being executed and if you restore its information, its job, job net or group is abnormally terminated with completion code 239.
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 place the group for Systemwalker Centric Manager offline before backing up:
Microsoft(R) Failover Clustering
Failover Cluster Manager
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)