SAP redirected restore sample environment (UNIX)
This sample environment shows how a redirected restore uses the restore_filter script.
This example assumes the following:
Source client
Actual path is /home_db/oracle/sap
Includes soft link /oracle/SAP (SAP is the sytem ID), which points to /home_db/oracle/sap.
Destination client
Actual path is /home2/sap
Also has soft link /oracle/SAP, which points to /home2/sap.
Make soft link /home_db/oracle/sap, which points to /home2/sap
In the restore_filter script, substitute the path that was provided in the input file list of the destination client with the actual path of the source client. The resulting script sample might look like the following:
#!/bin/sh # this shell is used to change some logically linked files # during a restore sed -e ' s\/oracle\/SAP\/home_db\/oracle\/sap\/' $1 > $2
When the backup starts, the file list contains the file path with the following soft link:
/oracle/SAP/sapdata1/btabd_1/btabd.data1
However, the file is backed up with the following actual path:
/home_db/oracle/sap/sapdata1/btab_d/btabd.data
When the request for a restore is issued, the input file list contains file paths with soft links. These are converted to the actual path of the destination client. Because this path is different from the source client path, the restore would fail in the inquire phase. To prevent this kind of failure, use the restore_filter script.