System Administrator’s Guide U42252-J-Z915-1-76
Installation and Configuration Configuration
●GZIP is used with the default value 1.
●BZIP2 no level is given to, so the default value of the algorithm will be
used (see the uasm(1) manpage for further information).
4.3.5 Defining backup sets (save sets)The NSR-ORA administrator is able to specify save sets (offline backups, full
backups, partial backups) by defining corresponding sub-directories in the
directory $DBO_CONFIG_DIRECTORY. The path to these sub-directories is
entered as Save Set in NetWorker’s client windows. Furthermore, empty files
must be created in the sub-directories (e.g. with touch) to represent the names
of tablespaces requiring backup.
The configuration tool config.sh can be used to get an overview of the available
tablespaces and their space requirements (see section “Establishing table-
space names”).
Example
Suppose the configuration directory (DBO_CONFIG_DIRECTORY) is
/nsr/oracle/ora. The database consists of the tablespaces SYSTEM,
ROLLBACK_TS, TEMP_TS, USER1_TS and USER2_TS. The objective is to perform
a full backup of the database once a week every Saturday and partial backups
of it daily (except Sunday). Furthermore, the frequently modified tablespace
USER1_TS is to be backed up daily to ensure quick restarting in case of a failure.
Automatic offline backups should also be performed occasionally.
The backup concept described herein (backup of tablespaces in a
weekly cycle) is not mandatory. You may also develop different backup
concepts.
The NSR-ORA administrator creates the directories monday to friday and
${ORACLE_SID}_full_save for full and ${ORACLE_SID}_offline for offline backups,
under /nsr/oracle/ora, which contain the following empty files:
/nsr/oracle/ora/monday:
SYSTEM
USER1_TS
/nsr/oracle/ora/tuesday:
TEMP_TS
USER1_TS
i