05_backup_JFV4.pptVIP

Managing Backup and Recovery in RAC Objectives After completing this lesson, you should be able to: Configure the RAC database to use ARCHIVELOG mode and the flash recovery area Configure RMAN for the RAC environment Protecting Against Media Failure Archived Log File Configurations RAC and the Flash Recovery Area RAC Backup and Recovery Using EM Configure RAC Recovery Settings with EM Archived Redo File Conventions in RAC Configure RAC Backup Settings with EM Oracle Recovery Manager RMAN provides the following benefits for Real Application Clusters: Can read cluster files or raw partitions with no configuration changes Can access multiple archive log destinations Configure RMAN Snapshot Control File Location The snapshot control file path must be valid on every node from which you might initiate an RMAN backup. Configure the snapshot control file location in RMAN. Determine the current location: You can use a shared file system location or a shared raw device if you prefer: Configure Control File and SPFILE Autobackup RMAN automatically creates a control file and SPFILE backup after BACKUP or COPY: Change default location: Location must be available to all nodes in your RAC database. Channel Connections to Cluster Instances When backing up, each allocated channel can connect to a different instance in the cluster. Instances to which the channels connect must be either all mounted or all open. RMAN Channel Support for the Grid RAC allows the use of nondeterministic connect strings. It simplifies the use of parallelism with RMAN in a RAC environment. It uses the load-balancing characteristics of the grid environment. Channels connect to RAC instances that are the least loaded. RMAN Default Autolocation Recovery Manager autolocates the following files: Backup pieces Archived redo logs during backup Data file or control file copies If local archiving is used, a node can read only those archived logs that were generated on that node. When restoring, a channel c