oracle-rman-survival-guideakadia.doc

aknight

26页

1次

2025-04-02

免费下载

Oracle RMAN Survival Guide or ...

... «when a crisis is in progress, it is easy to make a simple mistake»

Overview

This guide is a quick-reference guide for Recovery Manager (RMAN), Oracle's

utility to manage all of the Oracle database backup and recovery activities. This

guide is not a comprehensive backup and recovery book. It contains an

overview of RMAN architecture, shows briefly how to backup and restore

databases using RMAN, describes catalog setup issues, and provides quick-

reference syntax diagrams of RMAN commands.

The purpose of this guide is to help you quickly find the syntax for, and use,

RMAN commands to back up, restore, and recover a database. We also point

out that the batch mode examples in this guide are scripted with Unix shell

scripts. Many of these examples contain Unix paths that are appropriate for our

environment. If you are developing your own set of scripts, you will want to

change the examples to reflect your own environment.

The real success of a backup depends on how effectively you can restore the

databases from these backups. Develop recovery scripts and make sure to test

and practice the different recovery scenarios. After a new incarnation of a

database is created, make sure to run a full backup of the database. Also,

make sure to run a full export of the database once the database is recovered.

It will go through all the database blocks and is a good way to check whether

there are still corrupt datafiles.

Which Files must be backed up?

All files in the grey area below must be backed up.

Database Files (with RMAN)

Control Files (with RMAN)

Offline Redolog Files (with RMAN)

INIT.ORA (manually)

Password Files (manually)

Note that the Online Redolog Files are not backed up !

The parameter file INIT.ORA and the password file must be backed up manually.

RMAN Architecture

Recovery Manager (RMAN) is a utility that can manage all of your Oracle backup and recovery activities. DBAs are often wary of

using RMAN because of its perceived complexity and its control over performing critical tasks. The traditional backup and recovery

methods are tried-and-true. Thus, when your livelihood depends on your ability to back up and recover the database, why implement

a technology like RMAN? The reason is that RMAN comes with several benefits:

← Incremental backups that only copy data blocks that have changed since the last backup.

← Tablespaces are not put in backup mode, thus there is no extra redo log generation during online backups.

← Detection of corrupt blocks during backups.

← Parallelization of I/O operations.

← Automatic logging of all backup and recovery operations.

← Built-in reporting and listing commands.

RMAN's architecture is a combination of an executable program (the RMAN utility) and background processes that interact with one

or more databases and with I/O devices. There are several key architectural components to be aware of:

← RMAN executable

← Server processes

← Channels

← Target database

← Recovery catalog database (optional)

← Media management layer (optional)

← Backups, backup sets, and backup pieces

The following sections describe each of these components.

of 26

免费下载

oracle rman

相关文档

评论