HP A.06.11 - Manual (Page 268)

7. Start the restore from a Data Protector backup session by executing the following
command:
recover_start media_group_name backup_type EBID "inst_name
SessionID:1 pipe_name1,inst_name SessionID:2 pipe_name2[,
...]"
Windows:
recover_start BACKDP-Data[2] DATA EBID "inst_name
SessionID:1 \\.\Pipe\inst_name.BACKDP-Data[2].1,TEST
SessionID:2 \\.\Pipe\inst_name.BACKDP-Data[2].2"
UNIX:
recover_start BACKDP-Data[2] DATA EBID "inst_name
SessionID:1
/var/opt/omni/tmp/inst_name.BACKDP-Data[2].1,inst_name
SessionID:2 /var/opt/omni/tmp/inst_name.BACKDP-Data[2].2"
Repeat this step for every session in the required chain of backup sessions.
8. Use one of the commands recover_start and recover_replace, based
on the exit code from the previous execution of recover_start or
recover_replace
.
For more information, see the SAP DB/MaxDB documentation.
9. If the command recover_start or recover_replace from the previous
step returned an exit code of -8020, and you have already restored all relevant
data, execute the following command:
recover_ignore
For more information, see the SAP DB/MaxDB documentation.
10. When the restore has finished, the database can be recovered either until the
last redo log or until the specified point in time.
a. To recover the database until the last redo log, execute the following
command in the SAP DB/MaxDB database manager:
db_online
b. To recover the database until the specified point in time, execute the
following command in the SAP DB/MaxDB database manager:
db_warm -f -u yyyymmdd hhmmss
Where yyyymmdd and hhmmss parameters set the time for the last redo
log to be applied.
Integrating SAP DB/MaxDB and Data Protector 268