Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
10.2.2 Whole d<strong>at</strong>abase backup<br />
A whole d<strong>at</strong>abase backup set contains the control files and all d<strong>at</strong>abase files<br />
th<strong>at</strong> belong to th<strong>at</strong> d<strong>at</strong>abase. Whole d<strong>at</strong>abase backups do not require the<br />
d<strong>at</strong>abase to be oper<strong>at</strong>ed in a specific archiving mode. They can be taken<br />
whether a d<strong>at</strong>abase is oper<strong>at</strong>ing in ARCHIVELOG or NOARCHIVELOG<br />
mode. If the d<strong>at</strong>abase is in ARCHIVELOG mode, you can choose to back up<br />
the d<strong>at</strong>abase while it is open or closed. If running in NOARCHIVELOG mode,<br />
the d<strong>at</strong>abase must be shut down first. There are two types of whole d<strong>at</strong>abase<br />
backups:<br />
Consistent whole d<strong>at</strong>abase backup<br />
A consistent whole d<strong>at</strong>abase backup is a backup set where all files within<br />
it are consistent to the same point in time. A consistent whole d<strong>at</strong>abase is<br />
the only valid backup for d<strong>at</strong>abases running in NOARCHIVELOG mode.<br />
The only way to take a consistent whole d<strong>at</strong>abase backup is to shut down<br />
the d<strong>at</strong>abase cleanly and take a backup while the d<strong>at</strong>abase is offline.<br />
Inconsistent whole d<strong>at</strong>abase backup<br />
An inconsistent whole d<strong>at</strong>abase backup is a backup of an online d<strong>at</strong>abase.<br />
It is inconsistent because portions of the d<strong>at</strong>abases may have been<br />
modified and written to disk during the backup process. The d<strong>at</strong>abase<br />
must be in ARCHIVELOG mode in order to run an inconsistent backup.<br />
After an inconsistent backup is performed, the archived and online redo<br />
logs should also be backed up. Inconsistent whole d<strong>at</strong>abase backups are<br />
restored and made consistent by applying any subsequent incremental<br />
backups and redo logs, online and archive, during the recovery process.<br />
10.2.3 Incremental backup<br />
RMAN provides the capability of incrementally backing up d<strong>at</strong>abases <strong>at</strong> the<br />
individual block level. An incremental backup is a backup of one or more d<strong>at</strong>a<br />
files and contains only those blocks th<strong>at</strong> have been modified since a previous<br />
backup <strong>at</strong> the same or lower level.<br />
The multilevel incremental backup fe<strong>at</strong>ure allows you to cre<strong>at</strong>e different levels<br />
of incremental backups. Each level is denoted by an integer, with 0 being the<br />
lowest backup level. An incremental backup performed <strong>at</strong> a given level backs<br />
up only those blocks th<strong>at</strong> have been modified since the last backup <strong>at</strong> the<br />
same or lower level. An incremental backup can be performed on:<br />
Individual d<strong>at</strong>a files<br />
Tablespaces<br />
The entire d<strong>at</strong>abase<br />
160 <strong>Backing</strong> <strong>Up</strong> <strong>Oracle</strong> using Tivoli Storage Management
Change language