HP OpenView Operations Administrator's Reference - filibeto.org

Maintaining OVO
Backing up Data on the Management Server
534
Recovering Configuration Data after an Automatic
Backup
Automatic backup scripts back up only configuration data and dynamic
data. If binaries or static configuration files are lost, you have to recover
them before restoring the database.
You can recover binaries or static configuration files in one of the
following ways:
❏ Re-install OVO
If Software Distributor indicates that OVO is already installed, you
may need to use the option Reinstall Fileset even if the same
revision already exists.
❏ Run a Full Offline Backup
Use a full offline backup that was taken with opc_backup with the
full option.
❏ Restore a Full Offline Backup
Restore a full offline backup of the complete system.
Restoring a Database to its State at the Latest Backup
Restoring the database to its state at the time of the last backup requires
data contained in the backup only. As a result, you can restore the
database even if you have to re-install OVO. However, the restoring the
database in this way is incorrect in Oracle because the latest state of the
database is not restored. In addition, Oracle log numbers are reset in the
control files and in the online redo logs. The control files are restored
from a backup control file. Missing online redo log files are re-created by
the Oracle recover process.
Recovering a Database to its Latest State
Recovering the database to the latest state more complicated than
restoring the database to its state at the time of the last backup.
Recovering the database to its last state uses not only the data contained
in the backup but also data on the system itself (that is, online redo logs
and archive logs since the last backup). In addition, this method may
introduce inconsistencies between the configuration files (restored to the
state of the backup) and the data in the database (restored to the latest
possible state).
Chapter 13