Rman backup at which node

which should be primary node or satandby node for rman backup

afzal wrote:
thanks
i want to take weekly full backup and daily incremental cumulative backup
i want to keep one week backupYou can delete the 1 week older files by:
find /rman_backup_folder/ -type f -mtime +7 -exec rm -f {} \;So all you need is to take your backups into this folder, and then run the above code weekly (after you take a new full backup). You can use the following configuration to take your backups into a specific directory:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rman_backup_folder/RMAN_%t.%p.BAK'You can examine the backup scripts here: RMAN Scripts
You shouldn't use rman commands such as "delete obsolete" because retention policy will probably do not work for you.
On the other hand, I will suggest you to use a rman catalog to manage your incremental backups, so you can also easily set the retention policy.
Regards
Gokhan

Similar Messages

RMAN backup problems, which one first?

Oracle 11g on Windows 2008Std I've inherited. It has a nightly backup job set in Ent Mgr, the Oracle-suggested disk backup, script:
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA\$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA\$OEM_LEVEL_0' database;
The backup fails every night with log:
allocate channel oem_disk_backup device type disk;
recover
allocated channel: oem_disk_backup
channel oem_disk_backup: SID=154 device type=DISK
Starting recover at 08-JUL-10
Finished recover at 08-JUL-10
no copy of datafile 5 found to recover
no copy of datafile 4 found to recover
no copy of datafile 3 found to recover
no copy of datafile 2 found to recover
no copy of datafile 1 found to recover
Starting backup at 08-JUL-10
input datafile file number=00002 name=C:\ORACLE\ORADATA\UC4\UC4\SYSAUX01.DBF
input datafile file number=00001 name=C:\ORACLE\ORADATA\UC4\UC4\SYSTEM01.DBF
channel oem_disk_backup: specifying datafile(s) in backup set
channel oem_disk_backup: starting incremental level 1 datafile backup set
channel oem_disk_backup: starting piece 1 at 08-JUL-10
input datafile file number=00004 name=C:\ORACLE\ORADATA\UC4\UC4\USERS01.DBF
input datafile file number=00003 name=C:\ORACLE\ORADATA\UC4\UC4\UNDOTBS01.DBF
input datafile file number=00005 name=C:\ORACLE\ORADATA\UC4\UC4\APPWORX1
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
I see the space limit error. The database is defined with flash_recovery_area 2GB. So I should just enlarge the flash_recovery_area to make the backup work. BUT the real puzzler before I go making changes is, this database is in NOARCHIVELOG mode. What I find in the books say don't do incremental backups in NOARCHIVELOG mode; and don't do NOARCHIVELOG unless you don't care much about being able to recover your data. So, not being able to ask the guy who set this up, "Why is it NOARCHIVELOG, especially when set for incremental backups, I pose these here:
1. Switch to ARCHIVELOG?
2. Enlarge flash_recovery_area to get these backups working first?

You can do incremental backups in noarchivelog mode - it's just that the database must be in mount mode. But I agree - unless the data is not important (and if you are taking backups then it seems to be important) I would have the database in archivelog mode.

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.

About RMAN backup !!!!

Dear Friends,
Let my production server running starts from 1st June .
In 15 june , I take the First rman full (or level0) backup using the command :
RMAN> backup database plus archivelog;
In 20 June I take 2nd rman full backup using : RMAN> backup database plus archivelog;
Again in 30 June , I take the Third(3rd) rman full (or level 0) backup using the command :
RMAN> backup database plus archivelog;
And also my rman policy set as :
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
In the above scenario , I have the following questions :
1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?
2) Is the above all RMAN backup make a link between them ?
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?
4) when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backup .what is the actual scenario ......
plz help me to make clear concept about it .......
thx in advance .....

1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many backups of each datafile and control file that RMAN should keep. In other words, if the number of backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete.So as in your case the redundancy is 1 so the 1st and 2nd backup are obsolete.
To check the obsolete backups run
rman> report obsolete;
To delete them
rman> delete obsolete;
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup005.htm#BRBSC400]
Is the above all RMAN backup make a link between them ?I am not very much clear with the question.The RMAN information is stored in the controlfile.You can also create a new recovery catalog and register the target database. The RMAN repository records in the control file will be copied to the new recovery catalog.
when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backupThe 3rd RMAN backup will contain all the information of the DB from the very 1st day.You will get all the information in the 3rd rman backup as its a level 0 or what we say a FULL DATABASE BACKUP.If suppose the 3rd rman backup would have been a incremental backup, then you would have required a full backup, previous to the incremental one, so that after restoring the full backup, you restore the incremental to recover the DB completely.
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/part1.htm#i996723]
[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#BRBSC133]
Forgot to answer the 3rd question
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?well, i am not very much sure , but i think is , if you have the 1st rman backup pieces physically present on the disk, you can catalog it and then use the rman command to restore the data from it of till 1st june.
To catalog the backup pieces use
rman> catalog backuppiece 'filename';
Link: [http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/maint007.htm]
HTH
Anand
Edited by: Anand... on Oct 15, 2008 10:51 AM

Create Data Guard Using ASM Managed RMAN backup

we have an oracle database 11.1.0.7 working on Windows server 2003 (64bit). The storage in ASM managed (same 11.1.0.7). Our total database size is 4TB.
I will have to create a physical standby database (Data Guard) of this instance. Now I am having issues on how to transport my RMAN backup pieces (which is also ASM managed).
I cannot do an over the network RMAN backup because it will take months to complete.
We have external 4 hard disks (2 TB each). But my RMAN backup pieces are ASM in format.
Any ideas on how to easily create a data guard in this set up.

TheAlchemist wrote:
can you provide us any clear steps....Hope you asked for Restoring from backups.
1) Prepare PFILE and put in nomount status.
2) Restore standby controlfile
RMAN> restore standby controlfile from '+DG/...'
3) Mount controlfile
SQL> alter database mount standby database;
4) Restore database.
If you are restoring into another diskgroups, then use as below.
RUN {
SET NEWNAME FOR DATAFILE 1 TO '+Dg1/....';
SET NEWNAME FOR DATAFILE 2 TO "+Dg1/...';
RESTORE DATABASE
If same diskgroup you want to use then, just give RMAN> restore database;
After successful restore
5) Start MRP
SQL> alter database recover managed standby database disconnect from session;

Last SCN in RMAN backups

Hi,
in 10g R2 how to know Last SCN in RMAN backups (to which we can recover) ?
Thank you.

Hi,
try to use the LIST command acorss backupsets or data files as per your need / requirement. Checkfor column
Ckp SCN and time Ckp Time. Based on that you find which is lastest, same works for Archive log too, perhaps check with Next SCN
- Pavan Kumar N
- ORACLE OCP - 9i/10g
https://www.oracleinternals.blogspot.com

RMAN Backup Script not running in cron tab

Hi,
I am having rman backup script which is being executed successfully through shell.
but when scheduled in cron the script is being called but RMAN commands are not getting executed.
i have scheduled cron using oracle user.
Attached below the rman script for taking LEVEL 1 backup
#! /bin/ksh
DATE=`date +%Y-%m-%d`
export ORACLE_SID=ACIDC
export ORACLE_BASE='/home/app/oracle/product/10.2.0'
PATH=$PATH:${ORACLE_HOME}/bin
export PATH
export ULIMIT=unlimited
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/network/lib
export LIBPATH=$LD_LIBRARY_PATH:/usr/lib
export TNS_ADMIN=$ORACLE_HOME/network/admin
cd $ORACLE_HOME/bin
rman TARGET= / << EOF > /oraclebkp/rmanlogs/ACIDC/$DATE.log
backup incremental level 1 database;
report obsolete;
delete noprompt obsolete;
exit;
EOF
exit 0
Attached cron script
SHELL=/bin/sh
PATH=:/usr/ucb:/bin:/usr/bin
10 17 * * 2 /oraclebkp/rmanscripts/rmandclvl1.sh 2>&1 >/oraclebkp/cronlogs/delobs.log
Files delobs.log
and oraclebkp/rmanlogs/ACIDC/$DATE.log are being created but with 0 bytes .
Thanks in Advance
HariPriya,

rman TARGET= / << EOF > /oraclebkp/rmanlogs/ACIDC/$DATE.log Change this line to and try..
$ORACLE_HOME/bin/rman TARGET= / << EOF > /oraclebkp/rmanlogs/ACIDC/$DATE.log

Archive files and rman backup

Hi Experts,
For testing, I creates a testing DB. after that, I delete some archive file from physical side.
testing DB works well.
However, I tyr to back up thsi testing DB. I got below error message
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\Oraclebackup\CLS\exports\RMAN\%U
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
Starting backup at 15-JAN-09
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 01/15/2009 15:18:13
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file D:\test\ARC00001_0675529905.001
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
So How to fix this issue?
That means we can not delete any archive log files that we do not need it.
Otherwise there are a problemwhen we try to backup later
JIm

Hi Jim,
change archivelog all crosscheck ;
will do the trick.
You can purge archive files but do it within rman.
Add a line in your rman backup script which makes backup your database and archive files like this.
delete noprompt copy of archivelog all completed before 'SYSDATE-3';
Regards,
Tycho

Which views have RMAN backup jobs information?

Hi there,
I use EM to schedule the db backup using RMAN.
I can view the jobs in the EM.
But I can not find out which views have RMAN backup jobs information in sqlplus.
like dba_scheduler_jobs.
Your advice will be appreciated.
Thanks,
SZ

Hi,
V$RMAN_STATUS - Shows the success/failure status of all recently completed RMAN jobs.
V$RMAN_OUTPUT
Displays messages reported by an RMAN job in progress
If you want to monitor then go the following :-
Monitoring RMAN Job Progress :- view V$SESSION_LONGOPS.
first Step :-
Before starting the job, create a script file (called, for this example, longops) containing the following SQL statement:
SELECT SID, SERIAL#, CONTEXT, SOFAR, TOTALWORK,
ROUND(SOFAR/TOTALWORK*100,2) "%_COMPLETE"
FROM V$SESSION_LONGOPS
WHERE OPNAME LIKE 'RMAN%'
AND OPNAME NOT LIKE '%aggregate%'
AND TOTALWORK != 0
AND SOFAR <> TOTALWORK
After connecting to the target database and, if desired, the recovery catalog database, start an RMAN job. For example, enter:
RESTORE DATABASE;
While the job is running, start SQL*Plus connected to the target database, and execute the longops script to check the progress of the RMAN job. If you repeat the query while the restore progresses, then you see output such as the following:
SQL> @longops
SID SERIAL# CONTEXT SOFAR TOTALWORK %_COMPLETE
8 19 1 10377 36617 28.34
SQL> @longops
SID SERIAL# CONTEXT SOFAR TOTALWORK % COMPLETE
8 19 1 21513 36617 58.75
Cheers
Pavan Kumar N

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 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 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 in HP Ultrium 3-SCSI(3mn) tape device

Dear All
IS it possible to take online RMAN backup in HP Ultrium 3-SCSI(3mn) tape device?
Note: this is not a tape library, a stand alone tape device.
Thanks & Regards
Quazi Abdur Rab

In RAC, Please note that you can take backup from any node and you can able to restore from any node.
If you taking backup to disk then you must mount the same backup mount on both servers in order to able to backup and restore.
In your case you are taking backup to FRA and from there taking to tape.
The TSM wtih tdop agent is congiured on Node1 and not on Node 2 thats why you are not able to restore from node2.
27029, 00000, "skgfrtrv: sbtrestore returned error"
// *Cause: sbtrestore returned an error. This happens when retrieving a
// backup file during a restore operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
/u01/home/oracle:DBA>
If you restore from FRA or using RMAN both nodes know the backup location and able to restore.
Hope this helps,
Regards
http://www.oracleracexpert.com
Cross platform Transportable tablespace using RMAN
http://www.oracleracexpert.com/2009/10/cross-platform-transportable-tablespace.html
Duplicate RAC Database using RMAN
http://www.oracleracexpert.com/2009/12/duplicate-rac-database-using-rman.html

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 at which node

Similar Messages

Maybe you are looking for