The IRIX NetWorker BusinesSuite Module for Oracle provides a connection between the Oracle7 Enterprise Backup Utility (EBU) and NetWorker. The BusinesSuite Module for Oracle integrates backup and restore procedures for Oracle7 Server databases into the comprehensive network–wide data protection facilities that NetWorker provides.
In the previous release, BusinesSuite Module for Oracle was called Database Module for Oracle, abbreviated DMO. This acronym still exists in subsystem names.
This chapter provides a brief introduction to the three product components: Oracle7 Enterprise Backup Utility, IRIX NetWorker, and BusinesSuite Module for Oracle. After the introduction come BusinesSuite Module for Oracle installation instructions.
Although the reliability of computer equipment has improved greatly in recent years, hardware failures still occur, sometimes with catastrophic results.
In a client-server environment, data can be lost not only after hardware failures, but also because of user errors. Software bugs or procedural flaws and simple user error are common culprits, requiring database media restores. A viable backup strategy can help you recover from these potentially disastrous situations.
Many database administrators do not recognize the jeopardy of failing to take regular backups of database tablespaces and frequent backups of archived redo logs. If all archived redo logs are lost, a database can only be recovered to the time of its last full backup. Without backups or archived redo logs, the database cannot be recovered at all.
The Oracle7 Enterprise Backup Utility (EBU), available from Oracle Corporation, provides database backup and restore services for Oracle7 Server database files.
The Enterprise Backup Utility provides
online and offline database backup
high performance through parallel backups and restores
an intelligent interface to Oracle databases
parallel processing
well-defined backup strategies
error checking
IRIX NetWorker is a high-capacity, easy-to-use, network data storage-management solution that provides data backup and recovery for heterogeneous networks of servers and clients. NetWorker simplifies the storage management process and reduces the administrative burden by automating and centralizing your data storage operations.
With NetWorker, you can
perform automated “lights–out” backups during off-peak hours
use centralized administration to configure, monitor, and control backups from anywhere on a network
automate tape handling tasks using an intelligent media manager that NetWorker provides, supporting a wide variety of 4 mm DAT, 8 mm, and high-end devices, as well as bar code label recognition and cleaning cartridge support
increase backup performance by simultaneously sending data from multiple datafiles to the backup server
use concurrent device support to direct data streams to multiple backup devices for even greater speed
BusinesSuite Module for Oracle is an add-on module for NetWorker that provides automated backup media management and scheduling for the Enterprise Backup Utility.
NetWorker BusinesSuite Module for Oracle provides
support for local backup or distributed backup to a centralized backup server
high performance throughput with support for multiple, concurrent high-speed devices, such as DLT drives
Database Module for Oracle (DMO) is the former non-marketing name for the component now called BusinesSuite Module for Oracle. The two are completely equivalent. The name “DMO” still survives in package and program names.
If you have not already done so, refer to the IRIX NetWorker Installation Guide for instructions on how to install, license, and configure the NetWorker server.
Before installing the BusinesSuite Module for Oracle, you should have the following:
a Silicon Graphics server running Oracle® and IRIX™ 6.2 or higher
5 MB of free disk space to store software and provide space for new indexes
a large storage media device that is supported by IRIX NetWorker
Follow this procedure to install the IRIX NetWorker BusinesSuite Module for Oracle:
On the NetWorker server, switch user to root.
% /bin/su - Password:
If the NetWorker server is already running, stop it now:
# /etc/init.d/networker stop
Run the inst command, specifying the location of the NetWorker distribution:
# inst -f /CDROM/dist inst> list
Select subsystems inside inst. Use Table 1-1 as a guide to selecting product images. To install the DMO software and documentation, enter these commands:
Inst> keep * Inst> install networker4.sw.DMO networker4.books.NetWorkerDMO
For more information on the available product images, refer to the IRIX NetWorker Release Notes. For details about inst, refer to IRIX Admin: Software Installation and Licensing, or see the inst(1M) reference page.
Table 1-1. Subsystems for NetWorker Servers
Subsystem
Description
Required/Optional
networker4.sw.DMO
Database Module for ORACLE, connector for parallel backups
Optional; license required
networker4.books.NetWorkerDMO
Online version of DMO book
Optional; InSight needed
Perform the installation and exit inst:
Inst> go ... Inst> quit
Start the NetWorker daemons with this command:
# /etc/init.d/networker start
You must purchase an IRIX NetWorker BusinesSuite Module for Oracle for every NetWorker server (machine) on which you wish to use NetWorker. Each NetWorker Database Module must be licensed separately. Refer to “Licensing NetWorker Severs” in the IRIX NetWorker Installation Guide for more information.
For specific Oracle Enterprise Backup Utility installation instructions, refer to your Oracle Enterprise Backup Utility Installation Guide.
If the Enterprise Backup Utility is not yet installed on the database server when you install BusinesSuite Module for Oracle, be sure to install BusinesSuite Module for Oracle first—then install the Enterprise Backup Utility. However, if you are upgrading and the Enterprise Backup Utility was already installed, you do not need to reinstall it after upgrading BusinesSuite Module for Oracle.
Below are the general steps to install the Oracle Enterprise Backup Utility. These are provided only as a reminder; refer to the manual cited above for specifics.
Run orainst.
Select the Oracle7 Enterprise Backup Utility Executables choice.
Select the Third Party Media Management Software Vendor. If Legato is not offered as a choice, select other.
Specify the Vendor Software Installation directory. Enter /usr/lib, where the library modules (libobk.so and libobk.so.1) are installed.
Specify the UNIX group for the Oracle Enterprise Backup Utility executables. Commonly dba, this is the user group that perform backup and restore operations.
Enter the Backup Catalog connection information. You may enter a value here even if the Catalog has not been created, because the Oracle Installer does not verify the connection. An example connection string could be obk/[email protected].
Note: If you have not yet created the Backup Catalog, be sure to note the connection information you enter for use when creating the Backup Catalog. The connection string can be modified manually by editing $OBK_HOME/admin/catalog.obk. Check the orainst installation log file to verify that no errors have been logged in it. By default, $ORACLE_HOME/orainst/install.log is the log file.
Create the Backup Catalog database. This is a separate Oracle database containing information used by the Enterprise Backup Utility. This database can be created by using the Oracle Installer or any script normally used.
In orainst again, select the Backup Catalog choice.
Enter the SQL*Net connection string for the Backup Catalog database. For example, use P:OBK for SQL*Net v1 and use OBK for SQL*Net v2.
Enter the password for SYS database user if this password was not already changed after creation of the Backup Catalog. The default password is change_on_install.
Specify the user who will own the Backup Catalog. This should be the same user as specified in the connection string of step 6.
The Oracle Installer creates the Backup Catalog tables. This may take a while.
Check the installation log file, as in step 7.
As superuser, run the root.sh script.
If you encounter problems during this phase, please refer to the Oracle documentation, or contact Oracle technical support.
Follow these guidelines to ease the burden of disaster recovery:
Frequency of backups is a trade-off of time spent now against time spent later recovering your database after a crash.
Run in ARCHIVELOG mode. You cannot perform online backups in NOARCHIVELOG mode.
Institute mirrored control files.
More importantly, institute mirrored online redo logs. If you lose the current redo logs, you will be able to recover your database only from the point of the last archived redo log. This is because any recovery relies on the redo logs to synchronize your database with the latest transactions.
If you are using EBU 2.0 or earlier, back up your Backup Catalog using obkexp.sh after every database backup. If you are using EBU 2.1 or later, you do not need to do this, because the program performs the backup automatically.
Back up your archived redo logs frequently between database backups.