RMAN incremental backup tips

Incremental Backup greatly reduces the cost of Oracle backup time, but this mechanism may be cumbersome

In versions 10 GB and later, you can use the Incremental backup of RMAN to roll the image copy of data files to the specified time point. This new feature provides the following benefits:

① Using Incremental backup to regularly update the image copy of the data file, the updated image will be rolled to an updated status (that is, the latest SCN) before the update, this may reduce the recovery time

② Using Incremental backup again after Incremental Backup will avoid another full backup

Use the following statement to roll forward an image copy of a data file:

U01/app/oracle/backup/grid/data01.imgcopy:

RMAN> recover datafilecopy '/u01/app/oracle/backup/grid/data15.imgcopy ';

Or, the equivalent command is as follows:

RMAN> recovery copy of datafile 15;

When Incremental backup is used, we need a mechanism to bypass unchanged blocks. For a common tablespace, the INSERT operation will INSERT new blocks into the "Hotspot" Area of the data file.

Block change tracking can be used to maximize the benefits of Incremental backup. when inserting, try to use the APPEND prompt or use a lower PCTUSED value for the table/index to ensure that all new rows are inserted to the new block.

This reduces maintenance costs, because the block change tracking mechanism only needs to track new blocks.

The simple block change tracking syntax is as follows:

Alter database enable block change tracking using file OS _file_name;