HP B6960-90078 - Manual (Page 460)

Managing the Data Protector Internal Database
Recovering the IDB
Chapter 9 430
Replaying IDB Transaction Logs
In a successful omnidbrestore -autorecover , transaction logs are
already replayed. Use this procedure only if you need to retry replaying
of transaction logs or you postponed it before.
Replaying transaction logs after the IDB restore is completed recovers
the IDB to the same state as before the crash, except that binary files are
not updated and changes to binary files are lost.
The following are not available for the backups that were running from
the last IDB backup until the IDB corruption:
• Session messages.
• Browsing of file versions (restores of complete objects are possible).
Perform the import catalog on the media used by the backups, to
recover the changes.
• SIBF updates. Export and import the media used by the backups to
recover the changes.
Limitation Replay of the transaction logs can only be done if archiving of the
transaction logs is enabled. (The archiving parameter in the
velocis.ini file must be set to 1.)
Prerequisites • Transaction logs must be available. For more information on
transaction logs, refer to “Preparing for IDB Recovery” on page 390.
You can verify that the transaction logs are available by listing the
directory:
/db40/logfiles/syslog
If transaction logs are not available, refer to “Updating the IDB by
Importing Media” on page 433.
• If the IDB is installed on MC/ServiceGuard, run the cmhaltpkg
command on the active node before running the
omnidbrestore command in the procedure below, to stop the Data
Protector package. Before running the omnidbcheck command in the
procedure below, run the cmrunpkg command on the
active node to start the Data Protector package, where
is the name of the Data Protector cluster package.
• If the IDB is installed on Microsoft Cluster Server, take the
OBVS_VELOCIS cluster group offline using the Cluster Administrator
utility on the active node before running the omnidbrestore command
in the procedure below. Before running the omnidbcheck command in