Restoring RMAN backup on a different server

Question

Hi oracle gurus
i have following scenario
i have a compressed backup set of a database
i want to restore that rman backup on to a different server.
both the server have same version of oracle.and both the server are of 32 bit.
please reply if any more info is required.

Answer 1

RESTORE AND RECOVERY PROCEDURE OF PRODUCTION DATABASE BACKUP ON TEST SERVERS
As part of disaster recovery exercise or to test the validity of a RMAN backup, a full restore and recovery of databases can be performed on scratch or test servers utilising the production RMAN backups which have been restored from the tape backups on these test or scratch servers.
This note will illustrate the above procedure by detailing the steps required to restore the backup of a production database (prod1) on a test server linux01 .
The following assumptions are made in this note:
The RMAN backups have been restored from tape backups to the same backup location on the test server as the production server where the backup was originally taken
The identical directory structure as is present on production has been created on the test server. This will apply to not only the location of the database files (data, control files, redo log files), but also to the bdump,cdump, udump and adump locations.
Controlfile autobackup has been enabled. This is important.
Overview
Restore the spfile from the autobackup
Restore the controlfile from the autobackup
Restore the data files
Recover by applying archived redo log files
Open the database with resetlogs
Restore the SPFILE
[oracle@linux01 prod1]$ rman target /
connected to target database (not started)
RMAN> set dbid=4266928631
executing command: SET DBID
RMAN> startup force nomount;
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/10.2.0/dbs/initprod1.ora'
starting Oracle instance without parameter file for retrival of spfile
Oracle instance started
Total System Global Area 159383552 bytes
Fixed Size 2039056 bytes
Variable Size 67109616 bytes
Database Buffers 83886080 bytes
Redo Buffers 6348800 bytes
RMAN> run
2> {SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/backup/prod1/%F';
3> restore spfile from autobackup;
4> }
RMAN> shutdown immediate;
Restore the Control File
In this case, the instance is now being started with the restored spfile. We can create a pfile as well from this spfile is so required.
RMAN> startup nomount
connected to target database (not started)
Oracle instance started
RMAN> set dbid=4266928631
executing command: SET DBID
RMAN> run
2> {SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/backup/prod1/%F';
3> restore controlfile from autobackup;
4> }
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
Restore the database
RMAN> restore database;
Recover the database
The recovery will fail at a point where it cannot restore any more archived redo log files.
In this case the last archived log file which has been backed up is sequence 613.
This information can be obtained by issuing a LIST BACKUP OF ARCHIVELOG ALL command.
So RMAN will fail when it tries to apply sequence 614 ….
RMAN> recover database
[oracle@linux01 PROD1]$ rman target /
connected to target database: PROD1 (DBID=4266928631, not open)
RMAN> sql 'alter database open resetlogs';
RMAN>
reference: http://gavinsoorma.com/recovery-scenarios/