10 Copyright © 2007, Oracle. All rights reserved. Using RMAN Enhancements

Copyright © 2007, Oracle. All rights reserved Objectives After completing this lesson, you should be able to: Describe the new and enhanced RMAN features in Oracle Database 11g Configure archivelog deletion policies Duplicate active databases by using the Oracle network (without backups) Back up large files in multiple sections Create archival backups for long-term storage Manage the recovery catalog—for example, merge multiple catalog versions Describe the use of virtual private catalogs

Copyright © 2007, Oracle. All rights reserved RMAN: New Features Image copies Backup pieces Backup data Data files Flash Recovery Area Auxiliary database Change tracking file Recovery Manager (RMAN) Improved performance by: –Fast incremental backups on physical standby –Improved block media recovery Target database

Copyright © 2007, Oracle. All rights reserved Optimized Backups Increased speed of compression by using the ZLIB algorithm Improved protection by enhanced block corruption detection CONFIGURE COMPRESSION ALGORITHM TO ZLIB;

Copyright © 2007, Oracle. All rights reserved Optimized Backups Optimized undo backup for automatically reduced backup time and storage Flexibility to use VSS-enabled software –Allows the database to participate in snapshots coordinated by VSS-compliant backup management tools and storage products –Database automatically recovered upon snapshot restore via RMAN

Copyright © 2007, Oracle. All rights reserved Optimized Backups Simplified archive log management in a multiple- component environment Increased availability by failover of backup to optional destinations Image copies Backup pieces Backup data Data files Flash Recovery Area Target database Redundant archive log files Archive log files X

Copyright © 2007, Oracle. All rights reserved RMAN: New Features The following pages have more details about: Faster and optimized backup through intrafile parallel backup and restore Simplified active database duplication Simplified archival backups for long-term storage Simplified information infrastructure by merging catalogs Enhanced security by restricting DBA backup catalog access to owned databases “virtual private catalog”

Copyright © 2007, Oracle. All rights reserved RMAN Notes Only

Copyright © 2007, Oracle. All rights reserved Parallel Backup and Restore for Very Large Files Multisection backups of a single file: Are created by RMAN, with your specified size value Are processed independently (serially or in parallel) Produce multipiece backup sets Improve performance of the backup

Copyright © 2007, Oracle. All rights reserved Using RMAN Multisection Backups The BACKUP and VALIDATE DATAFILE commands option: SECTION SIZE [M | K | G] Section 1 Section 2 Section 3 Section 4 Channel 1 Channel 2 Channel 3 Channel 4 One large data file

Copyright © 2007, Oracle. All rights reserved Duplicating a Database With network (no backups required) Including customized SPFILE Via Enterprise Manager or RMAN command line Active source database Destination or AUXILIARY database TCP/IP

Copyright © 2007, Oracle. All rights reserved Active Database Duplication: Selecting the Source

Copyright © 2007, Oracle. All rights reserved Selecting the Destination

Copyright © 2007, Oracle. All rights reserved Customizing Destination Options

Copyright © 2007, Oracle. All rights reserved Choosing Database Configuration

Copyright © 2007, Oracle. All rights reserved Scheduling Job Execution

Copyright © 2007, Oracle. All rights reserved Reviewing the Job

Copyright © 2007, Oracle. All rights reserved Database Duplication: Job Run

Copyright © 2007, Oracle. All rights reserved The RMAN DUPLICATE Command DUPLICATE TARGET DATABASE TO dbtest FROM ACTIVE DATABASE SPFILE PARAMETER_VALUE_CONVERT '/u01', '/u02' SET SGA_MAX_SIZE = '200M' SET SGA_TARGET = '125M' SET LOG_FILE_NAME_CONVERT = '/u01','/u02' DB_FILE_NAME_CONVERT = '/u01','/u02';

Copyright © 2007, Oracle. All rights reserved Creating a Standby Database with the DUPLICATE Command DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE SPFILE PARAMETER_VALUE_CONVERT '/u01', '/u02' SET "DB_UNIQUE_NAME"="FOO" SET SGA_MAX_SIZE = "200M" SET SGA_TARGET = "125M" SET LOG_FILE_NAME_CONVERT = '/u01','/u02' DB_FILE_NAME_CONVERT = '/u01','/u02';

Copyright © 2007, Oracle. All rights reserved Creating Archival Backups with EM

Copyright © 2007, Oracle. All rights reserved Creating Archival Backups with RMAN Specifying the KEEP clause, when the database is online includes both data file and archive log backup sets: List all restore points, known to the RMAN repository: Display a specific restore point: KEEP {FOREVER | UNTIL TIME [=] ' date_string '} NOKEEP [RESTORE POINT rsname] LIST RESTORE POINT ALL; LIST RESTORE POINT 'rsname';

Copyright © 2007, Oracle. All rights reserved Managing Archival Database Backups 1.Archiving a database backup: 2.Changing the status of a database copy: CHANGE COPY OF DATABASE CONTROLFILE NOKEEP; CONNECT TARGET / CONNECT CATALOG CHANGE BACKUP TAG 'consistent_db_bkup' KEEP FOREVER;

Copyright © 2007, Oracle. All rights reserved Managing Recovery Catalogs Managing recovery catalogs: 1.Create the recovery catalog. 2.Register your target databases in the recovery catalog. 3.If desired, merge recovery catalogs. 4.If needed, catalog any older backups. 5.If needed, create virtual recovery catalogs for specific users. 6.Protect the recovery catalog.

Copyright © 2007, Oracle. All rights reserved Notes Only

Copyright © 2007, Oracle. All rights reserved Managing Catalogs: Using EM 3 2 1

Copyright © 2007, Oracle. All rights reserved The IMPORT CATALOG Command 1.Connecting to the destination recovery catalog: 2.Importing metadata for all registered databases: 3.Importing metadata for two registered databases: 4.Importing metadata from multiple catalogs: IMPORT CATALOG IMPORT CATALOG IMPORT CATALOG IMPORT CATALOG NO UNREGISTER; IMPORT CATALOG DBID= , ; CONNECT CATALOG

Copyright © 2007, Oracle. All rights reserved The IMPORT CATALOG Command Notes Page

Copyright © 2007, Oracle. All rights reserved RMAN base catalog Virtual private catalogs (VPC) Enhancing security by restricting access to metadata Databases registered in RMAN catalog Creating and Using Virtual Private Catalogs

Copyright © 2007, Oracle. All rights reserved Using RMAN Virtual Private Catalogs 1.Create an RMAN base catalog: 2.Grant RECOVERY_CATALOG_OWNER to VPC owner: 3a.Grant REGISTER to the VPC owner, or: 3b.Grant CATALOG FOR DATABASE to the VPC owner: RMAN> CONNECT CATALOG RMAN> CREATE CATALOG; SQL> CONNECT AS SYSDBA SQL> GRANT RECOVERY_CATALOG_OWNER to vpcowner RMAN> CONNECT CATALOG RMAN> GRANT REGISTER DATABASE TO vpcowner; RMAN>GRANT CATALOG FOR DATABASE db10g TO vpcowner

Copyright © 2007, Oracle. All rights reserved Using RMAN Virtual Private Catalogs 4a.Create a virtual catalog for 11g clients, or: 4b.Create a virtual catalog for pre-11g clients: 5.Register a new database in the catalog: 6.Use the virtual catalog: RMAN> CONNECT CATALOG RMAN> CREATE VIRTUAL CATALOG; SQL> CONNECT SQL> exec catowner.dbms_rcvcat.create_virtual_catalog; RMAN> CONNECT TARGET / CATALOG RMAN> REGISTER DATABASE; RMAN> CONNECT TARGET / CATALOG RMAN> BACKUP DATABASE;

Copyright © 2007, Oracle. All rights reserved Summary In this lesson, you should have learned how to: Describe the new and enhanced RMAN features in Oracle Database 11g Configure archivelog deletion policies Duplicate active databases by using the Oracle network (without backups) Back up large files in multiple sections Create archival backups for long-term storage Manage recovery catalog—for example, merge multiple catalog versions Describe the use of virtual private catalogs

Copyright © 2007, Oracle. All rights reserved Practice 10: Overview Using RMAN Enhancements This practice covers the following topics: Duplicating an active database Merging catalogs

Copyright © 2007, Oracle. All rights reserved