Problem solve Get help with specific problems with your technologies, process and projects.

Effectiveness of RMAN backups for busy databases

Database Backup and Recovery expert Brian Peasland explains the internal process of an RMAN backup.

I read somewhere that during RMAN backups, RMAN reads the blocks for backup and skips the blocks which are being updated, and revisits at a later time to copy the blocks. Suppose I am trying to copy a huge database online, which is a 24/7 busy database with lot of updates. How is RMAN going to be a faster backup solution? Could you please explain how RMAN does internally while backing up the database?
What you read is not my experience with RMAN. As far as I know, RMAN does not skip blocks being updated. In fact, when a record is being updated, the database generally does not update the block on disk (which RMAN is reading) until some time after the commit. There are exceptions to this generalization though. RMAN will backup a block that is being changed. To ensure data consistency, RMAN uses the archived redo logs to recreate a consistent block.
This was last published in January 2008

Dig Deeper on Oracle database administration

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.