Obviously, with large databases, it takes a very long time to back them up. The best course of action is to put...
all of your static data into READ ONLY tablespaces. For a 10TB database, it is highly unlikely that all of your tables are changing regularly. So put static tables in tablespaces apart from tables which undergo DML. Then backup those tablespaces in RMAN with the BACKUP TABLESPACE command. Next time you do a full or incremental database backup, tell RMAN to SKIP READ ONLY tablespaces. This way, you are not backing up your static data over and over again.
Another strategy is to spread out your tablespace backups over multiple nights. Have RMAN back up some tablespaces tonight and other tablespaces tomorrow night.
The RMAN documentation also has many hints on how to tune RMAN for better performance.
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.