RMAN Hot backup Restore in new Server

Hi,
Our Current Environment:
Source: Current Production
Database: 11.1.0.7
OS: Windows server 2003 R2
Target Environemnt:
Database 11.2.0.1
OS:windows server 2008 R2
Here my scenario is need to take RMAN Hot backup in Prod Instance and need to restore in New Server with smae SID which is going to use as Prod instance.
Please suggest the detailed steps in order to achive the goal.
Waiting for your thoughts.
Thanks
Shaik

RMAN can make it easy to restore a database to a new host.
Notice that: Using RMAN RESTORE and RECOVER commands to move a database permanently to another host, will keep the original database identifier (DBID) and will therefore cause a conflict in the RMAN repository, because the restored database with the same DBID will be considered the current target database.
Below you may find the steps:
Preparing the New Host
Record the DBID of the source database.
Copy the initialization parameter file from the source database to the new host.
Make sure that all source database backups are available to the new host. Do not connect to the recovery catalog.
Restoring and Recovering on the New Host
Configure environment variables on the new host.
Connect to the new target database with NOCATALOG.
Set the DBID.
Start the instance with NOMOUNT.
Restore the SPFILE from backup.
Shut down the new instance.
Edit the PFILE.
Start the instance with NOMOUNT (again).
Create an RMAN RUN block to restore the control file.
Create an RMAN RUN block to restore and recover the database.
Open the database with RESETLOGS.
Regards,

Similar Messages

RMAN backup restoring to new server help!

I'm using Oracle 8.1.7. The production database was copied (datafiles, controlfile etc) to a NEW server that I'm trying to set up as a development DB. I take full database backups using RMAN from the production server, and I want to restore them on the development server. I think I somehow have to specify the filename/location of the backup file but I can't seem to figure out how to do it.
I am not using a recovery catalog.
Any help is appreciated.

If you restore the controlfile backup to the development server RMAN
will "read" the expected location of the backupsets from there.
In 8i you cannot use the CATALOG command so you have to copy all
the backupsets to the same path on the development server as on the
production server.
Once you have your init.ora and controlfiles in place (and created the
expected target directory structure for the database and redolog files),
you can use STARTUP MOUNT and thene RESTORE from RMAN.
I believe that you should be able to rename files in 8i RMAN as well.
If not, you'll have to stick to restoring to the same location.
The key thing is that the controlfile records the "location" of the RMAN backupsets
and the "location" where datafiles are to be restored to.

RMAN backup restore on new server with CATALOG START WITH

Hello Experts,
CATALOG START WITH
is this required RMAN in catalog mode ?
reference of post
Disastor Recovery with RMAN : Restore backup on new separate Server
Edited by: 873142 on Jul 18, 2011 9:27 PM

If you use a recovery catalog and want to duplicate database in a fresh server.
1. connect with the target database.
2. connect with the recovery catalog.
3. connect with the auxiliary database.
4. Run the duplicate command.
Before running the duplicate command copy the backup piece to your fresh server from the target server. Both mount point should be same.
Regards
Asif Kabir
-- mark your helpful post as correct/helpful.

How to restore RMAN hot backup to another database on another server?

I want to know how to restore RMAN hot backup from production server to another database on a testing server.
The hot backup is from a database named PROD on the production server
The database to be restored with the hot backup is TEST on the testing server. There is already a PROD database on the testing server and this PROD database must be kept.
I have read some threads about changing initTEST.ora to PROD to restore such backup but (I think) will not work in my case since I already have a PROD database on the testing server.
The version is 11gR2 on Linux but the compatible parameter is set to 10.2.0.1.0.
Thanks for any help.

Hi,
Since you are on 11g, hope this helps you http://shivanandarao.wordpress.com/2012/04/28/duplicating-database-without-connecting-to-target-database-or-catalog-database-in-oracle-11g/
881656
Handle:     881656
Status Level:     Newbie
Registered:     Aug 25, 2011
Total Posts:     53
Total Questions:      31 (31 unresolved)
Looks like forum is of no help to you. To get better responses, consider closing your threads by providing appropriate points if you feel that they have been answered. Keep the forum clean !!

RMAN & Hot backup cloning taking long time

Dear DBAs,
We are doing both RMAN & Hot backup cloning foe that taking more time to restore data files to TEST instance. scp taking too much time to copy to target server because of its volume of data (1.5 TB) & Mounting the RMAN backups drive on test server and restoring from that drive taking more than 8 hours.
I heard that some companies are using some device to move heavy volume Hot backup copy from source to dest faster for clone the instance easily with in minutes. What is that device name to take hot backup copies from source and restore it in target server.
Test server Specs
Processor 8 cores with 32GB Memory.
Thanks
DBA

Hot backup is not recommanded for the database size more than 1T.
RMAN backup and restore is the only opiton available for a DBA.
Other option is to use EMC Symmentrix/BCV's/Snapshots. EMC uses pair of disks to achive synch the produciton data with test server. read more about EMC symmentrix or ask your storage team.

Rman hot backup

hello
i am using rman hot backup script to take backup database everyday but the problem is it is working but not deleting old backup older than 2 days .
also i have question .. my database is in archive log mode and everyday about 6-7 .arch files generating in my archive directory.
it is not deleting the old files but generating new files everyday so adding up to the space.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string /u03/archive_logs/DEVL
log_archive_dest_1 string
also should i set dest_1 as archive location or just log_archive_dest
whats is the difference.?
my rman script is
RMAN Hot backup.unix script
The RMAN hot backup script rman_backup.sh:
# !/bin/bash
# Declare your environment variables
export ORACLE_SID=DEVL
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target=/ << EOF
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/backup/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/u03/backup/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/u03/backup/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/u03/backup/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
thanks

Ahmer Mansoor wrote:
RMAN never deletes the Backups unless there is a space pressure in the Recovery Area. Instead it marks the Backups as OBSOLETE based on Retention Policy (in your case it is 2 Days),
To confirm it SET DB_RECOVERY_FILE_DEST_SIZE to some smaller value, the RMAN will remove all the Obsolete Backups automatically to reclaim space.Be very careful with this. If you generate a LOT of archivelog files and you exceed this size, on the next archivelog switch your database will hang with "cannot continue until archiver freed". RMAN will not automatically remove anything. RMAN only removes stuff when you program it in your script.
See:
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmconfb.htm#insertedID4 Retention Policy (recovery window or redundancy)
things like:
set retention window and number of copies
crosscheck backup
delete obsolete <-- delete old, redundant, no longer necessary backups/archivelogs
delete expired <-- NOTE: If you manually delete files and do not execute delete expired (missing file), the DB_RECOVERY_FILE_DEST_SIZE remains the same. So, you can clean out the space and oracle will still say the location is "full".
Understand that if you also set this parameter too small and your backup recovery window/redundancy are incorrectly set, you can also exhaust the "logical" space of this location again, putting your database at risk. Your parameter could be set to 100G on a 400G file system and even though you have 300G available, Oracle will see the limit of this parameter.
My suggestion, get in a DEV/TEST environment and test to see how to best configure your environment for RMAN database backups/control file, archivelog backups also taking into consideration OS tape backup solutions. I always configure DISK for RMAN backups, then have some other tape backup utility sweep those locations to tape ensuring that I have sufficient backups to reconstitute my database - I also include a copy of the init.ora file, password file as well as the spfile backup in this location.
>
In case of Archivelogs, It is better to create and execute a Purge Job to remove Archivelogs after backup them on tape.I almost agree. I try to keep all archivelogs necessary for recovery from last full backup online. I try to keep a full backup online as well. much faster at restoring stuff instead of trying to locate it on tape.

Hot Backup & Restore Files.

Hi Team ,
I am new to the RMAN. Working on HOT backup & restore operation.
I want to know while taking backup which are the files i.e DataFiles , ControlFiles, Snapshot files , password files & archive log files we needed.
Also same for the restore operation.
Thanks.

RMAN can backup:
Datafile
Controlfile
SPFile
Archivelogs
If you want to backup anything else like ini.ora, password file etc then you have to do it manually.
Daljit Singh

Creating RAC database thru RMAN hot backup

Hi Guys,
I am having ERP PROD database on 2 nodes 116 and 117(RAC) server. We have a scheduled RMAN HOT backup of this database
WE also have ASM implemented.
We have another 2 servers named 36 and 37(RAC and ASM) which has ERP Test Database and the thing is that we want to refresh this
test database using ERP PROD RMAN backup.
Can someone please post the proper steps to restore the RMAN backup to ERP Test database as ASM is alos there.
As it is little urgent for us.
help will be appreciated.
Regards,
Milan Rathod

1. take the backup of production database
rman connect target /
backup as compressed backupset database plus archivelog format '/u01/db/backup/%d_%I_%s_%T';
move the backup to test server (same location /u01/db/backup/ bcoz rman checks for backupset in the same location only)
add the below two lines in the test database-- initTEST.ora file
comment cluster_ parameters in initTEST.ora file
eg:-
DB_FILE_NAME_CONVERT = (+EBAOUATDATADG1/prod/,/u01/db/app/admin/test/)
LOG_FILE_NAME_CONVERT = (+EBAOUATDATADG1/prod/,/u01/db/app/admin/test/)
check the connectivity between prod and test database.
from test
$tnsping PROD
from prod machine
$tnsping TEST
in test server
startup nomount
rman target sys@proddb auxiliary /
duplicate target database to test;
after completion of duplicate/clone step convert the single instance test to rac instance by uncomment the cluster_ parameters in initTEST.ora parameter
startup mount the second node in TEST
ALTER DATABASE ENABLE PUBLIC THREAD 2 ;
alter database open;
hope, this will helps you.
Good Luck

Oracle 10.2.0.3 Databases - Restore to New Server

We will soon be replacing an old server with a new server and I need to restore all Oracle 10.2.0.3 databases to the new server
and ensure Oracle functionality/connectivity with all databases.
I am in the process of testing and need advice and hopefully a 'Step by Step' process I can follow.
I am a systems admin - not an Oracle db admin - so please explain details of any commands I may have to run.
I have already tested once:
ran command prompt: sqplus / as sysdba
SQL>shutdown immediate;
Stopped all Oracle services:
Oracle Database
Oracle Listener
Oracle DBConsole
Installed Oracle 10.2.0.3 on new server
Ensured that the SID and all other Oracle services information matched the old server during installation on the new server.
Stopped all Oracle services on the new server (used the steps above).
Backed-up and test restored to new server.
Enterprise Manager shows: Listener Up Database Instance Down Agent Down
Any help would be appreciated

It would be good to know your operation system. I hope both new and old match or similar.
You can use RMAN to dumplicate you DB so you can follow [Creating a Duplicate Database on a New Host. Doc ID: 388431.1|https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=388431.1]
but a simple file system copy based manual duplication is also possible if new and old OS system is similar...

User hot and Rman hot backup

During user mode hot backup lots of redo gets generated as the entire block is written when any changes are made to a block which is in hot backup mode.But during Rman hot backup less redo are generated why is this so and whatz the logic invloved? and how oracle recovers the file that has been backed up through Rman.
Could you please explain me regarding this in detail it will be really helpful.
kumaresh

From Article Note:76736.1 RMAN FAQ: Recovery Manager -- Frequently Asked
To understand why RMAN does not require extra logging or backup mode,
you must first understand why those features are required for non-RMAN
online backups.
A non-RMAN online backup consists of a non-Oracle tool, such as cp or
dd, backing up a datafile at the same time that DBWR is updating the
file. We can't prevent the tool from reading a particular block at the
exact same time that DBWR is updating that block. When that happens,
the non-Oracle tool might read a block in a half-updated state, so that
the block which is copied to the backup media might only have been
updated in its first half, while the second half contains older data.
This is called a "fractured block". If this backup needs to be restored
later, and that block needs to be recovered, recovery will fail because
that block is not usable.
The 'alter tablespace begin backup' command is our solution for the
fractured block problem. When a tablespace is in backup mode, and a
change is made to a data block, instead of logging just the changed
bytes to the redo log, we also log a copy of the entire block image
before the change, so that we can reconstruct this block if media
recovery finds that this block was fractured. That block image logging
is what causes extra redo to be generated while files are in backup
mode.
The reason that RMAN does not require extra logging is that it
guarantees that it will never back up a fractured block. We can make
that guarantee because we know the format of Oracle data blocks, and we
verify that each block that we read is complete before we copy it to the
backup. If we read a fractured block, we read the block again to obtain
a complete block before backing it up. non-Oracle tools are not able to
do the same thing because they do not know how to verify the contents of
an Oracle data block.
Backup mode has another effect, which is to 'freeze' the checkpoint in
the header of the file until the file is removed from backup mode.
We do this because we cannot guarantee that the third-party backup
tool will copy the file header prior to copying the data blocks.
RMAN does not need to freeze the file header checkpoint because we
know the order in which we will read the blocks, which enables us to
capture a known good checkpoint for the file.

Automating refreshing one system with the rman hot backup copy from another

Hi Apps DBAs,
Right now we have two systems: production (OPEBSN) and production support (FINSUP).
I implemented a cronjob, which can refresh FINSUP every night from the cold backup of production. We shutdown the production system at night.
But our istore on production will go live soon and our production system will run 24*7.
The production is already hot backed up from RMAN.
Is it possible to do the following?
Automating refreshing FINSUP from the RMAN hot backup of OPEBSN?
If it is possible, would you please outline the general idea or give me a reference documentation?
If it is not possible, is there any other way to realize our purpose?
Thank you in advance!
Lily

There is some discussion about this topic in the belwo askTom thread.
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:21934468026100
Sam
http://appstech-sam.blogspot.com

BACKUP FROM OLD SERVER & RESTORE TO NEW SERVER

Hi ,
i have install SAP on New Server (ADM X86) , it has good hardware. that why i want to shiftout from old deveopment Server to new Server . From old server i want to take backup through DB13 and restore through Brtools on new server. backup will be on disk.
please guide me which type of backup should be taken ?
and what is difft b/t whole backup and full backup ?
NEW SERVER with 2 Quard core processor, 24 GB RAM
OS= SOLARIS 10
DB= Oracle 10.2.0.4 with 39 Interim opatch
SAP= Ecc 6.0
Hostname=sapdev
System No.=00
OLD Server(SPARK) WITH 1 Dual Core Processor , 6 GB RAM
OS= SOLARIS 10
DB= Oracle 10.2.0.4 with 39 Interim opatch
SAP= Ecc 6.0
Hostname=devsap
System No.=00
Best Regard
Imran Khan

Hi Imran,
In you have a full backup, using this existing backup further you can take incremental backups. The incremental backup is based on the previous full backup. The full and incremental backups is controlled by RMAN (Recovery manager).
You can take a full backup and restore the same in your new server and later take an incremental backup from your old server and restore it to the new server for all the delta changes made. By this you can make sure that your production data is made consistent in the new server.
If you have sufficient dowtime then, you can take a whole DB backup with redo log files and restore them in your new server.
There is no difference between whole backup and full backup, with respect to the database data.
784118 - System Copy Java Tools
check the OraBrcopy tool in this note. It might help you.
regards,
chandru.

RMAN RESTORE A NEW SERVER

I have a complete backup of the source server and I would like to restore it to target server.
Problem is that on my source server I have the complete backup on "E" Drive.
On My target server I just have C and D Drives.
When I try to run Restore database command I get
RMAN-06023: no backup or copy of datafile 1 found to restore
for all the data files as it is looking for my backups on "E" drive which does not exist on Target Server.
Is there a way I can guide RMAN to look on D: drive when restoring?
Thanks
Edited by: user12180649 on May 16, 2012 8:07 AM

user12180649 wrote:
I have a complete backup of the source server and I would like to restore it to target server.
Problem is that on my source server I have the complete backup on "E" Drive.
On My target server I just have C and D Drives.
When I try to run Restore database command I get
RMAN-06023: no backup or copy of datafile 1 found to restore
for all the data files as it is looking for my backups on "E" drive which does not exist on Target Server.
Is there a way I can guide RMAN to look on D: drive when restoring?
Thanks
Edited by: user12180649 on May 16, 2012 8:07 AMOnce you have your controlfile, you can connect to RMAN, delete all the backup piece, and add the new with the new position.
The syntax is:
delete backup; -- to delete all the backups information
catalog start with 'PATH'; -- to add all the backup piece to the "catalog" that in this case could is in the controlfiles.
Other syntax:
http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta011.htm
Hope this helps.
Nunzio

Rman restore in new server?

My linux machine hardisk has crashed, i am rebuilt entire thing from begining, we have the rman backup & controlfiles & init.ora, pwd file in the tape.
How to rebuild the database from the new catalog. appreciate any body provide a rman step to restore & rebuild...
Adv thanks

>>
Whether i need to create catalog first?. Steps pls
>>
Tell us onething, were was the catalog kept? Was it in the same database? or any other database? or you were using controlfile instead catalog to backup your database?
Lets, catalog is maintained in another database or nocatalog (controlfile) is used to backup.
set oracle_sid
startup nomount
rman target /
run {
allocate channel t1 type 'sbt_tape';
restore controlfile to '<destination>';
sql "alter database mount";
restore database;
recover database;
sql "alter database open resetlogs";
}Jaffar

RMAN Hot Backup Errors.

Hello Everyone
I would appreciate if someone can assist me in resolving a problem. Starting from December of last year, we were able to take daily hot backups of our ORACLE 10g database server successfully with no issues. Presently we have been experiencing a number of errors in the logs, even though the script has not been changed. The main errors are as follows:
RMAN-03009: failure of backup command on t1 channel at 05/08/2007 00:01:19
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
In investigating the errors, it seemed to be associated to the tablespace not being put offline or backup mode cleanly, I assumed this was due to persons working later, so I scheduled the backup for a later time but I still got the same error in the log the following day. Can you assist me in resolving this problem please?

Is the db running in ARCH mode?
Error:     ORA 19602
Text:     cannot backup or copy active file in NOARCHIVELOG mode
Cause:     You tried to copy or backup a file that was not closed cleanly, and
     the database was in NOARCHIVELOG mode. This is not allowed because when
     restored, the file will require redo application before it is usable,
     and redo is not currently being saved beyond the contents of the online
     redo logs.
Action:     Take the tablespace offline clean or close the database and retry the
     copy or backup. Take the tablespace offline clean or close the database
     and retry

RMAN Hot backup Restore in new Server

Similar Messages

Maybe you are looking for