Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 

 

Oracle Recovery Manager (RMAN) on RAC

Oracle RAC Cluster Tips by Burleson Consulting


Oracle RMAN provides the DBA with a comprehensive backup environment. Using RMAN, a DBA can perform a multitude of backup types. The abilities of RMAN depend entirely on whether a backup catalog is being used or not. A backup catalog is a set of tables stored in an Oracle database that track backup sets, pieces, and databases. If a catalog is not available, RMAN stores the backup data in the control file of the instance against which it is performing the backup.

RMAN also allows a block level backup, where only the changed blocks of a tablespace get backed up. For large databases, the space savings in using a block level backup can be enormous.

RMAN is also critical to Automatic Storage Management (ASM).  Since ASM is critical to GRID operations, RMAN is then critical for GRID based systems. In ASM, RMAN is responsible for tracking the ASM filenames and for performing the deletion of obsolete ASM files. ASM files cannot, however, be accessed through normal operating system interfaces; therefore, RMAN is the preferred means of copying ASM files.  It is also possible to use FTP through XDB, but generally, RMAN will be less complex. It is important to learn to use RMAN first because RMAN is the only method for performing backups of a database containing ASM files.

During conversion to ASM, RMAN is used for moving databases or files into ASM storage.

Using RMAN with the Oracle Enterprise Manager (OEM) allows for the scheduling of backup jobs with automated notification capabilities. Using OEM requires that Oracle Intelligent Agents be running on all RAC nodes. The configuration of Oracle Intelligent Agents can sometimes be complex, and the DBA needs to be careful in the setup of the OEM agents in a RAC environment. Later sections will provide a look at various RMAN scenarios in detail.

Third Party Solutions

Many providers of SAN and NAS storage also provide backup capabilities with their hardware. Complete backups of databases can be maintained with no impact on database operations with the use of shadow volumes or the Third Mirrors, EMC�s Business Continuance Volumes (BCV). Recovery using third party solutions can also be incredibly fast, as these solutions often either mirror the entire database to a second location or provide only for backup of changed blocks.

Backup of RAC Databases

The two major backup modes are cold, where the database is shutdown, and hot, where the database is open and in use. An Oracle DBA can use either of these modes to backup a RAC database. However, the main reason for utilizing Oracle RAC is to provide uninterrupted service to the customer base, so it makes little sense to use a cold backup with RAC because it requires the shutdown of all instances that are using the Oracle database.

The DBA must also ensure that all archive log files from all instances are gathered into the backup set.  If even a single archive log is missed, the integrity of the backup is placed in serious question.

Using RMAN for Backups

The DBA should seriously consider using RMAN for all RAC backups. By following a few simple requirements, a RAC instance can be backed up with little or no human intervention. If GRID and ASM storage are used for storage, RMAN must be for backups.

The RMAN process can only attach to a single RAC instance at any one point in time. The RMAN connection is called a utility connection because it does not perform any of the backup or restore operations itself.  The connection is only an information gathering tool for RMAN.

 
 
 
Get the Complete
Oracle Backup & Recovery Details 

The landmark book "Oracle Backup & Recovery: Expert secrets for using RMAN and Data Pump " provides real world advice for resolving the most difficult Oracle performance and recovery issues. Buy it for 40% off directly from the publisher.
 

 


 

 
��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational