Oracle Recovery Manager (RMAN) Best Practices

Backups are a foundation of a complete disaster recovery strategy, yet many database administrators aren't fully aware of RMAN's features and capabilities. I'll share the key skills you need to ensure you're getting the most from RMAN, optimize and tune backups, identify common mistakes DBAs make when setting up backups, and show how to verify that RMAN fully protects a database.

Transcript

1. Oracle RMAN Best Practices RMOUG Training Days 2025 Sean Scott Managing Principal Consultant — Viscosity North America Oracle ACE Director
2. Database Reliability Engineering MAA ⁘ RAC ⁘ RMAN Data Guard ⁘ Sharding ⁘ Partitioning Information Lifecycle Management Exadata & Engineered Systems Database Modernization Upgrades ⁘ Patching ⁘ Migrations Cloud ⁘ Hybrid Automation DevOps ⁘ IaC ⁘ Containers ⁘ Terraform Vagrant ⁘ Ansible Observability AHF ⁘ TFA ⁘ CHA ⁘ CHM
4. www.viscosityna.com @ViscosityNA Oracle on Docker Running Oracle Databases in Linux Containers Free sample chapter: https://oraclesean.com
5. What's Missing From Your RMAN Backup? Tomorrow at 10:40!
6. www.viscosityna.com @ViscosityNA RMAN Best Practices*
7. www.viscosityna.com @ViscosityNA ✅ Turn on Backup Optimization
8. www.viscosityna.com @ViscosityNA Backup Optimization RMAN Best Practices • Allows RMAN to skip backup of offline & read-only data files if: • Their most recent backups are included/after the earliest backup that meets the Retention Policy • The files were not subsequently brought online/made read-write • RMAN skips backup of archivelogs that meet the deletion policy • Optimization off: All archivelogs • Optimization on: Only archivelogs ineligible for deletion • Override with backup ... force
9. www.viscosityna.com @ViscosityNA ✅ Use Block Change Tracking*
10. www.viscosityna.com @ViscosityNA Block Change Tracking RMAN Best Practices • Improves incremental backup performance. • Set on primary or standby • Block Change Tracking file records block changes in a bitmap • Bitmaps are updated with each backup • The bitmap covers the eight most recent backups* • Requires Enterprise Edition license • Use on standby requires an Active Data Guard license
11. www.viscosityna.com @ViscosityNA Block Change Tracking - Bitmap RMAN Best Practices • Level 0 scans the full file and sets the bitmap • Redo activity records block changes to bitmaps in the BCT file • Subsequent incremental backups only scan updated blocks • Consider the 8-backup limit when developing a backup strategy • Level 0 + 7 differential backups will exhaust the bitmap • Any subsequent cumulative backups cannot be optimized • When BCT is enabled, VALIDATE only scans changed blocks
12. www.viscosityna.com @ViscosityNA Block Change Tracking - Space Use RMAN Best Practices • BCT file size is proportional to DB size & number of threads • ~(DB size * number of enabled threads) / 30,000 • File allocation per 300M database size: • Initial = 10M, Next = 10M • For database size <= 300M, BCT = ~10M • For databases from 300M - 600M, BCT = ~20M+ • Internally allocates ~320k/data file • Many small data files can artificially inflate BCT file size
13. www.viscosityna.com @ViscosityNA Block Change Tracking - Considerations RMAN Best Practices • MOS Doc ID 2821967.1 - How to Manage & Evaluate BCT Benefits • Block changes <= 15% between backups • Do NOT tune BCT w/hidden params except: • _bct_bitmaps_per_file: adjust bitmap depth • _disable_primary_bitmap_switch=TRUE: backup @ standby • MOS Doc ID 2836206.1 - BCT Known Issues • BCT files are not backed up/duplicated!
14. www.viscosityna.com @ViscosityNA ✅ Enable Controlfile Autobackup* * And understand what it really does
15. www.viscosityna.com @ViscosityNA Control fi le Backup, Autobackup, and Snapshots RMAN Best Practices • Controlfile backup: Image (bit-for-bit) copy of the control file • Controlfile Autobackup: Backup of the control file and spfile (if used) • Autobackup is NOT a copy of the control file! • Always a full backup set • Can never be duplexed • Controlfile Snapshot: Read-consistent version of the control file • When resynchronizing recovery catalog • When backing up the current control file
16. www.viscosityna.com @ViscosityNA Control fi le Autobackup Behavior RMAN Best Practices • The spfile (if used) is included in control file autobackups • Autobackup OFF & datafile 1 is backed up • RMAN includes the control file and spfile (if used) in the backup • Autobackup ON & datafile 1 is backed up • RMAN creates a separate controlfile autobackup piece • If CONTROLFILE AUTOBACKUP=ON, RMAN skips control file copies • INCLUDE CURRENT CONTROLFILE forces a control file copy
17. www.viscosityna.com @ViscosityNA Control fi le Autobackup Behavior RMAN Best Practices • ON: Controlfile autobackup performed after: • After every BACKUP command • At the end of a RUN block, if the last command was BACKUP • Whenever a BACKUP command in a RUN block is followed by a non- BACKUP command
18. www.viscosityna.com @ViscosityNA Controlfile Autobackup Behavior run { <command ≠ backup> backup ...; } - CF Autobackup run { backup ...; - CF Autobackup <command ≠ backup>; <command ≠ backup>; } - No CF Autobackup!
19. www.viscosityna.com @ViscosityNA Controlfile Autobackup Behavior run { backup database; backup current controlfile; backup archivelog all; } - CF Autobackup run { backup database plus archivelog; } - CF Autobackup backup database; - CF Autobackup 1 backup current controlfile; - CF Autobackup 2 backup archivelog all; - CF Autobackup 3
20. www.viscosityna.com @ViscosityNA Control fi le Autobackup Behavior RMAN Best Practices • ON: Controlfile autobackup performed by: • BACKUP CATALOG, CREATE CATALOG • Add/drop/alter tablespace, datafile, online log • Renaming a file • Add/drop redo log thread • Enable/disable flashback database • 11gR2+: Structural changes grouped into one backup
21. www.viscosityna.com @ViscosityNA Control fi le Autobackup Behavior RMAN Best Practices • OFF: Controlfile backup, then archivelog backup • Restore and mount controlfile • Then, CATALOG backups of archivelogs
22. www.viscosityna.com @ViscosityNA Controlfile Autobackup Location Priority # First priority: run { set controlfile autobackup format=... } # Second priority: RMAN> set controlfile autobackup format=... # Third priority: configure controlfile autobackup format=...
23. www.viscosityna.com @ViscosityNA Control fi le Snapshot RMAN Best Practices • Default location (Linux): • Non-RAC: $ORACLE_HOME/dbs • (RAC): +RECO/$ORACLE_UNQNAME/controlfile • On RAC, location must be available to all instances • Default name: snapcf_${ORACLE_UNQNAME}.f
24. www.viscosityna.com @ViscosityNA HINT: Backup Controlfile & spfile/pfile sql "alter database backup controlfile to '/dir/backup.ctl'"; sql "alter system create pfile='/dir/init.YYYYMMDDHH24MISS.spfile.ora' from spfile"; sql "alter system create pfile='/dir/init.YYYYMMDDHH24MISS.memory.ora' from memory";
25. www.viscosityna.com @ViscosityNA ✅ Increase RMAN Output Retention
26. www.viscosityna.com @ViscosityNA Increase RMAN output retention RMAN Best Practices select * from v$rman_output; select recid, output from v$rman_output; # Default = 7 days configure rman output to keep for 14 days;
27. www.viscosityna.com @ViscosityNA ✅ INCREMENTAL LEVEL 0 🚫 FULL
28. www.viscosityna.com @ViscosityNA Full vs. Incremental Level 0 Backups RMAN Best Practices • Full = Level 0 • Both include every allocated block in backed-up files • Image copies must be Full or Level 0 backups • Level 0 is a special type of Full backup • Full ≠ Level 0 • Full backups can never be part of an incremental strategy • Level 0 can be parents of higher-level incremental backups
29. www.viscosityna.com @ViscosityNA ✅ INCREMENTAL LEVEL 1+ 🚫 BACKUP ARCHIVELOG ALL* * Exclusively/only
30. www.viscosityna.com @ViscosityNA Restore vs. Recover RMAN Best Practices • Restore writes media to disk • Recover applies block changes to media • First, from incremental backups • Then, from archive logs
31. www.viscosityna.com @ViscosityNA ✅ BACKUPSET 🚫 IMAGE COPY* * For "ordinary" backups
32. www.viscosityna.com @ViscosityNA Image Copy vs. Backup Set RMAN Best Practices • Image Copy • Exact, bit-for-bit copy of a file • Cannot be multiplexed during backup, restore • Can be performed outside of RMAN (e.g., using OS commands) • RMAN recognizes external image copies via the CATALOG command • Can only be Full backups • Incremental Level 1+ cannot be image copies • In RMAN, used to instantiate an incremental forever strategy • (...but not for Recovery Appliance)
33. www.viscosityna.com @ViscosityNA Image Copy vs. Backup Set RMAN Best Practices • Backup Set • RMAN-proprietary binary file format • May include multiple data files and be multiplexed • A Backup Set is one or more Backup Pieces • Mandatory for use with Media Managers (tape) • Level 1+ incremental backups must be backup sets • Used for incremental forever strategy on Recovery Appliance
34. www.viscosityna.com @ViscosityNA ✅ RECOVERY WINDOW or REDUNDANCY 🚫 RECOVERY WINDOW and REDUNDANCY
35. www.viscosityna.com @ViscosityNA Retention, Redundancy, Recovery Window: What's the difference? RMAN Best Practices • Retention • A storage policy for all backups • Defined as a Redundancy or Recovery Window • Redundancy and Recovery Window are mutually exclusive! • Recovery Window • How many days back recovery is possible • Redundancy • Number of copies of each file (data, control, Level 0) to keep
36. www.viscosityna.com @ViscosityNA Oracle recommends Redundancy RMAN Best Practices • Recovery Window • The window is the minimum retention • Can cause extreme variation in backup storage requirements • Redundancy • Backup frequency + copies define the effective "recovery window" • Two copies of a weekly level 0 = two week recovery window • More predictable storage requirements
37. www.viscosityna.com @ViscosityNA ✅ DELETE OBSOLETE 🚫 DELETE EXPIRED* * Usually
38. www.viscosityna.com @ViscosityNA Obsolete vs. Expired RMAN Best Practices • Obsolete: Backups no longer required to meet retention policies • No crosscheck is necessary • report obsolete; • delete obsolete; • Expired: Backups not found by a CROSSCHECK command • RMAN won't recognize backups as expired without crosscheck
39. www.viscosityna.com @ViscosityNA Expired Backups RMAN Best Practices • EXPIRED represents the state of a backup in the recovery catalog • It is not definitive or final! • May be caused by: • Media Manager misconfiguration • Device availability • Network/DNS issues • File movement • Rerun crosscheck after resolution to reset state to AVAILABLE
40. www.viscosityna.com @ViscosityNA ✅ Validate backups
41. www.viscosityna.com @ViscosityNA Backup Validation RMAN Best Practices restore database validate; restore database validate check logical; restore archivelog all validate;
42. www.viscosityna.com @ViscosityNA Lesser Known and Misunderstood Features
43. www.viscosityna.com @ViscosityNA How RMAN Manages the Flash Recovery Area (FRA) Lesser Known/Misunderstood Features • Oracle maintains space in FRA automatically • DELETE OBSOLETE|ARCHIVELOG ALL shouldn't be necessary • When archivelogs are in FRA, they may not be deleted. Why? • If space isn't an issue, it's better to leave files than delete them • Specify a sequence or date when deleting manually • Don't obsess too much over free space in FRA when space is mostly: • Archived and/or flashback logs • Incremental Level 1+ backup pieces
44. www.viscosityna.com @ViscosityNA How RMAN Manages the Flash Recovery Area (FRA) Lesser Known/Misunderstood Features • Oracle purges (non-GRP) flashback logs to free space for archive • Yet flashback logs may not be deleted even when space fills! Why? • Default minimum age for purging flashback logs = 60 minutes • Younger flashback logs can't be purged; FRA fills; archiver hangs • Solution: Add space to FRA • Solution: Backup (and/or ship) archivelogs • Solution: Relocate flashback logs outside FRA (23ai) • Solution: Delete GRP to free space
45. www.viscosityna.com @ViscosityNA Backup ... Plus Archivelog Lesser Known/Misunderstood Features • Conventional Wisdom for archivelog backups: Run alter system archive log current beforehand • Operations under BACKUP ... PLUS ARCHIVELOG: alter system archive log current; backup archivelog all; backup <spec>; alter system archive log current; backup archivelog all;
46. www.viscosityna.com @ViscosityNA Backup ... Plus Archivelog without Backup Optimization Lesser Known/Misunderstood Features alter system archive log current; backup archivelog all; backup <spec>; alter system archive log current; backup archivelog all; Backs up all archivelogs Backs up all archivelogs again!
47. www.viscosityna.com @ViscosityNA CONTROL_FILE_RECORD_KEEP_TIME Lesser Known/Misunderstood Features • Control files use reusable, circular record keeping (think redo logs) • CONTROL_FILE_RECORD_KEEP_TIME = the minimum number of days before circular records are eligible for reuse • RMAN records backups in reusable sections • If the oldest record < the keep time, the section expands • If the oldest record => the keep time, it's overwritten
48. www.viscosityna.com @ViscosityNA CONTROL_FILE_RECORD_KEEP_TIME Lesser Known/Misunderstood Features • However, if the number of reusable records > UB4MAXVAL reusable records are overwritten even if records don't meet the keep time • UB4MAXVAL = 4,294,967,295 (Whew!) • CONTROL_FILE_RECORD_KEEP_TIME should be > Retention Policy • If not, backup records may be overwritten!
49. www.viscosityna.com @ViscosityNA CONTROL_FILE_RECORD_KEEP_TIME Lesser Known/Misunderstood Features • NEVER use RMAN if CONTROL_FILE_RECORD_KEEP_TIME = 0 • You may lose backup records! • With or without a Recovery Catalog!
50. www.viscosityna.com @ViscosityNA BACKUP RECOVERY AREA vs. BACKUP RECOVERY FILES Lesser Known/Misunderstood Features • BACKUP RECOVERY AREA: Files in the FRA, including • Full, incremental backup sets, datafile copies • Control file autobackups • Archivelogs (RMAN searches outside FRA for missing archivelogs) • But NOT: • Flashback logs • Current control file • Online redo logs
51. www.viscosityna.com @ViscosityNA BACKUP RECOVERY AREA vs. BACKUP RECOVERY FILES Lesser Known/Misunderstood Features • BACKUP RECOVERY FILES: Recovery files on disk • Regardless of location • Full, incremental backup sets, datafile copies • Control file autobackups • Archivelogs • Backup optimization is used unless FORCE specified
52. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 tag 'test1' database; } BACKUP ... DURATION Lesser Known/Misunderstood Features
53. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial tag 'test2' database; } BACKUP ... DURATION ... PARTIAL Lesser Known/Misunderstood Features
54. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial minimize time tag 'test3' database; } BACKUP ... DURATION ... PARTIAL ... MINIMIZE TIME Lesser Known/Misunderstood Features
55. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial minimize load tag 'test4' database; } BACKUP ... DURATION ... PARTIAL ... MINIMIZE LOAD Lesser Known/Misunderstood Features
56. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial minimize time tag 'not_allowed' database plus archivelog; } 🚫 DURATION ... PLUS ARCHIVELOG: not supported Lesser Known/Misunderstood Features
57. www.viscosityna.com @ViscosityNA run { backup format '/u03/app/oracle/ORCL/backup/%U' tag 'keep_60_days' keep until time 'sysdate + 60' restore point '60DAY' database plus archivelog delete all input; } ✅ KEEP UNTIL: Create backups independent of retention policy Lesser Known/Misunderstood Features
58. www.viscosityna.com @ViscosityNA Set meaningful dates in the RMAN CLI Lesser Known/Misunderstood Features Starting backup at 24-APR-24 export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS' Starting backup at 2024-04-12 14:18:46
59. www.viscosityna.com @ViscosityNA Display commands and spool output Lesser Known/Misunderstood Features # Echo command input: set echo on # Spool output (for scripts) spool log to /tmp/rman.log # Spool output (interactively) rman target / | tee /tmp/rman.log
60. www.viscosityna.com @ViscosityNA Check RMAN syntax Lesser Known/Misunderstood Features # Check syntax: rman checksyntax
61. www.viscosityna.com @ViscosityNA Sets, Pieces and Sections
62. www.viscosityna.com @ViscosityNA Backup Sets and Backup Pieces • A Backup Set is a logical collection of one or more Backup Pieces • A Backup Piece is a physical file generated by a backup • A Multiplexed Backup Set is a backup of multiple database files, eg: • A controlfile autobackup = a Backup Set • A database backup = a Multiplexed Backup Set
63. www.viscosityna.com @ViscosityNA Backup Sets and Backup Pieces • Database file backups are NEVER split across Backup Sets, eg: • Parts of the SYSTEM tablespace cannot be in different Backup Sets • HOWEVER, parts of a tablespace may be in different Backup Pieces, eg • Individual datafiles belonging to a single tablespace • Files that exceed a configuration limit • Files split into Sections
64. www.viscosityna.com @ViscosityNA File Sections • File Sections are a set of contiguous blocks belonging to a file • 100M = 12,800 blocks (when DB_BLOCK_SIZE = 8k) • 100M Sections of a datafile would include: • Blocks 1 - 12,800 (Section 1) • Blocks 12,801 - 25,600 (Section 2) • ...etc. • Section sizes are limits imposed by configurations or users
65. www.viscosityna.com @ViscosityNA Multisection Backups • A Multisection Backup is • ...a Backup Set • ...containing multiple Backup Pieces • ...each containing one or more file sections
66. www.viscosityna.com @ViscosityNA Example Database Schema Report of database schema for database with db_unique_name ORCL List of Permanent Datafiles =========================== File Size(MB) Tablespace RB segs Datafile Name ---- -------- -------------------- ------- ------------------------ 1 1130 SYSTEM YES /u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf 3 1240 SYSAUX NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf 4 760 UNDOTBS1 YES /u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf 5 10240 BIG NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf 7 5 USERS NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf
67. www.viscosityna.com @ViscosityNA MAXSETSIZE, MAXPIECESIZE Tuning Multisection Backups • MAXSETSIZE is a limit on the size of a Backup Set • The default is UNLIMITED • MAXPIECESIZE limits the size of Backup Pieces • The default is UNLIMITED
68. www.viscosityna.com @ViscosityNA MAXSETSIZE < database size produces multiple Backup Sets Tuning Multisection Backups RMAN> backup database; ... channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf ... piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T124956_moopznbv_.bkp channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01 channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf input datafile file number=00007 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf ... piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T124956_moopzofk_.bkp channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
69. www.viscosityna.com @ViscosityNA MAXPIECESIZE UNLIMITED Tuning Multisection Backups RMAN> backup database; ... channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf input datafile file number=00007 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf channel ORA_DISK_1: starting piece 1 at 12-DEC-24 channel ORA_DISK_1: finished piece 1 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T130519_mooqwj8m_.bkp tag=TAG20241212T130519 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15 Finished backup at 12-DEC-24
70. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G Tuning Multisection Backups RMAN> configure channel device type disk maxpiecesize 1g; new RMAN configuration parameters: CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 1 G; new RMAN configuration parameters are successfully stored released channel: ORA_DISK_1
71. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G Tuning Multisection Backups RMAN> backup database; Starting backup at 12-DEC-24 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=23 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf input datafile file number=00007 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf channel ORA_DISK_1: starting piece 1 at 12-DEC-24 channel ORA_DISK_1: finished piece 1 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorfowr_.bkp channel ORA_DISK_1: starting piece 2 at 12-DEC-24 channel ORA_DISK_1: finished piece 2 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorfwwg_.bkp channel ORA_DISK_1: starting piece 3 at 12-DEC-24 channel ORA_DISK_1: finished piece 3 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorg3wl_.bkp channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15 Finished backup at 12-DEC-24
72. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G Tuning Multisection Backups RMAN> list backup summary; List of Backups =============== Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 35 B F A DISK 12-DEC-24 3 1 NO TAG20241212T131429 36 B F A DISK 12-DEC-24 1 1 NO TAG20241212T131444
73. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G Tuning Multisection Backups RMAN> list backupset 35; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 35 Full 2.10G DISK 00:00:14 12-DEC-24 List of Datafiles in backup set 35 ... Backup Set Copy #1 of backup set 35 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ --------------- ---------- --- DISK 00:00:14 12-DEC-24 NO TAG20241212T131429 List of Backup Pieces for backup set 35 Copy #1 BP Key Pc# Status Piece Name ------- --- ----------- ---------- 43 1 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorfowr_.bkp 44 2 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorfwwg_.bkp 45 3 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorg3wl_.bkp
74. www.viscosityna.com @ViscosityNA FILESPERSET Tuning Multisection Backups • FILESPERSET is a limit on the number of files per Backup Set • The default is 64
75. www.viscosityna.com @ViscosityNA FILESPERSET = 2 Tuning Multisection Backups RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK CLEAR; old RMAN configuration parameters: CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 0; old RMAN configuration parameters are successfully deleted RMAN> backup database filesperset 2; Starting backup at 12-DEC-24 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=23 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf channel ORA_DISK_1: starting piece 1 at 12-DEC-24 channel ORA_DISK_1: finished piece 1 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T132420_moos044l_.bkp channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01 ...
76. www.viscosityna.com @ViscosityNA FILESPERSET = 2 Tuning Multisection Backups channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf channel ORA_DISK_1: starting piece 1 at 12-DEC-24 channel ORA_DISK_1: finished piece 1 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T132420_moos0577_.bkp channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07 channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf input datafile file number=00007 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf channel ORA_DISK_1: starting piece 1 at 12-DEC-24 channel ORA_DISK_1: finished piece 1 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T132420_moos0d94_.bkp channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07 Finished backup at 12-DEC-24
77. www.viscosityna.com @ViscosityNA FILESPERSET = 2 Tuning Multisection Backups RMAN> list backup summary; List of Backups =============== Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 37 B F A DISK 12-DEC-24 1 1 NO TAG20241212T132420 38 B F A DISK 12-DEC-24 1 1 NO TAG20241212T132420 39 B F A DISK 12-DEC-24 1 1 NO TAG20241212T132420 40 B F A DISK 12-DEC-24 1 1 NO TAG20241212T132435
78. www.viscosityna.com @ViscosityNA Backup Set 37 Tuning Multisection Backups BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 37 Full 67.98M DISK 00:00:00 12-DEC-24 BP Key: 47 Status: AVAILABLE Compressed: NO Tag: TAG20241212T132420 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T132420_moos044l_.bkp List of Datafiles in backup set 37 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 5 Full 6244578 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_big.dbf
79. www.viscosityna.com @ViscosityNA Backup Set 38 Tuning Multisection Backups BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 38 Full 1003.74M DISK 00:00:00 12-DEC-24 BP Key: 48 Status: AVAILABLE Compressed: NO Tag: TAG20241212T132420 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T132420_moos0577_.bkp List of Datafiles in backup set 38 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 1 Full 6244580 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_system.dbf 4 Full 6244580 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs.dbf
80. www.viscosityna.com @ViscosityNA Backup Set 39 Tuning Multisection Backups BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 39 Full 1.06G DISK 00:00:01 12-DEC-24 BP Key: 49 Status: AVAILABLE Compressed: NO Tag: TAG20241212T132420 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T132420_moos0d94_.bkp List of Datafiles in backup set 39 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 3 Full 6244584 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux.dbf 7 Full 6244584 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_users.dbf
81. www.viscosityna.com @ViscosityNA PARALLELISM Tuning Multisection Backups • PARALLELISM sets the number of channels available to RMAN jobs • Channels create separate Backup Sets
82. www.viscosityna.com @ViscosityNA PARALLELISM = 2 Tuning Multisection Backups RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2; old RMAN configuration parameters: CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; new RMAN configuration parameters: CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET; new RMAN configuration parameters are successfully stored released channel: ORA_DISK_1
83. www.viscosityna.com @ViscosityNA PARALLELISM = 2 Tuning Multisection Backups RMAN> backup database; ... channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf input datafile file number=00007 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf channel ORA_DISK_2: starting full datafile backup set channel ORA_DISK_2: specifying datafile(s) in backup set input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf
84. www.viscosityna.com @ViscosityNA PARALLELISM = 2 Tuning Multisection Backups RMAN> list backup summary; List of Backups =============== Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 41 B F A DISK 12-DEC-24 1 1 NO TAG20241212T134436 42 B F A DISK 12-DEC-24 1 1 NO TAG20241212T134436 43 B F A DISK 12-DEC-24 1 1 NO TAG20241212T134451
85. www.viscosityna.com @ViscosityNA Backup Set 41 Tuning Multisection Backups BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 41 Full 69.00M DISK 00:00:00 12-DEC-24 BP Key: 51 Status: AVAILABLE Compressed: NO Tag: TAG20241212T134436 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T134436_moot64fc_.bkp List of Datafiles in backup set 41 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 5 Full 6245345 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_big.dbf 7 Full 6245345 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_users.dbf
86. www.viscosityna.com @ViscosityNA Tuning Multisection Backups BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 42 Full 2.03G DISK 00:00:02 12-DEC-24 BP Key: 52 Status: AVAILABLE Compressed: NO Tag: TAG20241212T134436 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T134436_moot64fv_.bkp List of Datafiles in backup set 42 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 1 Full 6245347 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_system.dbf 3 Full 6245347 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux.dbf 4 Full 6245347 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs.dbf Backup Set 42
87. www.viscosityna.com @ViscosityNA Tuning Multisection Backups • Database file backups are NEVER split across Backup Sets! • Parts of a tablespace may be in different Backup Pieces • Channels create Backup Sets (since a channel is confined to a file) Therefore, a datafile cannot be backed up by more than one channel and the largest datafile limits backup performance. Right?
88. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G, PARALLELISM = 2 Tuning Multisection Backups RMAN> configure channel device type disk maxpiecesize 1g; new RMAN configuration parameters: CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 1 G; new RMAN configuration parameters are successfully stored released channel: ORA_DISK_1 released channel: ORA_DISK_2
89. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G, PARALLELISM = 2 Tuning Multisection Backups RMAN> backup database; allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=256 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=25 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf input datafile file number=00007 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T140028_moov3wfb_.bkp
90. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G, PARALLELISM = 2 Tuning Multisection Backups channel ORA_DISK_2: specifying datafile(s) in backup set input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf channel ORA_DISK_2: finished piece 1 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T140028_moov3wfs_.bkp channel ORA_DISK_2: finished piece 2 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T140028_moov43pn_.bkp channel ORA_DISK_2: finished piece 3 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T140028_moov4bpq_.bkp
91. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G, PARALLELISM = 2 Tuning Multisection Backups channel ORA_DISK_2: specifying datafile(s) in backup set input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf channel ORA_DISK_2: finished piece 1 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T140028_moov3wfs_.bkp channel ORA_DISK_2: finished piece 2 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T140028_moov43pn_.bkp channel ORA_DISK_2: finished piece 3 at 12-DEC-24 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T140028_moov4bpq_.bkp Database files are NEVER backed up across Backup Sets! Channels create Backup Sets; Therefore, each database file should be backed up within a single channel.
92. www.viscosityna.com @ViscosityNA Section Size
93. www.viscosityna.com @ViscosityNA Section Size • SECTION SIZE enables parallel backups of large files • Normally, database files are backed up • ...serially • ...by a single channel • ...to a single Backup Piece
94. www.viscosityna.com @ViscosityNA SECTION SIZE 2G, PARALLELISM = 8 Section Size RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK CLEAR; old RMAN configuration parameters: CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 1 G; old RMAN configuration parameters are successfully deleted released channel: ORA_DISK_1 released channel: ORA_DISK_2 RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 8; old RMAN configuration parameters: CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET; new RMAN configuration parameters: CONFIGURE DEVICE TYPE DISK PARALLELISM 8 BACKUP TYPE TO BACKUPSET; new RMAN configuration parameters are successfully stored released channel: ORA_DISK_1 released channel: ORA_DISK_2
95. www.viscosityna.com @ViscosityNA SECTION SIZE 2G, PARALLELISM = 8 Section Size RMAN> backup database section size 2g; allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=256 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=24 device type=DISK allocated channel: ORA_DISK_3 channel ORA_DISK_3: SID=257 device type=DISK allocated channel: ORA_DISK_4 channel ORA_DISK_4: SID=370 device type=DISK allocated channel: ORA_DISK_5 channel ORA_DISK_5: SID=23 device type=DISK allocated channel: ORA_DISK_6 channel ORA_DISK_6: SID=128 device type=DISK allocated channel: ORA_DISK_7 channel ORA_DISK_7: SID=260 device type=DISK allocated channel: ORA_DISK_8 channel ORA_DISK_8: SID=377 device type=DISK
96. www.viscosityna.com @ViscosityNA Channel 3, File 1 Section Size channel ORA_DISK_3: specifying datafile(s) in backup set input datafile file number=00001 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_system_mkfct5kw_.dbf piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fqk_.bkp Channel 2, File 3 channel ORA_DISK_2: specifying datafile(s) in backup set input datafile file number=00003 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_mom9qxlw_.dbf piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fqb_.bkp Channel 4, File 4 channel ORA_DISK_4: specifying datafile(s) in backup set input datafile file number=00004 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_mkfcw1s6_.dbf piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fr9_.bkp Channel 5, File 7 channel ORA_DISK_5: specifying datafile(s) in backup set input datafile file number=00007 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_users_mkfcw2vw_.dbf piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3frx_.bkp
97. www.viscosityna.com @ViscosityNA Channel 6, File 5 Section Size channel ORA_DISK_6: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf backing up blocks 262145 through 524288 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3g52_.bkp Channel 7, File 5 channel ORA_DISK_7: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf backing up blocks 524289 through 786432 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3g5r_.bkp Channel 8, File 5 channel ORA_DISK_8: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf backing up blocks 786433 through 1048576 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3g6k_.bkp
98. www.viscosityna.com @ViscosityNA Channel 1, File 5 Section Size channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf backing up blocks 1 through 262144 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fpn_.bkp channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf backing up blocks 1048577 through 1310720 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3gbk_.bkp
99. www.viscosityna.com @ViscosityNA Channel 1, File 5 Section Size channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf backing up blocks 1 through 262144 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fpn_.bkp channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00005 name=/u02/app/oracle/oradata/ORCL/datafile/o1_mf_big_momkgwoz_.dbf backing up blocks 1048577 through 1310720 piece handle=/u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3gbk_.bkp Channels create Backup Sets; Therefore, each database file should be backed up within a single channel. Where did the multiple Backup Pieces for File 5 created in different channels go?
100. www.viscosityna.com @ViscosityNA RMAN> list backup summary; List of Backups =============== Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 69 B F A DISK 12-DEC-24 1 1 NO TAG20241212T141717 70 B F A DISK 12-DEC-24 1 1 NO TAG20241212T141717 71 B F A DISK 12-DEC-24 5 1 NO TAG20241212T141717 72 B F A DISK 12-DEC-24 1 1 NO TAG20241212T141717 73 B F A DISK 12-DEC-24 1 1 NO TAG20241212T141717 74 B F A DISK 12-DEC-24 1 1 NO TAG20241212T141733 Section Size
101. www.viscosityna.com @ViscosityNA Backup Set 72, File 1 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 72 Full 1001.89M DISK 00:00:02 12-DEC-24 BP Key: 262 Status: AVAILABLE Compressed: NO Tag: TAG20241212T141717 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fqk_.bkp List of Datafiles in backup set 72 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 1 Full 6247507 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_system.dbf Section Size Backup Set 73, File 3 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 73 Full 1.06G DISK 00:00:02 12-DEC-24 BP Key: 263 Status: AVAILABLE Compressed: NO Tag: TAG20241212T141717 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fqb_.bkp List of Datafiles in backup set 73 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 3 Full 6247505 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux.dbf
102. www.viscosityna.com @ViscosityNA Backup Set 70, File 4 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 70 Full 4.26M DISK 00:00:00 12-DEC-24 BP Key: 256 Status: AVAILABLE Compressed: NO Tag: TAG20241212T141717 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fr9_.bkp List of Datafiles in backup set 70 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 4 Full 6247509 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs.dbf Section Size Backup Set 69, File 7 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 69 Full 1.05M DISK 00:00:00 12-DEC-24 BP Key: 255 Status: AVAILABLE Compressed: NO Tag: TAG20241212T141717 Piece Name: /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3frx_.bkp List of Datafiles in backup set 69 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 7 Full 6247511 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_users.dbf
103. www.viscosityna.com @ViscosityNA Backup Set 71, File 5, Pieces 257 - 261 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 71 Full 68.20M DISK 00:00:01 12-DEC-24 List of Datafiles in backup set 71 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- --------- ----------- ------ ---- 5 Full 6247503 12-DEC-24 NO /u02/app/oracle/oradata/ORCL/datafile/o1_mf_big.dbf Backup Set Copy #1 of backup set 71 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ --------------- ---------- --- DISK 00:00:01 12-DEC-24 NO TAG20241212T141717 List of Backup Pieces for backup set 71 Copy #1 BP Key Pc# Status Piece Name ------- --- ----------- ---------- 257 1 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3fpn_.bkp 258 2 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3g52_.bkp 259 3 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3g5r_.bkp 260 4 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3g6k_.bkp 261 5 AVAILABLE /u03/app/oracle/ORCL/backupset/2024_12_12/o1_mf_nnndf_TAG20241212T141717_moow3gbk_.bkp Section Size
104. www.viscosityna.com @ViscosityNA Backup Set 71, File 5, Pieces 257 - 261 List of Backup Pieces for backup set 71 Copy #1 BP Key ------- 257 Created by Channel 1, blocks 1 - 262,144 258 Created by Channel 6, blocks 262,145 - 524,288 259 Created by Channel 7, blocks 524,289 - 786,432 260 Created by Channel 8, blocks 786,433 - 1,048,576 261 Created by Channel 1, blocks 1,048,577 - 1,310,720 Section Size
105. www.viscosityna.com @ViscosityNA Summary: Tuning Multisection Backups • MAXSETSIZE splits database files across Backup Sets • MAXPIECESIZE divides Backup Sets • FILESPERSET spawns multiple Backup Sets per backup • PARALLELISM creates a Backup Set for each channel • SECTION SIZE splits database file backups across channels
106. Questions? Contact Me! sean.scott@viscosityna.com https://linktr.ee/oraclesean www.viscosityna.com