RMAN backup on RAC

Question

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

Answer 1

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