RMAN Best Practices - CASOUG 25 - Bishkek - 27 October 2025

Transcript

1. Oracle RMAN Best Practices CASOUG 25 Bishkek 27 October 2025 Seàn Scott Managing Principal Consultant, Viscosity North America Oracle ACE Director
2. Get the slides:
3. 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. Oracle on Docker Running Oracle Databases in Linux Containers Free sample chapter: h tt ps://oraclesean.com
5. Tech Superstars Unite Get worldwide recognition as an Oracle ACE Oracle.com profile page Exclusive content Your own Oracle cloud account Swag, certification exam credit & event passes Networking events Travel support Learn more at: ace.oracle.com @oracleace Linkedin.com/groups/72183 @oracleace.bsky.social
6. 10 Conferences 15 Presentations 5 Panels 🌐 15 Time Zones 33 Days 54:28 Hours 15 Nations • 16 Airports • 20 Flights 43,826 km 23,664 nm and More Trains Trains Trains
7. www.viscosityna.com @ViscosityNA RMAN does not magically perform the fastest or best backup! Let's talk about trains
8. www.viscosityna.com @ViscosityNA RMAN does not magically perform the fastest or best backup! There are boring trains...
9. www.viscosityna.com @ViscosityNA RMAN does not magically perform the fastest or best backup! ...and exciting trains
10. www.viscosityna.com @ViscosityNA RMAN does not magically perform the fastest or best backup! The difference? Configuration.
11. RMAN does not magically perform the fastest or best backup.
12. www.viscosityna.com @ViscosityNA RMAN Best Practices*
13. www.viscosityna.com @ViscosityNA ✅ Turn on Backup Optimization
14. www.viscosityna.com @ViscosityNA Backup Optimization 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
15. www.viscosityna.com @ViscosityNA ✅ Use Block Change Tracking*
16. www.viscosityna.com @ViscosityNA Block Change Tracking Improves incremental backup performance 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 for backup on standby requires an Active Data Guard license
17. www.viscosityna.com @ViscosityNA Block Change Tracking Bitmap 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 incremental backups exhausts the bitmap • Any subsequent incremental backups won't be optimized When BCT is enabled, VALIDATE only scans changed blocks
18. www.viscosityna.com @ViscosityNA 32k block chunk 8k block 8k block 8k block 8k block Block Change Tracking Bitmap • BCT Bitmaps track 32k block chunks • If any block in the chunk changes, the chunk's BCT bit is TRUE • RMAN reads the chunk's bitmap, then: • Scans for changed blocks • Backs up those blocks
19. Backups with/without Block Change Tracking
20. www.viscosityna.com @ViscosityNA Block Change Tracking - Considerations MOS Doc ID 2836206.1 - BCT Known Issues MOS Doc ID 2821967.1 - How to Manage & Evaluate BCT Benefits • BCT is effective when <= 15% blocks changed between backups Do NOT tune BCT w/hidden params except: • _bct_bitmaps_per_file: adjust the bitmap depth • _disable_primary_bitmap_switch=TRUE: backup @ standby
21. www.viscosityna.com @ViscosityNA ✅ Enable Controlfile Autobackup* * And understand what it does
22. www.viscosityna.com @ViscosityNA Controlfile Backups, Autobackups, and Snapshots Controlfile backup: Bit-for-bit image copy of the control file Controlfile Autobackup: Backup of the control file and spfile (if used) • A Controlfile Autobackup is NOT a copy of the control file! • It is always a full backup set • It can never be duplexed Controlfile Snapshot: Read-consistent version of the control file • When resynchronizing recovery catalog • When backing up the current control file
23. www.viscosityna.com @ViscosityNA How RMAN Uses Controlfile Autobackups Controlfile Autobackup: Standard location and format • Oracle knows where and what to look for • No repository/catalog needed! • Autobackup contains the spfile and controlfile • Once these files are restored, RMAN can: • Start (mount) the instance; • Access the recovery catalog; • Restore other files; • Perform recovery using archive logs.
24. www.viscosityna.com @ViscosityNA Controlfile Autobackup Behavior 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
25. www.viscosityna.com @ViscosityNA Controlfile Autobackup Behavior 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
26. www.viscosityna.com @ViscosityNA run { <command ≠ backup> backup ...; } - CF Autobackup run { backup ...; - CF Autobackup <command ≠ backup>; <command ≠ backup>; } - No CF Autobackup! Controlfile Autobackup Behavior
27. www.viscosityna.com @ViscosityNA 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 Controlfile Autobackup Behavior
28. www.viscosityna.com @ViscosityNA 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 Controlfile Autobackup Behavior
29. www.viscosityna.com @ViscosityNA # First priority: run { set controlfile autobackup format=... } # Second priority: RMAN> set controlfile autobackup format=... # Third priority: configure controlfile autobackup format=... Controlfile Autobackup Location Priority
30. www.viscosityna.com @ViscosityNA ✅ INCREMENTAL LEVEL 0 🚫 FULL
31. www.viscosityna.com @ViscosityNA Full vs. Incremental Level 0 Backups Shared Behavior: 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 Different Behavior: Full ≠ Level 0 • Full backups can never be part of an incremental strategy • Level 0 can be parents of higher-level incremental backups • Full backups do not use Block Change Tracking
32. www.viscosityna.com @ViscosityNA ✅ INCREMENTAL LEVEL 1 🚫 BACKUP ARCHIVELOG ALL* * Exclusively/only
33. www.viscosityna.com @ViscosityNA Restore vs. Recover Restore writes media to disk Recover applies block changes to media • First, from incremental backups • Then, from archive logs
34. www.viscosityna.com @ViscosityNA ✅ RECOVERY WINDOW or REDUNDANCY 🚫 RECOVERY WINDOW and REDUNDANCY
35. www.viscosityna.com @ViscosityNA Retention, Redundancy, Recovery Window 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 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 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 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 Lesser Known and Misunderstood Features
41. www.viscosityna.com @ViscosityNA How RMAN Manages FRA 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
42. www.viscosityna.com @ViscosityNA How RMAN Manages FRA 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: Delete GRP to free space • Solution: Backup (and/or ship) archivelogs • Solution: Relocate flashback logs outside FRA (23ai+)
43. www.viscosityna.com @ViscosityNA CONTROL_FILE_RECORD_KEEP_TIME Control files use reusable, circular record keeping (think redo logs) • 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 CONTROL_FILE_RECORD_KEEP_TIME • Minimum days before circular records become eligible for reuse • Set ≥ Retention Policy, else RMAN may overwrite backup records!
44. www.viscosityna.com @ViscosityNA NEVER use RMAN if CONTROL_FILE_RECORD_KEEP_TIME = 0 • You may lose backup records! • With or without a Recovery Catalog! CONTROL_FILE_RECORD_KEEP_TIME
45. www.viscosityna.com @ViscosityNA Optimizes recovery after instance failure by reducing cache recovery Introduces additional incremental checkpoint operations Lower values = busier DBWR (more frequent dirty block flushes) When FAST_START_MTTR_TARGET = 0, every commit is a checkpoint Ignored if log_checkpoint_interval is set FAST_START_MTTR_TARGET
46. www.viscosityna.com @ViscosityNA Duration- and Load-Based Backups
47. www.viscosityna.com @ViscosityNA run { backup duration 0:01 tag 'test1' database; } BACKUP DURATION
48. www.viscosityna.com @ViscosityNA run { backup duration 0:01 partial tag 'test2' database; } BACKUP DURATION PARTIAL
49. www.viscosityna.com @ViscosityNA run { backup duration 0:01 partial minimize time tag 'test3' database; } BACKUP DURATION PARTIAL MINIMIZE TIME
50. www.viscosityna.com @ViscosityNA run { backup duration 0:01 partial minimize load tag 'test4' database; } BACKUP DURATION PARTIAL MINIMIZE LOAD
51. www.viscosityna.com @ViscosityNA run { backup duration 0:01 partial minimize time tag 'not_allowed' database plus archivelog; } 🚫 Not Supported: DURATION PLUS ARCHIVELOG
52. www.viscosityna.com @ViscosityNA Tips and Tricks
53. www.viscosityna.com @ViscosityNA run { backup ... keep until time 'sysdate + 60' restore point '60DAY_GRP' tag 'keep_60_days' database plus archivelog delete all input; } ✅ Override Retention Policies with KEEP UNTIL
54. www.viscosityna.com @ViscosityNA RMAN> backup database; ... Starting backup at 20-OCT-25 ✅ Set Meaningful Dates in RMAN CLI
55. www.viscosityna.com @ViscosityNA # export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS' # rman target / ... RMAN> backup database; ... Starting backup at 2025-10-20 14:18:46 ✅ Set Meaningful Dates in RMAN CLI
56. www.viscosityna.com @ViscosityNA # Set an alias for RMAN that includes the NLS_DATE_FORMAT: alias rman= 'NLS_DATE_FORMAT='\''YYYY-MM-DD HH24:MI:SS'\'' $ORACLE_HOME/bin/rman' ✅ Set Meaningful Dates in RMAN CLI
57. www.viscosityna.com @ViscosityNA # 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 ✅ Echo Commands, Spool Output
58. www.viscosityna.com @ViscosityNA # Check syntax: rman checksyntax ✅ Validate RMAN Command Syntax
59. www.viscosityna.com @ViscosityNA select * from v$rman_output; select recid, output from v$rman_output; # Default = 7 days configure rman output to keep for 14 days; ✅ Increase RMAN Output Retention
60. www.viscosityna.com @ViscosityNA How to Build Boringer Trains
61. www.viscosityna.com @ViscosityNA Backup Sets and Backup Pieces Backup Set: A logical collection of one or more Backup Pieces Backup Piece: A physical file generated by a backup Multiplexed Backup Set: A backup containing multiple database files A controlfile autobackup is a Backup Set (always a single file). A database backup is a Multiplexed Backup Set (contains multiple files).
62. 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
63. www.viscosityna.com @ViscosityNA Multiplexed Backups • A Multiplexed Backup is • ...a Backup • ...that runs multiple Channels • ...that each create one or more Backup Sets • AKA a multi-channel, multi-threaded, or parallelized backup • Uses more cores but reduces backup duration (and thus restore time)
64. www.viscosityna.com @ViscosityNA DF001 DF002 DF003 DF004 DF005 DF006 DF007 DF008 One Channel, One Backup Set One channel = One Backup Set • A Backup Set can only be written (or read) by a single channel • A channel is associated with a database session • Tuning RMAN throughput requires resource optimization (CPU, I/O) • The objective is reducing overall time required for backup
65. www.viscosityna.com @ViscosityNA DF001 DF002 DF003 DF004 DF005 DF006 DF007 DF008 DF001 DF002 DF003 DF004 DF005 DF006 DF007 DF008 Multiplexed Backups One channel Total Time Two Channels Total Time
66. www.viscosityna.com @ViscosityNA DF003 DF004 DF005 DF006 DF007 DF008 DF001 DF002 DF001 DF002 DF003 DF004 DF005 DF006 DF007 DF008 Multiplexed Backups Four Channels Total Time Two Channels Total Time
67. www.viscosityna.com @ViscosityNA MAXSETSIZE, MAXPIECESIZE 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 Setting non-UNLIMITED values creates more backup sets and/or pieces.
68. www.viscosityna.com @ViscosityNA FILESPERSET FILESPERSET is a limit on the number of files per Backup Set • The default is 64 Reducing this value creates more backup sets (fewer files per set) Increasing this value creates fewer backup sets (more files per set)
69. www.viscosityna.com @ViscosityNA PARALLELISM PARALLELISM sets the number of channels available to RMAN jobs • Channels create separate Backup Sets Increasing PARALLELISM creates more channels; Each channel creates a separate backup set. Channels ⩰ Backup Sets
70. www.viscosityna.com @ViscosityNA Tuning Multi-Section Backups What do we know? • Database file backups are NEVER split across Backup Sets! • Parts of a tablespace may be in different Backup Pieces • Channels can only process one file at a time • Channels create Backup Sets (channel & file have a 1:1 relationship) Therefore, if a datafile is backed up by a single channel then the largest datafile limits backup duration. Right?
71. www.viscosityna.com @ViscosityNA Tuning Multi-Section Backups What do we know? • Database file backups are NEVER split across Backup Sets! • Parts of a tablespace may be in different Backup Pieces • Channels can only process one file at a time • Channels create Backup Sets (channel & file have a 1:1 relationship) Therefore, if a datafile is backed up by a single channel then the largest datafile limits backup duration. Right? 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.
72. www.viscosityna.com @ViscosityNA DF006 DF007 DF008 DF005 DF004 DF003 DF002 DF001 DF003 DF004 DF005 DF006 DF007 DF008 DF001 DF002 Multiplexed Backups Four Channels Total Time Eight Channels Total Time
73. www.viscosityna.com @ViscosityNA DF006 DF007 DF008 DF005 DF004 DF003 DF002 DF001 DF003 DF004 DF005 DF006 DF007 DF008 DF001 DF002 Multiplexed Backups Four Channels Total Time Eight Channels Total Time Session idle! Session idle! Session idle! Session idle! Session idle! Session idle! Session idle! Session idle! Session idle! Session idle! Datafile 8 limits backup performance!
74. www.viscosityna.com @ViscosityNA DF006 DF007 DF008 DF005 DF004 DF003 DF002 DF001 Multiplexed Backups - Limits A datafile is a member of a backup set A backup set is assigned to a channel A datafile is processed by one channel ORA_DISK_1 ORA_DISK_2 ORA_DISK_3 ORA_DISK_4 ORA_DISK_5 ORA_DISK_6 ORA_DISK_7 ORA_DISK_8
75. www.viscosityna.com @ViscosityNA DF006 DF007 DF005 DF004 DF003 DF002 DF001 Multisection Backups ORA_DISK_1 ORA_DISK_2 ORA_DISK_3 ORA_DISK_4 ORA_DISK_5 ORA_DISK_6 ORA_DISK_7 ORA_DISK_8 DF008
76. www.viscosityna.com @ViscosityNA Sectioning
77. www.viscosityna.com @ViscosityNA File Sectioning • 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 - 12800 Section 0 • Blocks 12801 - 25600 Section 1 • etc.
78. www.viscosityna.com @ViscosityNA Multisection Backups • A Multisection Backup is • ...a Backup Set • ...containing multiple Backup Pieces • ...each containing one or more file sections • Multiple channels can write sections simultaneously • Each channel's activity is confined to a Backup Piece • Idle channels are assigned outstanding work
79. www.viscosityna.com @ViscosityNA DF006 DF007 DF005 DF004 DF003 DF002 DF001 Multisection Backups ORA_DISK_1 ORA_DISK_2 ORA_DISK_3 ORA_DISK_4 ORA_DISK_5 ORA_DISK_6 ORA_DISK_7 ORA_DISK_8 DF008 Session idle! Session idle! Session idle! Session idle! Session idle! Session idle! Session idle! Serialized datafile backups take a long time, leaving some sessions (channels) idle!
80. www.viscosityna.com @ViscosityNA DF006 DF007 DF008.1 DF005 DF004 DF003 DF002 DF001 Multisection Backups SECTION SIZE splits large datafiles into smaller block ranges ORA_DISK_1 ORA_DISK_2 ORA_DISK_3 ORA_DISK_4 ORA_DISK_5 ORA_DISK_6 ORA_DISK_7 ORA_DISK_8 DF008.2 DF008.3 DF008.4 DF008.5 DF008.6 DF008.7
81. www.viscosityna.com @ViscosityNA DF006 DF007 DF008.1 DF005 DF004 DF003 DF002 DF001 Multisection Backups When backups use SECTION SIZE, RMAN sessions can "change channels" during a backup! ORA_DISK_1 ORA_DISK_2 ORA_DISK_3 ORA_DISK_4 ORA_DISK_5 ORA_DISK_6 ORA_DISK_7 ORA_DISK_8 DF008.2 DF008.3 DF008.4 DF008.5 DF008.6 DF008.7
82. www.viscosityna.com @ViscosityNA SECTION SIZE = 1G, PARALLELISM = 8 Section Size RMAN> backup database section size 1g tag 'section_1g'; Starting backup at 2025-08-20 22:27:43 channel ORA_DISK_1: SID=932 instance=DB231 device type=DISK channel ORA_DISK_2: SID=630 instance=DB231 device type=DISK channel ORA_DISK_3: SID=788 instance=DB231 device type=DISK channel ORA_DISK_4: SID=944 instance=DB231 device type=DISK channel ORA_DISK_5: SID=175 instance=DB231 device type=DISK channel ORA_DISK_6: SID=331 instance=DB231 device type=DISK channel ORA_DISK_7: SID=473 instance=DB231 device type=DISK channel ORA_DISK_8: SID=627 instance=DB231 device type=DISK
83. www.viscosityna.com @ViscosityNA SECTION SIZE = 1G, PARALLELISM = 8 Section Size channel ORA_DISK_4: File 00001, section 0 blocks 1 through 131072 channel ORA_DISK_1: File 00001, section 1 blocks 131073 through 145920 channel ORA_DISK_3: File 00003, section 0 blocks 1 through 131072 channel ORA_DISK_5: File 00003, section 1 blocks 131073 through 262144 channel ORA_DISK_6: File 00003, section 2 blocks 262145 through 304640 channel ORA_DISK_2: File 00011, section 0 blocks 1 through 131072 channel ORA_DISK_1: File 00011, section 1 blocks 131073 through 144640 channel ORA_DISK_1: File 00015, section 0 blocks 1 through 131072 channel ORA_DISK_3: File 00015, section 1 blocks 131073 through 262144 channel ORA_DISK_4: File 00015, section 2 blocks 262145 through 393216 channel ORA_DISK_5: File 00015, section 3 blocks 393217 through 524288 channel ORA_DISK_6: File 00015, section 4 blocks 524289 through 655360 channel ORA_DISK_7: File 00015, section 5 blocks 655361 through 786432 channel ORA_DISK_8: File 00015, section 6 blocks 786433 through 917504 channel ORA_DISK_3: File 00015, section 7 blocks 917505 through 1048576 channel ORA_DISK_4: File 00015, section 8 blocks 1048577 through 1179648 channel ORA_DISK_5: File 00015, section 9 blocks 1179649 through 1310720
84. www.viscosityna.com @ViscosityNA SECTION SIZE = 1G, PARALLELISM = 8 Section Size RMAN> list backup of datafile 1,3,11,15 summary; List of Backups =============== Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- ------------------- ------- ------- ---------- --- 144 B F A DISK 2025-08-20 22:27:50 10 1 NO SECTION_1G 145 B F A DISK 2025-08-20 22:28:11 2 1 NO SECTION_1G 149 B F A DISK 2025-08-20 22:28:35 2 1 NO SECTION_1G 152 B F A DISK 2025-08-20 22:28:35 3 1 NO SECTION_1G
85. www.viscosityna.com @ViscosityNA SECTION SIZE = 1G, PARALLELISM = 8 Section Size BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ ------------------- 149 Full 993.56M DISK 00:00:43 2025-08-20 22:28:35 List of Datafiles in backup set 149 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- ------------------- ----------- ------ ---- 1 Full 5984811 2025-08-20 22:27:52 NO +DATA/DB23_SJO/DATAFILE/system.264.1209076319 Backup Set Copy #1 of backup set 149 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ ------------------- ---------- --- DISK 00:00:43 2025-08-20 22:28:35 NO SECTION_1G List of Backup Pieces for backup set 149 Copy #1 BP Key Pc# Status Piece Name ------- --- ----------- ---------- 197 1 AVAILABLE +RECO/DB23_SJO/BACKUPSET/2025_08_20/nnndf0_section_1g_0.351.1209680875 <<< ORA_DISK_4 183 2 AVAILABLE +RECO/DB23_SJO/BACKUPSET/2025_08_20/nnndf0_section_1g_0.340.1209680875 <<< ORA_DISK_1
86. www.viscosityna.com @ViscosityNA SECTION SIZE = 1G, PARALLELISM = 8 Section Size BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ ------------------- 152 Full 1.89G DISK 00:00:44 2025-08-20 22:28:35 List of Datafiles in backup set 152 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- ------------------- ----------- ------ ---- 3 Full 5984807 2025-08-20 22:27:51 NO +DATA/DB23_SJO/DATAFILE/sysaux.273.1209076299 Backup Set Copy #1 of backup set 152 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ ------------------- ---------- --- DISK 00:00:44 2025-08-20 22:28:35 NO SECTION_1G List of Backup Pieces for backup set 152 Copy #1 BP Key Pc# Status Piece Name ------- --- ----------- ---------- 195 1 AVAILABLE +RECO/DB23_SJO/BACKUPSET/2025_08_20/nnndf0_section_1g_0.296.1209680873 <<< ORA_DISK_3 196 2 AVAILABLE +RECO/DB23_SJO/BACKUPSET/2025_08_20/nnndf0_section_1g_0.329.1209680875 <<< ORA_DISK_5 186 3 AVAILABLE +RECO/DB23_SJO/BACKUPSET/2025_08_20/nnndf0_section_1g_0.347.1209680875 <<< ORA_DISK_6
87. www.viscosityna.com @ViscosityNA SECTION SIZE = 1G, PARALLELISM = 8 Section Size BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ ------------------- 145 Full 947.27M DISK 00:00:24 2025-08-20 22:28:11 List of Datafiles in backup set 145 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- ------------------- ----------- ------ ---- 11 Full 5984787 2025-08-20 22:27:47 NO +DATA/DB23_SJO/.../DATAFILE/sysaux.275.1209076583 Backup Set Copy #1 of backup set 145 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ ------------------- ---------- --- DISK 00:00:24 2025-08-20 22:28:11 NO SECTION_1G List of Backup Pieces for backup set 145 Copy #1 BP Key Pc# Status Piece Name ------- --- ----------- ---------- 187 1 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.312.1209680869 <<< ORA_DISK_2 176 2 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.295.1209680869 <<< ORA_DISK_1
88. www.viscosityna.com @ViscosityNA SECTION SIZE = 1G, PARALLELISM = 8 Section Size BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ ------------------- 144 Full 68.48M DISK 00:00:04 2025-08-20 22:27:50 List of Datafiles in backup set 144 File LV Type Ckp SCN Ckp Time Abs Fuz SCN Sparse Name ---- -- ---- ---------- ------------------- ----------- ------ ---- 15 Full 5984782 2025-08-20 22:27:46 NO +DATA/DB23_SJO/.../DATAFILE/big.292.1209585015 Backup Set Copy #1 of backup set 144 Device Type Elapsed Time Completion Time Compressed Tag ----------- ------------ ------------------- ---------- --- DISK 00:00:04 2025-08-20 22:27:50 NO SECTION_1G List of Backup Pieces for backup set 144 Copy #1 BP Key Pc# Status Piece Name ------- --- ----------- ---------- 169 1 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.328.1209680867 <<< ORA_DISK_1 170 2 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.315.1209680869 <<< ORA_DISK_3 171 3 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.333.1209680869 <<< ORA_DISK_4 173 4 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.338.1209680869 <<< ORA_DISK_5 172 5 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.327.1209680869 <<< ORA_DISK_6 174 6 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.302.1209680869 <<< ORA_DISK_7 175 7 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.330.1209680869 <<< ORA_DISK_8 177 8 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.308.1209680871 <<< ORA_DISK_3 178 9 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.317.1209680871 <<< ORA_DISK_4 179 10 AVAILABLE +RECO/DB23_SJO/.../BACKUPSET/2025_08_20/nnndf0_section_1g_0.313.1209680871 <<< ORA_DISK_5
89. www.viscosityna.com @ViscosityNA Summary: Configurations That Affect Sectioning • MAXSETSIZE: Tune Backup Set size (increase sets/backup) • MAXPIECESIZE: Tune Backup Piece size (control pieces/set) • FILESPERSET: Tune RMAN I/O (adjust set parallelism) • MAXOPENFILES: Tune RMAN I/O (upper limit for files/channel) • Also affects the number and size of input buffers • PARALLELISM: Tune parallelism/CPU (maximize CPU) • Note this is further limited by min(MAXOPENFILES, FILESPERSET) • SECTION SIZE: Tune large file backup (optimize RMAN sessions)
90. Questions? Contact Me! sean.scott@viscosityna.com https://linktr.ee/oraclesean www.viscosityna.com
91. Get the slides: