How to redirect a Oracle restore to a different client ?

Article:TECH77362  |  Created: 2009-01-27  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH77362
Article Type
Technical Solution


Environment

Issue



How to redirect an Oracle restore to a different client


Solution



With NetBackup for Oracle you have the option to restore a database to a client other than the one that originally performed the backup. The process of restoring data to another client is called a redirected restore or alternate client restore. For a alternate client  restore, the user on original client A cannot initiate a redirected restore to alternate client B. Only the user on alternate client B, which is the client receiving the backup image, can initiate the redirected restore.

The following sections describe how to perform a redirected restore using Oracle RMAN.

Server configuration

Ensure that the NetBackup server is configured to allow a redirected restore.
The administrator can remove restrictions for all clients by creating the following file on the Netbackup master server:
install_path\NetBackup\db\altnames\No.Restrictions

Or,

to restrict clients to restore only from certain other clients, create the following file:

install_path\NetBackup\db\altnames\client_name

Where client_name is the name of the client allowed to do the redirected restore (the destination client). Then, add the name of the NetBackup for oracle source client to that file.

NOTE: See VERITAS NetBackup for UNIX System Administrator's Guide,version 6.5 for details on creating the /usr/openv/netbackup/db/altnames directory.

Alternate client configuration

Perform the following procedure on the destination client host if you want to restore any RMAN backups that another client owns.

1 Enable a network connection to the RMAN catalog database that the source client used.

Note: If the RMAN catalog database has been lost, restore the catalog database first before continuing with the redirected restore.

2 Use the rman parms option to set the NB_ORA_CLIENT environment variable to the source client.

3 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.

4 Create and start an Oracle service for the previously set ORACLE_SID.

5 Create the folder to which you want to restore the data files.

6 Set up a password file for the destination client database.

7 Start up the database in the nomount state.

8 Start RMAN, connecting to the catalog and the target database.

9 Run an RMAN restore script.

Example

For example, assume the following:

¦ Source client is camel
¦ Destination client is giraffe
¦ Master server is lion
¦ ORACLE_SID is test

¦ The user is connected to the Oracle database using a local connection, not SQL*Net

1 Create the following file on server lion:
install_path\NetBackup\db\altnames\No.restrictions

2 Modify the network tnsnames.ora file to enable RMAN catalog connection.

3 Create inittest.ora.

4 Using Oracle administration, create and start ORACLESERVICETEST.

5 Set the environment variable ORACLE_SID to test.

6 Make sure the destination database directory exists and has appropriate access permissions.
The data files are restored to the directory path with the same name they had when they were backed up.

7 Start up the database in a nomount state.

8 Run rman.
rman rcvcat rman/rman@rcat
Recovery Manager: Release 8.0.5.0.0 - Production
RMAN> @restore_database.rcv
where restore_database.rcv is the RMAN script that contains the restore commands.

:
run
{
# Allocates tape channel and sets RMAN environment variable
allocate channel t1 type 'SBT_TAPE'
parms="ENV=(NB_ORA_CLIENT=camel,NB_ORA_SERV=lion)";
restore
(database);
restore
controlfile to 'D:\orant805\database\ctl1TEST.ora';
release channel t1;
}

 


Legacy ID



337870


Article URL http://www.symantec.com/docs/TECH77362


Terms of use for this information are found in Legal Notices