Be sure you have installed the software as described in Chapter 1, “Module Components and Installation,” before beginning this chapter. This chapter describes configuration options to enable the system running BusinesSuite Module for Oracle to perform manual and scheduled backups.
|Caution: Silicon Graphics strongly recommends that you institute mirroring (plexing) of the online redo logs and the control file of your target database. A target database is the database that you want NetWorker to back up as a safeguard against data loss or corruption. Keep mirrored copies on different disks. If online redo logs are lost in a disk crash, all changes made to the database since its last backup will be lost permanently.|
This section describes the five supported options for setting up the BusinesSuite Module for Oracle in your Oracle7 and NetWorker environment. Each of these five configurations consists of the following six components:
|Note: The Oracle7 Enterprise Backup Utility software, Oracle7 RDBMS Server, NetWorker client, and the BusinesSuite Module for Oracle software must be installed on the same machine. The other two components, the Oracle7 Enterprise Backup Utility Backup Catalog and the NetWorker server software, may reside on one or two other separate machines. For more information on the Enterprise Backup Utility Backup Catalog, see the section “The Oracle Backup Catalog”.|
In this first configuration option, all six components are installed on the same machine in your enterprise, as shown in Figure 3-1.
The advantage of this installation, in addition to requiring only a single computer, is that it provides higher performance than a backup over the network. The main disadvantage
of this configuration is the risk of it being a single point of failure.
In this configuration, five of the six components are installed on the same machine—the Enterprise Backup Utility and its Backup Catalog, the Oracle7 RDBMS, NetWorker client, and BusinesSuite Module for Oracle. The NetWorker server is installed on a separate machine, as shown in Figure 3-2. Here, your Oracle7 Server is a remote NetWorker client.
The advantage of this configuration is that it provides some independence for your NetWorker server and the NetWorker indexes while it maintains the independence of having your backups on a separate machine. The disadvantage of this configuration is the risk of the Backup Catalog being unavailable in a disaster recovery scenario on your Oracle7 Server platform. Should the Backup Catalog become unavailable during a system failure, you would need to recover the Backup Catalog before you could recover your Oracle7 database.
In this third possible configuration, five of the six components are again installed on the same machine—the Enterprise Backup Utility, Oracle7 RDBMS, BusinesSuite Module for Oracle, NetWorker client, and NetWorker server. The Enterprise Backup Utility Backup Catalog is installed on a separate machine, as shown in Figure 3-3. This installation is one of those recommended by Oracle.
One advantage of this configuration is the location independence of the Enterprise Backup Utility Backup Catalog. Another advantage is that the backup of the Oracle7 database is local to the NetWorker server, which generally gives higher performance than backups over the network. The disadvantage of this configuration is the additional maintenance required for the machine hosting the Backup Catalog.
Another configuration option recommended by Oracle is shown in Figure 3-4. In this configuration, the Enterprise Backup Utility, Oracle7 RDBMS, NetWorker client, and BusinesSuite Module for Oracle are all installed on the same machine, while the Enterprise Backup Utility Backup Catalog and NetWorker server are both installed on a separate machine.
The principal advantage of this configuration is the location independence of both the Backup Catalog and NetWorker server from the Oracle7 database server machine. The availability of both the Backup Catalog and NetWorker server is critical in being able to perform a restore operation. The disadvantages of this configuration are the additional maintenance required for the machine hosting the Backup Catalog and NetWorker server, as well as the potential performance loss during backups over the network.
In the most complex of the five possible configurations, the components are installed on three separate systems, as shown in Figure 3-5.
Here, the Enterprise Backup Utility, Oracle7 RDBMS, NetWorker client, and BusinesSuite Module for Oracle are all installed on the same system. The Enterprise Backup Utility Backup Catalog is installed on a second system, and the NetWorker server is installed on a third system. In this type of three-system installation, each system has a well-defined role in the backup scheme. This installation is also one of the configurations recommended by Oracle.
The advantage of this configuration is the independence of the Backup Catalog and NetWorker server from the Oracle7 database server. The disadvantage is the additional maintenance required for all three systems, plus the potential performance loss during backup over the network.
Each of the five possible configuration options presented above has its advantages and disadvantages. The level of protection you can afford depends on both your available resources and your priorities.
For sites with a small backup window, where performance is critical and backups over the network are undesirable, Silicon Graphics recommends configuration Option 3, shown in Figure 3-3. For sites where rapid restore of the Oracle7 server will be critical in a disaster recovery scenario, Silicon Graphics recommends either Option 4 (Figure 3-4) or Option 5 (Figure 3-5). These Options are also recommended for sites that back up more than one database using the Enterprise Backup Utility.
Oracle Corporation recommends that any given site have only one Backup Catalog database per enterprise.
You must install the Oracle7 Enterprise Backup Utility executables one per Oracle database instance. That is, for every database that operates under a different oracle owner account on the same machine, you must install a separate copy of the Enterprise Backup Utility executables. Note that you do not need a separate installation of the Enterprise Backup Utility executables if all Oracle7 databases on a particular machine operate under the same oracle owner.
You need to install BusinesSuite Module for Oracle only once per system, regardless of how many separate Enterprise Backup Utility installations may be on that machine. The BusinesSuite Module for Oracle also supports concurrent backup of separate databases on the same system using separate Enterprise Backup Utility instances.
The Oracle Backup Catalog is where the Enterprise Backup Utility stores historical information about database backups. It is a collection of Oracle database tables containing structural information about target databases, along with backup and restore history for each database. The Backup Catalog should be stored in the Backup Catalog Database, a dedicated database about 20 megabytes in size. If the catalog database fails, you must recover it before you can start recovering your target database.
|Caution: Inability to access the catalog database implies inability to recover the target database. This is why Oracle recommends that you keep your backup catalog on a separate machine from the target database.|
The Oracle Enterprise Backup Utility uses SQL*Net™ to access the Backup Catalog. If you are using EBU 2.0 or earlier, you should use NetWorker to back up the Backup Catalog database so it can be restored in case of failure. To back up the Backup Catalog database, use Oracle's shell script obkexp.sh to export the database to disk. Refer to the Oracle7 Enterprise Backup Utility Administrator's Guide for the procedure. Then use NetWorker to back up the files.
With EBU 2.1, your Backup Catalog Data is backed up automatically after every series of backups of the target database.
Before performing backup or restore operations on your database, you must register it in the Backup Catalog database. Refer to the Oracle7 Enterprise Backup Utility Administrator's Guide Release 2.0 for a detailed description of registration, in the section “Registering a Target Database” on page 2-5.
Here is a sample script, called register_db:
register db_name = “TARGET01” oracle_sid = “TARGET01” oracle_home = “/oracle” pfile = “?/dbs/[email protected]”, “?/dbs/[email protected]” log = “/oracle/obackup/logs/register.log”
To run obackup using the register_db command script, enter the following command as oracle owner:
% obackup register_db
When an Oracle registration script completes successfully on a system, you see the following type of output from it:
Oracle7 Enterprise Backup Utility: Release 126.96.36.199.2 Copyright (c) Oracle Corporation 1979, 1996. All rights reserved. CORE Version 188.8.131.52.0 - Production NLSRTL Version 184.108.40.206.0 - Production
Once a target database has been initially registered, if the Enterprise Backup Utility finds that the Backup Catalog configuration is outdated prior to an online backup, it will automatically update it before starting the backup of the target database. This autoconfiguration feature requires that the target database be online and does not apply to offline backups.
If you are conducting offline backups and the target database configuration changes, be sure to run the REGISTER command manually to update the Backup Catalog. The types of changes that require updating of the Backup Catalog include
adding or dropping a tablespace
adding or dropping control files
moving database files to a different location
resizing database files
performing an OPEN RESETLOGS
To enable the proper use of NetWorker with BusinesSuite Module for Oracle, the oracle owner must be on the NetWorker Administrator list on your NetWorker server machine.
To add the oracle owner to the UNIX NetWorker server's Administrator list, perform the following steps:
Log in as root user on the NetWorker server machine.
Run the NetWorker Administrator GUI on the NetWorker server:
# nwadmin &
In the nwadmin window, choose Server Setup from the Server menu, to open the Server window.
In the Server window, if [email protected]db_servername (where db_servername is the fully qualified name of the database server machine) does not already appear in the Administrator list, enter it in the text field next to Administrator, click the add button beside the list. The oracle user appears in the list below, as shown in Figure 3-6. Finally, click Apply at the bottom of the window.
Close the Server window by choosing Exit from the File menu. You might want to close the nwadmin window as well, by choosing Exit from the File menu.
Now, proceed to Chapter 4.