3com database adapter module for networker nsr-ora v3.2 Manuel D’Utilisation

System Administrator’s Guide

U42252-J-Z915-1-76

Introduction

NSR-ORA checks that the database is in ARCHIVELOG mode, and will abort 
the backup of the database if this is not the case if an online backup is to be car-
ried out. An offline backup can be performed even if the database is not in 
ARCHIVELOG mode.

Figure 3: Database running in ARCHIVELOG mode

The database system deals only with archiving, it does not provide for the 
subsequent management of the redolog files. The database will come to a halt 
as soon as the archive directory is full. NSR-ORA therefore contains a module 
which monitors the archiving process, the archiving monitor amon. At regular 
time intervals, the daemon of the archiving monitor transfers the redolog files 
archived by ORACLE to external backup media.

To make a full database backup, all file types must be included in the saving 
procedure.

Both the control file and the database programs (executables) can be backed 
up using standard NetWorker functions (i.e. without NSR-ORA).

For securing the database files, NSR-ORA supports full backup as well as 
restoration and recovery of the database by reapplying the redolog files.

For a backup, a correlation is first made between tablespaces and database 
files. In this manner, the logical tablespace concept of the database is mapped 
onto a physical structure, and the database files are then backed up. In the case 
of an online backup, the ORACLE-specific commands begin backup and end 
backup

 are included. 

When a recovery is required, shutdown of the database is followed by a crash 
analysis. If a database file has been lost, the required backup files are first 
restored from the backup medium. The recovery of the database is subse-
quently commenced; this involves reapplying the appropriate redolog files. If 

control file

USER

database files

redolog files

SYSTEM

TEMP

Tablespaces

Oracles

archiving

process

archive

directory