RMAN backup node in RAC

We have three node RAC database. I want to know about the backup from which node it runs daily. We schedule the backup using cron. However, is there any view can provide the details of node name from which server the backup runs daily?.

You can try to adapt following scripts http://docs.oracle.com/cd/B19306_01/backup.102/b14191/advmaint.htm#i1008121 to use GV$SESSION/GV$PROCESS with INST_ID column instead of V$SESSION/V$PROCESS but you should run these scripts when RMAN backup is running.

Similar Messages

RMAN backup in ORACLE RAC database

Hi there,
We are using RMAN backup strategy for taking backups from one node(eg.node1).Database is RAC database, version 9.2.3. and OS is Solaris 5.10.
this is the configuration which we use, as follows:
Connecting to Prod.Database using catalog database.
rman catalog=rman/rman@CATDB target=sys/oracle@PRODDB(node 2).
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 30;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanback/_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
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 '/rmanback/CMWPROD_%s.bak';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/oracle@PRODDB(node2)';
CONFIGURE MAXSETSIZE TO 7 G;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/9.2.3/dbs/snapcf_CMWPROD1.f';
As the above config shows RMAN is connecting to PROD DB (node 2). But we need to take backups (datafiles and as well as archive logs) from two nodes (i.e from node 1 and as well as node 2).
Is there any possibility for taking backups from two nodes?
Thanks,
Balu.

Duplicate thread
RMAN configuration in ORACLE RAC database
Khurram

RMAN backup restore from RAC to single instance ASM

Hi,
We are using oracle 11gR2 on AIX 6.1,
We need to restore RMAN backup from RAC to single instance ASM,
Im new to RAC & ASM, What will be the changes
What will be steps involved into it.
Thanks

Hello,
Refer this MOS doc *HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node [ID 415579.1]*
On the Single Instance ASM, you need to specify the diskgroup name for the parameters "control_files, db_create_file_dest"
Handle:      user10745179
Email:      [email protected]
Status Level:      Newbie (5)
Registered:      Feb 24, 2009
Total Posts:      168
Total Questions:      74 (52 unresolved)
Name      Devesh
Location      Mumbai If you feel that your questions have been answered, then please consider closing the threads by providing appropriate points. Please keep the forum clean !!
Regards,
Shivananda

Restoring RMAN Backup from ASM RAC env to Non ASM standalone environment

Hi,
Can anyone please tell me how to restore database using RMAN in a Non ASM environment as my backup file with ASM RAC environment.
i was also looking for some documentation which provides clear explanation about RMAN backup and Restore in ASM and Non ASM environment.
Thanks

You can set the parameter db_file_name_convert in init.ora in you new database with [ID 47325.1]
or
you can set parameter "set newname" in your script rman. [ID 549972.1]
if you have one or two destinations of dbfiles in ASM I seggest to you set parameter db_file_name_convert in init.
example:
db_file_name_convert=('+DGDATA','/u01/oradata/');
remenber you need set log_file_name_convert to.
log_file_name_convert=('+DGREDO','/u01/redo/');
if you use "set newname" commands you need set this lines in your script rman.
set newname for datafile 1 to '/u01/oradata/system01.dbf';
set newname for datafile 2 to '/u01/oradata/undotbs01.dbf';
set newname for datafile 3 to '/u01/oradata/sysaux01.dbf';
set newname for datafile 4 to '/u01/oradata/users01.dbf';
and every datafiles you need set!
Edited by: user1107977 on 21/07/2011 13:47

RMAN Backup script for RAC Database..please suggest

Hi All,
I am currently working on backup policy for RAC Database for my client.The client requirement is to backup while database is shutdown(mount state).I have made below script and could any one please suggest what further things should I need to add with below rman script.
echo "Shutdown Database";date
srvctl stop database -d PROD
srvctl status database -d PROD
echo "Database shutdown on";date
echo "Mount Database ";date
srvctl start instance -d PROD -i "PROD1" -o mount
srvctl status database -d PROD
echo "Start Full Database Backup on";date
$ORACLE_HOME/bin/rman target / nocatalog <<EOF
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '/BACKUP/PRODBKP/%F';
run{
allocate channel c1 device type disk connect 'sys/******@node1-vip:1521/PROD';
allocate channel c2 device type disk connect 'sys/*****@node2-vip:1521/PROD';
backup format '/BACKUP/PRODBKP/PROD_df_%t_%s_%p.bak'(database);
backup format '/BACKUP/PRODBKP/archive_%t_%s_%p.bak' archivelog all;
copy current controlfile to '/BACKUP/PRODBKP/PROD.ctl';
delete noprompt obsolete;
release channel c1;
release channel c2;
exit
EOF
echo "RMAN Backup Finished on";date
echo "Shutdown Database";date
srvctl stop database -d PROD
echo "Start Database";date
srvctl start database -d PROD
srvctl status database -d PROD
Please share your experiences.
Regards

Hi,
Some tweaks for your script.
echo "Shutdown Database";date
srvctl stop database -d PROD
srvctl status database -d PROD
echo "Database shutdown on";date
echo "Mount Database ";date
srvctl start instance -d PROD -i "PROD1" -o mount1. If you database does not shutdown properly , does your script stops the execution of next step?
2. configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '/BACKUP/PRODBKP/%F';(Why you need to configure this every time) ?
It's persistent at db level one time setting (until some other script changes the settings by other dba - else remove that - set the configuration at db level once for all)
- Pavan Kumar N
3.

RMAN backup and Oracle RAC

Hello,
I am newbie with Oracle RAC 11g.
So, I do the following steps to configure RMAN to back up the Oracle RAC:
- Create a tablespace to RMAN User;
- Create the user rman;
- Connect to catalog (the databsae RAC itself);
- Register the database;
- Create the "complete_backup" script on catalog.
So, when I enter on Enterprise Manager, I can see
the "Availability" tab and the "Recovery Catalog Settings" link.
I setup the user rman that I've created with the host RAC1.
Is this really necessary on EM? The "Backup Setting" on EM
is equals to rman (database user) catalog?
When I go to "Schedule backup", I want to use the "complete_backup" script
that I've created. What the best way to schedule this script
to run each sunday, for example?
Thank you.

Hi,
To perfom a test you can create a new single database (RCVCAT) in one of the hosts that you have.
Create a database without any option with and use minimum of memory (don't use memory_target) set pga (50M) and sga(400M).
Create a user RMAN; with Grant connect,resource,recovery_catalog_owner.
Tablespace RCVCAT;
With RMAN connect on RCVCAT and create your catalog.
Levi Pereira

Rman backup and restore from ASM env to Non ASM Environment

Hi,
I got a situation where i need to take RMAN Backup from ASM RAC environment and Restore that back to Non ASM standalone database.
Please let me know the procedure.
would appreciate your quick response

874152 wrote:
Hi,
I got a situation where i need to take RMAN Backup from ASM RAC environment and Restore that back to Non ASM standalone database.
Please let me know the procedure.
would appreciate your quick response
Hi,
You can follow this procedure
1. take the backup to destination host
2. restore spfile and controlfile
3. catalog the backup with command 'catalog start with <location of backup>'
4. use "set newname for datafile" to restore the datafile to non asm disk
5. restore database
6. recover database until point in time
7. rename redolog and tempfile
8. open database with resetlogs
9. remove redolog group from another instance
10. you might want to drop undo tablespace from another instance too
11. task complete
Cheers

RMAN backup uses more space than actual DB size

Hi All,
Yesterday, we have configured the RMAN backup for an RAC db in HP-UX. The total DB size is 82GB
but the RMAN took around 250G space for backup and the backup failed. The oracle db is 10.2.0.1.
$ ls -artl
total 520626852
drwxr-xr-x 23 root root 8192 Feb 10 15:49 ..
drwxr-xr-x 2 root root 96 Feb 10 16:09 lost+found
-rw-rw-rw- 1 oracle dba 290 Feb 10 20:35 backup.log
-rw-rw---- 1 oracle dba 22768640000 Feb 10 21:30 bk_4_1_678488912
-rw-rw---- 1 oracle dba 37469036544 Feb 10 21:40 bk_3_1_678488912
-rw-rw---- 1 oracle dba 28807331840 Feb 10 21:52 bk_5_1_678490229
-rw-rw---- 1 oracle dba 22659448832 Feb 10 22:01 bk_6_1_678490845
-rw-rw---- 1 oracle dba 22775595008 Feb 10 22:14 bk_7_1_678491581
-rw-rw---- 1 oracle dba 19507593216 Feb 10 22:15 bk_8_1_678492076
-rw-rw---- 1 oracle dba 18644811776 Feb 10 22:29 bk_9_1_678492883
-rw-rw---- 1 oracle dba 19040927744 Feb 10 22:31 bk_10_1_678492958
-rw-rw---- 1 oracle dba 18791776256 Feb 10 22:44 bk_11_1_678493794
-rw-rw---- 1 oracle dba 15491096576 Feb 10 22:45 bk_12_1_678493889
-rw-rw---- 1 oracle dba 19860652032 Feb 10 23:00 bk_13_1_678494656
-rw-rw---- 1 oracle dba 20742381568 Feb 10 23:01 bk_14_1_678494701
drwxrwxrwx 3 oracle dba 1024 Feb 10 23:01 .
Why this is happening ? Any bug or i am missing out anything. Please help.
Regards,
Anand.

We are using the belwo scripts,
rman target sys/system nocatalog msglog /backup/backup.log
RUN {
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
INCREMENTAL LEVEL=0
SKIP INACCESSIBLE
TAG hot_db_bk_level0
FILESPERSET 5
FORMAT '/backup/bk_%s_%p_%t'
DATABASE;
sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
filesperset 20
FORMAT '/backup/al_%s_%p_%t'
ARCHIVELOG from time 'sysdate - 1' ;]
#For backing up the archive of the second server.
ALLOCATE CHANNEL ch02 TYPE DISK connect 'sys/system@qicdbr2';
BACKUP
filesperset 20
FORMAT 'al2_%s_%p_%t'
ARCHIVELOG from time sysdate - 1 ;
RELEASE CHANNEL ch02;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
BACKUP
FORMAT '/backup/cntrl_%s_%p_%t'
CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
RMAN> LIST BACKUPSET SUMMARY;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
1 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
2 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
3 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
4 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
5 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
6 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
7 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
8 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
9 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
10 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
11 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
12 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
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 '/oracle/orahome/OraRAC/dbs/snapcf_QICDB1
.f'; # default

Daily database backup runnig on RAC 10.2.0.3 with two Solaris nodes & ASM

Hello,
I'm confused about making daily incremental RMAN backup of a database runnig on Oracle RAC 10.2.0.3 on two Solaris nodes and ASM.
Databases cannot be stopped for backup and point in time recovery is needed.
Please correct me if I am doing wrong:
1) Backup must be Weekly database Level 0 and Daily database Level 1 is appropriate.
2) Is best to use a Flash Recovery Area (FRA) - I've setup one on a separate ASM volume. I have enough space to do the backup on FRA.
3) I am confused about the number channels I need to use. Do I need to use separate RMAN backup channels for each node or I can just leave the default:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
4) Below are the RMAN scripts I plan to use for
- Weekly database backup Level 0:
#!/usr/bin/ksh
echo BACKUP FULL: $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append
$ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
run {
backup incremental level 0 database TAG bkp_level0_200906010;
SQL 'alter system archive log current';
backup archivelog all;
delete noprompt obsolete;
exit;
eof
- Daily database backup Level 1:
#!/usr/bin/ksh
echo BACKUP INCREMENTAL: $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append
$ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
run {
backup incremental level 1 database TAG bkp_level1_20090611;
SQL 'alter system archive log current';
backup archivelog all;
delete noprompt obsolete;
exit;
eof
I'm I doing things wrong?

Show also the parameter I have set for RMAN:
node1:oracle$ rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Tue Jun 9 23:46:05 2009
connected to target database: ORCL (DBID=1198388159)
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 7;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
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/oracle/product/10gr2/db/dbs/snapcf_orcl1.f'; # default
Showing some instance parameters on node1:
SQL> show parameter recovery;
NAME                                 TYPE        VALUE
db_recovery_file_dest                string      DGFRA+
db_recovery_file_dest_size           big integer 300G
recovery_parallelism                 integer     0
SQL> show parameter archive;
NAME                                 TYPE        VALUE
archive_lag_target                   integer     0
log_archive_config                   string
log_archive_dest                     string
log_archive_dest_1                   string
log_archive_dest_10                  string      location=use_db_recovery_file_
dest
log_archive_dest_2                   string
log_archive_dest_3                   string
log_archive_dest_4                   string
log_archive_dest_5                   string
log_archive_dest_6                   string
NAME                                 TYPE        VALUE
log_archive_dest_7                   string
log_archive_dest_8                   string
log_archive_dest_9                   string
log_archive_dest_state_1             string      enable
log_archive_dest_state_10            string      enable
log_archive_dest_state_2             string      enable
log_archive_dest_state_3             string      enable
log_archive_dest_state_4             string      enable
log_archive_dest_state_5             string      enable
log_archive_dest_state_6             string      enable
log_archive_dest_state_7             string      enable
NAME                                 TYPE        VALUE
log_archive_dest_state_8             string      enable
log_archive_dest_state_9             string      enable
log_archive_duplex_dest              string
log_archive_format                   string      %t_%s_%r.dbf
log_archive_local_first              boolean     TRUE
log_archive_max_processes            integer     2
log_archive_min_succeed_dest         integer     1
log_archive_start                    boolean     FALSE
log_archive_trace                    integer     0
remote_archive_enable                string      true
standby_archive_dest                 string      ?/dbs/arch

RMAN Backup in RAC

Dear DBAs,
Is there a V$VIEW that maintains information about the node that was used for taking RMAN backup.
I have a 3 node RAC database, and would like to know which node db backup was run from? These are OEM scheduled backup jobs.
Thanks

Hi;
1. There is seeded RMAN forum site:
Forum Home » High Availability » RMAN
2. Please see:
LIST and REPORT Commands in RMAN [ID 114284.1]
http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcviews001.htm
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

RMAN backup in RAC failing with error ORA-19566

Hi all, i have 2 node RAC and i am trying to take rman backup of the database which is in ASM filesystem.
There is a corruption in SYSAUX file and rman is failing to take backup of the sysaux datafile and error thrown at the end like
piece handle=/home/oracle/orabackup/BLOOM_LVL0_20120627_1qnejueh_s58_p1 tag=TAG20120627T185538 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/27/2012 18:56:17
*ORA-19566: exceeded limit of 0 corrupt blocks for file +DATA/bloom/datafile/sysaux.257.775475317*
Then i tried to validate the backup in rman of the datafile sysaux nad fired the following query
SQL> SELECT * FROM v$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
3 32011 1 0 ALL ZERO
3 32049 40 0 ALL ZERO
3 32034 1 0 ALL ZERO
3 28964 1 1399837 LOGICAL
3 32015 2 0 ALL ZERO
and found all the blocks in the table WRH$_SQL_PLAN.
Then dropped the table, and tried to take backup of the database and it is failing again with the same error..
ANY SOLUTION TO TAKE BACKUP OF THE DATABASE.
anyhow we can SET MAXCORRUPT FOR DATAFILE 3 to value, but does this works all time...
Thanks in advance,
TEJAS

Both are good suggestions, but
Osama-mustafa wrote:
RMAN> blockrecover datafile 5 block 2684; -- Fix Eror That ship has already sailed:
TEJAS_DBA wrote:
And Yes this is the first time i am taking backup on the database.And:
Osama-mustafa wrote:
Or Skip Option
Like
RMAN> RUN{
2> SET MAXCORRUPT FOR DATAFILE 1,3 to 1;
3> BACKUP DATABASE;
4> }The OP was aware of this option and hopefully was able to get at least some sort of a backup eventually. But as for the dropped WRH$_SQL_PLAN, TEJAS is, I will use the word "braver" than most. And as often is the case, Dan Morgan offered the only bit of sensible advise.
Open an SR.
Good luck.

RMAN backup on RAC

Hi,
DB=10.2.0.4 OS=RHL (RAC with 2 nodes db01,db02). Following are the types of automated RMAN backups taken on db01.
- OCR
- Voting Disk
- Talespaces Snapshot
- Archivelog (every hour)
- Backup Incremental level 0 (SUNDAY)
-- backup incrementa level 1 (Mon-SAT)
- Autobackup of Control file and SPFILE (CONTROLFILE AUTOBACKUP ON)
Two main questions please. First, are these backups/backup types are enough FOR FULL RESTORE when talking about RMAN backup on RAC environment with 2 nodes? If not please suggest what else I need to backup?
Secondly, backup home location is /rman which I can see on db01 ONLY. This /rman directory I cannot see on db02. My question is that In case of db02 failure can I restore from this /rman directory? or do I need to automate backup schedules also on db02 separately?
[root@db01~]# df -h
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G 2.9G 814M 79% /
/dev/sda3             190M   34M 147M 19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G 137M 3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G 225M 3.5G   6% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G 3.7G 3.8G 50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G 379M 3.4G 11% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G 8.7G 2.6G 78% /oracle
10.10.28.140:/vol/px4cinconso
                       40G 1.4G   39G   4% /inconso_px
/dev/mapper/36001ec9000d5ea810000061349015d98
                      1.3T 551G 665G 46% /rman
[root@db02~]# df -h
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G 887M 2.9G 24% /
/dev/sda3             190M   34M 147M 19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G 137M 3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G 261M 3.5G   7% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G 3.7G 3.8G 50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G 355M 3.4G 10% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G 6.5G 4.8G 58% /oracle
10.10.28.140:/vol/px4cinconso
                       40G 1.4G   39G   4% /inconso_px
[oracle@db01~]$ rman target /
Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: F1 (DBID=1245145263)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
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 '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default
# Script for backup
level0 ()
run {
allocate channel c1 type disk maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
allocate channel c2 type disk maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
backup incremental level 0 tag = weeklyfull database channel c1
plus archivelog tag = ARCH_$TODAY delete all input channel c2;
release channel c1;
release channel c2;
run {
allocate channel c1 type disk;
delete noprompt obsolete;
release channel c1;
}Bundle of thanks.
Regards,
Edited by: 910385 on Feb 24, 2012 3:00 AM

Hi,
THanks alot for your feedback. Makes my life easier :) . But actually I started studying this all subject because of the following error message in the log file. I found out about this error that doesn't seem to harm. Just wait for the job to finish or it will sort out automatically. Here are the lines from the log file.
Fehler in Backuplogs gefunden:/oracle/log/fcp11-backup-2300.log: RMAN-00571:
===========================================================brRMAN-00569: ===============
ERROR MESSAGE STACK FOLLOWS ===============brRMAN-00571:
===========================================================brRMAN-03009: failure of
Control File and SPFILE Autobackup command on c1 channel at 02/08/2012
06:10:41brORA-00230: operation disallowed: snapshot control file enqueue unavailableI studied few important lines from one of my book, Oracle 11g RMAN backup and recovery (Roberg G Freeman) that I am going to write after the following MAIN ISSUE:
Node 1
RMAN> show all;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp11.f'; # default
Node 2
RMAN> show all;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp12.f'; # default
Thing which I just noticed regarding the above RMAN error is that snapcf_fp11.f can be seen on the Node 1 on todays date but snapcf_fp12.f was only on 10th jan.
[oracle@db01dbs]$ ls -lrth
-rw-r----- 1 oracle oinstall 20M Feb 27 15:10 snapcf_fcp11.f
[oracle@db02dbs]$ ls -lrth
-rw-r----- 1 oracle oinstall 20M Jan 10 13:28 snapcf_fcp12.fTHe few lines from the book which I mentioned above are: (Though you might not need to read those lines):
"You need to move the snapshot control file to a shared location if you plan to run backups from more than one node. If you do not move the snapshot control file to a shared file system such as OCFS or an ASM disk group, then you must make sure that the local destination is identical on all nodes."
My question is of course, how to sort out the above log file error. Becuse in our case, backups are run only from one node, and snaphost control file is not being moved to ASM disk groups. Local destination is also same on both the Nodes, isn't it (with different names). Why on Node 2 last snapshot was taken on 10th jan while on Node 1 it is todays date which seems fine.
Control file and SPFILE which I noticed are stored on ASM disk groups also, so being shared between the two Nodes.
(Sanme names/same location for control file and SPFILE on Node 1 and Node 2)
Control file:
+REDO1/fp1/controlfile/current.256.652803827
+DATA1/fp1/controlfile/current.441.652869697
SPFILE:
+DATA1/fp1/spfilefcp1.oraPlease suggest.
Thank you.
Regards,
Edited by: 910385 on Feb 27, 2012 7:43 AM

Best practice for RAC RMAN backup

I have a 10gR2 RAC db that is 3.5TB. It is a 2 node cluster on AIX. Each instance is db1 on node1, and db2 on node2, the "world" database name is db.
Currently we are doing our backup from 1 node of the cluster, specifying that it connect to to db2, so this instance is doing all of the backup work. We allocate 14 channels to back this database up to tape (yes, we have plenty of tape resources, connecting to a tape machine with > 20 physical tape drives). Would it be better to have our rman script connect to the general database db and let the listener decide which instance to send the channel allocation to, or keep all the work on one node.

I seem to remember that when I was reading up on RAC and RMAN a couple of years ago (maybe up to 4 years ago) that there was something about always doing backups from the same node in a RAC configuration i.e. you have logically 'db' in your network configuration and also direct names of 'db1' and 'db2', and you should always use one of 'db1' or 'db2' but never 'db'. And I also mean do not alternate between 'db1' and 'db2'. Pick one of them and always do your backups from that instance.
I think this was to do with things like the database identifier, and the instance identifier too, which RMAN reads and puts into the backup. It also affects things like reading the archive logs, which must be cross mounted to both nodes. I have this feeling that using the same node kept a kind of consistency within the backups, and meant that Oracle was getting all of the block images from one node i.e. from one of the SGAs. If you used both nodes simultaneously you could run into issues with their SGAs being out of sync. I know this does not make much sense, given that RAC is all about keeping the SGAs consistent with each other. But at the end of the day I do remember something about always using one node all the time to do your RMAN backups.
Not sure if these rules hold true if you are using ASM, which itself is shared in a RAC environment.
Things may have moved on since then, but that was still 10g Release 2 documentation, so I would guess it is still true. At the end of the day, it is not the backup that is important, but the recovery. You don't want to create any kind of inconsistent backup that RMAN cannot successfully recover, even though the backup may look good when you create it.
I'd check out the RMAN and RAC documentation further to see if this is supported.
John

Rman backup for rac by oem

Br,Hi,
DB : 10.2 and 11.2
How to schedule rman backup for cluster in OEM?How to schedule without OEM?
If one of the node failed,Is it possible to run in another node automatcially?
How to schduel export/datadump in rac by oem?
Br,
Raj

I Am not using oem, without oem you should write several scripts....
for linux hot backup(archive log enabled):
bck.sh
set ORACLE_SID=mydb
set ORACLE_HOME=....
rman target sys/.... @'.../bck.ora'
bck.ora
run
BACKUP AS COMPRESSED BACKUPSET FORMAT "..../db_%d_%T_%s_%p_%U.bak" INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG DELETE INPUT FORMAT "...../archivelogBackup/arch_%d_%T_%s_%p_%U.bak";
delete force noprompt obsolete redundancy 3;
backup FORMAT '..../ctl_%d_%T_%s_%p_%U' current controlfile spfile;
And create executable job which instance_id=1 and will run your bck.sh script and create schedule for this job, when first node will down you must change instance_id attribute to second one, and be sure that all backup paths exists in all nodes.
Ramin Hashimzade

How to RMAN backup in RAC with OCFS

hi,
Iam using RAC 10.2.0 in windows 2003 server with OCFS .. i want to take backup using RMAN utility. can any sugest me how take RMAN backup..
Thanks
harish

The only real consideration in RMAN on RAC is a one-off configuration issue as to whether the snapshot controlfile is written to the shared disk or not (it needs to be on the shared disk, or on a location that is common to all nodes, otherwise a backup that includes the control file will fail at the point a node tries to write it to a destination directory that only made sense to another node).
Otherwise, there's not a lot that's different about an RMAN backup in RAC versus non-RAC.
Simple answer, as a result: open a DOS window, type rman target /, then type backup database;

RMAN backup node in RAC

Similar Messages

Maybe you are looking for