In this Document Goal Solution References

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.8 Information in this document applies to any platform.

Goal

Restoring Rman backup on a different node with different backup directory structures and different database directory structures .

Solution

ASSUMPTIONS -----------------------

Steps to acheive the goal: 1) Connect to the target database using rman and backup the database ---> ON NODE 1

Subject: How To Restore Rman Backups On A Different Node When The Directory Structures Are Different

Doc ID: 419137.1 Type: HOWTO

Modified Date: 05-OCT-2008 Status: MODERATED

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

++ Rman backup of database is done on NODE 1. ++ The database has to be has to be restored from t he Rman backup on NODE 2. ++ The directory structures for the backups and the database files are different on NODE 2. ++ The Rman backups have to put in new directory st ructure on NODE 2 unlike as they were on NODE 1. ++ Also the database has to be restored to a differ ent directory structure on NODE 2.

++ The backups on NODE 1 are done to '/node1/databa se/backup' ++ The database files on NODE 1 are in '/node1/data base/prod' ++ The backups on NODE 2 will be in location '/node 2/database/backup' ++ The database files on NODE 2 will be restored to '/node2/database/prod

$ rman target / Recovery Manager: Release 10.2.0.1.0 - Production o n Tue Feb 13 00:29:33 2007 Copyright (c) 1982, 2005, Oracle. All rights reserv ed. connected to target database: ORA10G (DBID=39320561 36)

Page 1 of 5

10/23/2009https://metalink.oracle.com/CSP/main/article?cmd=show&type=NOT&id=419137.1

2) Move the following files to the NODE 2:

RMAN> backup database plus archivelog; Starting backup at 13-FEB-07 current log archived using channel ORA_DISK_1 channel ORA_DISK_1: starting archive log backupset channel ORA_DISK_1: specifying archive log(s) in ba ckup set input archive log thread=1 sequence=143 recid=109 s tamp=614392105 channel ORA_DISK_1: starting piece 1 at 13-FEB-07 channel ORA_DISK_1: finished piece 1 at 13-FEB-07 piece handle=/node1/database/backup/o1_mf_annnn_TAG 20070213T002825_2x21kbds _.bkp tag=TAG20070213T002825 comment=NONE channel ORA_DISK_1: backup set complete, elapsed ti me: 00:00:02 Finished backup at 13-FEB-07 Starting backup at 13-FEB-07 using channel ORA_DISK_1 channel ORA_DISK_1: starting full datafile backupse t channel ORA_DISK_1: specifying datafile(s) in backu pset input datafile fno=00003 name=/node1/database/prod/ sysaux01.dbf input datafile fno=00001 name=/node1/database/prod/ system01.dbf input datafile fno=00002 name=/node1/database/prod/ undotbs01.dbf input datafile fno=00004 name=/node1/database/prod/ users01.dbf input datafile fno=00005 name=/node1/database/prod/ 1.dbf input datafile fno=00006 name=/node1/database/prod/ sysaux02.dbf input datafile fno=00007 name=/node1/database/prod/ undotbs02.dbf channel ORA_DISK_1: starting piece 1 at 13-FEB-07 channel ORA_DISK_1: finished piece 1 at 13-FEB-07 piece handle=/node1/database/backup/o1_mf_nnndf_TAG 20070213T002827_2x21kd12 _.bkp tag=TAG20070213T002827 comment=NONE channel ORA_DISK_1: backup set complete, elapsed ti me: 00:00:55 Finished backup at 13-FEB-07 Starting backup at 13-FEB-07 current log archived using channel ORA_DISK_1 channel ORA_DISK_1: starting archive log backupset channel ORA_DISK_1: specifying archive log(s) in ba ckup set input archive log thread=1 sequence=144 recid=110 s tamp=614392165 channel ORA_DISK_1: starting piece 1 at 13-FEB-07 channel ORA_DISK_1: finished piece 1 at 13-FEB-07 piece handle=/node1/database/backup/o1_mf_annnn_TAG 20070213T002925_2x21m6ty _.bkp tag=TAG20070213T002925 comment=NONE channel ORA_DISK_1: backup set complete, elapsed ti me: 00:00:02 Finished backup at 13-FEB-07 Starting Control File and SPFILE Autobackup at 13-F EB-07 piece handle=/u01/oracle/product/ora10g/dbs/c-39320 56136-20070213-02 comment=NONE Finished Control File and SPFILE Autobackup at 13-F EB-07 RMAN> exit

+ The database backup pieces to location '/node2/database/backup'

Page 2 of 5

10/23/2009https://metalink.oracle.com/CSP/main/article?cmd=show&type=NOT&id=419137.1

3) Edit the PFILE on NODE 2 to change the environment specific parameters like .

4) Once the PFILE is suitably modified invoke Rman on the NODE 2 after setting the Oracle environment variables and start the database in nomount mode:

5) Restore the controlfile from the backup piece.

6) Mount the database

7) Now catalog the backup pieces that were shipped from NODE 1

+ Controlfile backup piece to the location '/node2/database/backup' + The parameter file i.e init.ora file to the default location i.e $ORACLE_HOME/dbs

user_dump_dest = background_dump_dest = control_files =

[oracle@test-br test]$ export ORACLE_HOME=/u01/oracle/product/ora10g [oracle@test-br test]$ export ORACLE_SID=ora10g [oracle@test-br test]$ export PATH=$ORACLE_HOME/bin:$PATH [oracle@test-br test]$ rman target / Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database (not started) RMAN> startup nomount Oracle instance started Total System Global Area 205520896 bytes Fixed Size 1218508 bytes Variable Size 75499572 bytes Database Buffers 121634816 bytes Redo Buffers 7168000 bytes

RMAN> restore controlfile from '/node2/database/ba ckup/c-3932056136-20070213-02'; Starting restore at 13-FEB-07 using target database control file instead of recov ery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=155 devtype=DISK channel ORA_DISK_1: restoring control file channel ORA_DISK_1: restore complete, elapsed time: 00:00:02 output filename=/node2/database/prod/control01.ctl Finished restore at 13-FEB-07

RMAN > alter database mount

RMAN> catalog backuppiece

Page 3 of 5

10/23/2009https://metalink.oracle.com/CSP/main/article?cmd=show&type=NOT&id=419137.1

This feature of cataloging backup pieces is available from ORACLE 10g versions. Prior to Oracle 10g we were not able to catalog the backup pieces. For more information on cataloging options refer the metalink note 470463.1

8) Get to know the last sequence available in the archivelog backup using the following command.This will help us in recovering the database till that archivelog.

9) Rename the Redologfiles,so that they can be created in new locations when opened the database is opened in resetlogs

10) Now restore the datafiles to new locations and recover. Since we are recovering the database here till the archivelog sequence 50 the sequence number in the SET UNTIL SEQUENCE clause should be 50 (+1)

If we are restoring the Rman backups from tapes,then we should ensure the same media manager variables that were used during backups are maintained during restore too.

'/node2/database/backup/o1_mf_annnn_TAG20070213T002925_2x21m6ty_.bkp'; RMAN> catalog backuppiece '/node2/database/backup/o1_mf_annnn_TAG20070213T002825_2x21kbds_.bkp'; RMAN> catalog backuppiece '/node2/database/backup/o1_mf_nnndf_TAG20070213T002827_2x21kd12_.bkp';

RMAN > list backup of archivelog all;

Let us assume the last sequence of last archivelog in the backup is 50.

SQL> alter database rename file '/node1/database/pr od/redo01.log' to '/node2/database/prod/redo01.log' ; ...... ...... ......

RMAN> run { set until sequence 51; set newname for datafile 1 to '/node2/database/pro d/sys01.dbf'; set newname for datafile 2 to '/node2/database/pro d/undotbs01.dbf'; set newname for datafile 3 to '/node2/database/pro d/sysaux01.dbf'; set newname for datafile 4 to '/node2/database/pro d/users01.dbf'; set newname for datafile 5 to '/node2/database/pro d/1.dbf'; set newname for datafile 6 to '/node2/database/pro d/sysaux02.dbf'; set newname for datafile 7 to '/node2/database/pro d/undotbs02.dbf'; restore database; switch datafile all; recover database; alter database open resetlogs; }

Page 4 of 5

10/23/2009https://metalink.oracle.com/CSP/main/article?cmd=show&type=NOT&id=419137.1

The below article gives the information of various media manager Environment Variables. NOTE.312737.1 RMAN and Specific Media Managers Environment Variables.

References

Note 228257.1 - RMAN 'Duplicate Database' Feature in Oracle9i / Oracle 10G Note 73974.1 - RMAN: Restoring an RMAN Backup to Another Node

Keywords

ALTERNATE ; CLIENT ; DIFFERENT ; NODE ; RESTORE ; RMAN ;

Help us improve our service. Please email us your comments for this document. .

Page 5 of 5

10/23/2009https://metalink.oracle.com/CSP/main/article?cmd=show&type=NOT&id=419137.1