RMAN Best Practices - SOUG - 23 October 2025

RMAN is awesome, but its defaults aren’t always ideal. Do you know the difference between a database restore and a recovery? Between backups performed with and without Block Change Tracking? How to make backups use channels more efficiently? If not, this session is for you!

Transcript

1. Oracle RMAN Best Practices Swiss Oracle User Group - 23 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
5. www.viscosityna.com @ViscosityNA Oracle on Docker Running Oracle Databases in Linux Containers Free sample chapter: https://oraclesean.com
6. www.viscosityna.com @ViscosityNA RMAN Best Practices*
7. www.viscosityna.com @ViscosityNA ✅ Turn on Backup Optimization
8. 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
9. www.viscosityna.com @ViscosityNA ✅ Use Block Change Tracking*
10. 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
11. 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
12. www.viscosityna.com @ViscosityNA BCT Bitmap 32k block chunk 8k block 8k block 8k block 8k block 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 Block Change Tracking Bitmap
13. www.viscosityna.com @ViscosityNA Block Change Tracking - File Size BCT file size is proportional to DB size & thread count: • ~(DB size * enabled threads) / 30,000 • File allocation per 300M database size, initial = 10M, next = 10M • DB size <= 300M; BCT file = ~10M • DB size 300M - 600M; BCT file = ~20M • DB size 600M - 900M; BCT file = ~30M, etc. Internally allocates ~320k/data file • Many small data files may artificially inflate BCT file size
14. 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
15. www.viscosityna.com @ViscosityNA Block Change Tracking select * from v$block_change_tracking; -- For ASM: alter system set db_create_file_dest='+DATA' scope=both; alter database enable block change tracking; -- For Filesystem mkdir -p /oradata/$ORACLE_UNQNAME/BCT alter database enable block change tracking using file '/oradata/$ORACLE_UNQNAME/CHANGETRACKING/ctf.dat';
16. www.viscosityna.com @ViscosityNA ✅ Enable Controlfile Autobackup* * And understand what it really does
17. 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
18. 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
19. 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
20. www.viscosityna.com @ViscosityNA run { <command ≠ backup> backup ...; } - CF Autobackup run { backup ...; - CF Autobackup <command ≠ backup>; <command ≠ backup>; } - No CF Autobackup! Controlfile Autobackup Behavior
21. 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
22. 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
23. www.viscosityna.com @ViscosityNA OFF: Controlfile backup, then archivelog backup • Restore and mount controlfile • Then, CATALOG backups of archivelogs Controlfile Autobackup Behavior
24. 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
25. www.viscosityna.com @ViscosityNA Controlfile Snapshot 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
26. www.viscosityna.com @ViscosityNA 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"; HINT: Backup Controlfile + SPFile/PFile
27. www.viscosityna.com @ViscosityNA ✅ Increase RMAN Output Retention
28. 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
29. www.viscosityna.com @ViscosityNA ✅ INCREMENTAL LEVEL 0 🚫 FULL
30. 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
31. www.viscosityna.com @ViscosityNA ✅ INCREMENTAL LEVEL 1+ 🚫 BACKUP ARCHIVELOG ALL* * Exclusively/only
32. 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
33. www.viscosityna.com @ViscosityNA ✅ BACKUPSET 🚫 IMAGE COPY* * For "ordinary" backups
34. www.viscosityna.com @ViscosityNA Image Copy vs. Backup Set 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)
35. www.viscosityna.com @ViscosityNA 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 Image Copy vs. Backup Set
36. www.viscosityna.com @ViscosityNA ✅ RECOVERY WINDOW or REDUNDANCY 🚫 RECOVERY WINDOW and REDUNDANCY
37. 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
38. 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
39. www.viscosityna.com @ViscosityNA ✅ DELETE OBSOLETE 🚫 DELETE EXPIRED* * Usually
40. 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
41. 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
42. www.viscosityna.com @ViscosityNA ✅ Validate backups
43. www.viscosityna.com @ViscosityNA restore database validate; restore database validate check logical; restore archivelog all validate; Backup Validation
44. www.viscosityna.com @ViscosityNA Lesser Known and Misunderstood Features
45. 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
46. www.viscosityna.com @ViscosityNA backup ... plus archivelog 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;
47. 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+)
48. www.viscosityna.com @ViscosityNA alter system archive log current; backup archivelog all; backup ...; alter system archive log current; backup archivelog all; backup ... plus archivelog without optimization Backs up all archivelogs Backs up all archivelogs again!
49. 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
50. www.viscosityna.com @ViscosityNA 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! CONTROL_FILE_RECORD_KEEP_TIME
51. 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
52. www.viscosityna.com @ViscosityNA Recovery Area vs. Recovery Files 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
53. www.viscosityna.com @ViscosityNA 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 Recovery Area vs. Recovery Files
54. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 tag 'test1' database; } BACKUP DURATION
55. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial tag 'test2' database; } BACKUP DURATION PARTIAL
56. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial minimize time tag 'test3' database; } BACKUP DURATION PARTIAL MINIMIZE TIME
57. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial minimize load tag 'test4' database; } BACKUP DURATION PARTIAL MINIMIZE LOAD
58. www.viscosityna.com @ViscosityNA run { backup as copy duration 0:01 partial minimize time tag 'not_allowed' database plus archivelog; } 🚫 Not Supported: DURATION PLUS ARCHIVELOG
59. 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; } ✅ Override Retention Policies with KEEP UNTIL
60. www.viscosityna.com @ViscosityNA RMAN> backup database; backup database; Starting backup at 20-OCT-25 ... Set Meaningful Dates in RMAN CLI
61. www.viscosityna.com @ViscosityNA # export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS' # rman target / ... RMAN> backup database; backup database; Starting backup at 2025-10-20 14:18:46 Set Meaningful Dates in RMAN CLI
62. 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
63. 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
64. www.viscosityna.com @ViscosityNA # Check syntax: rman checksyntax Validate RMAN Command Syntax
65. www.viscosityna.com @ViscosityNA RMAN does not magically perform the fastest-possible backup.
66. www.viscosityna.com @ViscosityNA Optimize backups by manipulating RMAN configurations.
67. www.viscosityna.com @ViscosityNA Sets, Pieces and Sections
68. 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).
69. 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
70. 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
71. www.viscosityna.com @ViscosityNA Multi-Section Backups A Multi-Section Backup is ...a Backup Set ...containing multiple Backup Pieces ...each containing one or more File Sections
72. 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
73. 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
74. www.viscosityna.com @ViscosityNA MAXSETSIZE < DB Size = Multiple Backup Sets 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
75. www.viscosityna.com @ViscosityNA MAXPIECESIZE UNLIMITED 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
76. www.viscosityna.com @ViscosityNA MAXPIECESIZE = 1G 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
77. www.viscosityna.com @ViscosityNA 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 MAXPIECESIZE = 1G
78. www.viscosityna.com @ViscosityNA 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 MAXPIECESIZE = 1G
79. www.viscosityna.com @ViscosityNA 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 .../2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorfowr_.bkp 44 2 AVAILABLE .../2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorfwwg_.bkp 45 3 AVAILABLE .../2024_12_12/o1_mf_nnndf_TAG20241212T131429_moorg3wl_.bkp MAXPIECESIZE = 1G
80. www.viscosityna.com @ViscosityNA FILESPERSET FILESPERSET is a limit on the number of files per Backup Set • The default is 64
81. www.viscosityna.com @ViscosityNA FILESPERSET = 2 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 ...
82. www.viscosityna.com @ViscosityNA FILESPERSET = 2 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
83. www.viscosityna.com @ViscosityNA FILESPERSET = 2 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
84. www.viscosityna.com @ViscosityNA Backup Set 37 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 FILESPERSET = 2
85. www.viscosityna.com @ViscosityNA Backup Set 38 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 FILESPERSET = 2
86. www.viscosityna.com @ViscosityNA Backup Set 39 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 FILESPERSET = 2
87. www.viscosityna.com @ViscosityNA PARALLELISM PARALLELISM sets the number of channels available to RMAN jobs • Channels create separate Backup Sets
88. www.viscosityna.com @ViscosityNA PARALLELISM = 2 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
89. www.viscosityna.com @ViscosityNA PARALLELISM = 2 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
90. www.viscosityna.com @ViscosityNA PARALLELISM = 2 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
91. www.viscosityna.com @ViscosityNA Backup Set 41 PARALLELISM = 2 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
92. www.viscosityna.com @ViscosityNA PARALLELISM = 2 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
93. 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?
94. www.viscosityna.com @ViscosityNA 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 Tuning Multi-Section Backups
95. www.viscosityna.com @ViscosityNA 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 Tuning Multi-Section Backups
96. www.viscosityna.com @ViscosityNA 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 Tuning Multi-Section Backups
97. www.viscosityna.com @ViscosityNA 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. Tuning Multi-Section Backups
98. www.viscosityna.com @ViscosityNA Section Size
99. 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
100. www.viscosityna.com @ViscosityNA SECTION SIZE 2G, PARALLELISM = 8 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
101. www.viscosityna.com @ViscosityNA SECTION SIZE 2G, PARALLELISM = 8 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
102. 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
103. 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
104. 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
105. 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?
106. 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
107. 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
108. 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
109. 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
110. 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
111. www.viscosityna.com @ViscosityNA 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
112. Questions? Contact Me! sean.scott@viscosityna.com https://linktr.ee/oraclesean www.viscosityna.com