RMAN Backup testing

Hi,
Daily I am taking the RMAN Full Hot Backup into the Disk and later to tape....so we need to test the whether backups are occuring correctly or not....means..we need to test full RMAN restore and recovery to some other machine.......
How can we acheive this...can anybody sched some light on this....Please it is urgent.....

Hi,
thank you....
I got the following procedure...to test it and restore to some other machine and recover there....and check the production and restored one data...I got the material from RMAN Documents regarding restore and reocover to some other machine with same INSTANCE_NAME and ORACLE_SID and DB_NAME.......
can we do the RMAN clone to some other machine with different oracle_sid,db_name,instance_name using PRODUCTION RMAN FULL HOT BACKUP.....

Similar Messages

RMAN backup testing using networker and NMO

I want to do some RMAN backup testing using networker 7.5 and NMO 5.0. I am doing these testing on VMware. I am not sure whether I need to buy some tape drive for my home PC to do backup testing or I can mimic hard drive as tape drive in VMWARE.
Do you have any idea? any suggestion please?
Thanks..

I think this is not a RMAN/Oracle issue, as soon as you configure networker MML it's up to networker to define the real backup destination behind. Maybe networker has also a 'fake' tape destination,but I don't know this. There's a networker forum:
http://www.tek-tips.com/threadminder.cfm?pid=480
Werner

Testing Rman Backup

Im testing my Rman backup.
We do our backup with the following command:
BACKUP AS COPY DATABASE TAG = 'Full Copy 2007/03/11 19:15:02';
On another machine, im testing the recovery like the following:
rman TARGET / NOCATALOG
startup nomount;
SET DBID my_bd_id;
RESTORE CONTROLFILE FROM '/mnt/jukprod_rman/rman_backup/20070311/c-3976015942-20070311-00';
alter database mount;
RESTORE DATABASE UNTIL TIME "TO_DATE('20070311 21:35:00','YYYYMMDD HH24:MI:SS')" PREVIEW;
Problem:
Rman wants 2 months of archive logs!!
no backup of log thread 1 seq 80017 lowscn 10641963078 found to restore
To
no backup of log thread 1 seq 85592 lowscn 13248466314 found to restore
That is 5575 archive logs that Rman needs. 100 Megs in size.
so Rman needs 557 gig of archive!
Whats wrong here?
How come Rman needs all those archive?
Why would rman need archive older that the backup since we did a backup as copy?
We want full backup with not need older archive logs.

Hi,
I don't think that BACKUP AS COPY is a real backup for future RESTORE command. May be you could use this statement for next commands:
BACKUP DATAFILECOPY
SWITCH DATAFILE TO
For good backup strategy you have to use statement like
BACKUP DATABASE INCREMENTAL LEVEL=0 PLUS ARCHIVELOG DELETE INPUT;
or simply
BACKUP DATABASE.
Than you have many old backups and you would like to restore in point of past
you have to use SET command.
If you use COPY of datafiles you have to do next:
restore spfile;
startup nomount
run{
set newname for_all_datafile_to_copy;
RESTORE CONTROLFILE FROM '/mnt/jukprod_rman/rman_backup/20070311/c-3976015942-20070311-00';
alter database mount;
switch all;
recover database;
open resetlogs;
Sergey

Can not recover table from rman backup

For testing I want to recover deleted table from rman backup.
I have make vm of oracle 11g. the following step i have applied but could not recover the table.
rman> backup database ;
On sqlplus create login as scott/tiger
create table scott.emp1(col1 varchar2(10));
insert into emp1(col1) value('Yasir ') ;
commit ;
select * from emp1 ;
it shows me one row successfully.
Now i have login the sys as sysdba
sqlplus> alter system switch logfile ;
after this i have drop the table .
Now to recover the table i have restored database on same vm.
rman>restore database ;
rman> recover database ;
rman> alter database open ;
on sqlplus i have issued
sqlplus> select * from scott.emp1 ;
table or view does not exist.
any help how to recover the deleted table from rman backup

Hi,
Check this test case
SQL> create table TEST2 as select * from emp;
Table created.
SQL> select count(*) from TEST2;
COUNT(*)
15
SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
TO_CHAR(SYSDATE,'DD-
10-SEP-2013 10:57:05
SQL> alter system switch logfile;
System altered.
SQL> drop table TEST2 purge;
Table dropped.
SQL> shu immediate
[oracle@vnode MYSHELL]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DDTEST (DBID=1667776968, not open)
RMAN> run{
set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
restore database;
recover database;
alter database open resetlogs;
}2> 3> 4> 5> 6>
media recovery complete, elapsed time: 00:00:02
Finished recover at 10-SEP-13
database opened
RMAN> exit
SQL> set lin 200 pages 100
SQL> select count(*) from test2;
COUNT(*)
15
HTH

NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

제품 : RMAN
작성날짜 : 2004-05-20
NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
=======================================================
오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
전략을 세울 수 있다.
1. 백업 화일 최적화 방법 (Backup File Optimization)
백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
된다.
이때 같은 화일이라고 판단하는 기준은 다음과 같다.
* Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
되어야 함.
* Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
SCN 과 time.
* Backup Set: 같은 Backup Set recid 와 stamp.
RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
되어도 화일을 지우게 된다.
RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
않는다.
그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
Note:
자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
예:
CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
2. Backup Optimization에 Retention Policies 적용 하기
Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
REDUNDANCY = 1 이 적용 된다.
a. Recovery Window 를 이용한 Backup Optimization
만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
Window 보다 오래된 데이터 화일을 백업한다.
예를 들면 다음과 같은 조건에서
o Today is February 21.
o The recovery window is 7 days.
o The most recent backup of tablespace tbs2 to tape is January 3.
o Tablespace tbs2 is read-only.
2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
조건을 지키게 된다.
이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
b. Redundancy 를 이용한 Backup Optimization
Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
Redundancy의 갯수를 정한다.
아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
동안 한다고 하자.
Day Action Result Redundant Backup
Monday Take tablespace archive offline clean.
Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
Friday Run BACKUP DATABASE. n/a Tuesday backup.
Saturday Run BACKUP DATABASE. n/a Tuesday backup.
Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
복사하지 않게 된다.
RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
사이클이 진행 된다.
3. RETENTION POLICY NONE vs. DEFAULT
주의 사항:
'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
(REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
제거 하라는 명령이다.
보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
--------------THE END----------------------------------------------

Hi,
Backup optimisation = +- do not copy empty space.
So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
Regards,
Yoann.

Restore RMAN Backup

Dear All,
I am practicing Oracle Restore scenarios on my Oracle 9i database. Once I complete my tests in Oracle 9i I will move up to 10g and then finally to 11g.
Following is my recovery scenario:
1) I did NOT configure Recovery Catalog
2) I would like to restore my databse from a 15 days old backup
3) control_file_record_keep_time is set to 7 days.
4) Backups are on tape.
Can you guys please shed some light on how to I proceed?
- P

In oracle 9i , check , which situation you can perform complete recovery and in which situations you have to select incomplete recovery.
check the notes by Alejandro Vargas, BACKUP AND RECOVERY SCENARIOS
http://www.google.co.in/#hl=en&q=oracle+backup+and+recovery+scenarios&aq=0&aqi=g10&aql=&oq=oracle+backup+and+reco&gs_rfai=&fp=aa24f2b3591f5f42
[PDF]
Backup and Recovery Scenarios - Backup & Recovery Check List
- 4:11am
File Format: PDF/Adobe Acrobat - Quick View
Oracle Support Israel. User Managed Recovery Scenarios And Configuration .... 4. recover automatic database using backup controlfile; ...
static7.userland.com/oracle/gems/.../BackupAndRecoveryChecklist.pdf
refer this, this will helps you.
Can one restore RMAN backups without a CONTROLFILE and RECOVERY CATALOG?_
http://www.orafaq.com/wiki/Oracle_database_Backup_and_Recovery_FAQ#Can_one_restore_RMAN_backups_without_a_CONTROLFILE_and_RECOVERY_CATALOG.3F
Edited by: rajeysh on Jun 20, 2010 6:36 PM

Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

I will explain my scenario below:
We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
Please suggest me the best way forward...
Many Thanks
Nukesh

Hi Asif,
I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
RMAN> list incarnation;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
RMAN> exit
TEST1DB-> rman target sys@MYTEST1
Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: MYTEST (DBID=2433328848, not open)
RMAN> reset database to incarnation 2;
using target database control file instead of recovery catalog
database reset to incarnation 2
RMAN> run {
2> restore database until scn 10000;
3> recover database until scn 10000;
4> alter database open resetlogs;
5> };
Starting restore at 07-NOV-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/07/2010 11:45:18
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
RMAN-01007: at line 0 column 2 file: standard input
RMAN>
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
RMAN> exit
SQL> select name from v$database;
NAME
MYTEST
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>

Oracle 10g Enterprise manager Solaris 9 (Rman backups)

Hi Guys,
I changed the OS and oracle user's password on my database server and OS user on the backup server and since then my rman backups don''t run. What could be the reason because when I click on the Disk Test Backup it says I must supply the Host Credentials
To save the backup settings, supply operating system login credentials to access the target database. and when I do that I get an error
The specified host user is not a member of the operating system DBA group. The host user must be a DBA group member since the database user does not have the SYSDBA role.

Hi,
The specified host user is not a member of the operating system DBA group. The host user must be a DBA group member since the database user does not have the SYSDBA role.Assign DBA group to the newly created oracle user.
This should work
Regards,
X A H E E R

Rman backup 11g rel2

Hello Guys
I was testing rman backup on oracle 11g rel2 , logging time for backup using rman as in 2 ways 1) full database backup
2)full database backup /parallel feature say "section size 200M" in script
i was expecting due to new 11g feature option 2 should complete faster ,but its reverse without using this feature
its running more fast (completing by 4-5 minutes less time)
I also tried taking backup of 1 datafile or 1 tablespace using both the option and also placing backupsets
on different folders/mountpoints ,but result is same
if you had worked on this feature ,please give details what is benefit of using this feature,i can see disadvantage here
Thanks

804719 wrote:
so without section size this operation is not actually parallelYes, it's not parallel for datafile, but it parallel for the entire job.
You can analyze the backup log. It should contains the records about opening several channels simultaneously, for instance:
Starting backup at 26/04/12 23:14:19
channel tape1: starting full datafile backup set
channel tape1: specifying datafile(s) in backup set
input datafile file number=00049 name=/home/oracle/oradata/...
channel tape1: starting piece 1 at 26/04/12 23:14:21
channel tape2: starting full datafile backup set
channel tape2: specifying datafile(s) in backup set
input datafile file number=00050 name=/home/oracle/oradata/...
channel tape2: starting piece 1 at 26/04/12 23:14:22
channel tape3: starting full datafile backup set
channel tape3: specifying datafile(s) in backup set
All within 3 seconds, and working in parallel...

Need help in the RMAN backup

Hi everybody
What are the steps needed if move the RMAN backup to other location in the OS level
(ie) every week i have to move the backup to other location

There are not problem for example:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\comp>set ORACLE_SID=W
C:\Documents and Settings\comp>sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 26 14:53:08 2010
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name:
C:\Documents and Settings\comp>sqlplus "sys/sm as sysdba"
SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 26 14:53:15 2010
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 12
Current log sequence 14
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 125829120 bytes
Fixed Size 1288100 bytes
Variable Size 71305308 bytes
Database Buffers 46137344 bytes
Redo Buffers 7098368 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter databaseop;
alter databaseop
ERROR at line 1:
ORA-00940: invalid ALTER command
SQL> alter database open;
Database altered.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options
C:\Documents and Settings\comp>rman target sys/sm
Recovery Manager: Release 10.2.0.2.0 - Production on Mon Apr 26 14:55:58 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: W (DBID=754336873)
RMAN> backup database;
Starting backup at 26-APR-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=144 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSTEM01.DBF
input datafile fno=00003 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSAUX01.DBF
input datafile fno=00005 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\EXAMPLE01.DBF
input datafile fno=00002 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\UNDOTBS01.DBF
input datafile fno=00004 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 26-APR-10
channel ORA_DISK_1: finished piece 1 at 26-APR-10
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\2010_04_26
\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP tag=TAG20100426T145611 comment=NON
E
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:34
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 26-APR-10
channel ORA_DISK_1: finished piece 1 at 26-APR-10
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\2010_04_26
\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP tag=TAG20100426T145611 comment=NON
E
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
Finished backup at 26-APR-10
RMAN> crossckeck backupset;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "allocate, alter
, backup, beginline, blockrecover, catalog, change, connect, copy, convert, crea
te, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flas
hback, host, {, library, list, mount, open, print, quit, recover, register, rele
ase, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, s
et, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport
, upgrade, unregister, validate"
RMAN-01008: the bad identifier was: crossckeck
RMAN-01007: at line 1 column 1 file: standard input
RMAN> crosscheck backupset;
using channel ORA_DISK_1
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
0_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP recid=1 stamp=717346573
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
0_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP recid=2 stamp=717346669
Crosschecked 2 objects
RMAN> delete expired backupset
2> ;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
1 1 1 1 EXPIRED DISK D:\ORACLE\PRODUCT\10.2.0\FLASH_R
ECOVERY_AREA\W\BACKUPSET\2010_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
2 2 1 1 EXPIRED DISK D:\ORACLE\PRODUCT\10.2.0\FLASH_R
ECOVERY_AREA\W\BACKUPSET\2010_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
0_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP recid=1 stamp=717346573
deleted backup piece
backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
0_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP recid=2 stamp=717346669
Deleted 2 EXPIRED objects
now i copy all backup to c:\db
then
RMAN> catalog start with 'c:\db';
searching for all files that match the pattern c:\db
List of Files Unknown to the Database
=====================================
File Name: C:\db\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
File Name: C:\db\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
Do you really want to catalog the above files (enter YES or NO)? y
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: C:\db\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
File Name: C:\db\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
RMAN> list backupset;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1 Full 592.76M DISK 00:01:26 26-APR-10
BP Key: 4 Status: AVAILABLE Compressed: NO Tag: TAG20100426T145611
Piece Name: C:\DB\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
List of Datafiles in backup set 1
File LV Type Ckp SCN Ckp Time Name
1 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSTEM01.
DBF
2 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\UNDOTBS01
.DBF
3 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSAUX01.
DBF
4 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\USERS01.D
BF
5 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\EXAMPLE01
.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
2 Full 6.80M DISK 00:00:04 26-APR-10
BP Key: 3 Status: AVAILABLE Compressed: NO Tag: TAG20100426T145611
Piece Name: C:\DB\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
Control File Included: Ckp SCN: 947720 Ckp time: 26-APR-10
SPFILE Included: Modification time: 26-APR-10
RMAN>

RMAN backup issue

Oracle 11.2.0.1
Windows 7 Home Premium
RMAN> backup database;
Starting backup at 05-MAR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 05-MAR-12
channel ORA_DISK_1: finished piece 1 at 05-MAR-12
piece handle=E:\APP\NISHA\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_03_05\O1_MF_NCSNF_TAG20120305T122505_7O8RTBXJ_.BKP tag=TAG20120305T122505 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN> 1.What is the problem in above scnerio ?
2.How to take RMAN backup when db is down ?
3.How to take RMAN backup when db is noarchivelog mode ?
Please help me. Thank you.

I am trying to do a full RMAN cold backup and am getting the following :
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
What’s the cause ?
Here’s the example
connected to target database (not started)
Oracle instance started
database mounted Total System Global Area 1610612736 bytes Fixed Size 2056504 bytes
Variable Size 603983560 bytes
Database Buffers 989855744 bytes
Redo Buffers 14716928 bytes using target database control file instead of recovery catalog
allocated channel: backup_disk1
channel backup_disk1: sid=4977 instance=TEST1 devtype=DISK Starting backup at 31-OCT-13
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 31/10/2013 20:18:45
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:45
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:46
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
released channel: backup_disk1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:47
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN>
The cause is simple, the database has not been shutdown cleanly. You will require to restart the database and shutdown again, if in a RAC you will have to shutdown all instances cleanly.
Disabing archive log and attempting to backup the database will demonstrate the cause.
SQL> startup force;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
Database opened.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
SQL>
Now we’ll try again to backup datafile 1.
RMAN> backup datafile 1;
Starting backup at 31-OCT-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 13/10/2013 20:43:34
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
This is simply because we issue a shutdown abort on the instance. However, just preforming a recovery will allow you to backup as required.
SQL> recover database;
Media recovery complete.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:UsersGary>rman target sys/passwd@db11g
Recovery Manager: Release 11.2.0.1.0 – Production on Thu Oct 31 20:44:15 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DB10G (DBID=3002158372, not open)
RMAN> backup datafile 1;
Starting backup at 06-DEC-10using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=125 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=C:APPGARYORACLEPRODUCT10.2.0DB_1ORADATADB10GSYSTEM01.DBF
channel ORA_DISK_1: starting piece 1 at 31-OCT-13
channel ORA_DISK_1: finished piece 1 at 31-OCT-13
piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GBACKUPSET2010_12_06O1_MF_NNNDF_TAG20101206T204423_6HTCR810_.BKP tag=TAG20101206T204423 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 31-OCT-13
Starting Control File and SPFILE Autobackup at 31-OCT-13
piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GAUTOBACKUP2010_12_06O1_MF_S_737066556_6HTCSQVF_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 31-OCT-13
RMAN> exit
Interestingly, even with the recovery performed, we cannot switch back to archivelog mode without a clean shutdown.
SQL> alter database archivelog;
alter database archivelog*
ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> alter database archivelog;
alter database archivelog*
ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
So we’ll startup and shutdown again. You cannot use the force option since that still does not perform a normal shutdown and you’ll get the same error.
SQL> alter database open;
Database altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.

Can rman backups be used to restore to a different server

We are using R12 with 10gr2 database
If i take Rman backups, can they be used to restore on some other test server for cloning and bringing that test server upto date like the production.
I am confues and dont know and This is the only reason i dont use rman for backups, instead take cold backups manually every night as they are used every week to clone some other server for testing purpose
Please advice
Thanks

Hi..
1. Copy the pfile to the new server.
2. startup nomount the database using the pfile.
3. Open a new RMAN session and connect to this database
4. Restore the controlfile, this will bring the database in mount stage
5. Once step 4 is completed, restore and recover the database.
NOTE:-- These are the steps for restoring the database when the RMAN backup pieces are copied to the same location as they are on the main server.If you copy the rman backup to some different location, then you will have to use the CATALOG BACKUPPIECE 'location' command before restoring the database.
Go through [http://download.oracle.com/docs/cd/B10500_01/server.920/a96566/rcmdupdb.htm]
HTH
Anand
Edited by: Anand... on Dec 23, 2008 8:13 PM Added link

Restoring RMAN backup on a different server

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.

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/

RMAN backup slow

Hi,
I have a Production Database (10204) running on HP Unix (B.11.11).
Daily morning 6AM, a full RMAN backup runs. The db size is only around 225GB. But it takes 4.5 hours to complete.
The syntax which I use is given below.
RMAN> run {
     allocate channel ch1 type "sbt_tape";
     allocate channel ch2 type "sbt_tape";
     allocate channel ch3 type "sbt_tape";
send
'NB_ORA_CLIENT=jjcprd04-back.backup.ncsus.jnj.com,NB_ORA_POLICY=JJCPRD04-RMAN';
     backup
     format 'bk_%s_%p_%t'
     (database include current controlfile);
     sql 'alter system archive log current';
     backup
     format 'arch_%d_%s_%p_%t'
     (archivelog all delete input );
Is there a way to increase the speed of this backup? Currently the backup is way too slow as it takes 4.5 hours to copy 225GB of data!
Thanks!

I'll start by stating that backups directly to tape are generally quite slow.
I'd still recommend moving to disk backups though... and just archiving it to a tape...Hi Jony,
You can of course backup to disk. Thats a common solution. But you have to deal with space more than everything. In addition to that backing up to disk does not free you from moving/copying your data - depending on your backup strategy - to a long-term storage.
So you have two different and not conjunct backup operations: the rman backup itself and the job which backups the rman area to another media.
In recovery cases you might end up with RMAN requesting older backupsets which are not on disk anymore. This will most probably lead to recovery failures and manual intervention which is not desirable in recovery scenarios.
Another point is the control of the data flow. Backing up via a MML (i.e. "to tape") does not necessarily mean "to tape". Instead it means "to the backup software" which is responsible for managing the backup data. Common scenarios involve backing up the full backups via SAN directly to tape and backing up the archivelogs or incremental backups over LAN which will be stored by the backup software on a hard disk and later copied and/or moved on to tape. The data flow (to SAN / to disk / whereever) is solely controlled by the backup software.
The advantage here is one continuous backup and restore job. The backup software deals with "where is my saveset located" and requests automatically the needed tapes or disks in recovery scenarios. This makes recoveries far more flexible and comfortable.
Regarding the throughput i have set up a rather large OLTP database ( 12 TB currently) which is backed up with EMC Networker. Full backups are written via SAN directly to tape. The average speed with four LTO-3 drives is approx. 550 MB/s (the tape drives compress the data in hardware; the database itself is text-only and seems rather good compressable). I guess thats not too bad.
you can also compress the BACKUPSETS (this generates a little more CPU but less network IO)He said he is on HP-UX. These kind of CPUs tend to be not that fast. Using compression is an option worth testing but there is another point to test when doing compressed backups: The RESTORE TIME.
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

Best pratices for RMAN backup management for many databases

Dear all,
We have many 10g databases (>40) hosted on multiple Windows servers which are backup up using RMAN.
A year ago, all backup's were implemented through Windows Scheduled Tasks using some batch files.
We have been busy (re)implementing / migrating such backup in Grid Control.
I personally prefer to maintain the backup management in Grid Control, but a colleague wants now to go back to the batch files.
What i am looking for here, are advices in the management of RMAN backup for multiple databases: do you guys use Grid Control or any third-party backup management tool or even got your home-made solution?
One of the discussion topic is the work involved in case that the central backup location changes.
Well... any real-life advices on best practices / strategies for RMAN backup management for many databases will be appreciated!
Thanks,
Thierry

Hi Thierry,
Thierry H. wrote:
Thanks for your reaction.
So, i understand that Grid Control is for you not used to manage the backups, and as a consequence, you also have no 'direct' overview of the job schedules.
One of my concern is also to avoid that too many backups are started at the same time to avoid network / storage overload. Such overview is availble in Grid Control's Jobs screen.
And, based on your strategy, do you recreate a 'one-time' Oracle scheduled job for every backup, or do your scripts create an Oracle job with multiple schedule?
You're very welcome!
Well, Grid Control is not an option for us, since each customer is in a separate infrastructure, and with their own licensing. I have no real way (in difference to your situation) to have a centralized point of control, but that on the other hand mean that I don't have to consider network/storage congestion, like you have to.
The script is run from a "permanent" job within the dba-scheduler, created like this:
dbms_scheduler.create_job(
        job_name        => 'BACKUP',
        job_type        => 'EXECUTABLE',
        job_action      => '/home/oracle/scripts/rman_backup.sh',
        start_date      => trunc(sysdate)+1+7/48,
        repeat_interval => 'trunc(sysdate)+1+7/48',
        enabled         => true,
        auto_drop       => false,
        comments        => 'execute backup script at 03:30');and then the "master-script", determines which level to use, based on weekday from the OS. The actual job schedule (start date, run interval etc) is set together with the customer IT/IS dept, to avoid congestion on the backup resources.
I have no overview of the backup status, run times etc, but have made monitoring scripts that will alert me if/when a backup either fails, or runs for too long. This, in addition with scheduled disaster/recovery tests makes me sleep rather well at night.. ;-)
I realize that there (might be) better ways of doing backup scheduling in your environment, since my requirements are so completely different than yours, but I guess that we all face the same challenges in unifying the environments as much as possible, to minimize the amount of actual work we have to do. :-)
Good luck!
//Johan

RMAN Backup testing

Similar Messages

Maybe you are looking for