About performing a redirected restore with RMAN
Perform the following procedure on the destination client host if you want to restore any RMAN backups that another client owns.
The user on client A cannot initiate a redirected restore to client B. Only the user on client B, which is the client receiving the backup image, can initiate the redirected restore. Any user who belongs to the database group that performed the backup can restore it, unless the BKUP_IMAGE_PERM variable is set to USER.
If you use a non-root service user account, specific access must be allowed for that user when you add files to the /usr/openv/netbackup/db/altnames directory. The service user account must have full access to these files through the ownership or group and the permissions. For example, if the service user is svcname and its group is srvgrp, the file can have permissions of 400. If the file owner is for a different user and group, the file permissions must allow access to the service user. For example, 777. Equivalent permission settings must be used in a Windows environment.
Note:
If the RMAN catalog database has been lost, restore the catalog database first before continuing with the redirected restore.
To perform a redirected restore
- Enable a network connection to the RMAN catalog database that the source client used.
- Do one of the following:
On Windows, use the rman parms option to set the NB_ORA_CLIENT environment variable to the source client.
On UNIX, set the NB_ORA_CLIENT environment variable to the source client.
- On UNIX, check the bp.conf files on the source client. Make sure that the CLIENT_NAME variable either is not set or is set to the host name of the source client.
- Make the init.ora file of the source client available to the destination client.
Copy the file to the destination client or modify the file on the destination client. Change all location-specific parameters.
- Create a folder or set the permissions for a directory to restore the data files:
On Windows, create and start an Oracle service for the previously set ORACLE_SID. Create the folder to which you want to restore the data files.
On UNIX, grant write permission to the directory to which you want to restore the data files.
- Set up a password file for the destination client database.
- Start the database in the nomount state.
- Start RMAN, connecting to the catalog. On Windows, also connect to the target database.
- On UNIX, set dbid to be the DBID of the source client database. Connect to the target database without using a user ID and password.
- Run an RMAN restore script. On UNIX, you can alternatively type the RMAN commands for the restore.