You have the option to restore an SAP database to a client other than the one that originally supplied the backup. This process of restoring data to a different client is called a redirected restore.
(NetBackup for SAP on Oracle Databases Only)
In order to perform a redirected restore, the following conditions must be present:
◆ The source and destination clients must have identical computer system architectures, OS versions, and bit levels.
◆ The source and destination clients must have identical Oracle RDBMS levels.
Note In some situations, it is possible to restore from lower to higher release levels of Oracle. For more information, see your Oracle documentation.
The redirected restore is a 4-part process:
1. Configure the NetBackup server
2. Copy files from the source client to the destination client
3. Configure the NetBackup for SAP destination client
4. Perform the redirected restore
The following procedure explains each part of the process. For more information on redirected restores, see the NetBackup System Administrator’s Guide.
▼ To perform a NetBackup for SAP redirected restore
1. Verify that you are logged in as the NetBackup administrator.
2. Configure the NetBackup server to allow redirected restores.
This step differs depending on whether you want to allow restores from any client or from only selected clients.
a. To remove restrictions for all clients, create the following file on the Netbackup master server:
/usr/openv/netbackup/db/altnames/No.Restrictions
OR
b. To restrict clients to restore only from certain other clients, create the following file:
/usr/openv/netbackup/db/altnames/client_name
client_name Specify the name of the client allowed to perform the redirected restore.
Performing a Restore
68 NetBackup for SAP System Administrator’s Guide for UNIX and Linux
c. If you performed step b, add the name of the NetBackup for SAP source client to the client_name file.
3. On the destination client, back up the existing control files to preserve the original configuration. These files are usually in the $ORACLE_HOME/dbs directory.
4. Copy configuration and control files from the NetBackup for SAP source client to the NetBackup for SAP destination client.
For example, you can use ftp(1) to perform the copies.
a. Copy the following files from the source client, usually $ORACLE_HOME/dbs, to the same location on the destination client:
◆ initSID.sap
◆ initSID.utl
◆ initSID.ora
◆ initSID.dba
b. Copy the $SAPDATA_HOME/sapbackup directory from the source client to the same location on the destination client.
5. Configure the NetBackup for SAP destination client.
a. Change the client parameter in the initSID.utl file on the destination client to the name of the source client.
OR
Set the SAP_CLIENT environment variable on the destination client to the name of the source client. For example:
SAP_CLIENT=source_client
export SAP_CLIENT
Note The SAP_CLIENT variable has higher priority than the value in the initSID.utl
file.
b. (Conditional) Set the restore_filter parameter in the initSID.utl file on the destination client. Perform this step only if you are restoring images created with a NetBackup for SAP version before 6.0.
For example, if the source client path is set to /home_db/oracle/sap and the input file contains the path /oracle/SAP, then the value of restore_filter is a script such as 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
c. Create a symbolic link on the destination client that resembles the actual path of the source client and point it to the directory that points to the SAP files. Note Do not use the -m dest_dir option with brrestore to achieve the same effect.
This restores the files to the directory you specify, rather than to the original directories.
6. Perform the redirected restore.
a. Log onto the NetBackup for SAP destination client.
b. Enter the following command:
brrestore -d util_file -b last -m full
Redirected Restore Sample Environment
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 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:
Performing a Restore
70 NetBackup for SAP System Administrator’s Guide for UNIX and Linux
#!/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 really 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, use the restore_filter script.
