RMAN incremental backups : tracking changed blocks
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: RMAN incremental backups : tracking changed blocks

  1. #1
    Join Date
    Oct 2002
    Posts
    807

    RMAN incremental backups : tracking changed blocks

    Here's excerpt from 10g documentation :

    "Change-Aware Incremental Backups
    By using a new type of log file to track blocks that have changed in the database, Recovery Manager (RMAN) can avoid scanning the entire datafile during an incremental backup. Instead, the amount of data scanned is proportional to the amount of data changed."

    Woohoo!!

    Got a question though - What "log file" are they referring to? How do they keep track of changed blocks?

  2. #2
    Join Date
    Oct 2002
    Posts
    807
    FYI - For the benefit of all. Something I recently read.

    10g uses a file, analogous to journals in filesystems, to track the blocks that have changed since the last backup. RMAN reads this file to determine which blocks are to be backed up.

    You can enable this tracking mechanism by issuing the following command:

    SQL> alter database enable block change tracking using file '/rman_bkups/change.log';


    This command creates a binary file called /rman_bkups/change.log for tracking purposes. Conversely, you can disable tracking with

    SQL> alter database disable block change tracking;


    To see whether change tracking is currently enabled, you can query:

    SQL> select filename, status from v$block_change_tracking;
    Obviously, I'm having an easy day with so many posts..

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width