Video Screencast Help

NB RMAN restore on different client.

Created: 05 Jun 2013 • Updated: 17 Jun 2013 | 3 comments
This issue has been solved. See solution.

Hello,

 

I have a latest RMAN backup which i need to restore on different host.

 

Both is Solaris 10.what is prerequisite to restore this and how to attach new host with Media server.

NB-7.1.0.4

 

Operating Systems:

Comments 3 CommentsJump to latest comment

vjuhola's picture

what do you mean by "how to attach new host with Media server"?

did you use RMAN catalog database to take the backup?

wizard_s32's picture

Ankit, 

You would need to have the netbackup oracle agent installed on both clients and configured. 

You would need to have RMAN restore script edited correctly to run the restore from destination machine . 

This is an alternate client restore and can work by a file called No.restriction on the master server under 

 

usr/openv/netbackup/db/altnames/No.Restrictions 

 

Hope that helps. 

 

 

The Comments posted here are not that of the Organisation i work for, i do solely own these as my OWN.

Will Restore's picture

from the NetBackup for Oracle Admin Guide:

 

About performing a redirected restore with RMAN

 

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

client used.

2 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 and Linux, set the NB_ORA_CLIENT environment variable to the

source client.

3 On UNIX and Linux, 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 hostname of

the source client.

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

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

6 On UNIX and Linux, grant write permission to the directory to which you

want to restore the data files.

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

8 Start up the database in the nomount state.

9 Start RMAN, connecting to the catalog. On Windows, also connect to the

target database.

10 On UNIX and Linux, set dbid to be the DBID of the source client database.

Connect to the target database without using a user ID and password.

11 Run an RMAN restore script. On UNIX and Linux, you can alternatively type

the RMAN commands for the restore.

 

Will Restore -- where there is a Will there is a way

SOLUTION