Tablespace Backups
Use
It is important to keep the volume of data to be backed up or restored as small as possible, especially when backing up large Oracle databases. One way to do this is by backing up specific tablespaces.
Activities
You do not have to back up pure index tablespaces during a database backup. Index definitions are stored in the
SYSTEM tablespace as a matter of course. Therefore, indexes can always be recreated.To make a backup of all tablespaces except index tablespaces, perform one of the following:
For more information, see
For more information, see
During the backup, BRBACKUP indicates all pure index tablespaces, so that BRRESTORE recognizes these. In the restore process, which uses a complete backup (
brrestore -m all), you can exclude the pure index tablespaces with the command brrestore -m all_data. For more information, see -m|-mode.
After restoring the backed-up data tablespaces both the index tablespaces and the indexes must be newly created with the definitions in the
After new indexes have been created, you must
update optimizer statistics on these indexes. For example, you can use brconnect -f stats -t <tablespace name> to do this. For more information, see -f stats. This requires extra time, possibly canceling the expected time reduction from a new index.We recommend you to test the complete recovery procedure to find out whether you can indeed expect a time reduction of this approach.