Another timesaver with RMAN is to skip READ ONLY tablespaces. It is rare for a 10TB+ database to update many of those terabytes of data on a regular basis. Place the data that is not getting updated in tablespaces separate from the data that does get updated. Then, make the non-updated tablespace READ ONLY. Back it up with RMAN. Since the tablespace is READ ONLY, you do not need to back it up again. You can have RMAN perform a full backup of your database, but skip the READ ONLY tablespaces. You may find that you only need to back up 1TB on a regular basis and your other 9TB were last backed up nine months ago!
Using RMAN is vital to backing up a VLDB. I would suggest going to http://tahiti.oracle.com and reading the backup and recovery guides for your version.
Dig Deeper on Oracle database backup and recovery
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.