| <
font color="#330099" face="Helvetica, Arial, sans-serif">Oracle® Database Backup and Recovery Advanced User's Guide 1 0g Release 1 (10.1) Part Number B10734-01 |
|
|
View PDF |
This section describes new features of Recovery Manager in Oracle Database Release 10g and provides pointers to additional information. For information on new features in Ora cle9i and previous releases, refer to the documentation for those releases.
The new features for this release greatly increase the manageability of RMAN, making backup and recovery simpler and more performant.
A flash recovery area is a directory, file system, or Automatic Storage Man agement disk group that serves as the default storage area for files related to recovery. Such files include
RESTORE and RECOVER commands<
/li>Recovery components of the database interact with the flash recovery area to ensure t hat the database is completely recoverable using files in the flash recovery area. The database manages the disk space in the flash r ecovery area, and when there is not sufficient disk space to create new files, the database creates more room automatically by deleti ng the minimum set of files from flash recovery area that are obsolete, backed up to tertiary storage, or redundant.
See Also:
|
With the FLASHBACK DATABASE command, you can q
uickly revert a database to a previous time--without restoring datafiles and performing media recovery. When you enable the Flashback
Database feature, the database automatically creates, deletes, and manages flashback logs inside the flash recovery area. When you r
un the FLASHBACK DATABASE command, the database uses the flashback logs as well as the archived redo logs t
o reconstruct its contents at the specified time.
You can apply backup incrementals to datafile image copies--not current datafiles--to roll them forward to a specified point in time. In this way, you can potentially reduce recovery time by applying incrementals to copies and avoid taking a full image copy again af ter incremental backups.
| See Also:
Oracle Database Backup and Recovery Basics to learn how to roll forward image copies |
The new disk topology API extends RMAN's capability to more platforms and file types. RMAN is also able to tune its p arameters automatically according to disk topology information, which decreases the degree of user intervention required for performa nce tuning. RMAN can automatically tune the following:
| See Also:
"Tuning Recovery Manager: Overview" to learn more about RMAN performance tuning |
RMAN can create datafiles automatically
when the user executes RESTORE or RECOVER commands in the following situations:
| See Also:
Oracle Dat
abase Recovery Manager Reference to learn about the behavior of the |
RMAN simplifies recovery with backups taken from an earlier incarnation so that it is as easy as recovering a backup from the sam
e incarnation. Hence, you no longer need to make new backups of a database after a RESETLOGS. The procedure is as easy a
nd transparent as recovering a backup from the same incarnation. Also, the ALTER DATABASE OPEN
RESETLOGS statement is now modified so that the database now archives the current online redo logs (if possible) before
clearing the logs.
If a backup piece is inaccessible or corrupted, then RMAN can automatically fail over to
another copy of this backup piece during RESTORE. If all copies of this backup set are unusable, then RMAN can fail over
to previous redundant backup sets. RMAN continously fails over to previous backups until it exhausts all possibilities. This feature
is similar to archived log failover.
See Also:
|
tr>
BACKUP Command Creates Backup Sets or Image Copi
es
In previous releases, RMAN had two separate commands to back up datafiles: BACK
UP and COPY. The BACKUP command backed up the datafile into a backup set, which is a proprietary for
mat that allows multiple datafiles to be multiplexed together. The COPY command generated image copies, that is, bit-by-
bit copies of datafiles.
Starting in Release 10g, the COPY command is deprecated in favor of an enhanced BACKUP command that enables you to specify whether RMAN should create
copies or backup sets. As a result, BACKUP AS COPY can copy a database or multiple tablespace
s, datafiles, archived logs and datafile copies.
See Also:
|
RMAN can create and restore proxy backups of archived redo logs.
Users ca
n now catalog user-specified backup pieces with the CATALOG command. Cataloging a backup piece adds it to the RMAN repos
itory so that it is available for use in recovery operations. This enhanced functionality is useful when you make a copy of a backup
piece with an operating system utility, or when you move a backup piece from one disk to another so that it has a different absolute
path name.
See Also:
<
p class="NB">Oracle Database Backup
and Recovery Basics to learn how to catalog backup pieces, and Oracle Database Recovery Manager Reference for CATALOG syntax |
If you enable block change tracking, then the database automatically tracks which datafile blocks have changed
in change tracking files. When you execute BACKUP INCREMENTAL, RMAN uses the change tracking file to more q
uickly identify the blocks changed since the previous incremental backup. As a result, RMAN creates incremental backups much faster t
han in prior releases.
See Also:
|
If multiple channels are allocated for a BACKUP comman
d, and if RMAN encounters a retriable error (for example, an unplanned instance shutdown in RAC, or a media management error), then R
MAN attempts to move the backup to a different channel and complete the work.
For most RMAN commands, RMAN will report errors in the output when they occur and then continue to execute the command if possible. If RMAN can retry a job step on another channel, then it will report a message to this effect. If some job steps could not be completed, then the error stack at the end of command execution will display errors for failed steps.
The V$RMAN_OUTPUT memory-only view shows the output of a
currently executing RMAN job, whereas the V$RMAN_STATUS control file view indicates the status of both executing and com
pleted RMAN jobs. The V$BACKUP_FILES provides access to the information used as the basis of the LIST BACKUP and REPORT OBSOLETE commands.
RMAN can create an auxiliary instance automatica lly when you perform RMAN TSPITR. RMAN creates the auxiliary instance in the same machine as the target database. RMAN provides intel ligent defaults for the instance, but you can provide nondefault initialization parameters if desired. RMAN automatically dismantles the auxiliary database and instance after a successful TSPITR.
The RMAN command CONV
ERT TABLESPACE enables you to transport a tablespace from a database running on one platform (for example, Solari
s) to a database running on a different platform (for example, Windows).
| See Also:
Oracle Database Recovery Manager Reference to learn abou
t the |
The recovery catalog now supports global stored scripts, which can be a pplied to any database in the recovery catalog. A number of new commands have been added to allow for easier manipulation and display ing of stored scripts from the recovery catalog.
| See Also:
"Working with RMAN St ored Scripts in the Recovery Catalog" for the new commands and options |
RMAN can now write backup sets in a format that uses binary compression to reduce backup set size. Using compressed ba ckup sets can save storage space, as well as network bandwidth when backing up across a network.
| See Also:
Oracle Database Backup and Recovery Basics for more details o n using compressed backupsets. |
The PREVIEW option to the RESTORE command can now tell you whi ch backups will be accessed during a RESTORE operation.
| See A
lso:
Oracle Database Backup and Recovery Basics for more details on RESTORE PREVIEW |
The BACKUP command now accepts a DURATION clause, which lets you specify limited time windows for backup activi ties and minimize load imposed by backup activities during those backup windows. .
| See Also:
"Managing Backup Windows and Performance: BACKUP... DURATION" for more details on managing backup duration and throttling |