Set the database into backup state (prior to Oracle 10g, the only option was to enable
backup on a tablespace-by-tablespace basis) by using the alter tablespace . . . begin
backup command for each tablespace or alter database begin backup to put all
tablespaces into online backup mode.
2. Back up the datafiles using operating system commands.
3. Set the database back to its normal state by issuing alter tablespace . . . end backup for
each tablespace or alter database end backup for all tablespaces in the database.
4. Archive the unarchived redo logs so that the redo required to recover the tablespace
backup is used by issuing the command alter system archive log current.
5. Back up the archived redo log files. If necessary, compress or delete the backed-up
archived redo log files to free space on disk.
6. Back up the control file.
See Chapter 12 for details on RMAN??™s automation of this process.
Integration of Backup Procedures
Because there are multiple methods for backing up the Oracle database, there is no need to have
a single point of failure in your backup strategy. Depending on your database??™s characteristics,
one method should be chosen, and at least one of the remaining methods should be used as a
backup to your primary backup method.
Chapter 11: Backup and Recovery Options 415
NOTE
When considering physical backups, you should also evaluate the use
of RMAN to perform incremental physical backups.
Pages:
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646