RMAN Compressed Backupset

RMAN Compressed Backupset: [plain] There is some CPU overhead associated with compressing backup sets. if the database being backed up is running at or near its maximum load, you may find the overhead from using as compressed backupset unacceptable. in most other circumstances, compressing backupsets saves enough disk space to be worth the CPU overhead In short, occupying more CPU overhead, but the backup set reduces the test (platform: 10gR2 redhat ): do not use compressed backup: [SQL] RMAN> list backup; RMAN> list copy; RMAN> backup database plus archivelog delete all input; RMAN> list backup; size Device Elapsed Time ------- ---- -- ------ -------- 606.06 m disk 00:01:26 use compressed backup: [SQL] RMAN> list backup; RMAN> list copy; RMAN> backup as compressed backupset database plus archivelog delete all input; RMAN> list backup; size Device Elapsed Time ------- ---- -- ----- ------ 112.27 m disk 00:01:43 applicable scenarios in systems where the CPU is not the main bottleneck. If compression backup can be started but the database is large, we recommend that you use Image Copy incremental Updates (ICIU) policy to solve