1 / 37

RMAN Backups

RMAN Backups. Objectives. After completing this lesson, you should be able to do the following: Identify types of RMAN specific backups Use the RMAN BACKUP command to create backup sets Back up the control file Back up the the archived redo log files

gitano
Download Presentation

RMAN Backups

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RMAN Backups

  2. Objectives • After completing this lesson, you should be able to do the following: • Identify types of RMAN specific backups • Use the RMAN BACKUP command to create backup sets • Back up the control file • Back up the the archived redo log files • Use the RMAN COPY command to create image copies

  3. RMAN Backup Concepts • Recovery Manager backup is a server-managed backup • Recovery Manager uses Oracle server sessions for backup operations • Can back up entire database, all datafiles in a tablespace, selected datafiles, control files, archived redo log files • Closed database backup • Target database must be mounted (not open) • Includes datafiles, control files, archived redo log files • Open database backup • Tablespaces should not be put in backup mode • Includes datafiles, control files, archived redo log files

  4. Image copy Recovery Manager Backups Copy of datafile 3 Datafile 3 Datafile 3 Control file Copy of control file Control file ArchivedLog file ArchivedLog file Copy of archived log Backup set Datafile 1 Datafile 4 Datafile 3 Controlfile Datafile 1 Datafile 2 Controlfile Datafile 2 Datafile 4 Datafile 3 Backup set 3 Backup set 2 Backup set 1

  5. Backup Sets Datafile 1 Datafile 4 Datafile 1 Datafile 3 Controlfile Datafile 2 Controlfile Datafile 2 Datafile 4 Datafile 3 Backup set 3 Backup set 1 Backup set 2

  6. Characteristics of Backup Sets • The BACKUP command creates backup sets. • Backup sets usually contain more than one file. • Backup sets can be written to a disk or tape. • A restore operation is required to extract files from a backup set. • Datafile backup sets can be incremental or full. • Backup sets do not include never-used blocks.

  7. Set 2 Backup Piece • A backup piece is a file in a backup set. • A backup piece can contain blocks from more than one datafile. Backup set 1 (Logical) Piece 1 Serverprocess(channel) Piece 1 (file) Piece 2 (file) Datafile 1 Datafile 4 Datafile 5 Piece 2 MML Set 1 Backup set 2 (Logical) Serverprocess(channel) Piece 1 (file) Datafile 2 Datafile 3 Datafile 9 MML

  8. Backup Piece Size • Backup piece size can be limited as follows: RMAN> RUN { 2> ALLOCATE CHANNEL t1 TYPE 'SBT' 3> MAXPIECESIZE = 4G; 4> BACKUP 5> FORMAT 'df_%t_%s_%p' FILESPERSET 3 6> (tablespace users); }

  9. The BACKUP Command RMAN> BACKUP 2> FORMAT '/BACKUP/df_%d_%s_%p.bus' 3> DATABASE filesperset = 2; Datafile 1 Datafile 4 Datafile 1 Datafile 3 Controlfile Datafile 2 Controlfile Datafile 2 Datafile 4 Datafile 3 Backup set 1 Backup set 2 Backup set 3

  10. Creating a Backup Set

  11. Multiplexed Backup Sets • Multiplex two or more datafiles into a backup set for tape streaming. filesperset = 3 Backup set Datafile 1 Datafile 1,2,3,1,2,3… Serverprocess(channel) Datafile 2 Tape MML Datafile 3

  12. Parallelization of Backup Sets • Allocate multiple channels, optionally specify filesperset, and include many files. Serverprocess(channel) Backup Set 1 Datafile 1 Datafile 4 Datafile 5 Set 1 MML Backup Set 2 Serverprocess(channel) Datafile 2 Datafile 3 Datafile 9 Set 2 MML Backup Set 3 Serverprocess(channel) Datafile 6 Datafile 7 Datafile 8 Set 3 MML

  13. Duplexed Backup Sets Datafile 1 Datafile 1 Datafile 1 Datafile 2 Datafile 2 Datafile 2 BACKUP1 BACKUP2 Backup set

  14. Backups of Backup Sets Datafile 1 Datafile 1 Datafile 2 Datafile 2 Backup set Backup set

  15. Archived Redo Log File Backups • Online redo log file switch is automatic. • Archived log failover is performed. • Back up archived logs that need backing up.

  16. Archived Redo Log Backup Sets • Include only archived redo log files • Are always full backups RMAN> BACKUP 2> FORMAT '/disk1/backup/ar_%t_%s_%p' 3> ARCHIVELOG ALL DELETE ALL INPUT;

  17. Backup Constraints • The database must be mounted or open. • Online redo log backups are not supported. • Only “clean” backups are usable in NOARCHIVELOG mode. • Only “current” datafile backups are usable in ARCHIVELOG mode.

  18. Image Copies Copy of datafile 3 Datafile 3 Datafile 3 ArchivedLog file Copy of archived log ArchivedLog file

  19. Characteristics of an Image Copy • Can be written only to a disk • Can be used for recovery immediately; does not need to be restored • Is a physical copy of a single datafile, archived log, or control file • Is most like an operating system backup (contains all blocks) • Can be part of an incremental strategy

  20. Creating an Image Copy

  21. Image Copy: Example Copy of datafile 3 Datafile 3 Datafile 3 Archivedlog file Archivedlog file Copy of archived log RMAN> COPY 2> DATAFILE '/ORADATA/users_01_db01.dbf' TO 3> '/BACKUP/users01.dbf' tag=DF3, 4> ARCHIVELOG 'arch_1060.arc' TO 5> 'arch_1060.bak';

  22. The COPY Command RMAN> COPY 2> DATAFILE 3 TO '/BACKUP/file3.dbf', 3> DATAFILE 1 TO '/BACKUP/file1.dbf'; Datafile 1 Datafile 1 Controlfiles Redo logfile 1 Image copy Datafile 2 Redo logfile 2 Datafile 3 Datafile 3 Database Image copy

  23. Image Copy Parallelization • One COPY command with many channels RMAN> CONFIGURE DEVICE TYPE disk parallelism 4; 2> COPY # 3 files copied in parallel 3> datafile 1 TO '/BACKUP/df1.dbf', 4> datafile 2 TO '/BACKUP/df2.dbf', 5> datafile 3 TO '/BACKUP/df3.dbf';RMAN> COPY # Second copy command 2> datafile 4 TO '/BACKUP/df4.dbf';

  24. Copying the Whole Database • Mount the database for a whole consistent backup. • Use the REPORTSCHEMA command to list the files. • Use the COPY command or make an image copy of each datafile. • Use the LISTCOPY command to verify the copies.

  25. Making Incremental Backups • Full backups contain all datafile blocks. • Differential incremental backups contain only modified blocks fromlevel n or lower. • Cumulative incrementalbackups contain only modified blocks fromlevel n-1 or lower. Full backup Differential incremental backup Cumulative incremental backup

  26. Differential Incremental Backup: Example • n level backup of all blocks that have changed since the most recent backup at level n or lower. Level 0 Level 0 Lvl Day 2 2 1 2 2 2 0 0 Sun Mon Tue Wed Thu Fri Sat Sun

  27. Cumulative Incremental Backup: Example • n level backup which contains all blocks changed since the previous backup at a level n – 1 or lower Level 0 Level 0 Lvl Day 2 0 2 2C 1 2C 2C 0 Sun Mon Tue Wed Thu Fri Sat Sun

  28. Backup in NOARCHIVELOG Mode • Ensure sufficient space for the backup. • Shut down using the NORMAL or IMMEDIATE clause. • Mount the database. • Allocate multiple channels if not using automatic. • Run the BACKUP command. • Verify that the backup is finished and cataloged. • Open the database for normal use. RMAN> BACKUP DATABASE FILESPERSET 3;

  29. Control File and Server ParameterFile Autobackups • Use the CONFIGURE CONTROLFILEAUTOBACKUP command to enable • When enabled, RMAN automatically performs a back up of the control file and current server parameter file after BACKUP or COPY commands • Back ups also occur after structural changes to the database • Backup is given a default name

  30. Backing Up the Server Parameter File • Automatically backed up when CONFIGURE CONTROLFILE AUTOBACK = ON • Explicitly backed up with BACKUP SPFILE RMAN> BACKUP COPIES 2 DEVICE TYPE sbt SPFILE;

  31. Tags for Backups and Image Copies • Logical name assigned to a backup set or image copy week_full_backup month_full_backup Wednesday_1_backup Datafiles 1,3 Datafile 3 Datafile 1 Datafiles 2,4 Datafile 4 Backup set Backup set Backup set

  32. RMAN Dynamic Views • V$ARCHIVED_LOG • V$BACKUP_CORRUPTION • V$COPY_CORRUPTION • V$DATABASE_BLOCK_CORRUPTION • V$BACKUP_DATAFILE • V$BACKUP_REDOLOG • V$BACKUP_SET • V$BACKUP_PIECE

  33. Monitoring RMAN Backups • Correlate server sessions with channels using the SETCOMMANDID command. • Query V$PROCESS and V$SESSION to determine which sessions correspond to which RMAN channels. • Query V$SESSION_LONGOPS to monitor the progress of backups and copies. • Use an operating system utility to monitor the process or threads.

  34. Miscellaneous RMAN Issues • Abnormal termination of a Recovery Manager job • Detecting physical and logical block corruption • Detecting a fractured block during open backups

  35. Summary • In this lesson, you should have learned how to: • Determine what type of RMAN backups should be taken • Make backups with the RMAN COPY and BACKUP commands • Back up the control file • Back up the archived redo log files

  36. Practice 11 Overview • This practice covers the following topics: • Using Recovery Manager to back up one tablespace datafile and a controlfile • Using Recovery Manager to back up archived log files • Using the RMAN COPY command to create an image copy of a database file

More Related