Rogerio Antonio

 FRA – Flash Recover area   Central location for backup data Logs Archive logs Backups Control file Location a ASM filesystem Allow RMAN Retention policies Parameters DB_RECOVERY_FILE_DEST DB_RECOVERY_DEST_SIZE  How to ..  --- check the flash_recovery_area parameters SQL> show parameter DB_RECOVERY_FILE_DEST NAME                                             TYPE               VALUE ------------------------------------         -----------         ------------------------------ db_recovery_file_dest        ...

ASM - Automatic Storage Management Is a LVM   (Logical Volume Manager) that provides storage abstraction layer The  RDBMS  see only Diskgroups (set of  RAW disks ) Can’t  store binaries on Diskgroups Uses OMF (Oracle Managed Files) Striping Coarse - 1MB allocation units | OLTP | small IO Fine - 128 kb allocation units | Data warehouses | high IO Allows three Redundancy types High Normal External Installed in separated dedicated instance (+ASM) as part of Grid Infrastructure No DB or data dictionary => +ASM instance will be mount never open Where the users are saved?  Password file. Managed by users with SYSASM role Specific processes RBAL - Coordinates disk activity for disk groups (Rebalance Master)  ARBn - Perform the extent movement (Rebalance "Slave") ASMB -  Perform the communication between database and the ASM instance ASM  + RMAN Backup ASM dis...

RMAN> list backup; List of Backup Sets =================== BS Key  Type LV Size       Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 1       Full    281.02M    DISK        00:02:23     21-DEC-12              BP Key: 1   Status: AVAILABLE  Compressed: YES  Tag: TAG20121221T014321         Piece Name: /u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_12_21/o1_mf_nnndf_TAG20121221T014321_8f7d5blz_.bkp   List of Datafiles in backup set 1   File LV Type Ckp SCN    Ckp Time  Name   ---- -- ---- ---------- --------- ----   1       Full 923674   ...

@  backup as compressed backupset database RMAN> backup as compressed backupset database; Starting backup at 21-DEC-12 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=34 device type=DISK channel ORA_DISK_1: starting compressed full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf input datafile file number=00005 name=/u01/app/oracle/oradata/orcl/example01.dbf input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf channel ORA_DISK_1: starting piece 1 at 21-DEC-12 channel ORA_DISK_1: finished piece 1 at 21-DEC-12 piece handle=/u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_12_21...

Retention Policy Setting to specify how long to keep backups Any backups that are not needed to support this recovery window are marked as OBSOLETE and are automatically removed by RMAN if you are using a flash recovery area, if you are no user FRA  the deletion need to be done Manually  Applies to full back up only (level 0) not to level 1 Backups can be automatically retained and managed using one of two methods:  Redundancy :  X number of backups Default !! Recovery Window :  X number of days Recommended by Oracle How to .. RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name ORCL are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP O...

Control file In this post I approach RMAN Configuration, Metadata, Catalogues RMAN always stores its metadata in the target database  control file Whether you use or not the Recovery Catalog Oracle stores metadata into the targer database control file RMAN info on control file is is aged based on CONTROL_FILE_RECORD_KEEP_TIME Single point control ( control file) Does not required another DB Recovery Catalog keep info for long time single point to store many databases RESYNC CATALOG, syncronize the control file metadata with the recover catalog Can store "RMAN backup scripts" in the catalog ... is not possible do it on the control file Recovery Catalog control views RC_* Allow history commands BACKUP .. KEEP UNTIL TIME - keep the backup until point that referrers the configured retention police  BACKUP ... KEEP FOREVER - keep the backup forever, until manually removed REPORT SCHEMA ... AT - show the structure at specific time period Create a RMAN Catalog --1 create tablespace...

Control file RMAN always stores its metadata in the target database  control file Whether you use or not the Recovery Catalog Oracle stores metadata into the targer database control file RMAN info on control file is is agedbased on CONTROL_FILE_RECORD_KEEP_TIME Single point control ( control file) Does not required another DB How to .. [oracle@oracle ~]$ rman target / Recovery Manager: Release 11.2.0.1.0 - Production on Sun Feb 3 17:46:29 2013 Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL (DBID=1272537938) Recovery Catalog keep info for long time single point to store many databases RESYNC CATALOG, syncronize the control file metadata with the recover catalog Can store "RMAN backup scripts" in the catalog ... is not possible do it on the control file Recovery Catalog control views RC_* Allow history commands BACKUP .. KEEP...