Applicable versions and levels
Windows versions: V10.0L10 or later
Solaris versions: 10.0 or later
Linux versions: V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 10.0 or later
AIX versions: 10.0 or later
A
On V10.0L10 and 10.0 or later, you can schedule backup as a job by using the function (-SN option of the mpbko command) for backing up Systemwalker Operation Manager resources without stopping Systemwalker Operation Manager.
Operation cannot be guaranteed if you use a method other than that described above to back up Systemwalker Operation Manager resources while Systemwalker Operation Manager is operating.
This is because, if files in the Systemwalker Operation Manager database directory are accessed by a backup product while Systemwalker Operation Manager is operating, Systemwalker Operation Manager may no longer be able to access the files and therefore may not be able to perform processing properly.
Note the following points before backing up Systemwalker Operation Manager resources to the system as jobs:
On V10.0L10, V10.0L20, V10.0L21, and 10.0
Before performing backup, ensure that the backup directory is empty.
If the backup directory is not empty, a confirmation response is requested. This means that the job remains in "Executing" status and does not terminate.
On V11.0L10, V12.0L10, 10.1, 11.0, and 12.0
If you do not specify the -d option, note the same points as those for V10.0L10, V10.0L20, V10.0L21, and 10.0.
If you specify the -d option, you must ensure beforehand that the backup directory is empty. If any files exist in the backup directory, the backup command terminates abnormally.
