| Oracle® Database Recovery Manager Quick Start Guide |
|
|
|
Oracle® Database
Recovery Manager Quick Start Guide
10g Release 1 (10.1)
December 2003
Part No. B10769-01
Recovery Manager Quick Start Guide has three purposes:
· To introduce the basic concepts of Oracle backup and recovery, and the Recovery Manager (RMAN), the tool Oracle recommends that you use for your backup and recovery
· To orient you on the rest of the backup and recovery documentation set
· To serve as a convenient quick reference for the most frequently used RMAN commands, options and views
This document is organized into the following sections:
· Overview of Backup and Recovery Documentation Set
· Overview of the RMAN Environment
· Configuring Persistent Settings for the RMAN Environment
· Restoring and Recovering Database Files
· Reporting on RMAN Operations
· Managing the RMAN Repository
· Repetitive Tasks: RMAN and Scripting
Conventions for Command Syntax
The following table shows the syntax convention used in this manual.
| Convention | Meaning |
|
[ ] |
Brackets enclose one or more optional items. Do not enter the brackets. |
|
{ } |
Braces enclose two or more items, one of which is required. Do not enter the braces. |
|
| |
A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar. |
|
... |
Horizontal ellipsis points indicate either: · That we have omitted parts of the code that are not directly related to the example · That you can repeat a portion of the code |
|
. . . |
Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example. |
|
Other notation |
You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown. |
|
Bold |
Bold type indicates the introduction of a significant term. Usually a brief definition or a longer discussion follows the introduction of the term. |
|
Italics |
Italicized text indicates placeholders or variables for which you must supply particular values. |
|
UPPERCASE |
Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase. |
|
lowercase |
Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. |
Overview of Backup and Recovery Documentation Set
Besides this quick start guide, there are three volumes in the backup and recovery documentation set.
· Oracle Database Backup and Recovery Basics explains the concepts of backup and recovery and the most common techniques for using RMAN for backup, recovery and reporting in more detail, as well as providing more information on how to plan a backup and recovery strategy.
· Oracle Database Backup and Recovery Advanced User's Guide presents in-depth information on RMAN architecture, backup and recovery concepts and mechanisms, advanced recovery techniques such as point-in-time recovery and database flashback features, and backup and recovery performance tuning. It also covers user-managed backup and recovery, using host operating system facilities instead of RMAN. This volume is essential for backup and recovery of more sophisticated database deployments, and for advanced recovery scenarios.
· Oracle Database Recovery Manager Reference provides complete information on syntax and semantics for all Recovery Manager commands, and describes the database views available for reporting on backup and recovery activities.
Overview of the RMAN Environment
Installed with the database, Recovery Manager (RMAN) is an Oracle database client which performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files.
The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following:
· The target database to be backed up
· The RMAN client, which interprets backup and recovery commands, directs server sessions to execute those commands, and records your backup and recovery activity in the target database control file.
Some environments will also use these optional components:
· A flash recovery area, a disk location in which the database can store and manage files related to backup and recovery;
· Media management software, required for RMAN to interface with backup devices such as tape drives;
· A recovery catalog database, a separate database schema used to record RMAN activity against one or more target databases.
About the Target Database
The target database is the database that you are backing up, restoring, or recovering with RMAN.
About the RMAN Client
RMAN is a command-line-oriented database client, much like SQL*Plus, with its own command syntax. From the RMAN client you can issue RMAN commands and SQL statements to perform and report on backup and recovery operations.
RMAN can take interactive input or read input from plain text files (called command files). RMAN then communicates with one or more server processes on the target database server which actually perform the work. You can also access RMAN through the Enterprise Manager; for details see Oracle Enterprise Manager Administrator's Guide.
The RMAN executable is typically installed in the same directory as the other database executables. On Unix systems, for example, the RMAN executable is located in $ORACLE_HOME/bin.
About the RMAN Repository
RMAN maintains metadata about the target database and its backup and recovery operations in the RMAN repository. Among other things, RMAN stores information about its own configuration settings, the target database schema, archived redo logs, and all backup files on disk or tape. RMAN's LIST, REPORT, and SHOW commands display RMAN repository information.
RMAN repository data is always stored in the control file of the target database. The CONTROL_FILE_RECORD_KEEP_TIME initialization parameter controls how long backup records are kept in the control file before those records are re-used to hold information about more recent backups. The repository can also be kept in a recovery catalog, a separate database that keeps historical data on backup activities much longer than the control file and preserves backup information if the control file is lost.
About the Flash Recovery Area
The Automatic Disk-Based Backup and Recovery feature simplifies managing disk space and files related to backup and recovery, by managing all backup and recovery related files in a flash recovery area. You set the flash recovery area size and location, using the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization parameters. You also specify a retention policy that dictates when backups may be discarded. RMAN then manages your backup storage, deleting obsolete backups and backups already copied to tape when space is needed, but keeping as many backups on disk as space permits. This minimizes restores from tape during data recovery operations to shorten restore and recovery times.
About the Recovery Catalog
In addition to RMAN repository records, the recovery catalog can also hold RMAN
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/13750068/viewspace-509836/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/13750068/viewspace-509836/
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
