HP Application Recovery Manager software Integration guide (March 2008)

5. In the Options tab, set the general and database recovery options:
To ensure that the current control files and online redo logs are preserved, select
Keep current control files and redo logs. If set, the current control files and online
redo logs are copied to a temporary location (default AppRM_home\tmp on
Windows or /var/opt/omni/tmp on UNIX) before instant recovery starts.
When the instant recovery completes, the files are copied back to their original
location. To add or remove a control file from the list, click the Edit list button
and edit the list of files in the dialog window that opens. If the backed up
database was started using an spfile, the file is also automatically added to the
list of preserved files.
At this point, you can decide whether to perform a database recovery
immediately after an instant recovery or not:
• To perform only an instant recovery, click Restore.
• To automatically perform a database recovery after an instant recovery,
select the recovery options. For details refer to
“Database recovery options” on page 181.
NOTE:
If Application Recovery Manager detects that some of the archive logs that
are needed for database recovery are missing, it automatically tries to
restore the missing archive logs from a third-party backup by calling
BRRESTORE. Thus, before you start the instant recovery session, ensure that
the backup_dev_type parameter in the initSID.sap file on the
application system has the same value as during third–party archive log
backup. Otherwise, the restore of archive logs and, consequently, database
recovery will fail.
Click Restore.
Application Recovery Manager recovers the database after performing instant
recovery by switching the database to mount state and applying the redo
logs.
Application Recovery Manager SAP R/3 integration180