RAC Backup

Hi to All,
In my company,I'll backup the database at the servers with RAC.There is one database instance at 2 servers.I scheduled a backup job at one of them,is it enough,or do I have to do the same thing at the other one?
Can you give me information about backup at RAC Servers?
Thanks...

Dear Camelia,
Here are some links:
http://www.comp.dit.ie/btierney/Oracle11gDoc/rac.111/b28254/backup.htm
http://youngcow.net/doc/oracle10g/rac.102/b14197/backup.htm#i443637
Regards,
Francisco Munoz Alvarez

Similar Messages

Oracle 11gR2 RAC Backup & Recovery

I am new to Oracle RAC, I have installed Oracle 11gR2 RAC (2 node) on HP-UX with ASM, configured FRA location on ASM.
Now I would like to configure RMAN backup, Can someone give some idea or document to setup RMAN backup for Oracle 11gR2 RAC.
- Mano

ManoRangasamy wrote:
I am new to Oracle RAC, I have installed Oracle 11gR2 RAC (2 node) on HP-UX with ASM, configured FRA location on ASM.
Now I would like to configure RMAN backup, Can someone give some idea or document to setup RMAN backup for Oracle 11gR2 RAC. There won't be any different settings for RMAN for RAC except for where and how you would be configuring the Archive logs and place your backups. Both, ideally speaking, should be on the shared storage like ASM but there are other combinations also possible. Review the above given links for the same. That should provide a good starting point.
Aman....

RAC Backup of archivelogs in local destinations

Suppose there is 10g RAC Database using RMAN Backups.
Suppose It is a 2 node or 4 node RAC with archivelogs going to local destinations in all of them. What command we require to run to make sure all four node archivelogs are backed up at once ?
Is there such a command ? Or shall we run backup archivelog all command in all 4 nodes ?

two ways to do it:
1 automatic
configure parallelism to 4.
Backup archivelog etc.
This will automagically open a channel on each node and run a backup command.
2 semi-automatic
alllocate channel .... connect to 'sys/<password>@tns4node1'
alllocate channel .... connect to 'sys/<password>@tns4node2'
alllocate channel .... connect to 'sys/<password>@tns4node3'
alllocate channel .... connect to 'sys/<password>@tns4node4'
backup archivelog etc
Note: RMAN is a lot smarter than you seem to suggest in your last line.
Actually, you are handicapping recovery by setting up local archives.
If the destination would have been shared, all 4 nodes would automagically participate in recovery.
You may want to reconsider your archivelog strategy.
Sybrand Bakker
Senior Oracle DBA

RAC backup advice

Hi,
I have running Oracle 11gr2 RAC with R12.0.6 Oracle application. All databases are using ASM disk.
What are the best backup & recovery plan for RAC in ASM for database server?
I'm using RMAN daily backup for Database and Application backup on weekly basis.
thanks

Please refer to "Chapter 7 Managing Backup and Recovery" in (Oracle® Real Application Clusters Administration and Deployment Guide 11g Release 2 (11.2)) manual.
http://www.oracle.com/pls/db112/portal.portal_db?selected=16&frame=
Thanks,
Hussein

RAC backup procedure failover

We have Oracle 11gR2 RAC database on two nodes. We also have a RMAN backup script that works fine, using a recovery catalog database which is located in a town 20km from the data center. The script for database backup works fine, and is started from crontab Job or from Oracle dbconsole (for now it works from crontab). A recovery procedure is checked and everything is working properly.
The problem is that the script runs from the first node in the cluster, and if the node is turned off, backup can't be run. How can we ensure that our script have a failover backup version. We also tried to do the backup over dbconsole but this only works if the node from which to start job was started.
Essentially the question is "How to ensure that our backup works, whether or not both nodes are active"

Hi,
SerPedjasim wrote:
We have Oracle 11gR2 RAC database on two nodes. We also have a RMAN backup script that works fine, using a recovery catalog database which is located in a town 20km from the data center. The script for database backup works fine, and is started from crontab Job or from Oracle dbconsole (for now it works from crontab). A recovery procedure is checked and everything is working properly.
The problem is that the script runs from the first node in the cluster, and if the node is turned off, backup can't be run. How can we ensure that our script have a failover backup version. We also tried to do the backup over dbconsole but this only works if the node from which to start job was started.
Essentially the question is "How to ensure that our backup works, whether or not both nodes are active"Don't use nodes of clusterware to start backup. You can use the host of recovery catalog database which is located in a town 20km.
Move all scripts of rman to host of recovery catalog and configure the scripts in crontab of host of recovery catalog. The RMAN works as client only the backup is always performed on server side.
Create a Service on RAC to RMAN connect (e.g RMAN_BACKUP). The service should run on nodes 1 of the RAC, but is able to run on node 2 or 3 if nodes 1 are not available. (If you use the default service name of RAC (name of database) and you are using parallelism the RMAN can start a session in each node and the backup be perfomed by all nodes at same time, this is not a problem, but you can have perfomance problems on your environment). Because that I recommend create a Service.
http://download.oracle.com/docs/cd/E11882_01/rac.112/e16795/hafeats.htm
Configure a net service name using the local naming method on host of recovery catalog.
If you are using SCAN Feature do this above, if not put all VIP hostnames on Address.
e.g:
RMAN_BACKUP =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = node-scan.oracle.com)(PORT = 1521))
     (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RMAN_BACKUP)
)Regardless of the node that is active your backup will be started if a node is active
This will only work if you are performing online backup. I hope so.
Hope this helps,
Levi Pereira
Edited by: Levi Pereira on Aug 22, 2011 11:27 PM

Help required for RAC backup

Hello Support,
We have Oracle 11g R1 RAC enviornement on Windows 2003 Enterprise.
We want to take full database backup to restore in case of any failure.
We are planning to install Oracle on single instance to different hardware and location having same windows.
I appreciate to have proper steps for analysis please.
Currently what are considering are;
- Shutdown RAC database
- Copy control/datafile/redo log files
- paste to other hardware
- using Oracle configuration manager to create template for the existing RAC database.
please add further steps for anaylsis
Thanks

Copy the Cold Backup.
Startup one instance of the database.
And that's it. You are DONE.
If you want to do a cleaner job you can also
Disable the second instance (thread) and then drop the Redo Log Groups of that thread on the Single Node after you have copied the Cold Backup.
I agree with your customer and disagree with the other posters in this thread. A Cold Backup Restore is much much easier than an RMAN Duplicate.
The documentation, unfortunately, covers scenarios where you delete an ORACLE_HOME and/or a Node from an existing RAC Cluster :
http://download.oracle.com/docs/cd/B28359_01/rac.111/b28254/adddelwin.htm#CHDFAEJB
See the ALTER DATABASE commands : DISABLE INSTANCE and DROP LOGFILE clauses.
http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_1004.htm#i2079942
Do these only the the second database server where you copy the Cold Backup.
Do NOT DO NOT DO NOT DO NOT do anything on the actual RAC environment !!
Hemant K Chitale

Q: Oracle RAC backup

Hi Guys,
I'm new in RAC. I have a Oracle RAC database with 2 nodes. I want to know if it is good/appropriate to backup the 2 nodes instead of 1. Since I believe they both use the same database.
Thanks,
Benjo

>
Currently we are backing up two nodes of the Oracle RAC individually. What is on my mind is to backup only 1 node and that is all.
>
It seems to me that you should first get a clear understanding of what to backup . There is only one database to backup in a RAC, regardless of the number of nodes. If you are happy to connect with RMAN to one node and take a backup there, everything is fine. There is no need to connect to the other node and do the same there.
That is, if you have placed the archivelogs on the shared storage. This is a best practice. If they are on node-local devices, there is actually something node specific to backup. Else there is not.
Kind regards
Uwe
http://uhesse.wordpress.com

RAC Backup using RMAN

Hi Gurus
I want to know what are the reason we need to take a backup of all the instacnes means that why should rman create a channel for all the instances while taking a backup? Since RAC used a shared storage, so we can take a backup from any one instance is more enough right? Please clarfiy me.
Regards
Bathrinath

You need to back up all archive log threads one per instance.
If all of your archived redologs for all threads are on shared storage, as far as I know you don't need multiple channels.
If these threads are on local storage, you must allocate a channel per instance or you won't have a complete backup.
Sybrand Bakker
Senior Oracle DBA

RAC backup with RMAN...put backup on diff file system

hello all,
I have not work a lot on SAN storages. One of my client has implementated 9i RAC. Now he wants to Add two more disk in SAN storage (Implemented RAID). So sun engineers will do this but before this i have to take full database backup(80GB database) throught RMAN. The problem or confussion from my side is that the database is on Sun SAN storage and i have to put the Full database backup taken by RMAN on local hard disk on the node (node 1 of rac). Is the possible since the SAN storage is RAW file system (as i guess) and i am putting the backup on local system.
Please help me out ...i have do this in couple of days..
Please tell me prosedure too to how to change the path of backup in RMAN if above is possible..
Its urgent
Thanks and Regards!!
Pankaj Rawat

Two things:
1) You will not have any problems taking RMAN backup for RAC and raw devices. None of them make your backups any different.
2) Based on your post, you are not very confident in your RMAN skills and this is your real problem. What is a must for you - take the backup, copy it on another machine and try to restore from it. Note, that you should NOT look at your original database during restore or take any files from there (even init.ora or spfile). If you don't have this done and don't have exact procedure - consider your backup as useless. This is a conservative approach but believe me - it's wort it when you SAN engineers screw up your storage. And they warned you. ;-)

RAC RMAN backup

Hello,
i have two node 11gR2 on linux,
and right now i am writing a simple RMAN script to do backup of that database.
I am just not sure if it is prerequest for a multinode RAC that multiple chanels need to be used for this environment, do i need to use/open chanels at all , or
i can just perform rman commands without it ?

Vili Dialis wrote:
Interesting, so in my configuratiom where my backupset location is on the local disk of the node2, i am limited to perform restore only from one node.
Ok,
this would be my command to do two node rac backup,currently without channels and
i left other part of the sctipt,also i would put this in the crontab to execute from mon-fri at 3 in the morning:
backup as COMPRESSED BACKUPSET database FORMAT '/home/oracle/rman/%U' plus archivelog delete input;where i have rman configuration
this :
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;Does this means i am doing every day full compressed backup and i don't backup unused blocks only used,
and every day when cron executes rman, rman overwrites yesterdays backupset with the new one ?
As you all suggested,I am planning to use incremental level 0 ever monday, and incremental diferencial level 1 every day till monday,
so i will propably overwrite that script.
I am woried about the space , so i think infact i will not have enough space to do incremental backups...
But maybe it will be ok because i have
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
so this means that only one day is held in the backupsets, and with the incremental 1 every day ,only update of the backupsets is happening
so usage on the disk for backupsets will every day be almost the same ?IMHO, configure the redundancy policy to atleast 7 days.
backup is very important and essential for recovery in case of failures. no backup no recovery.
oracle RMAN takes only used blocks only.
rman not overrides the existing backup. the backup become obsolete based on the user-defined retention policy, that it is not needed for recovery.
A status of "obsolete" means the backup piece is still available, but it is no longer needed.
no the usage of disk is not same, until you give delete obsolete and release the space.
if you worried about the space, use tape device or external storage to store backups for future restore/recovery.

RMAN to connect to all nodes within the cluster to parallelize backups

Hi,
I wish to configure my RMAN catalog to backup my Production RAC backups. I wish to parallelize my backups to backup database files of different nodes.
Can anyone help me how can it be done?
Regards,
Srini

Hi,
May be you are right. I see my RAC cluster databases grow very fast and some nodes are not really performing well resources wise. So, i may need to parallalize the backups across the nodes.
However, i have another idea of finding the best node and take backup on it. checking with my system admins at this point.
Is there any way RMAN can know if the node went down so that it needs to backup the database on a different node instead of the first node it attempted?
May be this is a different question.
Regards,
srini

What are the RAC DBA daily tasks?

Hello Experts,
What are the RAC DBA daily(routine) tasks?
Thank you.

Hi Friend,
Good Query..
1. Make sure that all database instances are available.
Log into each instance and run daily
2. Checking CRS status
bash-3.00$ ./crs_stat -t
3. Checking Volumes Informations in each instances.
bash-3.00$ df –h
4. Verify success of database backup:
a. RMAN backup/Data Pump Backup/Cold backup
5. Check the Archive Log file locations in each instance
6. Check the Archive Log file location volume sizes in each instance
7. Check Alert Log files (Any ORA_600, oRA_07445 etc..) in each instance
8. Check the Statspack / AWR Report Peak hour reports
9. Check the ASM INSTANCE status in each instance
10. Check disk groups space and limitation
11. Always use EM and ADDM reports for performance health checks and analysis
12. verify the DR sync (if applicable):
13. If DR site is available :
a. Check to determine if latest archive logs have been applied to the database by looking at the alert
log file for the standby(DR) database.
14. Review contention for CPU, memory, network or disk resources:
a. Work with system administrators to develop methods to review contention for these resources.
15. Maintain Complete Database Details (Data Files locations, Control file locations, Redo Log file Locations etc...)
a. If any changes in production database or DR-Site database update manuals.
16. Check OCR and VD backup locations. (If possible take manually OCR and VD backup)
17. Check CRS logs in each instance
18. Check Listener Logs in each instance
19. If you are using RMAN backup, Use both the instances while taking RMAN backup (Multiple Channel allocations in Instances)
20. Weekly restore the RAC backup in Single Instance Database (If RAC setup is not available)
Hope it helps....
Thanks
LaserSoft

RMAN and RAC

Hi all,
Just a query with RMAN and backing up RAC databases.
Reading Metalink Note: 243760.1 (RMAN: RAC Backup and Recovery using RMAN) it suggests that, for a 2 node RAC cluster, 2 channels should be set up, with a connection to each instance. For example,
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node2';
On our systems though, which we inherited, the backup script has 4 channels, but all of them connecting to Instance A). For example,
CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node1';
Now, we have done backup/restoration testing and it all appears to work. I can confirm that both UNDO tablespaces are being backed up, and all archivelogs as well.
I believe the reason why all connections go to the A) node is because the backup storage is locally mounted on the A) node and accessible by the B) node over the private network.
(We use Sun Cluster to mount the backup storage globally between the nodes, with A) being the master/local access and B) having access over the network).
The question is, is there any critical reason why we should connect to each instance, or is it a best practice type thing (e.g. to share the load between nodes) ?
Thanks for you input.

Hi I am trying to register 2 instances in the recovery catalog also. What was the order of operations?
Is this sequesnce correct?
[oracle@vtl-rman ~]$ set ORACLE_SID=fprcprod1
[oracle@vtl-rman ~]$ rman target sys/password@fprcprod1 catalog rman/password@fprccat
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Sep 20 16:32:38 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: FPRCPROD (DBID=1881352426)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1179 1180 FPRCPROD 1881352426 CURRENT 1 18-SEP-07
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK connect 'sys/password@fprcprod1';
new RMAN configuration parameters:
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'sys/password@fprcprod2';
new RMAN configuration parameters:
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> list incarnation;

RMAN for 10g RAC in windows2003

Hello experts,
could any one help to configure RMAN for 10g RAC in windows2003?
thanks,

Hi;
Please check:
RMAN: RAC Backup and Recovery using RMAN [ID 243760.1]
RMAN configuration in ORACLE RAC database
RMAN configuration in ORACLE RAC database
RMAN and RAC
RMAN and RAC
Also check this search:
http://forums.oracle.com/forums/search.jspa?threadID=&q=RMAN+RAC&objID=f384&dateRange=all&userID=&numResults=15
I belive those are will answer your question
Regard
Helios

Rman Backups Failing

Hi All,
we have hot backups of DB scheduled(DB Full backup) thru RMAN for all prod DBs.. but since some days all the backups are failing with similar error.. the sample output of one of the backup job run is given below:
set command id to 'BACKUP_PRSAL41_FUL_091007040002';
echo set on
executing command: SET COMMAND ID
connected to recovery catalog database
connected to target database: PRSAL41 (DBID=3043389771)
input datafile fno=00002 name=/prddb02/u12/oradata/prsal41/undotbs01.dbf
input datafile fno=00007 name=/prddb02/u12/oradata/prsal41/autodba8601dat0101.dbf
input datafile fno=00008 name=/prddb02/u12/oradata/prsal41/autodba8601idx0101.dbf
input datafile fno=00004 name=/prddb02/u12/oradata/prsal41/users01.dbf
channel ORA_DISK_1: starting piece 1 at 10-SEP-07
input datafile fno=00006 name=/prddb02/u12/oradata/prsal41/IIS_INDEX_01.dbf
input datafile fno=00005 name=/prddb02/u12/oradata/prsal41/IIS_DATA_01.dbf
input datafile fno=00003 name=/prddb02/u12/oradata/prsal41/sysaux01.dbf
input datafile fno=00001 name=/prddb02/u12/oradata/prsal41/system01.dbf
channel ORA_DISK_1: specifying datafile(s) in backupset
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: sid=147 devtype=DISK
allocated channel: ORA_DISK_1
Starting backup at 10-SEP-07
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' da
Starting Control File and SPFILE Autobackup at 10-SEP-07
Finished backup at 10-SEP-07
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:25
piece handle=/back01/prsal41/5oiricui_1_1 tag=BACKUP_PRSAL41_FUL_091007040002 comment=NONE
channel ORA_DISK_1: finished piece 1 at 10-SEP-07
Finished Control File and SPFILE Autobackup at 10-SEP-07
piece handle=/back01/prsal41/c-3043389771-20070910-00 comment=NONE
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' ar
Starting backup at 10-SEP-07
current log archived
released channel: ORA_DISK_1
allocated channel: ORA_MAINT_DISK_1
channel ORA_MAINT_DISK_1: sid=147 devtype=DISK
delete noprompt obsolete device type disk;
allocate channel for maintenance type disk;
Additional information: 3
Linux-x86_64 Error: 2: No such file or directory
ORA-27037: unable to obtain file status
ORA-19625: error identifying file /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
RMAN-03002: failure of backup command at 09/10/2007 04:02:55
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 2 days
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Archive Log 275349 18-JUL-07 /hubudorap1/arch01/prsal41/1_132_626515083.arc
Archive Log 275350 18-JUL-07 /hubudorap1/arch01/prsal41/1_133_626515083.arc
Backup Set 383337 15-AUG-07
Backup Piece 383340 15-AUG-07 /back01/prsal41/44ipdr6h_1_1
Backup Set 383353 15-AUG-07
Backup Piece 383362 15-AUG-07 /back01/prsal41/c-3043389771-20070815-00
Backup Set 500971 07-SEP-07
Backup Piece 500974 07-SEP-07 /back01/prsal41/5iirafql_1_1
Archive Log 501025 07-SEP-07 /hubudorap1/arch01/prsal41/1_404_626515083.arc
Backup Set 500987 07-SEP-07
Backup Piece 500996 07-SEP-07 /back01/prsal41/c-3043389771-20070907-00
Archive Log 505768 07-SEP-07 /hubudorap1/arch01/prsal41/1_405_626515083.arc
Archive Log 505769 07-SEP-07 /hubudorap1/arch01/prsal41/1_406_626515083.arc
Archive Log 505770 07-SEP-07 /hubudorap1/arch01/prsal41/1_407_626515083.arc
Archive Log 505771 08-SEP-07 /hubudorap1/arch01/prsal41/1_408_626515083.arc
deleted backup piece
backup piece handle=/back01/prsal41/5iirafql_1_1 recid=178 stamp=632635222
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_404_626515083.arc recid=373 stamp=632635334
archive log filename=/hubudorap1/arch01/prsal41/1_405_626515083.arc recid=374 stamp=632661717
deleted archive log
backup piece handle=/back01/prsal41/c-3043389771-20070907-00 recid=179 stamp=632635329
deleted backup piece
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_408_626515083.arc recid=377 stamp=632718235
Deleted 7 objects
RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
archive log filename=/hubudorap1/arch01/prsal41/1_407_626515083.arc recid=376 stamp=632705451
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_406_626515083.arc recid=375 stamp=632685605
deleted archive log
RMAN-06212: Object Type Filename/Handle
RMAN-06214: Backup Piece /back01/prsal41/c-3043389771-20070815-00
RMAN-06214: Backup Piece /back01/prsal41/44ipdr6h_1_1
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_133_626515083.arc
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06213: --------------- ---------------------------------------------------
release channel;
exit;
released channel: ORA_MAINT_DISK_1
I am not able to detect why the archive log is missing... can anyone help me on this please..?
btw, DBs are oracle 10g R2 non-rac
Backup type : DB Full via RMAN.
Thanks

Hi,
Have you used the CROSSCHECK command?
I am not able to detect why the archive log is missing... can anyone help me on this please..?Could someone removed them through O/S commands (manually) ?
Adith

RAC Backup

Similar Messages

Maybe you are looking for