Oracle7 Enterprise Backup Utility Administrator's Guide

Library

Product

Contents

Index

CHAPTER 3. Invoking EBU and Registering Target Databases

• Enterprise Backup Utility Usage
• Registering a Target Database
• Target Database Specifiers
• Autoregistration

Topics covered in this chapter are:

• Enterprise Backup Utility Usage

• Registering a Target Database

• Target Database Specifiers

• Autoregistration

Enterprise Backup Utility Usage

Overview for Using the Utility

You only need to register a target database once. Subsequent registration updates are performed automatically by the utility. To register a database:

1. Create a register command script.

2. Invoke the script with the obackup command:

	$ obackup script_name

To back up a database:

1. Create a backup command script.

2. Invoke the script with the obackup command:

	$ obackup script_name

To restore a database, perform the following steps:

1. Depending on the type of restore, either shut down the target database, or bring a tablespace/datafile offline.

2. Create a restore command script.

3. Invoke the script with the obackup command:

	$ obackup script_name

The Enterprise Backup Utility builds a job list with the information in the backup catalog, then uses the media management software to retrieve backups from the appropriate media devices.

Additional Information: See Also: For a complete description of command scripts, see appendices A and B of this guide.

Invoking the Utility

To invoke an EBU operation from the UNIX shell, enter the obackup command with the desired script name at the command prompt. For example:

$ obackup backondb_prod1

where backondb_prod1 might be the name of your script to perform an online backup of the database with the ORACLE_SID prod1. Invoking the utility without any arguments returns the command usage:

obackup [ -ch[ecksum] | -t[est] ] 
        [ -noa[utoregister] ] 
        [ -s[ilent] ] 
        [ -ob[k_home]=path ] 
        command_filename 

or:

obackup -u[pgrade] 

Command Line Options

-ch

Checksum: invokes the utility with file checksumming enabled for backups and restores. Cannot be used with the test specifier or -test command option.

-t

Test: runs scripts without performing I/O operations. Use this specifier to verify that scripts work as expected. Test does not work with the register command, and cannot be used with the checksum command option or specifier.

-s

Silent: suppresses output to screen when a log file has been specified. Note that a log file must be specified in the script when using this option.

Syntax error messages are sent to standard error, even if the silent option has been set.

-noa

No autoregistration: disables the autoregistration feature for a particular job.

-ob

OBK_HOME: specifies the pathname of the OBK_HOME directory. Use if OBK_HOME not set in the environment or when invoking from another ORACLE_HOME.

-u

Upgrade: used only for upgrading the backup catalog from a prior release.

Specifying Path Names

pfile="?/dbs/my_init@.ora"

EBU interprets the ? and @ as the values of ORACLE_HOME and ORACLE_SID for the target database.

Note: Macro keys cannot be used in specifying log or trace file destinations.

The utility does not allow the use of wildcards or environment variables when specifying path names. For example, using syntaxes like *.dbf or $ORACLE_HOME in a command script results in an error.

Registering a Target Database

Once a database is initially registered, EBU maintains and updates the configuration information automatically. Changes which cause EBU to update target database configuration information include:

• adding or dropping a tablespace

• moving datafiles to a different location

• adding or dropping control file(s)

• resizing database files (Oracle7 Server release 7.2 and higher)

• opening target database with the RESETLOGS option

• changing file attributes

Using the register Command

1. Verify that the target database is online.

2. Create a command script to register or update target database information in the backup catalog. See the following sections for examples of command scripts.

3. Invoke obackup by entering the following at either the UNIX shell prompt, or from within your media management software:

	$ obackup script_name 

where script_name is the name of the command script you created for the target database registration or reconfiguration.

Example

The following sample script uses the register command to register a target database:

register

db_name = "PROD"

oracle_home = "/opt1/oracle"

oracle_sid = "PROD" 

pfile = "?/dbs/init@.ora","?/dbs/include@.ora" \ 
"?/dbs/config@.ora"

log = "/opt1/oracle/obackup/log/obkPROD.log" 

Note: EBU always takes the values of ORACLE_HOME and ORACLE_SID from either the command script or backup catalog, not from the environment.

Additional Information: See Also: For details on the syntax of the register command, see Appendix A, "Command Script Syntax".

Target Database Specifiers

db_name

The db_name specifier identifies the name of the target database. You must include this in each register command script.

oracle_home

The oracle_home specifier is used to specify the full or relative pathname of the ORACLE_HOME of the target database. You must use the oracle_home specifier when registering a target database.

For Parallel Server: The Enterprise Backup Utility identifies an instance uniquely by its combination of host, database name, and ORACLE_SID, which allows EBU to support Oracle Parallel Server. The database name uniquely identifies the shared components, such as control files, shared parameter files, and datafiles of the target database. The ORACLE_SID uniquely identifies each instance of the database and its instance-specific parameter file.

oracle_sid

The oracle_sid specifier is used to specify the ORACLE_SID of the target database. You must use the oracle_sid specifier in each register command script.

pfile

The pfile specifier is used to list one or more parameter files used by the target database. The parameter file information is required for both registration and reconfiguration.

Autoregistration

Note that outdated configuration information is still maintained in the backup catalog. This allows you to restore your database to any point-in-time, regardless of configuration changes.

Though EBU autoregistration keeps target database information up-to-date, users can also update database configuration by invoking the register command manually.

Note: Autoregistration can be disabled within an operation by the -noa command switch. See Appendix A for more information on register command syntax.

EBU automatically uses the configuration appropriate to the point in time to which you are restoring the database. For all restores where a specific time is not specified, the utility uses the current configuration stored in the backup catalog. For point-in-time restores, EBU uses the configuration which was active at the specified time.

The Enterprise Backup Utility does not automatically update the backup catalog following a point-in-time restore. If you restore a database to a previous configuration, you should use the register command to update the database information in the backup catalog. (EBU will update the configuration information automatically at the next online backup, if you choose not update the information at this point.)

Additional Information: See Also: Chapter 7, "The Backup Catalog", for details on the information stored in the backup catalog.

Prev Next

Copyright © 1996 Oracle Corporation. All Rights Reserved.

Library

Product

Contents

Index