Oracle9i Recovery Manager User's Guide Release 1 (9.0.1) Part Number A90135-01 |
|
This section describes new features of Recovery Manager in Oracle9i Release 1 (9.0.1) and provides pointers to additional information. New features information from previous releases is also retained to help those users migrating to the current release from releases prior to Oracle8i.
The following sections describe the new features in Recovery Manager:
The Oracle9i Release 1 (9.0.1) features and enhancements increase manageability and greatly expand functionality.
The CONFIGURE
command creates persistent RMAN settings that apply to any session. You can configure a variety of features including automatic channels, channel parallelism, retention policies, backup options, auxiliary filenames, and so forth.
See Also:
Chapter 8, "Configuring the Recovery Manager Environment" for configuration procedures, and Oracle9i Recovery Manager Reference for |
The CONFIGURE
command stores a persistent set of channel settings. RMAN automatically allocates these channels when you execute commands such as BACKUP
or COPY
at the RMAN prompt, abolishing the necessity for manual channel allocation.
Use the CONFIGURE
command to define backup attributes such as parallelism, duplexing, and channel control options. These settings are used by all commands that require channels unless you manually allocate channels in a RUN
command.
See Also:
"Automatic and Manual Channel Allocation" for concepts, and Oracle9i Recovery Manager Reference for |
Formerly, most backup and recovery commands had to be executed within a RUN
command. Now, many commands such as BACKUP,
COPY,
and RESTORE
can be executed at the RMAN prompt.
A retention policy is a configuration that specifies how long backups of control files and datafiles should be retained, as well how many of these backups should be retained. The retention policy also determines which archived logs are obsolete because they are not needed to recover these backups.
The REPORT
OBSOLETE
and DELETE
OBSOLETE
commands use the criteria specified in the retention policy to determine what is obsolete. You can specify a retention policy in these ways:
"Backup Retention Policies" for concepts, and Oracle9i Recovery Manager Reference for
See Also:
CONFIGURE
syntax.
The KEEP
option of the BACKUP
command marks a backup as exempt from the retention policy. The REPORT
OBSOLETE
and DELETE
OBSOLETE
commands only consider the backup as obsolete when the KEEP
time expires. You can alter the status of the backup with the CHANGE
...
KEEP
command.
See Also:
"Backups Exempt from the Retention Policy" for concepts, and Oracle9i Recovery Manager Reference for |
If you set CONFIGURE
CONTROLFILE
BACKUP
to ON
, then RMAN makes a mandatory and automatic control file autobackup after you run the BACKUP
or COPY
command. RMAN gives this backup a default name (which you can change using CONFIGURE
CONTROLFILE
BACKUP
FORMAT
), thereby allowing RMAN to restore this control file even in a disaster scenario in which the recovery catalog and current control file are lost.
Block media recovery can perform media recovery on individual blocks in a datafile while the datafile remains online. The new V$DATABASE_BLOCK_CORRUPTION
view displays corrupt blocks in the most recent backup or image copy of each datafile.
See Also:
"Block Media Recovery with RMAN" for concepts, and Oracle9i Recovery Manager Reference for |
RMAN enhances its treatment of archived redo logs in the following ways:
BACKUP
...
PLUS
ARCHIVELOG
command switches out of and archives the current online log, backs up archived logs, then performs another log switch and backs up remaining logs. This operation guarantees that the backed up datafiles can be recovered to a consistent state.
BACKUP
ARCHIVELOG
command does not discover any logs to back up.
DELETE
ALL
INPUT
option of the BACKUP
ARCHIVELOG
command deletes all logs that match the specified criteria. In this way, you can delete logs located in multiple archiving destinations.
BACKUP_COUNT
column in V$ARCHIVED_LOG
shows the number of times that a specified archived log was backed up.
"Backups of Archived Logs" for concepts, and Oracle9i Recovery Manager Reference for
See Also:
BACKUP
syntax
The LIST
command syntax is now more similar in structure to the CHANGE
, CROSSCHECK
, and DELETE
commands. You also have more control over how the LIST
output is displayed.
See Also:
"LIST Command Output" for concepts, and Oracle9i Recovery Manager Reference for |
The functionality of the CROSSCHECK
command is expanded, and the CHANGE
...
CROSSCHECK
is deprecated. The CROSSCHECK
command is now similar in syntax to the DELETE
and CHANGE
commands.
See Also:
"Crosschecks of RMAN Backups and Copies" for concepts, and Oracle9i Recovery Manager Reference for |
The CHANGE
command can make files available or unavailable, catalog or uncatalog them, and change the KEEP
setting, regardless of whether the backup repository is the control file or recovery catalog (except for CHANGE
...
KEEP
FOREVER
, which requires a catalog). The CHANGE
command operates on more types of files, and is now similar in syntax to the DELETE
and CROSSCHECK
commands.
See Also:
"Changes to Availability of RMAN Backups and Copies" for concepts, and Oracle9i Recovery Manager Reference for |
The DELETE
command combines the functionality of the previous CHANGE
...
DELETE
and DELETE
EXPIRED
commands. Additionally, you can run DELETE
OBSOLETE
to remove all files that are no longer needed. The DELETE
command is now similar in syntax to the CHANGE
and CROSSCHECK
commands.
Note that by default, DELETE
EXPIRED
and DELETE
OBSOLETE
prompt for confirmation before deleting files. In releases prior to Oracle9i, RMAN did not prompt when you ran DELETE
EXPIRED
.
See Also:
"Deletion of RMAN Backups and Copies" for concepts, and Oracle9i Recovery Manager Reference for |
You can now back up backup sets from disk to tape or from disk to disk. If RMAN discovers a corrupt block or missing backup piece during the backup, then RMAN automatically performs failover to an existing intact copy.
See Also:
"Backups of Backup Sets" for concepts, and Oracle9i Recovery Manager Reference for |
You can specify up to four different FORMAT
strings when generating a backup set, so each duplexed copy can have a different filename.
You can enable duplexing by specifying the COPIES
parameter on the following commands: CONFIGURE
, SET
, and BACKUP
.
See Also:
|
You can configure RMAN to skip backups of files that have already been backed up. In this way, you can avoid making multiple backups of unchanging files such as archived logs. You can override this functionality with the FORCE
option of the BACKUP
command.
See Also:
"Backup Optimization" for concepts, and Oracle9i Recovery Manager Reference for |
You can specify the NOT
BACKED
UP
SINCE
clause on the BACKUP
command to back up only those files that were not backed up after a specified time. Hence, if a backup fails partway through, you can restart it and back up only those files that were not previously backed up.
See Also:
"Restartable Backups" for concepts, and Oracle9i Recovery Manager Reference for |
When RMAN is restoring files, it checks the files on disk to determine whether a restore is necessary. If not, it does not restore the file. Hence, if a restore fails partway through, you can restart it and restore only those files that were not previously restored. You can override this behavior with the FORCE
option.
See Also:
"Restore Optimization" for concepts, and Oracle9i Recovery Manager Reference for |
Oracle allows different tablespaces in a database to use different block sizes. RMAN backs up tablespaces with different block sizes in the same BACKUP
command, but it never mixes datafiles with different block sizes in a single backup set. Each backup set contains only files with a single block size.
You can configure RMAN so that a specified tablespace is excluded from whole database backups.
See Also:
"Configuring Tablespaces for Exclusion from Whole Database Backups" for concepts, and Oracle9i Recovery Manager Reference for |
If you do not specify either CATALOG
or NOCATALOG
on the command line, and if you do not run CONNECT
CATALOG
at the prompt, then RMAN defaults to NOCATALOG
mode when you run a command requiring a repository.
The RMAN
prefix is removed from non-error messages.
On platforms that support third-party media managers through the Oracle Media Management (SBT) API, the new SBT_LIBRARY
parameter controls which media management library that RMAN uses on channels of DEVICE
TYPE
sbt
. Use SBT_LIBRARY
in the PARMS
setting of the ALLOCATE
CHANNEL
or CONFIGURE
CHANNEL
command to specify the filename of the shared library to be loaded. You can also specify SBT_LIBRARY=oracle.disksbt
, which causes the server to load Oracle's disk sbt
library (formerly called the "dummy API").
If no SBT_LIBRARY
parameter is specified in PARMS
, then the Oracle server attempts to load the dynamic libraries orasbt.dll
on Windows NT and libobk.so
on UNIX. If Oracle cannot locate the library, then the server returns an error.
See Also:
"Configuring RMAN to Make Backups to a Media Manager" to learn about linking to a media manager, and Oracle9i Recovery Manager Reference for |
The Oracle8i features and enhancements described in this section profoundly expanded the 8.0 RMAN functionality. Some of these features were not in all Oracle8i releases.
In release 8.1.7, you can use RMAN to create and back up a standby database.
In Oracle8i release 3 (8.1.7), the BACKUP
VALIDATE
command tests a backup without actually producing output files.
See Also:
"Test Backups Using RMAN" for concepts, and Oracle9i Recovery Manager Reference for syntax |
In Oracle8i release 3 (8.1.7), you can use the SET
SNAPSHOT
CONTROLFILE LOCATION TO DEFAULT
command to set the default filename that is used for the snapshot control file. This default value is platform-specific and depends on the location of the Oracle home.
In Oracle8i release 3 (8.1.7), you can allocate multiple maintenance channels before issuing RMAN maintenance commands. RMAN checks on all channels that have the same device type as the channel used to create the backup.
In Oracle8i release 3 (8.1.7), fewer maintenance commands require the use of a recovery catalog. The only options of the CHANGE
command that require a recovery catalog are the following:
CHANGE
...
AVAILABLE
(note that backup sets, backup pieces, and proxy copies do not require the use of a recovery catalog)
CHANGE
...
UNAVAILABLE
The CROSSCHECK
and DELETE
EXPIRED
commands no longer require a recovery catalog in release 8.1.7.
In Oracle8i release 2 (8.1.6), the CONFIGURE
COMPATIBLE
command set the compatibility level in the recovery catalog. This command helped to solve problems resulting from the way in which RMAN updated and deleted catalog records. These problems are solved in Oracle8i release 3 (8.1.7), so the CONFIGURE
COMPATIBLE
command is still accepted for compatibility, but has no effect.
In Oracle8i release 2 (8.1.6), the AUTOLOCATE
option of the SET
command automatically discovers which nodes of an Oracle Real Application Clusters configuration contain the backups that you want to restore.
In Oracle8i release 2 (8.1.6), the CONFIGURE
COMPATIBLE
command controls the compatibility of the recovery catalog packages with the RMAN executable.
In Oracle8i release 2 (8.1.6), the RESETLOGS
option of the ALTER
DATABASE
command opens the database and reset the online redo logs.
In Oracle8i release 2 (8.1.6), the CHANGE
...
DELETE
, DELETE
EXPIRED
, and BACKUP
...
DELETE
INPUT
commands can now remove catalog records rather than update them to status DELETED
.
Oracle releases the Media Management API, Version 2.0. Support for the version 1.1 Media Management API is maintained. The following are features of the new API:
POOL
parameter of the BACKUP
command provides integration between such products and RMAN.
SEND
command allows commands to be sent directly from an RMAN session to the media management software.
Oracle9i Recovery Manager Reference for
See Also:
BACKUP
syntax and see Oracle9i Recovery Manager Reference for SEND
syntax
The commands CROSSCHECK
BACKUP
, CHANGE
...
CROSSCHECK
, and DELETE
EXPIRED
BACKUP
allow for the synchronization of the recovery catalog with the media manager's catalog. RMAN can determine whether backups and copies are on disk or tape and update their repository record if they are not.
See Also:
|
The output of the LIST
BACKUP
command now prints the list of backups belonging to a backup set in a separate section of the report from the list of data files or archived logs included in the backup set.
A new command, REPORT
NEED
BACKUP
REDUNDANCY
, alerts the user that a new backup is required when fewer than a user-specified number of backups of a datafile exist.
The CREATE
CATALOG
command creates the recovery catalog. It replaces catrman.sql
and associated scripts in the ?/dbs/admin
directory.
Previously it was necessary to run a SQL script to perform a recovery catalog upgrade. Now you can upgrade the catalog with the UPGRADE
CATALOG
command.
The DROP
CATALOG
command removes the recovery catalog schema.
The RMAN commands STARTUP
, SHUTDOWN
, and ALTER
DATABASE
(MOUNT
and OPEN
options only) have the same syntax as their equivalent SQL*Plus commands.
See Also:
|
The DUPLICATE
command allows creation of a new database using the backups of another database.
When backing up on multiple nodes of an Oracle Real Application Clusters configuration, it is possible that some disks have affinity to certain nodes in the cluster such that access to those disks is faster from those nodes than from other nodes in the cluster. RMAN recognizes node affinity, if it exists, and attempts to schedule datafile backups on channels allocated at nodes that have affinity to those files.
RMAN can create up to four concurrent copies of each backup piece.
RMAN no longer requires that backup piece names be explicitly specified using the FORMAT
parameter. By default, RMAN chooses a unique name for each backup piece.
A backup piece is no longer overwritten if an attempt is made to create a backup piece with the same name as an existing one. Instead, RMAN issues an error message.
You can perform TSPITR (Tablespace Point -in-Time Recovery) without a recovery catalog.
Two new views are available to monitor the progress and performance of Recovery Manager backups: V$BACKUP_SYNC_IO
and V$BACKUP_ASYNC_IO
.
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|