Oracle7 Enterprise Backup Utility Administrator's Guide | ![]() Library |
![]() Product |
![]() Contents |
![]() Index |
This chapter describes how to set up the Enterprise Backup Utility
Topics covered in this chapter are:
Perform the following steps to install EBU and set up a EBU Catalog:
Additional Information:
Oracle7 Server Administrator's Guide for instructions on how to change the name of a target database, if necessary.
|
obk/obk@ebu_cat
Caution: Proper installation of the DMO and specifying its location in the search path for shared libraries is essential for using EBU. |
The different scenarios and procedures for creating the EBU Catalog are described beginning in the section "Setting Up the EBU Catalog".
Registration does the following:
catalog_user/password@connect_alias_to_backup_catalog
EBU includes a version of the DMO that bypasses the media management software and writes directly to disk. This DMO is in the file EBU_HOME/lib/libobk.{a,so}.DISK (the exact filename varies slightly from platform to platform). On NT, the file is named ORASBT.DSK. It should only be used for testing purposes, such as trying to determine whether a problem originates from EBU or the media management software.
The libobk.DISK DMO is indicated in the log file by the following message:
BACKUP_DIR is not set!!
The following banner may also be written to the log file, indicating the use of the libobk.DISK file:
Tape Management Software: Release 9.9.9.9 Vendor API: Disk API (Oracle Internal Only)
Unless you intend to perform all EBU operations as INTERNAL, each target database must have a backup user. This is the Oracle user under which all Enterprise Backup Utility operations are performed. Creating the backup user and performing all backup operations with it ensures that the Enterprise Backup Utility has sufficient privileges to execute the necessary SQL commands on the target database.
If not using INTERNAL, you must create the target database backup user with the ebutool utility before registering a database in the EBU Catalog.
$ ebutool -cretrgtusr
The utility prompts you for the SYS user password and other necessary information for creating the backup user. If you want to change any information about the target database or backup user, you can run ebutool -cretrgtusr again.
When you invoke ebu to register a database or update its configuration information, the Enterprise Backup Utility prompts you for the backup user/password and the connect alias to the target database. You can pre-empt these prompts by defining the environment variable EBU_DB_LOGIN in the startup files of EBU users.
The syntax for EBU_DB_LOGIN is:
backup_user/password[@connect_alias_to_target_database]
If you define a user/password in EBU_DB_LOGIN, but no connect alias, the Enterprise Backup Utility defaults to the SQL*Net V2 Pipe driver.
EBU requires INTERNAL, with the OS user being in the OSDBA group, or by a user with SYSDBA privileges. EBU attempts to connect to the database AS SYSDBA, unless the user is INTERNAL. You must grant the SYSDBA role to that user, or be in the OSDBA group. ebutool -cretrgtusr will perform the grant. When connecting, the backup user must then connect to the Server as SYSDBA or INTERNAL. For example:
SQL> CONNECT backup_user/password AS SYSDBA
Additional Information:
Chapter 1, "The Oracle7 Database Administrator", in the Oracle7 Server Administrator's Guide for more information on SYSDBA administrative privileges and how to grant them. |
Figure 2-1, "EBU Catalog Installation Scenarios" illustrates the possible scenarios for creating a EBU Catalog, and outlines the appropriate procedure for each one. Each procedure is described in detail, beginning.
EBU creates the EBU Catalog schema automatically, the first time it is invoked. Prior to invoking the utility, you must perform the following steps:
If all EBU installations can be upgraded within a single time frame, use the following procedure:
$ ebu -upgrade
If you intend to operate EBU release 2.0 or 2.1 and release 2.2 at the same time, use the following procedure:
$ ebutool -migrate
The utility prompts for the following connect strings:
The ebutool utility then creates the structures for the new catalog, copies job entries from the 2.0/2.1 catalog to the 2.2 catalog, and finally overwrites the catalog.ebu file in the EBU_HOME/admin directory to point to the new catalog database.
Remaining target databases running EBU 2.0/2.1 can be upgraded by installing EBU 2.2 on the target database and running the ebutool -migrate command.
Backing up, restoring, and recovering a database requires a high level of Oracle server privileges. The privileges required by EBU and the reasons for those privileges are summarized in the following sections.
The ebu executable assumes the privileges of the oracle software owner (setuid oracle) for the following reasons:
There are no special execution permission for EBU on the NT platform.
EBU starts the Instance Manager (the brd process) once (in Unix, once per oracle software owner) per host machine for the following reasons:
The Oracle user used to connect to the target database must be granted SYSDBA privileges for the following reasons:
![]() ![]() Prev Next |
![]() Copyright © 1997 Oracle Corporation. All Rights Reserved. |
![]() Library |
![]() Product |
![]() Contents |
![]() Index |