3com database adapter module for networker nsr-ora v3.2 ユーザーズマニュアル

System Administrator’s Guide

U42252-J-Z915-1-76

Installation and Configuration

...

Please also refer to the descriptions in the sections 

und 

●

All OPS nodes have to be entered as clients on the OPS node on which 
NSR-ORA is being configured. The clients do not have to belong to any 
group, they just need to have been configured.

●

The archiving monitor (amon) has to be present on each OPS node. Use the 
tool configure_nsrora for the configuration, however, the parameters applying 
to tablespace backup are irrelevant here. It is best to configure the monitors 
manually in NetWorker. Do not forget to start the monitors using the following 
command:

/opt/nsr/oracle/bin/start_amon.sh 

(on HP-UX: /opt/networker/oracle/bin/start_amon.sh).

●

If the tablespaces are to be backed up for several NetWorker servers using 
the file backup_TS_on_different_clients there has to be a save group (and also 
a pool) on each of the NetWorker servers. The name of the save group has 
to be identical in all of the pools (the default name is OPS_TS_BACKUP).

●

The OPS_INSTANCES variable contains the names of all the OPS instances 
that were active when the configure_nsrora command was called. If further 
instances are added later the variable definition in the 
dbo${ORACLE_SID}.init

 file has to be adjusted.

●

OPS does not support backups with the save set OFFLINE.

●

Different OPS instances are supported on the various OPS nodes with the 
environment variable OPS_DIFFERENT_SID_NAMES. This variable is not 
queried in the configure_nsrora script and may have to be set directly in the 
NSR-ORA configuration file dbo{$ORACLE_SID}.init.