nbu-290216-netbackup for oracle admin guide

7/28/2019 NBU-290216-Netbackup for Oracle Admin Guide

1/230

12308316

Veritas NetBackup for Oracle

Administrators Guide

for UNIX and Linux

Release 6.5


2/230

Veritas NetBackup for OracleAdministrators Guide

Copyright 2007 Symantec Corporation. All rights reserved.

NetBackup 6.5

Symantec, the Symantec logo, and NetBackup are trademarks or registered trademarks ofSymantec Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks of their respective owners.

Portions of this software are derived from the RSA Data Security, Inc. MD5Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. Allrights reserved.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THIS DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIEDWARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ORNON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCHDISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALLNOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTIONWITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THEINFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGEWITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer

software and commercial computer software documentation as defined in FARSections 12.212 and DFARS Section 227.7202.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014www.symantec.com

Printed in the United States of America.
http://www.symantec.com/http://www.symantec.com/


3/230

Third-party legal notices

Third-party software may be recommended, distributed, embedded, or bundledwith this Symantec product. Such third-party software is licensed separately byits copyright holder. All third-party copyrights associated with this product arelisted in the accompanying release notes.AIX is a registered trademark of IBM Corporation.HP-UX is a registered trademark of Hewlett-Packard Development Company, L.P.Linux is a registered trademark of Linus Torvalds.

Solaris is a trademark of Sun Microsystems, Inc.

Licensing and registration

Veritas NetBackup is a licensed product. See the NetBackup Installation Guidefor license installation instructions.

Technical support

For technical assistance, visit http://entsupport.symantec.comand select phone

or email support. Use the Knowledge Base search feature to access resourcessuch as TechNotes, product alerts, software downloads, hardware compatibilitylists, and our customer email notification service.
http://entsupport.symantec.com/http://entsupport.symantec.com/


4/230


5/230

Contents

Chapter 1 Introduction

NetBackup for Oracle features ...........................................................................11

NetBackup for Oracle terminology ...................................................................14

XML export and XML import terms ..........................................................14

Oracle terms ..................................................................................................17

Oracle RMAN terms .....................................................................................18

NetBackup for Oracle overview .........................................................................19

RMAN .............................................................................................................20

NetBackup for Oracle XML export and XML import ..............................22

Chapter 2 NetBackup for Oracle QuickStart

Installing NetBackup for Oracle ........................................................................27

Performing the NetBackup for Oracle installation .................................28

Linking NetBackup for Oracle with RMAN .............................................. 29

Configuring a NetBackup for Oracle policy and schedule .............................30

Invoking the NetBackup Administration Console ..................................30

Creating an Oracle policy and schedules ..................................................31

Backing up the Oracle database .........................................................................33

Chapter 3 Installing the agent

Verifying the installation prerequisites ...........................................................37

Operating system and platform compatibility ........................................37

NetBackup software .....................................................................................38

Database software ........................................................................................38

Cluster software ...........................................................................................39Installing NetBackup for Oracle ........................................................................39

Remote installation of NetBackup for Oracle ..........................................39

Local installation of NetBackup for Oracle ..............................................47

Linking the Oracle Recovery Manager (RMAN) with NetBackup .................50

Verifying environment variables and shutting down Oracle ...............51

Linking the library .......................................................................................52

Troubleshooting the linking procedure ...................................................76

About the Oracle recovery catalog ....................................................................76


6/230

6

Chapter 4 Configuration

User interface terminology notes ..................................................................... 77

Configuring the Maximum jobs per client ....................................................... 78

Configuring a backup policy for a database .................................................... 78

Adding a new policy .................................................................................... 79

Adding schedules ......................................................................................... 80

Adding clients .............................................................................................. 86

Adding backup selections ........................................................................... 87

Configuring the runtime environment ............................................................ 89Oracle RMAN environment ........................................................................ 91

Environment variables set by a user in the XML export parameter

file ........................................................................................................... 92

Environment variables set by NetBackup for Oracle ............................. 92

Creating a bp.conf file ................................................................................. 93

Creating templates and shell scripts ................................................................ 94

Recovery Manager (RMAN) ........................................................................ 94

XML export archive ...................................................................................100Storing templates and shell scripts ........................................................105

Testing configuration settings ........................................................................106

Chapter 5 Using NetBackup for Oracle

Maintaining the RMAN repository .................................................................109

Querying the RMAN repository .......................................................................112

Performing a backup .........................................................................................113

Automatic backups ....................................................................................113

Manual backups .........................................................................................114

Performing a user-directed backup from the client .............................114

Browsing backups ..............................................................................................116

Using the RMAN repository to browse backups ...................................116

Using bplist to browse backups ............................................................... 116

Performing a restore .........................................................................................117

Running the NetBackup for Oracle recovery wizard on the client ....117

Using bpdbsbora ........................................................................................121

Running a NetBackup for Oracle recovery shell script on the client 121

Running RMAN on the client ...................................................................122

Redirecting a restore to a different client ..............................................122

Performing other RMAN actions ....................................................................126

Performing an XML export archive ................................................................126

Automatic backup of an Oracle policy ....................................................126

Manual backup of an Oracle policy ......................................................... 126User-directed XML exports from the client ...........................................126

Browsing XML export archives ........................................................................133


7/230

7

Using bporaimp parameters to browse XML export archives ............133

Using bplist to browse XML export archives .........................................134Restoring an XML export archive ....................................................................135

Running the XML import wizard on the client ......................................135

Using bpdbsbora ........................................................................................137

Running an XML import script on the client .........................................137

Running bporaimp on the client ..............................................................138

Redirecting a restore of an XML export archive to a different client 144

Chapter 6 NetBackup for Oracle with Snapshot ClientInstallation and licensing requirements ........................................................147

NetBackup for Oracle with Snapshot Client overview .................................148

Snapshot backup ........................................................................................148

Instant recovery .........................................................................................148

Off-host backup ..........................................................................................148

Block-level incremental backup ..............................................................148

Proxy copy ...................................................................................................149File-based operations ................................................................................149

How does NetBackup for Oracle with Snapshot Client work? ....................151

Sequence of operation: Backup ................................................................152

Sequence of operation: Restore ...............................................................152

Database objects supported by advanced backup methods .................152

Multistreaming ...........................................................................................153

RMAN multiple channels ..........................................................................153

Restoring data files to a new location .....................................................153Redirecting a restore to a different client ..............................................154

Symbolic links and raw data files ............................................................154

Quick I/O data files ....................................................................................154

RMAN incremental backups .....................................................................155

Proxy backup examples .............................................................................155

Configuring snapshot backups ........................................................................158

Configuration requirements ....................................................................158

Configuring the Oracle policy with Snapshot Client backupmethods ...............................................................................................159

Restoring data from a snapshot backup .........................................................165

Restoring individual files ..........................................................................165

Restoring volumes and file systems using snapshot rollback ............165

Configuring block-level incremental backups ...............................................167

How does BLI work? ...................................................................................168

Storage Checkpoint ....................................................................................169

Configuration requirements ....................................................................171Configuring policies for BLI backups ......................................................171

Snapshot Client effects .....................................................................................173


8/230

8

Types of backups .......................................................................................173

Schedule properties ...................................................................................174Templates and scripts ...............................................................................175

Environment variables .............................................................................175

Chapter 7 Troubleshooting

General troubleshooting procedure ................................................................179

NetBackup reports .............................................................................................181

Enabling logging ........................................................................................182

Accessing the log files ...............................................................................182

Setting the debug level .....................................................................................184

NetBackup server reports .........................................................................184

RMAN utility logs ......................................................................................184

Additional XML export and import logs .................................................184

Troubleshooting backup or restore errors ....................................................185

Checking the logs to determine the source of the error ......................185

Troubleshooting each stage of the backup or restore ..........................186Troubleshooting XML export or XML import errors ....................................188

Checking the logs to determine the source of the error ......................188

Troubleshooting each stage of the XML export or XML import .........189

Troubleshooting the browser interface and wizards ...................................191

Troubleshooting NetBackup for Oracle with Snapshot Client ...................192

Minimizing timeout failures on large database restores ............................193

Appendix A Oracle 9i and 10g Real Application ClustersVirtual names .....................................................................................................195

Archiving schemes ............................................................................................196

Backing up a database .......................................................................................199

Restoring a database .........................................................................................200

Example .......................................................................................................200

Troubleshooting .........................................................................................200

Restoring archive logs ......................................................................................201

Appendix B Script-based block-level incremental (BLI) backups withoutRMAN

Script-based BLI backup overview ..................................................................204

Terms ...........................................................................................................204

How BLI backups and restores work .......................................................205

Installation requirements ................................................................................206

File system and Storage Checkpoint space management ....................206Configuring script-based BLI backups ...........................................................207

Creating NetBackup policies for script-based BLI backup ..................207


9/230

9

Setting the maximum jobs per client global attribute .........................212

Creating directories for logging NetBackup activity ............................212Selecting a backup method .......................................................................212

Creating notify scripts ..............................................................................213

Performing backups and restores ...................................................................217

Performing backups ..................................................................................217

Restoring backups ......................................................................................219

Troubleshooting .................................................................................................220

Checking logs ..............................................................................................220

Troubleshooting backup or restore errors .............................................221Improving netbackup backup performance ..........................................224

Database recovery ......................................................................................224

Index 225


10/230

10


11/230

Chapter 1

Introduction

This chapter includes the following topics:

NetBackup for Oracle features on page 11

NetBackup for Oracle terminology on page 14

NetBackup for Oracle overview on page 19

NetBackup integrates the database backup and recovery capabilities of the

Oracle Recovery Manager (RMAN) with the backup and recovery management

capabilities of NetBackup. NetBackup for Oracle also allows you to export and

import Oracle data in XML format for long-term archiving and retrieval.

This chapter introduces NetBackup. To install, configure, and run a test backup

of your Oracle database. Follow the instructions in the next chapter, NetBackup

for Oracle QuickStart on page 27.

NetBackup for Oracle featuresTable 1-1 shows NetBackup for Oracles main features and introduces some

terms used in the NetBackup for Oracle documentation.

Table 1-1 NetBackup for Oracle features and descriptions

Feature Description

Media and device

management

All devices supported by Media Manager are available to

NetBackup for Oracle.


12/230

12 Introduction

NetBackup for Oracle features

Scheduling facilities NetBackup scheduling facilities on the master server can be used

to schedule automatic and unattended Oracle backups.

This also lets you choose the times when these operations can

occur. For example, to prevent interference with normal daytime

operations, you can schedule your database backups to occur only

at night.

Multiplexed backups

and restores

NetBackup for Oracle lets you take advantage of NetBackups

multiplexing capabilities. Multiplexing directs multiple data

streams to one backup device, thereby reducing the time necessary

to complete the operation.

Transparent Oracle

and regular file

system backup and

restore operations

All backups and restores run simultaneously and transparently

without any action from the NetBackup administrator.

The database administrator can run database backup and restore

operations through NetBackup. Alternatively, you can use OraclesRecovery Manager (RMAN) as if NetBackup were not present.

Alternatively, if you are using NetBackup for Oracle on an Oracle

database, you can use RMAN as if NetBackup were not present.

An administrator or any other authorized user can use NetBackup

to run database backups and restores.

Sharing the same

storage units used

for other file

backups

It is possible to share the same devices and media used for other

backups or to give Oracle exclusive use of certain devices and

media. NetBackup for Oracle can use Media Manager, disk, and

PureDisk storage units.

Centralized and

networked backup

operations

From the NetBackup master server, you can schedule database

backups or start them manually for any client. The Oracle

databases can also reside on hosts that are different from the

devices on which NetBackup stores the backups.

Graphical user

interfaces

NetBackup provides the following graphical user interfaces for

client users and administrators:

Backup, Archive, and Restore user interface

NetBackup administration console for Java

NetBackup administration console for Windows

A database administrator or NetBackup administrator can start

backup or restore operations for Oracle from the NetBackup

graphical user interface on the master server.

Table 1-1 NetBackup for Oracle features and descriptions (continued)

Feature Description


13/230

13Introduction

NetBackup for Oracle features

For more information on general NetBackup terminology, see the NetBackup

Administrators Guide, Volume I.

Templates The NetBackup for Oracle database wizards can create backup and

recovery templates. You can launch the backup wizard and the

recovery wizard from the NetBackup Backup, Archive, and Restore

interface. The wizards generate platform-independent templates

that contain configuration information that the software uses

when performing backups and restores. Because the

wizard-generated templates do not support all the features nativeto Oracle, you might want to write a customized backup or restore

script in an operating-system defined scripting language. You can

use a template as the base for a script.

Parallel backup and

restore operations

NetBackup for Oracle supports the parallel backup and restore

capabilities of the RMAN. For example, this permits the user to

run more than one tape device at a time for a single Oracle backup

or restore, thereby reducing the time necessary to complete the

operation.

Compression Compression increases backup performance over the network and

reduces the size of the backup image that NetBackup writes to the

storage unit.

NetBackup for Oracle supports compression for stream-based

backups only. NetBackup for Oracle does not support compression

for Snapshot Client backups.

NetBackup for Oracle supports compression for the following

types of backups:

Stream-based backups through both MaxDB and RMAN.

File-based backups through backint.

Snapshot Client backups through backint.

NetBackup for Oracle does not support compression for snapshot

client backups through RMAN.

Table 1-1 NetBackup for Oracle features and descriptions (continued)

Feature Description


14/230

14 Introduction

NetBackup for Oracle terminology

Table 1-2 describes NetBackup for Oracle XML export and XML import archiving

features.

NetBackup for Oracle terminologyThis section explains important terms that might be new to an Oracle database

administrator or a NetBackup administrator.

XML export and XML import terms

This section describes XML exports and imports.

Table 1-2 NetBackup for Oracle XML export and XML import archiving features

Feature Description

System- and

database-independent

archive format

NetBackup for Oracle uses the eXtensible Markup Language

(XML) standard to represent relational database table data

extracted from an Oracle database.

The eXtensible Markup Language (XML) is a universal formatfor structured documents and data. The XML 1.0 standards are

produced by the World Wide Web Consortium and include the

XML Schema standard.

Unicode UTF-8 is the character set encoding generated by

NetBackup for Oracle. UTF-8 is supported by standard XML

processors and US7ASCII is a strict subset of UTF-8.

Self-identifying archive

format

The XML Schema standard is used to describe the table data

that is included in an archive. In this way, the archive containsthe key to understanding the format of the data as well as the

data itself.

Command line

interfaces that allow

export and import at

row-level granularity

Parameter files specify the table data to include in an archive

and the table data to extract from an archive for import into an

Oracle database.

Restore destinationoption

NetBackup for Oracle can either restore XML data to anOperating System directory or import the data back into the

Oracle database.

Flexible archive image

searches

The NetBackup catalog contains information on the contents

of the archive that can be searched using flexible search

criteria, such as tablename or user.


15/230

15Introduction


XML export archives

Figure 1-1 shows the XML export archive process.

Figure 1-1 XML export archives

The archive activity includes the following actions:

Activity Process

Oracle XML archive NetBackup for Oracle extracts database table data, converts it into

XML format, and stores XML data to either of the following types

of repositories: A directory

A storage unit

XML export NetBackup for Oracle converts Oracle table data to XML format

(XML schema, or metadata, and XML instance, or data).

Archive NetBackup stores the XML data on a NetBackup storage unit.

bporaexp command NetBackup for Oracles XML export utility converts Oracle

database table data into a self-identifying XML schema documentand instance document that can be archived by NetBackup or

redirected to an OS directory.

XMLFormat

OSDirectory

NetBackupXML

export

Archive


16/230

16 Introduction


XML import restores

Figure 1-2 shows the XML import restore process.

Figure 1-2 XML import restores

The restore activity includes the following actions:

Activity Process

Oracle XML Restore NetBackup for Oracle manages the retrieval of archived database

table data, the parsing of the XML format, and the insertion of the

data back into the Oracle database.

Restore NetBackup retrieves the XML-formatted data from the storage

unit.

XML import NetBackup for Oracle parses XML-formatted Oracle table data and

inserts data into the Oracle database.

bporaimp command NetBackup for Oracles XML import utility can parse the

XML-formatted data for re-insertion into the database or can

redirect the data to an OS directory.

XMLFormat

OS

Directory

NetBackupXMLimport

restore

OS

Directory


17/230

17Introduction


Oracle termsThe following list explains some Oracle terms as they pertain to NetBackup.

Term Definition

Full backup Afull backup copies all blocks into the backup set, skipping only

data file blocks that have never been used. Note that a full backup

is not the same as a whole database backup;fullis an indicator that

the backup is not incremental.

A full backup has no effect on subsequent incremental backups,which is why it is not considered part of the incremental strategy.

In other words, a full backup does not affect which blocks are

included in subsequent incremental backups.

Incremental backup An incremental backup is a backup of only those blocks that have

changed since a previous backup. Oracle allows you to create and

restore incremental backups of data files, tablespaces, and a

database. You can include a control file in an incremental backup

set, but the control file is always included in its entirety. No blocksare skipped.

Multilevel

incremental backup

RMAN allows you to create multilevel backups. An integer

identifies each level; for example, 0, 1, 2, and so on. A level 0

incremental backup, which is the base of subsequent incremental

backups, copies all blocks containing data.

When you generate a level n incremental backup in which n is

greater than 0, you back up the following:

All blocks that have been modified since the most recent

backup at a level n or lower. This is the default type of

incremental backup. It is called a differential incremental

backup.

All blocks that have been modified since the most recent

backup at level n-1 or lower. This is called a cumulative

incremental backup.

The benefit to performing multilevel incremental backups is that

you do not back up all of the blocks all of the time. Incremental

backups at a level greater than 0 only copy blocks that were

modified, which means that the backup size can be significantly

smaller and the backup might require much less time. The size of

the backup file depends solely upon the number of blocks modified

and the incremental backup level.


18/230

18 Introduction


Oracle RMAN termsThe following list explains Oracle RMAN terms as they pertain to NetBackup.

Differential

incremental backup

In a differential level n incremental backup, you back up all blocks

that have changed since the most recent backup at level n or lower.

For example, in a differential level 2 backup, you back up all blocks

modified since the last level 2, level 1, or level 0 backup.

Incremental backups are differential by default.

Cumulative

incremental backup

In a cumulative level n incremental backup, you back up all blocks

that have changed since the most recent backup at level n-1 or

lower. For example, in a cumulative level 2 backup, you back up allblocks changed since the most recent level 1 or level 0 backup.

Cumulative incremental backups reduce the work needed for a

restore by ensuring that you only need one incremental backup

from any particular level at restore time. Cumulative backups

require more space and time than differential incremental

backups, however, because they duplicate the work done by

previous backups at the same level.

Term Definition

Term Definition

RMAN RMAN backs up, restores, and recovers database files. RMAN starts

Oracle server processes on the target database. These Oracle server

processes perform the backup and restore. RMAN performs backup

and recovery procedures, and it greatly simplifies the tasks

administrators perform during these processes. However, RMAN

cannot directly manage the storage devices and media used in its

backups, so it must be integrated with an application that has these

capabilities. NetBackup for Oracle provides device and media

management capabilities by integrating RMAN with NetBackup and

its media management software. Other advantages are access toNetBackups automatic scheduling facilities and the graphical

interfaces.

RMAN repository An RMAN recovery catalog or the database control file is a

repository for information that is used and maintained by RMAN.

RMAN uses this information to determine how to run requested

backup and restore actions.

For a description of the recovery catalog, see your Oracle

documentation.


19/230

19Introduction

NetBackup for Oracle overview

NetBackup for Oracle overviewFigure 1-3 shows the major components in a NetBackup for Oracle

configuration. The server that hosts the Oracle database must be a NetBackup

client. It must also have NetBackup for Oracle installed.

rman command The rman command starts an RMAN backup or restore. Your Oracle

documentation describes this command.

RMAN script The RMAN script specifies the commands for RMAN to perform (for

example, backups, and restores). For information on RMAN

commands and script files, see your Oracle documentation.

There are example RMAN shell scripts in the following directory:

/usr/openv/netbackup/ext/db_ext/oracle/samples/

rman

These example scripts run RMAN commands and are fully

commented to explain the features used. You can review these

examples and use them as a starting point for developing backup,

restore, and recovery scripts.

Term Definition


20/230

20 Introduction


Figure 1-3 NetBackup for Oracle on a sample network

RMANThe following sections explain how RMAN works and how RMAN works with

NetBackup.

How does RMAN work?The RMAN performs a wide variety of automated backup and recovery

functions. During a backup or a restore, RMAN provides the interface to the

databases, and it extracts and inserts data.

To start a database backup or restore, the database administrator runs a

command called rman. This command can be run from the command line, a

script, or an application such as NetBackup. The RMAN script is used as a

parameter to the rman command and specifies the operations to be performed(for example, backup or restore). The RMAN script also defines other

NetBackup master serveror remote media server

Oracle database software supplies:

Oracle Recovery Manager (RMAN) Oracle Call Interface (OCI)

System hosting the Oracle database

Network (TCP/IP)

NetBackup for Oracle supplies:

Sample configuration program Sample script files Veritas I/O Library (libobk) bporaimp and bporaexp

NetBackup software:

NetBackup master server NetBackup media server

(if system is a media server)

Additional NetBackup software:

NetBackup client (required)

Storage unit

Oracle database toback up or restore

System containing Oracle databaseRecovery Catalog


21/230

21Introduction


components of the operation, such as the database objects to be backed up or

restored.During a backup or restore, RMAN controls the data streams going into or out of

a database. RMAN can access storage devices when it is integrated with a media

management system, such as that provided by NetBackup.

How does NetBackup for Oracle work?

The following are prerequisites for performing backups to a storage unit:

Linking with NetBackup

Generating unique file names

NetBackup for Oracle includes a library of functions that enable RMAN to use

NetBackup. To link with this library, see Linking the library on page 52.

When using the RMAN backup command, each resulting backup set contains at

least one backup piece (data file, data file copy, control file, or archive log) from

the target database. You must give each backup piece a unique name using the

format operand. Several substitution variables are available to aid ingenerating unique names. You can specify the format operand in the backup

command or in the allocate channel command. NetBackup considers the

backup piece name as the file being backed up, so this name must be unique in

the catalog.

If an Oracle 8.0.x RMAN backup uses a file name that already exists in the

catalog, the original backup that has that name is deleted. In Oracle 8i or later,

the RMAN backup fails with a file already exists in catalog error. For

information on generating unique file names, see your Oracle documentation.

Either NetBackup users or automatic schedules start database backups by

specifying a template or shell script in the file list of the Oracle policy. The

template or shell script specifies the backup commands that RMAN will perform

on the client.

For a backup:

1 The rman command starts the requested operation on the databases.

2 When the process requires media to store backup data, RMAN starts a

user-directed backup by issuing a backup request.

3 The NetBackup media server connects to NetBackup for Oracle on the client

and transfers the database data to secondary storage.

A restore works in essentially the same manner except that RMAN issues a

restore request. This causes NetBackup to retrieve the data from secondary

storage and send it to NetBackup for Oracle on the client.RMAN supports parallel operations, so a single rman command can start more

than one backup or restore on the NetBackup system.


22/230

22 Introduction


The status for an RMAN operation is stored in the RMAN catalog or in the

database control file. This is the same status that is indicated by the output ofthe RMAN command used to run the backup or restore. This is the only status

that a database administrator must check to verify that a backup or restore has

been successful.

NetBackup also logs status, but only for its own part of the operation. The

database administrator cannot use the NetBackup status to determine whether

rman was successful. Errors can occur in rman that do not affect NetBackup and

are not recorded in its logs.

Incremental backups of Oracle databases

The RMAN provides true incremental backups. An incremental backup backs up

data files and includes only the blocks that have been changed since the last

incremental backup. For more information on the backup and recovery process,

see your Oracle documentation.

About the Oracle recovery catalogThe recovery catalog is a repository of information. RMAN uses the information

in the recovery catalog to determine how to perform requested backup and

restore actions. The recovery catalog contains information about the following

software components:

Data file and archive log backup sets and backup pieces.

Data file copies.

Archived redo logs and their copies.

Tablespaces and data files on the target database.

Stored scripts. These are named, user-created sequences of RMAN and SQL

commands.

Oracle recommends you use RMAN with a recovery catalog, especially if you

have 20 or more data files. However, you are not required to maintain a recovery

catalog with RMAN.For information on the benefits and disadvantages of using a recovery catalog,

see your Oracle documentation.

NetBackup for Oracle XML export and XML importWhile Oracle RMAN performs backup, restore, and recovery of physical Oracle

database objects (data files, tablespaces, control files, and archived redo logs),

the NetBackup for Oracle XML export and XML import utilities provide backup

and restore of logical database objects (tables, users, and rows).


23/230

23Introduction


The XML format is used to provide a self-identifying and system-independent

format ideal for database archiving.

Sequence of operation: XML export archive

Figure 1-4 shows data flow.

Figure 1-4 XML export archive data flow

NetBackup for Oracle users or automatic schedules start database XML export

archives by performing a manual backup of an Oracle policy, by invoking the

script or template at the command line on the client, or by invoking a template

through the Backup, Archive, and Restore interface.

Script or template

(bporaexp)

(Parameter file)

Scheduler

NetBackup

Command line

Backup, archive, and restoreinterface

Table list WHERE clause

Query processor

Table(s) metadata, Table(s) data

XML generator XML schema(s), XMLinstance(s)

NetBackup

XML schema(s), XMLinstance(s)

Option tocreate XMLfiles on disk

Oracle DBMS

OCI

24 I d i


24/230

24 Introduction


For an XML export archive:

1 The NetBackup for Oracle script or template calls the bporaexp utility witha specified parameter file.

2 The query processor uses the parameters in the specified file to build an SQL

query for each table.

3 Oracles OCI API executes the queries on the Oracle instance to be archived.

4 The query processor passes the output (including metadata and data for a

single table or multiple tables) to the XML Generator.

5 For each table passed, the XML generator builds one or more sets of XML

schema and XML instance documents.

6 XML data streams are backed up by NetBackup.

7 Alternately, bporaexp allows the files to be saved to an operating system

directory.

Sequence of operation: XML import restoreFigure 1-5 shows data flow.

25Introduction


25/230

25Introduction


Figure 1-5 XML import restore data flow

NetBackup for Oracle users start database XML import restores by invoking a

NetBackup for Oracle script or template at the client command line or by

invoking an XML import restore template through the Backup, Archive, and

Restore interface.

For an XML import restore:

1 The NetBackup for Oracle script or template calls the bporaimp utility with

a specified parameter file.

2 The input parameters that identify the XML archive to restore are passed to

NetBackup.

Command line orBackup, Archive, and Restore interface

Script or template(bporaimp)

(Parameter file)

Archive name

Keyword

Table name

NetBackup


XML Parser

Option torestore XMLfiles on disk


Table(s) metadata,Table(s) data

XML data loaderOCI

Oracle DBMS

26 Introduction


26/230

26 Introduction


3 NetBackup locates and reads the set of XML schema and instance

documents from the NetBackup storage unit.4 The XML data stream is passed to an XML parser, which passes the data to

the XML data loader.

5 The XML data loader uses Oracles OCI API to insert the data into the

database.

Optionally, bporaimp allows the XML data stream to bypass the XML parser

and be sent to an operating system directory. In addition, users can restore the

table metadata only into an operating system directory. bporaimp also allowsimport from an operating system directory into Oracle.

2


27/230

Chapter 2

NetBackup for Oracle

QuickStart


Installing NetBackup for Oracle on page 27

Configuring a NetBackup for Oracle policy and schedule on page 30

Backing up the Oracle database on page 33

This chapter shows how to install and configure a simple NetBackup for Oracle

deployment and to run an Oracle RMAN database backup. The procedures in

this chapter assume a regular Oracle RMAN backup with NetBackup for Oracle.

For Snapshot Client options, see NetBackup for Oracle with Snapshot Client

on page 147.

For more detailed instructions, see the following chapters:

Installing the agent on page 37

Configuration on page 77

Using NetBackup for Oracle on page 109

Installing NetBackup for OracleTo install NetBackup for Oracle, ensure the following:

The NetBackup version on the local machine must be the same as the

NetBackup for Oracle version. For example, 6.5. The local machine can be a

client or a NetBackup server that also happens to be a client.

The local machine must have adequate disk space.

Reserve a minimum of two megabytes of disk space in the

/usr/openv/netbackup directory. More disk space might be necessary at

run time.

28 NetBackup for Oracle QuickStart


28/230

p

Installing NetBackup for Oracle

NetBackup version 6.5 client or server software is installed and operational.

This also means that the /usr/openv/netbackup directory alreadyexists.

For a more comprehensive list of installation prerequisites, see Verifying the

installation prerequisites on page 37.

Performing the NetBackup for Oracle installationDuring a local installation, the NetBackup for Oracle files are extracted and

installed. The instructions that follow are for an initial, local installation on theNetBackup client upon which the Oracle database resides.

To install NetBackup for Oracle

1 Log in as the root user on the machine.

If you are already logged in, but are not the root user, run the following

command.

su - root

If the local machine is a client, go to step 3.

If the local machine is a server, go to step 2.

2 Make sure a valid license key for NetBackup for Oracle has been registered.

To view or add license keys, perform one of the following:

Run the command

/usr/openv/netbackup/bin/admincmd/get_license_key.

Open the NetBackup Administration Console and choose Help >License Keys.

3 Insert the CD-ROM into the drive.

4 Change to the working directory to the CD-ROM directory.

cd /CD_mount_point

5 Load and install the software by running the install script.

./install

a Select the NetBackup Database Agent Software option.

The following prompt appears:

Do you want to do a local installation? (y/n) [n]

b Answery.

You are presented with a menu of all database agents available on the

CD-ROM.

c Select the NetBackup for Oracle option.

29NetBackup for Oracle QuickStart


29/230


d Enter q to quit selecting options.

A prompt appears asking if the list is correct.e Answery.

The following actions occur:

The version file, compressed tar file, and install_dbext script

are loaded to directory /usr/openv/netbackup/dbext.

The install script automatically runs the install_dbext

script.

If install_dbext completes successfully, it writes a version file indirectory /usr/openv/share that contains the version of

NetBackup for Oracle that was installed.

Linking NetBackup for Oracle with RMANBefore writing to sequential devices such as tape, you must link the Oracle

server software with the media management API library installed by NetBackup

for Oracle. Oracle uses this library when it needs to write to, or read from,devices.

To link Oracle with NetBackup for Oracle

1 Become the Oracle user.

su - oracle

2 (Conditional) Shut down all of the Oracle instances (SIDs).

Perform this step if you are using an Oracle8 release. Oracle releases 9 andlater do not need to perform this step.

The user must connect as the SYSDBA, either using OS Authentication or

Oracle Authentication (set up in the Oracle password file). The following

example is for Oracle9i.

a Set the $ORACLE_SID environment variable to the first SID.

b Connect as SYSDBA in one of the following ways:

Using OS Authentication:sqlplus /nolog

connect / as sysdba

shutdown immediate

exit

Using Oracle Authentication (via password file):

sqlplus /nolog

connect userid/passwordas sysdba

shutdown immediate

exit


C fi i N B k f O l li d h d l


30/230

Configuring a NetBackup for Oracle policy and schedule

c Change the $ORACLE_SID environment variable to any other SID that

uses this Oracle installation, and repeat the preceding commands.

3 Set up automatic linking.

a Change directory to /usr/openv/netbackup/bin/

b Run the oracle_link script:

./oracle_link

This script determines the Oracle version level and then links Oracle to

NetBackup. All output from this script is written to

/tmp/make_trace.pid. To change the trace file location, change theMAKE_TRACEvariable in the oracle_link script.

4 Restart the Oracle instances.

Configuring a NetBackup for Oracle policy andschedule

To run an Oracle backup, you must first configure an Oracle policy in

NetBackup. This section shows you how to invoke the NetBackup administration

console, how to create an Oracle policy, and how to create schedules for the

Oracle policy.

For more information on the steps in this section, see Configuration on

page 77.

Invoking the NetBackup Administration ConsoleYou configure an Oracle policy from the NetBackup Administration Console on

the master server. Depending on your master servers platform, the console is

available in one or two forms. NetBackup supports a Java interface for both

UNIX and Windows master servers. In addition, NetBackup supports a Windows

interface for Windows master servers.

Use one of the following procedures to invoke the NetBackup Administration

Console:

To invoke the NetBackup Administration Console on a UNIX master server

1 Log on to the NetBackup master server as root.

2 Start the NetBackup administration console by typing the following

command:

/usr/openv/java/jnbSA &




31/230


To invoke the NetBackup Administration Console on a Windows master

server

This procedure shows how to invoke the Windows interface on a Windows

master server. For information on invoking the Java interface on a Windows

master server, see the NetBackup Administration Guide for Windows, Volume I.

1 Log on to the NetBackup master server as the administrator.

2 Start the NetBackup administration console by clicking Start > All Programs

> Veritas NetBackup > NetBackup Administration Console.

Creating an Oracle policy and schedulesThe following procedures use the NetBackup Policy wizard to help you create a

NetBackup for Oracle policy. In most cases, you can accept the default entries.

To create a NetBackup policy

1 If necessary, use File > Change Server to select the master server upon

which you want to create the policy.2 In the left pane, click Policies.

3 Right-click in the All Policies pane, and click New Policy.

The Add a New Policy dialog displays.

a In the Policy name box, type a unique name for the new policy.

b Select Use Backup Policy Configuration Wizard to use the backup policy

configuration wizard. Click OK.c Click Next.

4 Complete the backup policy configuration wizard by supplying the following

information:

a On the Policy Name and Type screen, select Oracle as the policy type.

Click Next.

b On the Client List screen, click Add. Add the name of the NetBackup for

Oracle client. Select the hardware and operating system. Click OK. Click

Next.

c On the Backup Type screen, click Next to accept the defaults.

d On the Rotation screen, click Next to accept the defaults.

e On the Start Window screen, click Next to accept the defaults.

f Click Finish to create the policy.

5 Proceed to To create schedules on page 32 for information on creating

schedules for this policy.




32/230


To create schedules

Schedules determine when NetBackup for Oracle initiates a backup. An Oraclebackup requires at least two different schedules:

An Application Backup schedule. When you create an Oracle policy,

NetBackup for Oracle automatically creates a Default-Application-Backup

schedule.

An Automatic Full Backup schedule. You create this schedule. It enables

scheduled backup operations on the client.

1 Double-click the policy name. The Policy dialog appears.

2 Click the Schedules tab.

3 Double-click the schedule named Default-Application-Backup.

By default, the NetBackup sets the following:

The retention period is 1 month.

Multiplexing is 1.

The schedule is seven days per week and 24 hours per day. This ensuresthat your backups can always commence.

Make any changes to the Default-Application-Backup schedule if needed.

4 Click OK.

5 Click New to create another schedule.

6 Specify a unique name for the schedule.

7 Select Automatic Full Backup as the Type of Backup.8 Click the Start Window tab.

9 Follow the instructions on the Start screen to specify a time for this

schedule.

You must specify a time and a duration for the Automatic Full Backup

schedule. Depending on the size of the database and your site conditions, an

Automatic Full Backup can take a long time to complete. Choose a time

when your system is not likely to be in use. For example, you might specifySunday evenings from 1800-2300. By default, the retention period is

infinity, and the frequency is once per week.

10 Click OK.

11 Click Close.


Backing up the Oracle database


33/230


Backing up the Oracle databaseNetBackup for Oracle includes a backup wizard that solicits information about

desired RMAN backup operations. The wizard uses this information to create a

template that can back up the Oracle database. You can run this template

immediately, or you can save it to run later.

To back up an Oracle database, perform the following procedures:

To log into the client and invoke the backup wizard on page 33

To back up the Oracle database using the backup wizard on page 35

To log into the client and invoke the backup wizard

1 Use operating system methods to log into the client upon which NetBackup

for Oracle is installed.

2 Make sure that the Oracle database is in themount or open state.

If this is not the case, this procedure fails.

3 Start the NetBackup Backup, Archive, and Restore interface on theNetBackup client. Run the following command:

/usr/openv/java/jbpSA &

4 Provide the information requested by the login dialog box.

For the host name, type the name of the client upon which the Oracle

database and NetBackup for Oracle reside. Type your user name and

password in the other fields. You can log in as a regular user. You do not

have to log in as root or as the Oracle administrator.After NetBackup accepts your login information, the NetBackup

administration console appears.

5 Click the Backup Files tab.




34/230

g p

6 Expand the Oracle

node in the left

pane by clicking the

node icon to the left

ofOracle.

After you expand

the node, you see

the list of Oracle

instances that you

can back up.7 Decide whether you

want to back up an

entire Oracle

instance or an

individual Oracle

instance data file.

To back up an entire Oracle instance, go to step 8.

To back up an individual Oracle instance data file, go to step 9.

8 To back up an entire instance, perform the following steps:

a Click the check box to the left of the instance name.

b Proceed to step 10.

9 To back up individual instance data files, perform the following steps:

a Expand the instance by clicking the node icon to the left of the name ofthe Oracle instance data file you want to back up.

b (Conditional) If you are using Oracle authentication, the Database

Connect Information dialog box appears. Type the Oracle administrator

authentication information into the following fields:

User name: (must have SYSDBA privilege)

Password:

Net service name (TNS alias):

c Select the data files or tablespaces in the instance that you want to back

up by clicking in the checkbox to the left of each instance data files

name.

d Proceed to step 10.

10 Click Backup.

The NetBackup for Oracle backup wizard welcome screen displays.

Click here to expand the Oracle node




35/230

To back up the Oracle database using the backup wizard

Note: This procedure describes how to perform an ONLINE backup. It assumes

that the Oracle databases archiving mode is set to ARCHIVELOG.

1 Invoke the backup wizard.

The procedure in To log into the client and invoke the backup wizard on

page 33 describes how to invoke this wizard. If you just completed that

procedure, the backup wizard is displayed on your screen at this time.

2 Click Next.

The Target Database Logon Credentials dialog box displays. Fill in the fields

in this dialog box, as follows:

If you use OS authentication for Oracle, select OS Authentication.

If you use Oracle authentication via a password file, select

Oracle_Authentication and supply the following:

A User name

A Password with Oracle SYSDBA privileges

(Optional) A Net service name (TNS alias)

(Optional) Select Use Oracle RMAN recovery catalog. This is not

required. If this is your first NetBackup for Oracle backup, you can

leave this option unselected.

If you did not choose to use the recovery catalog, skip to step 4.

3 Click Next.If you chose to use the recovery catalog, you see the Recovery Catalog Logon

Credentials screen. Supply the appropriate User name and Password for the

recovery catalog.

4 Click Next. The Archived Redo Logs screen displays.

5 Click Next to accept all defaults. The Configuration Options screen displays.

6 Click Next to accept all defaults. The Backup Options screen displays.

7 Click Next to accept all defaults. The Database State screen displays.

8 Click Next to accept all defaults. The NetBackup Configuration Variables

screen displays.

In the Backup policy name field, enter the name of the Oracle policy you

created on the NetBackup master server.

9 Click Next. The Backup Limits screen displays.

10 Click Next to accept all defaults. The Template Summary screen displays.

11 Click Perform backup immediately after wizard finishes.




36/230

12 To start the backup, click Finish.

An ONLINE backup of your Oracle database begins. A NetBackup message

window displays that the backup was successfully initiated. To check the

progress of the backup in the Backup, Archive, and Restore status window,

choose Yes in the message window.

Chapter 3


37/230

Chapter 3

Installing the agent


Verifying the installation prerequisites on page 37

Installing NetBackup for Oracle on page 39

Linking the Oracle Recovery Manager (RMAN) with NetBackup on page 50

About the Oracle recovery catalog on page 76

Perform the procedures in this chapter before you configure NetBackup for

Oracle.

Verifying the installation prerequisitesPerform the procedures in this section before you install the database agent.

These requirements apply for remote and local installations.

Operating system and platform compatibilityVerify that NetBackup for Oracle is supported on your operating system or

platform.

To verify compatibility

1 Go to the technical support Web page: http://entsupport.symantec.com .

2 In the Product Lookup field, type in NetBackup Enterprise Server and click

on the > button.

3 From the list on the right, click on Compatibility List.

4 In the list of documents, click Veritas NetBackup Enterprise Server (tm)x.x/

NetBackup Serverx.xDatabase Agent Compatibility(Updateddate).

For x.x, look for the current release. For date, look for the most recent date.

38 Installing the agent

Verifying the installation prerequisites
http://entsupport.symantec.com/http://entsupport.symantec.com/


38/230

For information on supported cluster environments for NetBackup for

Oracle, see NetBackup (tm)x.xCluster Compatibility (updateddate).

5 Click the link for the PDF document, which is a downloadable file that

enables you to view the supported database spreadsheet for this release.

6 Read the document and verify that the software in your environment is

compatible with the NetBackup and the database agent.

NetBackup softwareVerify that the following requirements are met for the NetBackup server and

client software:

The NetBackup server software is installed and operational on the

NetBackup server.

The NetBackup server platform can be any that NetBackup supports. For

installation information, see the NetBackup Installation Guide.

The version of the NetBackup client and the version of the database agent

you want to install must be the same (for example, 6.5).

There must be adequate disk space on each machine upon which you want to

install the database agent. Less than two megabytes of additional disk space

is required in the /usr/openv/netbackup directory. However, more disk

space might be needed at run time.

Make sure that you configure any backup media that the storage unit uses.

The amount of backup media that is required depends on the devices that

are used, the sizes of the databases that you want to back up, the amount ofdata that you want to archive, the size of your backups, and the frequency of

backups or archives.

For information on using Media Manager, see the NetBackup

Administrators Guide, Volume I.

Database softwareVerify the following regarding the database software on the NetBackup client:

Oracle vendor software must be installed and operational.

One or more Oracle instances must exist.

For all Oracle 8 releases, make sure you have shut down the Oracle database.

For more information about when you need to perform this step, see your

Oracle documentation.

39Installing the agent



39/230

Cluster software

Verify the following requirements if you are installing the database agentsoftware on a NetBackup server configured in a NetBackup cluster:

The Oracle vendor software is installed and operational on each node to

which NetBackup can failover.

The NetBackup server software is installed and configured to work in a

NetBackup cluster. Follow the instructions in the NetBackup Installation

Guide, including running the cluster_config script after the NetBackup

server software has been installed.You only need to run the cluster_config script after you install the

NetBackup server software. You do not need to run cluster_config after

installing the database agent on a NetBackup server that is part of a

NetBackup cluster.

The following additional information also pertains to cluster environments:

Make sure you install the NetBackup client software and the database agent

software on each node to which NetBackup can failover. Run commands such as bpplclients and update_dbclients from the

active NetBackup master or media server. To perform a remote installation

where you push the database agent software to clients located in a cluster,

specify the individual node names in the client list, not the virtual names.

Installing NetBackup for OracleYou can install the database agent software in one of the following ways:

A remote installation. The user loads the software onto a master server or a

media server and then pushes the database software out to the clients. You

can perform an initial or upgrade remote installation in this manner.

Remote installation of NetBackup for Oracle on page 39 describes this

procedure.

A local installation. The user loads and installs the software onto the localmachine only.

Local installation of NetBackup for Oracle on page 47 describes this

procedure.

Remote installation of NetBackup for OracleDuring a remote installation, you load the database agent files onto either a

UNIX master server or media server. Then you push the software to the clientsto install it.




40/230

Loading the database agent files onto the server

Use the following procedure to load the files onto the server.

To load the database agent files on a UNIX server

1 Review Verifying the installation prerequisites on page 37.

If you want to install the database agent on a clustered NetBackup server,

read Cluster software on page 39.

2 (Conditional) Perform this step only if you want to install on a server that is

part of a NetBackup cluster.a Freeze the active NetBackup node.

When you install NetBackup for Oracle, install the software on all the

inactive nodes first, then install on the active node. For information on

how to freeze the active node in your specific cluster environment, see

the NetBackup High Availability Administrators Guide.

b Decide which of the inactive nodes to install the software on first.

In the next step, you log in to the first machine and start theinstallation process. Because you need to perform the installation on all

inactive nodes first, make sure that the first machine you select is an

inactive node.

3 Log in as the root user on the master server or media server.


command:

su - root

4 Verify that a registered and valid license key for NetBackup for Oracle

resides on the master server.

You can obtain master server license information from either the master

server or the media server. To view or add license keys, perform one of the

following actions:

From the master server or media server, run the following command:

/usr/openv/netbackup/bin/admincmd/get_license_key

When the system prompts you, type the host name of the NetBackupmaster server.

Open the NetBackup administration console and choose Help > License

Keys.

If the NetBackup master server is part of a NetBackup cluster, the license

key must be registered on each node.

5 Mount the CD-ROM.

For more information on how to mount a CD-ROM, see the NetBackupInstallation Guide.




41/230

6 Change the working directory to the CD-ROM directory.

For example:

cd /CD_mount_point

7 Run the install script to load and install the software.

For example:

./install

a Select the NetBackup Database Agent Software option.

The following prompt appears:

Do you want to do a local installation? (y/n) [n]b Type n.

c Select the NetBackup for Oracle option.

d Type q to quit selecting options.

A prompt appears that asks if the list is correct.

e Typey.

The install script identifies the types of client software that is loaded

during the installation of the NetBackup server. By default, any

matching NetBackup for Oracle software is automatically loaded. If

there are more platforms available, the script displays a menu that

gives you the opportunity to add more client types to the default list.

After the list is complete, the installation script copies the database

agent version files and the install_dbext script to directory

/usr/openv/netbackup/dbext. (These files are tar(1) files

compressed with gzip(1).)8 (Conditional) Select another node upon which to install the software.

Perform this step under the following circumstances:

If you want to install the NetBackup for Oracle software on a server

that is part of a NetBackup cluster.

and

If you have any nodes that still need the software installed.

If there are any inactive nodes that do not yet have the software installed,select one of these inactive nodes. Then repeat step 3 through step 8 for

that node.

If you installed the software on all the inactive nodes, select the active node

and repeat step 3 through step 8 for that node.

If you installed on all the nodes, proceed to step 9.

9 (Conditional) Unfreeze the active node.

Perform this step if you want to install the NetBackup for Oracle softwareon a server that is part of a NetBackup cluster. The last step in the




42/230

installation process is to unfreeze the active node. Unfreeze the active node

only after all the software is installed on all nodes.

For information on how to unfreeze the active node in your specific cluster

environment, see the NetBackup High Availability Administrators Guide.

10 Decide how you want to distribute the NetBackup for Oracle software to the

clients.

Use one of the following methods whether you want to upgrade clients in an

existing environment or you want to perform a new installation:

Distribute to all clients currently specified in the database policy. This

method distributes the NetBackup for Oracle software to all clients thatare currently included in the database policy. You can use this method

only if you want to push from a master server.

For information on this method, see Pushing the software to all

clients on page 42.

Distribute to selected clients. This method distributes the NetBackup

for Oracle software to selected clients only. If you want to perform a

new installation and you plan to add clients to a database policy afteryou install the software. You can install the software on such clients

now and configure the policy later. This method also allows you to skip

any clients that you do not want to upgrade to 6.5 at this time. You can

use this method whether you want to push from a master server or

from a media server.

For information on this method, seePushing the software to new or

selected clients on page 45.

Note: Make sure that the NetBackup for Oracle version is the same version as the

NetBackup client software.

Pushing the software to all clients

Use the following procedure to install or upgrade the database agent software

on all clients currently configured in a NetBackup database policy. You can usethis procedure only from a master server.

To push the software to all clients

Note: If you want to push the database agent software from a server that is part

of a NetBackup cluster, type all commands in this procedure from the active

NetBackup node.




43/230


of a NetBackup cluster to an inactive node in the cluster, you need to force theinstallation to the inactive node.

1 Run the update_dbclients command to launch the installation script.

Type the following command:

/usr/openv/netbackup/bin/update_dbclientsOracle ALL ALL

2 Examine the client list that the update_dbclients command returns.

a Locate the client list.The update_dbclients command compiles a list of clients that it

detects are included in the policy. It presents this list to you. If 9 or

fewer clients are in the client list, update_dbclients displays all the

client names. If 10 or more clients are on the client list,

update_dbclients writes the first 9 to standard output. It writes the

entire list to $TMPDIR/NB_DBCLIENT_LIST.identifier.

identifieris a mix of date, time, and process identifier information.

The TMPDIR environment variable is defined as /tmp.

b Check the client list.

The host names of the clients must be the clients individual node

names. They cannot be virtual names. The hostname(1) and the

domainname(1) commands return the correct value for the individual

node names. The format can be either hostnameor

hostname.domainname.

If the client list contains virtual names, you cannot complete thisprocedure. Do one of the following:

To exit this procedure if there are two or more clients, press the

Enter key. Then type n to stop the upgrade and exit from this

installation dialog box.

To install the software in this situation, use Pushing the software

to new or selected clients on page 45.

To exit this procedure if there is only one client, type n.To install the software in this situation, use Pushing the software

to new or selected clients on page 45.

If the client list contains only individual node names, proceed to the

following step.

c Check the skipped client list, if any.




44/230

Ifupdate_dbclients detects that it cannot update a particular

client, it does not include the name of that client in the client list. Such

clients are skipped for one or more of the following reasons:

The client is a PC client. You cannot install or upgrade NetBackup

for Oracle on a PC client from a UNIX server.

The database agent does not support the client's platform type.

The database agent software for that client type was not loaded

onto the server. (In the procedure To load the database agent files

on a UNIX server on page 40.)

The client does not belong to the database policy type.

The skipped client list is in $TMPDIR/skipped_clients.PID,

where PIDis the process identifier. The TMPDIR environment

variable is defined as /tmp. If no file is present, no clients were

skipped.

3 (Conditional) Specify the number of simultaneous client updates.

If you want to update more than one client, the installation software

displays the number of updates that are required to distribute the softwareto the clients. If the software detects the need to update more than one

client, it displays the following prompt:

Enter the number of simultaneous updates you wish to take place.

[1 -max] (default: dflt)

If you want the installation software to perform dflt simultaneous

updates, press Enter.

You can specify a different number of simultaneous updates. Indicate a

number that is greater or equal to 1 and less than or equal to themax, then

press Enter.For example, if three clients are to be updated, themaxand dflt values are

3. If 50 clients are to be updated, themaxvalue is 30, and the dflt value is

15.

update_dbclients starts the number of updates that you specify. This

number may be less than the total number of client updates to be

performed. If so, new updates start as the previous updates finish until all

of the updates have been completed.

4 Indicate whether or not you want to upgrade the clients at this time.

max The maximum number of simultaneous updates that is allowed. The value

that is displayed ranges from 1 to 30.

dflt The number the program uses if you press Enter without specifying a

number. The value that is displayed ranges from 1 to 15.




45/230

Based on your answer, the time it takes to update the clients appears,

followed by this question:

Do you want to upgrade the clients now? (y/n) [y]

Typey or n for the prompt.

If you type n, update_dbclients quits and leaves the list of clients it

would have updated in a file. You can use this file later as the argument to

the -ClientList parameter. By default, the installation software writes

the client list to $TMPDIR/NB_DBCLIENT_LIST.identifier, where

identifieris a mix of date, time, and process identifier information. The

TMPDIR environment variable is defined as /tmp.

If you typey, you continue the installation process. The following actions

occur:

The update_dbclients command distributes the software to the

client. If it is successful, update_dbclients invokes the

install_dbext script on the client.

The install_dbext script runs on each client. If it is successful, it

writes a version file in directory /usr/openv/share that contains the

version of NetBackup for Oracle that was installed.

The update_dbclients command displays a note on whether the

update was successful for each client. When the update_dbclients

command completes, it displays a file name that contains a complete

log of what happened for each client. If the update failed for any client,

examine the log file to determine the problem.

Pushing the software to new or selected clientsUse the following procedure if you want to install or upgrade the NetBackup for

Oracle software on selected clients. You can use this procedure from either a

master server or from a media server.

To push the software to new or selected clients

Note: If you want to push the NetBackup for Oracle software from a server that

is part of a NetBackup cluster, type all commands in this procedure from the

active NetBackup node.


of a NetBackup cluster to an inactive node in the cluster, you need to force the

installation to the inactive node.




46/230

1 On the master server, type the following command to ensure that the bpdbm

daemon is running:

/usr/openv/netbackup/bin/bpps

If the output shows that the bpdbmdaemon is not running, type the

following command to start the daemon:

/usr/openv/netbackup/bin/initbpdbm

2 Type the following command to change to the NetBackup bin directory:

cd /usr/openv/netbackup/bin

3 Use the bpplclients(1M) command to create a file that contains a list of

clients currently configured in the NetBackup database.

The options for this command depend on whether you want to install from a

master server or from a media server, as follows:

If you want to perform the install from the master server, type the

following command:

./admincmd/bpplclients -allunique -noheader > file

If you want to perform the install from a media server, type the

following command:./admincmd/bpplclients -allunique -noheader -M ms_name > file

bpplclients writes output to filein the following format:

hardwareop_systemclient

For example, filemight contain a line like the following:

Solaris Solaris8 curry

4 (Optional) Edit file.

Perform this step to change the contents offile. Edit fileto contain only

those clients you want to update with NetBackup for Oracle software.

ms_name Name of the NetBackup master server in this environment.

file Name of the file to contain the list of unique clients. If no clients have

been configured in the NetBackup database, fileis empty. Create

fileusing the same format as that generated by bpplclients.

hardware The hardware name. For examples, type the ls(1) command in

directory/usr/openv/netbackup/client.

op_system The operating system name. For examples, type the ls(1) command

in directory /usr/openv/netbackup/client/hardware.

client The name of the client.




47/230

The host names of the clients must be the clients individual node names.

They cannot be virtual names. The hostname(1) and the domainname(1)

commands return the correct value for the individual node names. Theformat can be either hostnameor hostname.domainname.

5 Run the update_dbclients command to install the software.

Specify the fileyou created in step 3 as the argument to

update_dbclients. The command installs the software on the clients

that are listed in file.

For example:

./update_dbclients Oracle -ClientListfile

6 Answer questions as prompted by the update_dbclients command.

The update_dbclients command initiates a dialog with you. It asks you

to confirm actions during the update process and presents options to you if

there are choices to be made.

For more information, see step 2 of the procedure To push the software to

all clients on page 42.

Note: You do notneed to run the cluster_config script after you install the

database agent on a server that is part of a NetBackup cluster.

Local installation of NetBackup for OracleDuring a local installation, the database agent files are extracted and installed.

The local machine can be a client or a server that also happens to be aNetBackup for Oracle client.

To install NetBackup for Oracle on a local machine

1 Review Verifying the installation prerequisites on page 37.

To install the database agent on a clustered NetBackup server, read Cluster

software on page 39.

2 (Conditional) Perform this step only if you want to install on a server that ispart of a NetBackup cluster.

a Freeze the active NetBackup node.

When you install NetBackup for Oracle, install the software on all the

inactive nodes first, then install on the active node. For information on

how to freeze the active node in your specific cluster environment, see

the NetBackup High Availability Administrators Guide.

b Decide which of the inactive nodes to install the software on first.




48/230

In the next step, you log in to the first machine and start the

installation process. Because you need to perform the installation on all

inactive nodes first, make sure that the first machine you select is aninactive node.

3 Log in as the root user on the machine.


command.

su - root

4 (Conditional) Log into a media server or the master server.

Perform this step if the local machine is a NetBackup client.

nbu-290216-netbackup for oracle admin guide

Documents