Block Compression for Backup Sets

RMAN uses two types of block compression when creating backup sets:

港閘網(wǎng)站建設(shè)公司創(chuàng)新互聯(lián)公司,港閘網(wǎng)站設(shè)計制作，有大型網(wǎng)站制作公司豐富經(jīng)驗。已為港閘近千家提供企業(yè)網(wǎng)站建設(shè)服務(wù)。企業(yè)網(wǎng)站搭建\外貿(mào)營銷網(wǎng)站建設(shè)要多少錢，請找那個售后服務(wù)好的港閘做網(wǎng)站的公司定做！

• Unused Block Compression (Supports disk backup and Oracle Secure Backup tape backup)

• Null Block Compression (Supports all backups)

Although it is referred to as block compression, it might be helpful to think of block compression as block skipping. Rather than compressing the data in the blocks, RMAN completely eliminates the blocks from the backup. RMAN reads blocks from a data file and writes them to a backup set. If unused block compression is enabled, RMAN reads only those blocks of the data file in an extent that currently belongs to a database segment. Unused block compression can only be employed when backing up tablespaces whose space is locally managed. When not employing unused block compression, RMAN reads every block of the data file. Before RMAN writes a block to the backup set, it applies the null block test, and if the block has never been used, it does not write that block to the backup set