Chapter 10 465
Tuning, Troubleshooting, Security, and Maintenance
System Maintenance
logs not moved by ito_oracle.sh and copies the ITO
configuration in the file system that is not backed up by
nnm_checkpoint.ovpl.
The NNM script nnm_checkpoint.ovpl backs up all operational
NNM databases and also backs up the directory $OV_CONF, which
includes some ITO configuration files, the NNM database (flat)
files, and the NNM configuration files.
4. Call ovresume to resume operation of NNM processes.
5. Run all of the backup scripts found in the directory;
$OV_CONF/ovbackup/post_resume
• Backup analytical data (if the -analytical option or no option at all
is specified):
Run all of the backup scripts found in the directory;
$OV_CONF/ovbackup/checkpoint/analytical including
nnm_checkpoint.ovpl and backs up the NNM analytical repository
if the embedded database is used.
NOTE ovbackup.ovpl stores progress information in the file:
/var/opt/OV/tmp/ovbackup.log.
The ovrestore.ovpl Command. The ovrestore.ovpl command
restores a backup or parts of a backup created with ovbackup.ovpl and
accepts the following command-line options:
ovrestore.ovpl [-operational] [-analytical] [-d \
<destination>]
If you still have the backup on disk, you can use the -d option to specify
the directory where the backup image resides. Otherwise, you will need
to restore the image to disk from the archive medium first before running
the ovrestore.ovpl command with the -d option. For more
information on the command-line options, see the man page
ovrestore.ovpl(1M). Briefly, ovrestore.ovpl carries out the
following high-level steps:
1. Check that no OpenView or integrated processes are running
2. Restore operational data (if the-operational option or no option at
all is specified):
