Summary of the content on the page No. 1
NSR-ORA V3.2
Database Adapter Module for NetWorker
Edition October 2001
Summary of the content on the page No. 2
Copyright and Trademarks Copyright © Fujitsu Siemens Computers GmbH 2001. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers. This manual was produced by cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de
Summary of the content on the page No. 3
1 Preface This guide provides information about how to install, configure and operate the “NetWorker Save and Restore for ORAcle (NSR-ORA)” V3.2 NetWorker com- ponent. 1.1 Audience The information in this guide is intended for system and database administra- tors. 1.2 Conventions This manual uses the following typographical conventions and symbols to make information easier to access and understand. boldface Indicates emphasized words, e.g.: Using Oracle 8 be always careful for every instance
Summary of the content on the page No. 4
Preface What is New in Release 3.2 1.3 What is New in Release 3.2 With release V3.2 a number of changes have been made to NSR-ORA, influen- cing this guide: ● NSR-ORA V3.2 does now support Oracle 8.x or 9i ● Version 9 of the Oracle database does not include the SVRMGRL command any more. So NSR-ORA now uses the command stored in the SQLDBA vari- able to communicate with the database. However, functionality of NSR-ORA has not been changed. ● NSR-ORA V3.2 now supports the backup on Network Attach
Summary of the content on the page No. 5
2 Introduction This guide to Backing up and Restoring a Database describes the functionality, installation, configuration and adminstration of the NetWorker component “Net- Worker Save and Restore for ORAcle (NSR-ORA)” V3.2. This software compo- nent allows to integrate ORACLE databases into the Networker data backup concept. NetWorker is intended for automatic data backup in heterogeneous networks. Among its advantages are the large number of supported backup media and simple user prompting
Summary of the content on the page No. 6
Introduction The Physical Database Structure 2.1 The Physical Database Structure The physical database (see figure 1) consists of at least one control file, one parameter file, at least two redolog files and at least one database file. control file redolog files database file configuration file Figure 1: The physical database structure ● The database file(s) contain the data dictionary as well as the actual user data (tables, indices, views etc.). ● The redolog files contain information on d
Summary of the content on the page No. 7
Introduction The Database Backup database files control file redolog files SYSTEM USER TEMP Tablespaces Figure 2: Logical database structure 2.3 The Database Backup Every recovery procedure depends on a correctly performed database backup, which consists of copies of the database files being made at operating system level and transferred to an external storage medium or created as a NAS snapshot. These copies depict a state that is not identical to the current one. In the case of one or more
Summary of the content on the page No. 8
Introduction Archive Mode of the Database 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. archive directory database files Oracles archiving process control file redolog files SYSTEM USER TEMP Tablespaces Figure 3: Database running in ARCHIVELOG mode The database system deals only with archiving,
Summary of the content on the page No. 9
Introduction Function Scope these redolog files had already been saved on the backup medium by the archiving monitor and then automatically deleted, they will be read in again and reapplied until the database is up to date. The database is then opened and is again ready for normal operation. The recovery is triggered by the ora_recut and nsrora_rec commands and proceeds automatically; a knowledge of ORACLE is not necessarily required for this (see also chapter “Recovery”). 2.5 Function Scop
Summary of the content on the page No. 10
3 The individual Components The individual components for backing up and recovering an ORACLE database in a NetWorker environment are described in the following section. Four different areas are dealt with: ● The archiving monitor ● The backup component ● The recovery component ● The overall configuration Each section starts with a functional description. This is followed by an expla- nation of the required configuration steps, after which the procedure and opera- tions are illustrated with th
Summary of the content on the page No. 11
The individual Components The Archiving Monitor DBMS database files Oracle’s archiving process control file SYSTEM USER TEMP redolog files Treshold value Tablespaces archive directory Database interface NSR-ORA Archiving monitor Volume management Volume pool management Multiplexing Jukebox support Tape library Figure 4: The archiving monitor The archiving monitor amon has the task of permanently and regularly monitoring and backing up the offline redolog files, which accrue in the archi
Summary of the content on the page No. 12
The individual Components The Archiving Monitor 3.1.1 Starting and Ending the Archiving Monitor A control program start_amon.sh is provided in the directory ${NSR_INST}/ora- cle/bin for coordinating the activities of the archiving monitor. This program can be invoked at operating system level with the relevant parameters (start, status, stop). start_amon.sh [-t {nsr|emc}] [ ...] The -t option is required if NSR-ORA (nsr) and NSR-ORA-EMC (emc) are installed on one machin
Summary of the content on the page No. 13
The individual Components The Archiving Monitor AMON_GROUP=amon_ora_psi AMON_MAX_LOGS=4 AMON_INTERVALL=1800 AMON_MIRROR_GROUP=amon2_ora_psi AMON_MIRROR_SERVER=psi With these prerequisites fulfilled, the user can start the archiving monitor: sh> start_amon.sh start ora ORACLE_SIDs : ora start amon for oracle instance ora ... A subsequent status enquiry generates the following output: # start_amon.sh status ora ORACLE_SIDs : ora Configuration and Status summary of amon at 15.09.00 (11:30:41): Sys
Summary of the content on the page No. 14
The individual Components The Archiving Monitor 3.1.2 Logging While the archiving monitor is active, the occupancy level of the archive direc- tory and other important events are logged at regular intervals (AMON_INTERVALL) in the protocol file ${DBO_CONFIG_DIRECTORY}/prot/redologs/amon.prot. Protocol file There are four generations of the protocol file. The current protocol file is appended to the file amon.old with each restart. If this file exceeds a size of 5 Mbytes, it is renamed fr
Summary of the content on the page No. 15
The individual Components The Backup Component ...... 00-05-08:16:52:01: DEBUG:oraarch1_54.dbf 01/21/00 13:13:15 s: 0 m: 0 00-05-08:16:52:01: DEBUG: Print of a save_cmd: /opt/networker/bin/save -i -l full -g amonorapsi -s psi 00-05-08:16:52:01: oraarch1_42.dbf oraarch1_43.dbf oraarch1_45.dbf oraarch1_44.dbf oraarch1_46.dbf oraarch1_47.dbf oraarch1_48.dbf oraarch1_49.dbf oraarch1_50.dbf oraarch1_51.dbf oraarch1_52.dbf oraarch1_53.dbf oraarch1_54.dbf. 3.2 The Backup Component The
Summary of the content on the page No. 16
The individual Components The Backup Component DBMS database files Oracle’s archiving process control file SYSTEM USER TEMP redolog files Treshold value Tablespaces archive directory Database interface NSR-ORA Backup Archiving component monitor NetWorker user interface Volume management Volume pool management Multiplexing Jukebox support Tape library Figure 5: The backup component 3.2.1 Offline Backup of the Database configure_nsrora and configure_networker can be used, if required, to cr
Summary of the content on the page No. 17
The individual Components The Backup Component 1. The database is started up briefly to determine the database files allocated to a tablespace. Normally, several tablespaces are backed up during an archiving process. 2. The database is closed. 3. All the database files of a tablespace are backed up, irrespective of whether system files or raw devices are involved. The database must not be started up during an offline backup! You will ! receive an error message at the end of the backup if
Summary of the content on the page No. 18
The individual Components The Backup Component 3.2.2 Online Backup of the Database An online backup of the database is performed whenever the database is open at the time of the backup. In contrast to offline backups, the following phases are carried out: 1. All database files allocated to a tablespace are determined. 2. Backup is commenced with the ORACLE-specific command alter tablespace begin backup. 3. All database files of this tablespace are backed up, irrespective of w
Summary of the content on the page No. 19
The individual Components The Backup Component 3.2.4 Checking backups (troubleshooting) If an error occurs when backing up the database or if one of the backup pro- cesses does not end cleanly, the entire database backup is aborted and all tablespaces are reset to the status NoSave. You can check whether a backup has been completed successfully by examining the protocol files (*.prot) which are located in the directory /nrs/oracle/${ORACLE_SID}/prot and its subdirectories. Log files from loca
Summary of the content on the page No. 20
The individual Components The Backup Component The shell script saveinfo.sh in the directory $NSR_INST/oracle/bin evaluates the protocol files save*.prot in the subdirectory tablespaces and tells you the status, the start and end of a backup, the type of backup (online|offline) and the names and sizes of the backed up tablespaces. You can call saveinfo.sh at any time, even while there is a backup in progress. It is called automatically when a tablespace backup has been completed and writes
