NBU-290216-Netbackup For Oracle Admin Guide

Veritas NetBackup for Oracle Administrators Guide
for UNIX and Linux
Release 6.5
12308316
Veritas NetBackup for Oracle Administrators Guide

Copyright 2007 Symantec Corporation. All rights reserved. NetBackup 6.5 Symantec, the Symantec logo, and NetBackup are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THIS DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software and commercial computer software documentation as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 www.symantec.com Printed in the United States of America.
Third-party legal notices

Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed 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 Guide for license installation instructions.
Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone or email support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer email notification service.
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 ...........................................................................................39 Installing 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
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 ............................................................ 89 Oracle 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 ................................................................................... 100 Storing 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 ......................................................... 126 User-directed XML exports from the client ........................................... 126 Browsing XML export archives ........................................................................ 133
Using bporaimp parameters to browse XML export archives ............133 Using bplist to browse XML export archives .........................................134 Restoring 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 Client

Installation 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 ...................................................................................................149 File-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 .....................................................153 Redirecting 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 backup methods ...............................................................................................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 ....................................................................171 Configuring policies for BLI backups ......................................................171 Snapshot Client effects .....................................................................................173
Types of backups ....................................................................................... 173 Schedule properties ................................................................................... 174 Templates 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 .......................... 186 Troubleshooting 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 Clusters

Virtual 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 without RMAN

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 .................... 206 Configuring script-based BLI backups ........................................................... 207 Creating NetBackup policies for script-based BLI backup .................. 207
Setting the maximum jobs per client global attribute .........................212 Creating directories for logging NetBackup activity ............................212 Selecting 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 .............................................221 Improving netbackup backup performance ..........................................224 Database recovery ......................................................................................224
Index
225
10
Chapter
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 features

Table 1-1 shows NetBackup for Oracles main features and introduces some terms used in the NetBackup for Oracle documentation.
Table 1-1 Feature

Media and device management
NetBackup for Oracle features and descriptions Description

All devices supported by Media Manager are available to NetBackup for Oracle.
12 Introduction NetBackup for Oracle features
Table 1-1 Feature
NetBackup for Oracle features and descriptions (continued) Description

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.
Scheduling facilities
Multiplexed backups NetBackup for Oracle lets you take advantage of NetBackups and restores 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 Oracles Recovery 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 Centralized and networked backup operations 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. 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. NetBackup provides the following graphical user interfaces for client users and administrators:

Graphical user interfaces
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.
Introduction NetBackup for Oracle features
13
Table 1-1 Feature

Templates
NetBackup for Oracle features and descriptions (continued) Description

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 native to 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. 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 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:

Parallel backup and restore operations
Compression
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.
For more information on general NetBackup terminology, see the NetBackup Administrators Guide, Volume I.
14 Introduction NetBackup for Oracle terminology
Table 1-2 describes NetBackup for Oracle XML export and XML import archiving features. Table 1-2 Feature
System- and database-independent archive format
NetBackup for Oracle XML export and XML import archiving features Description
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 format for 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 contains the key to understanding the format of the data as well as the data itself. 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.
Command line interfaces that allow export and import at row-level granularity Restore destination option
NetBackup for Oracle can either restore XML data to an Operating System directory or import the data back into the Oracle database. The NetBackup catalog contains information on the contents of the archive that can be searched using flexible search criteria, such as tablename or user.
Flexible archive image searches
NetBackup for Oracle terminology

This 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.
Introduction NetBackup for Oracle terminology
15
XML export archives

Figure 1-1 shows the XML export archive process. Figure 1-1 XML export archives
XML export
Archive
NetBackup
XML Format OS Directory
The archive activity includes the following actions: Activity

Oracle XML archive
Process
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). NetBackup stores the XML data on a NetBackup storage unit. NetBackup for Oracles XML export utility converts Oracle database table data into a self-identifying XML schema document and instance document that can be archived by NetBackup or redirected to an OS directory.
Archive bporaexp command
XML import restores

Figure 1-2 shows the XML import restore process. Figure 1-2 XML import restores
OS Directory
XML import restore
NetBackup
XML Format OS Directory
The restore activity includes the following actions: Activity

Oracle XML Restore
Process
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. NetBackup retrieves the XML-formatted data from the storage unit. NetBackup for Oracle parses XML-formatted Oracle table data and inserts data into the Oracle database. 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.
Restore
XML import
bporaimp command
Introduction NetBackup for Oracle terminology
17
Oracle terms
The following list explains some Oracle terms as they pertain to NetBackup. Term
Full backup
Definition
A full 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; full is 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 blocks are skipped. 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:
Multilevel incremental backup
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.
Term
Differential incremental backup
Definition
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. 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 all blocks 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.
Cumulative incremental backup
Oracle RMAN terms

The following list explains Oracle RMAN terms as they pertain to NetBackup. Term
RMAN
Definition
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 to NetBackups automatic scheduling facilities and the graphical interfaces. 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.
RMAN repository
Introduction NetBackup for Oracle overview
19
Term
rman command
Definition
The rman command starts an RMAN backup or restore. Your Oracle documentation describes this command. 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.
RMAN script
NetBackup for Oracle overview

Figure 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.
20 Introduction NetBackup for Oracle overview
Figure 1-3
NetBackup for Oracle on a sample network

System hosting the Oracle database NetBackup for Oracle supplies: Oracle database to back up or restore Sample configuration program Sample script files Veritas I/O Library (libobk) bporaimp and bporaexp
System containing Oracle database Recovery Catalog
Oracle database software supplies: Additional NetBackup software: Oracle Recovery Manager (RMAN) Oracle Call Interface (OCI) NetBackup client (required)
Network (TCP/IP)
NetBackup master server or remote media server NetBackup software: NetBackup master server NetBackup media server (if system is a media server)
Storage unit
RMAN
The 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
21
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 in generating 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 2 3 The rman command starts the requested operation on the databases. When the process requires media to store backup data, RMAN starts a user-directed backup by issuing a backup request. 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.
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 of the 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 catalog

The 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 import

While 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
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
XML schema(s), XML instance(s) XML schema(s), XML instance(s)
XML generator Option to create XML files on disk
NetBackup
Table(s) metadata, Table(s) data Query processor
Oracle DBMS
OCI Table list WHERE clause Script or template Command line (bporaexp) (Parameter file) Backup, archive, and restore interface
Scheduler NetBackup
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.
For an XML export archive: 1 2 3 4 5 6 7 The NetBackup for Oracle script or template calls the bporaexp utility with a specified parameter file. The query processor uses the parameters in the specified file to build an SQL query for each table. Oracles OCI API executes the queries on the Oracle instance to be archived. The query processor passes the output (including metadata and data for a single table or multiple tables) to the XML Generator. For each table passed, the XML generator builds one or more sets of XML schema and XML instance documents. XML data streams are backed up by NetBackup. Alternately, bporaexp allows the files to be saved to an operating system directory.
Sequence of operation: XML import restore

Figure 1-5 shows data flow.
25
Figure 1-5
XML import restore data flow
XML schema(s), XML instance(s)
Option to restore XML files on disk
XML Parser
XML schema(s), XML instance(s)
NetBackup
Table(s) metadata, Table(s) data
Archive name Keyword Table name
OCI Oracle DBMS XML data loader
Script or template (bporaimp) (Parameter file)
Command line or Backup, Archive, and Restore interface
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 2 The NetBackup for Oracle script or template calls the bporaimp utility with a specified parameter file. The input parameters that identify the XML archive to restore are passed to NetBackup.
3 4 5
NetBackup locates and reads the set of XML schema and instance documents from the NetBackup storage unit. The XML data stream is passed to an XML parser, which passes the data to the XML data loader. 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 allows import from an operating system directory into Oracle.
Chapter
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 Oracle

To 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 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 already exists.
For a more comprehensive list of installation prerequisites, see Verifying the installation prerequisites on page 37.
Performing the NetBackup for Oracle installation

During a local installation, the NetBackup for Oracle files are extracted and installed. The instructions that follow are for an initial, local installation on the NetBackup 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.
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 4 5
Insert the CD-ROM into the drive. Change to the working directory to the CD-ROM directory. cd /CD_mount_point Load and install the software by running the install script.
./install
Select the NetBackup Database Agent Software option. The following prompt appears: Answer y. You are presented with a menu of all database agents available on the CD-ROM. Select the NetBackup for Oracle option.
Do you want to do a local installation? (y/n) [n]
NetBackup for Oracle QuickStart Installing NetBackup for Oracle
29
d e
Enter q to quit selecting options. A prompt appears asking if the list is correct. Answer y. 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 in directory /usr/openv/share that contains the version of NetBackup for Oracle that was installed.
Linking NetBackup for Oracle with RMAN

Before 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 2 Become the Oracle user.
su - oracle
(Conditional) Shut down all of the Oracle instances (SIDs). Perform this step if you are using an Oracle8 release. Oracle releases 9 and later 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 b Set the $ORACLE_SID environment variable to the first SID. 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/password as sysdba shutdown immediate exit
30 NetBackup for Oracle QuickStart Configuring a NetBackup for Oracle policy and schedule
c 3
Change the $ORACLE_SID environment variable to any other SID that uses this Oracle installation, and repeat the preceding commands.
Set up automatic linking. a b Change directory to /usr/openv/netbackup/bin/ 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 the MAKE_TRACE variable in the oracle_link script.
Restart the Oracle instances.
Configuring a NetBackup for Oracle policy and schedule

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 Console

You 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 2 Log on to the NetBackup master server as root. Start the NetBackup administration console by typing the following command: /usr/openv/java/jnbSA &
NetBackup for Oracle QuickStart Configuring a NetBackup for Oracle policy and schedule
31
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 2 Log on to the NetBackup master server as the administrator. Start the NetBackup administration console by clicking Start > All Programs > Veritas NetBackup > NetBackup Administration Console.
Creating an Oracle policy and schedules

The 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 2 3 If necessary, use File > Change Server to select the master server upon which you want to create the policy. In the left pane, click Policies. Right-click in the All Policies pane, and click New Policy. The Add a New Policy dialog displays. a b c 4 In the Policy name box, type a unique name for the new policy. Select Use Backup Policy Configuration Wizard to use the backup policy configuration wizard. Click OK. Click Next.
Complete the backup policy configuration wizard by supplying the following information: a b On the Policy Name and Type screen, select Oracle as the policy type. Click Next. 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. On the Backup Type screen, click Next to accept the defaults. On the Rotation screen, click Next to accept the defaults. On the Start Window screen, click Next to accept the defaults. Click Finish to create the policy.
c d e f 5
Proceed to To create schedules on page 32 for information on creating schedules for this policy.
32 NetBackup for Oracle QuickStart Configuring a NetBackup for Oracle policy and schedule
To create schedules Schedules determine when NetBackup for Oracle initiates a backup. An Oracle backup 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. Double-click the policy name. The Policy dialog appears. Click the Schedules tab. Double-click the schedule named Default-Application-Backup. By default, the NetBackup sets the following:

1 2 3
The retention period is 1 month. Multiplexing is 1.
The schedule is seven days per week and 24 hours per day. This ensures that your backups can always commence. Make any changes to the Default-Application-Backup schedule if needed. 4 5 6 7 8 9 Click OK. Click New to create another schedule. Specify a unique name for the schedule. Select Automatic Full Backup as the Type of Backup. Click the Start Window tab. 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 specify Sunday evenings from 1800-2300. By default, the retention period is infinity, and the frequency is once per week.
10 Click OK. 11 Click Close.
NetBackup for Oracle QuickStart Backing up the Oracle database
33
Backing up the Oracle database

NetBackup 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 2 3 Use operating system methods to log into the client upon which NetBackup for Oracle is installed. Make sure that the Oracle database is in the mount or open state. If this is not the case, this procedure fails. Start the NetBackup Backup, Archive, and Restore interface on the NetBackup client. Run the following command: /usr/openv/java/jbpSA & 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. Click the Backup Files tab.
34 NetBackup for Oracle QuickStart Backing up the Oracle database
Expand the Oracle node in the left pane by clicking the node icon to the left of Oracle. After you expand the node, you see the list of Oracle instances that you can back up. Decide whether you want to back up an entire Oracle instance or an individual Oracle instance data file.

Click here to expand the Oracle node
To back up an entire Oracle instance, go to step 8. To back up an individual Oracle instance data file, go to step 9.
To back up an entire instance, perform the following steps: a b Click the check box to the left of the instance name. Proceed to step 10.
To back up individual instance data files, perform the following steps: a b Expand the instance by clicking the node icon to the left of the name of the Oracle instance data file you want to back up. (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):
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. Proceed to step 10.
10 Click Backup. The NetBackup for Oracle backup wizard welcome screen displays.
NetBackup for Oracle QuickStart Backing up the Oracle database
35
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. 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.
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. Click Next. The Archived Redo Logs screen displays. Click Next to accept all defaults. The Configuration Options screen displays. Click Next to accept all defaults. The Backup Options screen displays. Click Next to accept all defaults. The Database State screen displays. 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. Click Next. The Backup Limits screen displays.
4 5 6 7 8
10 Click Next to accept all defaults. The Template Summary screen displays. 11 Click Perform backup immediately after wizard finishes.
36 NetBackup for Oracle QuickStart Backing up the Oracle database
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
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 prerequisites

Perform the procedures in this section before you install the database agent. These requirements apply for remote and local installations.
Operating system and platform compatibility

Verify that NetBackup for Oracle is supported on your operating system or platform. To verify compatibility 1 2 3 4 Go to the technical support Web page: http://entsupport.symantec.com. In the Product Lookup field, type in NetBackup Enterprise Server and click on the > button. From the list on the right, click on Compatibility List. In the list of documents, click Veritas NetBackup Enterprise Server (tm) x.x / NetBackup Server x.x Database Agent Compatibility (Updated date). For x.x, look for the current release. For date, look for the most recent date.
38 Installing the agent Verifying the installation prerequisites
For information on supported cluster environments for NetBackup for Oracle, see NetBackup (tm) x.x Cluster Compatibility (updated date). 5 6 Click the link for the PDF document, which is a downloadable file that enables you to view the supported database spreadsheet for this release. Read the document and verify that the software in your environment is compatible with the NetBackup and the database agent.
NetBackup software
Verify 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 of data 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 software
Verify 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.
Installing the agent Installing NetBackup for Oracle
39
Cluster software
Verify the following requirements if you are installing the database agent software 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 Oracle

You 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 local machine only. Local installation of NetBackup for Oracle on page 47 describes this procedure.
Remote installation of NetBackup for Oracle

During 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 clients to install it.
40 Installing the agent Installing NetBackup for Oracle
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. (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. 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 the installation 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.
Log in as the root user on the master server or media server. If you are already logged in, but are not the root user, run the following command:
su - root
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 NetBackup master 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. Mount the CD-ROM. For more information on how to mount a CD-ROM, see the NetBackup Installation Guide.
41
Change the working directory to the CD-ROM directory. For example: cd /CD_mount_point 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:
b c d e
Type n. Select the NetBackup for Oracle option. Type q to quit selecting options. A prompt appears that asks if the list is correct. Type y. 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).)
(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.
(Conditional) Unfreeze the active node. Perform this step if you want to install the NetBackup for Oracle software on a server that is part of a NetBackup cluster. The last step in the
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 that are 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 after you 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 use this 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
Note: If you want to push the database agent software from a server that is part of a NetBackup cluster to an inactive node in the cluster, you need to force the installation to the inactive node. 1 Run the update_dbclients command to launch the installation script. Type the following command: 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. identifier is a mix of date, time, and process identifier information. The TMPDIR environment variable is defined as /tmp. 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 hostname or hostname.domainname. If the client list contains virtual names, you cannot complete this procedure. Do one of the following:
/usr/openv/netbackup/bin/update_dbclientsOracle ALL ALL
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.
Check the skipped client list, if any.
If update_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 PID is the process identifier. The TMPDIR environment variable is defined as /tmp. If no file is present, no clients were skipped.
(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 software to 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) max The maximum number of simultaneous updates that is allowed. The value that is displayed ranges from 1 to 30. The number the program uses if you press Enter without specifying a number. The value that is displayed ranges from 1 to 15.
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 the max, then press Enter. For example, if three clients are to be updated, the max and dflt values are 3. If 50 clients are to be updated, the max value 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.
45
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]
Type y 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 identifier is a mix of date, time, and process identifier information. The TMPDIR environment variable is defined as /tmp. If you type y, 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 clients

Use 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.
Note: If you want to push the database agent software from a server that is part of a NetBackup cluster to an inactive node in the cluster, you need to force the installation to the inactive node.
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 bpdbm daemon is not running, type the following command to start the daemon: /usr/openv/netbackup/bin/initbpdbm Type the following command to change to the NetBackup bin directory: cd /usr/openv/netbackup/bin 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:
2 3
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 ms_name file Name of the NetBackup master server in this environment. Name of the file to contain the list of unique clients. If no clients have been configured in the NetBackup database, file is empty. Create file using the same format as that generated by bpplclients.
bpplclients writes output to file in the following format: hardware op_system client
hardware The hardware name. For examples, type the ls(1) command in directory /usr/openv/netbackup/client. The operating system name. For examples, type the ls(1) command in directory /usr/openv/netbackup/client/hardware. The name of the client.
op_system
client
For example, file might contain a line like the following: Solaris Solaris8 curry 4 (Optional) Edit file. Perform this step to change the contents of file. Edit file to contain only those clients you want to update with NetBackup for Oracle software.
47
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 hostname or hostname.domainname. 5 Run the update_dbclients command to install the software. Specify the file you 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 -ClientList file 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 not need 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 Oracle

During 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 a NetBackup 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. (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. 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 the installation 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 machine. If you are already logged in, but are not the root user, run the following command. su - root (Conditional) Log into a media server or the master server. Perform this step if the local machine is a NetBackup client. 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:
4 5
From the master server or media server, type the following command: /usr/openv/netbackup/bin/admincmd/get_license_key When the system prompts you, type the host name of the NetBackup master 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. (Conditional) Log out of the media server or master server and return to the local client. Perform this step if you logged into a media server or the master server in step 4 to verify the license. Mount the CD-ROM. For more information on how to mount a CD-ROM, see the NetBackup Installation Guide. Change the working directory to the CD-ROM directory. For example: cd /CD_mount_point Run the install script to load and install the software.
Note: Make sure that the NetBackup for Oracle version is the same version as the NetBackup client software.
49
Type the following command: ./install a Select the NetBackup Database Agent Software option. The following prompt appears:
b c d e
Type y. A menu of all database agents available on the CD-ROM appears. Select the NetBackup for Oracle option. Type q to quit if you do not want to select other options. A prompt appears that asks if the list is correct. Type y. The following actions occur:
The script writes the version file, a tar(1) file compressed with gzip(1), and the install_dbext script 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 in directory /usr/openv/share that contains the version of NetBackup for Oracle that was installed.
Type q to quit from the script.
Note: You do not need to run the cluster_config script after you install NetBackup for Oracle on a server that is part of a NetBackup cluster. 10 (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 10 for that node. If you installed the software on all the inactive nodes, select the active node and repeat step 3 through step 10 for that node. If you installed on all the nodes, proceed to step 11.
11 (Conditional) Unfreeze the active node.
50 Installing the agent Linking the Oracle Recovery Manager (RMAN) with NetBackup
Perform this step to install the NetBackup for Oracle software on a server that is part of a NetBackup cluster. The last step in the installation process is to unfreeze the active node. Unfreeze the active node only after all the software has been 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.
Linking the Oracle Recovery Manager (RMAN) with NetBackup

Before writing to a storage unit, link the Oracle Server software with the NetBackup API library installed by NetBackup for Oracle. Oracle uses this library when it needs to write to, or read from, devices supported by Media Manager. The following subsections explain how to link your Oracle software with the NetBackup API library. You can use either the linking script that NetBackup provides, or you can create the links manually. The linking process differs depending on your hardware platform, your Oracle Server release level, and your OS level. This document does not address all the supported combinations, but it specifies OS level differences. The default location for the NetBackup API library is /usr/openv/netbackup/bin. The name of the NetBackup API library differs, depending on your platform, as show in Table 3-1. Table 3-1 Platform AIX AIX HP-UX HP-UX IRIX Linux Linux Linux Itanium IBM pSeries NetBackup API libraries Oracle 32-bit 64-bit 32-bit 64-bit 64-bit 32-bit 64-bit 64-bit 64-bit Library Name libobk.a libobk.a64 libobk.sl libobk.sl64 libobk.so64 libobk.so libobk.so64 libobk.so libobk.so
Installing the agent Linking the Oracle Recovery Manager (RMAN) with NetBackup
51
Table 3-1 Platform
NetBackup API libraries Oracle Library Name libobk.so.1 libobk.so64.1 libobk.so.1 libobk.so.1
Solaris (SPARC) and Digital 32-bit UNIX Solaris (SPARC) Solaris (Opteron) Tru64 64-bit 64-bit 64-bit
Verifying environment variables and shutting down Oracle

To verify environment variables and shut down Oracle instances 1 Make sure that your Oracle environment variables are defined according to the following list: Environment variable
ORACLE_HOME ORACLE_SID
Definition
The directory path to the Oracle software location. The name of the Oracle instance.
2 3
Become the Oracle user.

su - oracle
(Conditional) Enter commands to shut down all Oracle instances (SIDs). Perform this procedure only for the Oracle 8 releases. a b Set the ORACLE_SID environment variable to the first SID. Type the following commands to shut down Oracle: svrmgrl connect internal shutdown exit Change the ORACLE_SID environment variable to any other SID that uses this Oracle installation and repeat the commands in step b.
c 4
Determine whether to restart Oracle and resume operations or to link the library.
If you are upgrading an existing NetBackup for Oracle installation, restart the Oracle instance you stopped before you ran the update_dbclients command and then resume operations.
If you are performing an initial installation, follow the instructions in Linking the library on page 52. This section describes both an automatic and a manual method. The automatic method is preferred.
Linking the library

The following sections show how to link the library. The automatic method is preferred. Use the manual method only if the link script fails or if you receive Oracle messages to indicate that manual linking is required. Note: Perform the linking procedure in this section only if you are installing NetBackup for Oracle for the first time. You do not need to link the library if you are installing NetBackup for Oracle as an upgrade.
To link automatically
Run the oracle_link script located in /usr/openv/netbackup/bin/. This script determines the Oracle version level and then links Oracle with the NetBackup API library. This script writes output to /tmp/make_trace.<pid>. To change the trace file location, change the MAKE_TRACE variable in the oracle_link script.
To link manually
Follow the instructions in one of the following platform-specific subsections: For Oracle8 and Oracle8i:
Manually linking AIX (32-bit or 64-bit) using 32-bit Oracle8i software on page 54 Manually linking AIX (64-bit) using 64-bit Oracle8i software on page 55 Manually linking HP-UX (32-bit or 64-bit) using 32-bit Oracle8 or Oracle8i software on page 56 Manually linking HP-UX (64 bit) using 64-bit Oracle8 or Oracle8i software on page 58 Manually linking IRIX (64-bit) using 64-bit Oracle8 or Oracle8i software on page 60 Manually linking Solaris (32-bit or 64-bit) using 32-bit Oracle8 or Oracle 8i software on page 62 Manually linking Solaris (64-bit) using 64-bit Oracle 8i software on page 64
53
Manually linking Tru64/Digital UNIX (OSFI) using Oracle8 or Oracle8i software on page 65 Oracle9i and Oracle10g:

Manually linking AIX using 64-bit Oracle9i or later software on page 67 Manually linking HP-UX (64-bit) using 64-bit Oracle9i or later software on page 68 Manually linking Linux (32-bit) and Linux IA-64 using Oracle9i or later software on page 69 Manually linking Linux (64-bit) using Oracle9i or later software on page 70 Manually linking IBM pSeries using Oracle 10g R2 or later software on page 71 Manually linking Solaris (32-bit or 64-bit) using 32-bit Oracle9i or later software on page 72 Manually linking Solaris (Opteron, 64-bit) using 64-bit Oracle9i or later software on page 73 Manually linking Solaris (SPARC, 64-bit) using 64-bit Oracle9i or later software on page 74 Manually linking Tru64/Digital UNIX (OSFI) using Oracle9i or later software on page 75
Note: If you are using a later Oracle release, you do not have to use the make(1) command to make a new Oracle executable to use the NetBackup for Oracle API library because the Oracle executable always searches for the shared library (for example, $ORACLE_HOME/lib/libobk.so). The instructions in the following subsections reflect this change and describe the conditions under which you need to issue the make(1) command.
Manually linking AIX (32-bit or 64-bit) using 32-bit Oracle8i software

To link manually 1 Set the Oracle user's library search path. To prevent linking and runtime load errors, put $ORACLE_HOME/lib in the Oracle user's library search path. If $ORACLE_HOME/lib is not in the search path, the NetBackup API shared library, libobk, is not found when linking, and a runtime load error is issued when an application, such as svrmgrl, is run. Set the LIBPATH environment variable as follows:
In the C shell, edit the Oracle user's .cshrc file to include the following line:
setenv LIBPATH $ORACLE_HOME/lib:$LIBPATH
In the Bourne or Korn shells, edit the Oracle user's .profile file to include the following lines:
LIBPATH=$ORACLE_HOME/lib:$LIBPATH export LIBPATH
2 3
Type the following cd(1) command to change directories:

cd $ORACLE_HOME/lib
Type the following ls(1) command to determine whether the Oracle library exists:
ls -l libobk.a
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 3 shows that libobk.a is present. For example:
mv libobk.a libobk.a.orig
Type the following ln(1M) command to create a new link:

ln -s /usr/openv/netbackup/bin/libobk.a libobk.a
55
Manually linking AIX (64-bit) using 64-bit Oracle8i software

To link manually 1 Set the Oracle user's library search path. To prevent linking and runtime load errors, put $ORACLE_HOME/lib in the Oracle user's library search path. If $ORACLE_HOME/lib is not in the search path, the NetBackup API shared library, libobk, is not found when linking, and a runtime load error is issued when an application, such as svrmgrl, is run. Set the LIBPATH environment variable as follows:
setenv LIBPATH $ORACLE_HOME/lib:$LIBPATH
LIBPATH=$ORACLE_HOME/lib:$LIBPATH export LIBPATH
2 3

cd $ORACLE_HOME/lib64
ls -l libobk.a
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 3 shows that libobk.a is present. For example:
Type the following ln(1M) command to create a new link:

ln -s /usr/openv/netbackup/bin/libobk.a64 libobk.a
Manually linking HP-UX (32-bit or 64-bit) using 32-bit Oracle8 or Oracle8i software
To link manually 1 Set the Oracle user's library search path. To prevent linking and runtime load errors, put $ORACLE_HOME/lib in the Oracle user's library search path. If $ORACLE_HOME/lib is not in the search path, the NetBackup API shared library, libobk, is not found when linking, and a runtime load error is issued when an application, such as svrmgrl, is run. Set the SHLIB_PATH environment variable as follows:
setenv SHLIB_PATH $ORACLE_HOME/lib:$SHLIB_PATH
SHLIB_PATH=$ORACLE_HOME/lib:$SHLIB_PATH export SHLIB_PATH
2 3

cd $ORACLE_HOME/lib
ls -l libobk.sl
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 3 shows that libobk.sl is present. For example:
mv libobk.sl libobk.sl.orig
5 6
Type the following ln(1M) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.sl libobk.sl (Conditional) Make a new Oracle executable. Perform this step if you are using Oracle8 releases 8.0.4, 8.0.5, 8.0.5.1, or 8.0.6. a b Type the following cd(1) command to change directories: cd $ORACLE_HOME/rdbms/lib Use the make(1) command to create a new executable. This step differs depending on your Oracle release level. Make sure to use the quotation marks ( " " ) as shown.
On Oracle8 release 8.0.4, type the following command:
make -f ins_rdbms.mk ioracle LLIBMM="$ORACLE_HOME/lib/libobk.sl"
57
On Oracle8 releases 8.0.5, 8.0.5.1, and 8.0.6 for HP-UX 10.20 9000/816, type the following command and make sure to include the LIBMM= at the end: On Oracle8 releases 8.0.5, 8.0.5.1, and 8.0.6 for HP-UX 11.00 9000/879, type the following command:
make -f ins_rdbms.mk ioracle LLIBMM="$ORACLE_HOME/lib/libobk.sl" LIBMM=
make -f ins_rdbms.mk ioracle LLIBOBK="$ORACLE_HOME/lib/libobk.sl"
Manually linking HP-UX (64 bit) using 64-bit Oracle8 or Oracle8i software
To link manually 1 Set the Oracle user's library search path. To prevent linking and runtime load errors, put $ORACLE_HOME/lib in the Oracle user's library search path. If $ORACLE_HOME/lib is not in the search path, the NetBackup API shared library, libobk, is not found when linking, and a runtime load error is issued when an application, such as svrmgrl, is run. Set the SHLIB_PATH environment variable as follows:
In the C shell, edit the Oracle user's .cshrc file to include the following line: setenv SHLIB_PATH $ORACLE_HOME/lib:$SHLIB_PATH In the Bourne or Korn shells, edit the Oracle user's .profile file to include the following lines: SHLIB_PATH=$ORACLE_HOME/lib:$SHLIB_PATH export SHLIB_PATH
Use the cd(1) command to change directories. This step differs depending on your Oracle release level.
On Oracle8 release 8.0.5.1, type the following command: cd $ORACLE_HOME/lib On Oracle8 release 8.0.6 and on Oracle8i releases 8.1.6 and 8.1.7, type the following command: cd $ORACLE_HOME/lib64
3 4
Type the following command to determine whether the Oracle library exists:
ls -l libobk.*
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 3 shows that libobk.sl or libobk.a are present. For example:
mv libobk.a libobk.a.orig mv libobk.sl libobk.sl.orig
5 6
Type the following ln(1M) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.sl64 libobk.sl (Conditional) Make a new Oracle executable. Perform this step if you are using Oracle8 release 8.0.5.1 or 8.0.6. a Type the following cd(1) command to change directories: cd $ORACLE_HOME/rdbms/lib
59
Use the make(1) command to create a new executable. This step differs depending on your Oracle release level. Make sure to use the quotation marks (" ") as shown.
On Oracle 8.0.5.1, type the following command: On Oracle 8.0.6, type the following command:
make -f ins_rdbms.mk ioracle LLIBOBK="$ORACLE_HOME/lib/libobk.sl"
make -f ins_rdbms.mk ioracle LLIBOBK="$ORACLE_HOME/lib64/libobk.sl"
Note: Ignore the warnings generated during make(1) command execution.
Manually linking IRIX (64-bit) using 64-bit Oracle8 or Oracle8i software

To link manually 1 Set the Oracle user's library search path. To prevent linking and runtime load errors, put $ORACLE_HOME/lib in the Oracle user's library search path. If $ORACLE_HOME/lib is not in the search path, the NetBackup API shared library, libobk, is not found when linking, and a runtime load error is issued when an application, such as svrmgrl, is run. Set the LD_LIBRARY_PATH environment variable as follows:
In the C shell, edit the Oracle user's .cshrc file to include the following line: setenv LD_LIBRARY_PATH $ORACLE_HOME/lib:$LD_LIBRARY_PATH In the Bourne or Korn shells, edit the Oracle user's .profile file to include the following lines: LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH
2 3

cd $ORACLE_HOME/lib
Determine whether the Oracle library exists. This step differs depending on your Oracle release level.
On Oracle8i release 8.1.6, type the following commands: ls -l libobk.so ls -l libobk.so64 On Oracle8i release 8.1.7, type the following command: ls -l libobk.so
(Conditional) Use the mv(1) command to move the Oracle libraries to alternate locations. Perform this step if the output from step 3 shows that libobk.so or libobk.so64 are present. Perform this step if the output from step 3 shows that libobk.so is present. This step differs depending on your Oracle release level.
On Oracle8i 8.1.6, type the following commands: mv libobk.so libobk.so.orig mv libobk.so64 libobk.so64.orig On Oracle8i 8.1.7, type the following command: mv libobk.so libobk.so.orig
61
Use the ln(1M) command to create a new link. This step differs depending on your Oracle release level. On Oracle8i release 8.1.6, type the following command: ln -s /usr/openv/netbackup/bin/libobk.so64 libobk.so64

On Oracle8i release 8.1.7, type the following command: ln -s /usr/openv/netbackup/bin/libobk.so64 libobk.so
(Conditional) Create a new Oracle executable. Perform this step if you are using Oracle8i release 8.1.6. a b Type the following cd(1) command to change directories: cd $ORACLE_HOME/lib As the Oracle owner, type the following command to create the compiler.defaults file: Set the COMPILER_DEFAULTS_PATH environment variable. In the C shell, type the following: setenv COMPILER_DEFAULTS_PATH $ORACLE_HOME/lib In the Bourne or Korn shells, enter the following: COMPILER_DEFAULTS_PATH=$ORACLE_HOME/lib export COMPILER_DEFAULTS_PATH Type the following command to change to the rdbms/lib directory: cd $ORACLE_HOME/rdbms/lib Type the following command to create the new executable:
echo "-DEFAULT:abi=64:isa=mips3:proc=r10k" > compiler.defaults
d e
make -f ins_rdbms.mk ioracle LLIBOBK="$ORACLE_HOME/lib/libobk.so64" PL_FLAGS=-64
Note: Ignore the warnings generated during make(1) command execution.
Manually linking Solaris (32-bit or 64-bit) using 32-bit Oracle8 or Oracle 8i software
To link manually 1 2 Type the following cd(1) command to change directories:
cd $ORACLE_HOME/lib
On Oracle8 releases 8.0.5, 8.0.5.1, 8.0.6 or Oracle8i releases 8.1.5, 8.1.7, type the following command: ls -l libobk.so On Oracle8i release 8.1.6, type the following command: ls -l libdsbtsh8.so
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 2 shows that libobk.so or libdsbtsh8.so are present. This step differs depending on your Oracle release level.
On Oracle8 releases 8.0.5, 8.0.5.1, 8.0.6 or Oracle8i releases 8.1.5, 8.1.7, type the following command: mv libobk.so libobk.so.orig On Oracle8i release 8.1.6, type the following command: mv libdsbtsh8.so libdsbtsh8.so.orig
Use the ln(1M) command to create a new link. This step differs depending on your Oracle release level.
On Oracle8 releases 8.0.5, 8.0.5.1, 8.0.6 or Oracle8i releases 8.1.5, 8.1.7, type the following command: ln -s /usr/openv/netbackup/bin/libobk.so.1 libobk.so
On Oracle8i release 8.1.6, type the following command: ln -s /usr/openv/netbackup/bin/libobk.so.1 libdsbtsh8.so
(Conditional) Make a new Oracle executable. Perform this step only if you are using Oracle8 releases 8.0.5, 8.0.5.1, 8.0.6 or Oracle 8i release 8.1.6. a b Type the following cd(1) command to change directories: cd $ORACLE_HOME/rdbms/lib Use the make(1) command to create a new executable. This step differs depending on your Oracle release level. Make sure to enter the command as shown.
63
On Oracle8 releases 8.0.5, 8.0.5.1, 8.0.6, type the following command: make -f ins_rdbms.mk ioracle On Oracle8i release 8.1.6, type the following command: make -f ins_rdbms.mk ioracle LLIBOBK=-lobk
Manually linking Solaris (64-bit) using 64-bit Oracle 8i software

To link manually 1 2 Type the following cd(1) command to change directories:
cd $ORACLE_HOME/lib64
On Oracle8i release 8.1.6, type the following command: ls -l libdsbtsh8.so On Oracle8i release 8.1.7, type the following command: ls -l libobk.so
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 2 shows that libdsbtsh.so or libobk.so are present. This step differs depending on your Oracle release level.
On Oracle8i release 8.1.6, type the following command: mv libdsbtsh8.so libdsbtsh8.so.orig On Oracle8i release 8.1.7, type the following command: mv libobk.so libobk.so.orig
Use the ln(1M) command to create a new link. This step differs depending on your Oracle release level.
On Oracle8i release 8.1.6, type the following command:
ln -s /usr/openv/netbackup/bin/libobk.so64.1 libdsbtsh8.so On Oracle8i release 8.1.7, type the following command: ln -s /usr/openv/netbackup/bin/libobk.so64.1 libobk.so
(Conditional) Make a new Oracle executable. Perform this step only if you are using Oracle8i release 8.1.6. a b Type the following cd(1) command to change directories: cd $ORACLE_HOME/rdbms/lib Type the following make(1) command to create a new executable: make -f ins_rdbms.mk ioracle LLIBOBK=-lobk
65
Manually linking Tru64/Digital UNIX (OSFI) using Oracle8 or Oracle8i software

To link manually 1 Set the Oracle user's library search path. To prevent linking and runtime load errors, put $ORACLE_HOME/lib in the Oracle user's library search path. If $ORACLE_HOME/lib is not in the search path, the NetBackup API shared library, libobk, is not found when linking, and a runtime load error is issued when an application, such as svrmgrl, is run. Set the LD_LIBRARY_PATH environment variable as follows:
In the C shell, edit the Oracle user's .cshrc file to include the following line: setenv LD_LIBRARY_PATH $ORACLE_HOME/lib:$LD_LIBRARY_PATH In the Bourne or Korn shells, edit the Oracle user's .profile file to include the following lines: LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH
2 3

cd $ORACLE_HOME/lib
ls -l libobk.*
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 3 shows that libobk.so or libobk.a are present. Type one or both of the following commands:
mv libobk.a libobk.a.orig mv libobk.so libobk.so.orig
Use ln(1M) commands to create a new link. This platform requires two symbolic links. RMAN searches for libobk.so.1, but other applications search for libobk.so. Type the following commands: ln -s /usr/openv/netbackup/bin/libobk.so.1 libobk.so.1 ln -s libobk.so.1 libobk.so (Conditional) Make a new Oracle executable. Perform this step if you are using Oracle8 release 8.0.6 or Oracle 8i release 8.1.5. This step differs depending on your Oracle release level.
On Oracle8 release 8.0.6, type the following commands:
cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk ioracle PL_FLAGS=-call_shared LLIBMM=-lobk
On Oracle8i release 8.1.5, type only one of the following two command sets:
The following commands use the provided relinking script to create a new Oracle executable. This is the preferred method: cd $ORACLE_HOME/bin relink oracle The following commands use the make(1) command to create a new Oracle executable:
cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk ioracle PL_FLAGS="-rpath $ORACLE_HOME/lib"
Type the following odump(1) command, which shows the timestamp and checksum, to verify that the library is linked:
odump -Dl oracle ***LIBRARY LIST SECTION*** Name Time-Stamp CheckSum oracle: libobk.so.1 Aug 31 09:00:16 1999 0xe22db854 libjox8.so Mar 9 12:04:42 1999 0xae77f433 libexc.so Dec 29 17:09:57 1997 0x3184247e librt.so Dec 29 17:20:24 1997 0x3f3d024b libaio_raw.so Jan 5 14:40:38 1998 0x568dc639 libm.so Dec 29 17:09:53 1997 0xf29b0962 libxti.so Dec 29 17:20:11 1997 0x89ffa69d libc.so Dec 29 17:09:30 1997 0x5e955f9b
Flags Version 0 0 0 osf.1 0 osf.1 0 osf.1 0 osf.1 0 osf.1 0 osf.1
67
Manually linking AIX using 64-bit Oracle9i or later software

Use this procedure for Oracle9i or later releases. To link manually 1 2 Type the following cd(1) command to change directories:
cd $ORACLE_HOME/lib
ls -l libobk.*
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 2 shows that libobk.a exists. For example:
Type the following ln(1M) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.a64 libobk.a
Manually linking HP-UX (64-bit) using 64-bit Oracle9i or later software

Use this procedure for Oracle9i or later releases. To link manually 1 2 Type the following the cd(1) command to change directories:
cd $ORACLE_HOME/lib
ls -l libobk.*
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 2 shows that libobk.sl or libobk.a are present.
If libobk.sl exists, type the following command: mv libobk.sl libobk.sl.orig If libobk.a exists, type the following command: mv libobk.a libobk.a.orig
Type the following ln(1) command to create new links: ln -s /usr/openv/netbackup/bin/libobk.sl64
libobk.sl
69
Manually linking Linux (32-bit) and Linux IA-64 using Oracle9i or later software
cd $ORACLE_HOME/lib
ls -l libobk.so
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 2 shows that libobk.so is present. For example:
mv libobk.so libobk.so.orig
Type the following ln(1) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.so libobk.so
Manually linking Linux (64-bit) using Oracle9i or later software

cd $ORACLE_HOME/lib
ls -l libobk.so
Type the following ln(1) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.so64 libobk.so
71
Manually linking IBM pSeries using Oracle 10g R2 or later software

Use this procedure for Oracle 10g R2 or later releases. To link manually 1 2 Type the following cd(1) command to change directories:
cd $ORACLE_HOME/lib
ls -l libobk.so
Type the following ln(1) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.so libobk.so
Manually linking Solaris (32-bit or 64-bit) using 32-bit Oracle9i or later software
cd $ORACLE_HOME/lib
ls -l libobk.so
Type the following ln(1) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.so.1 libobk.so
73
Manually linking Solaris (Opteron, 64-bit) using 64-bit Oracle9i or later software
Use this procedure for Oracle 9i or later releases. To link manually 1 2 Type the following cd(1) command to change directories:
cd $ORACLE_HOME/lib
ls -l libobk.so
Type the following ln(1) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.so.1 libobk.so
Manually linking Solaris (SPARC, 64-bit) using 64-bit Oracle9i or later software
Use this procedure for Oracle 9i or later releases. To link manually 1 2 Type the following cd(1) command to change directories:
cd $ORACLE_HOME/lib
ls -l libobk.so
Type the following ln(1) command to create a new link: ln -s /usr/openv/netbackup/bin/libobk.so64.1 libobk.so
75
Manually linking Tru64/Digital UNIX (OSFI) using Oracle9i or later software

cd $ORACLE_HOME/lib
ls -l libobk.*
(Conditional) Use the mv(1) command to move the Oracle library to an alternate location. Perform this step if the output from step 2 shows that libobk.so or libobk.a are present.
If libobk.so exists, type the following command: mv libobk.so libobk.so.orig
Use the ln(1) command to create new links. This platform requires the two symbolic links shown in this step. RMAN searches for libobk.so.1, but other applications search for libobk.so. Type the following commands: ln -s /usr/openv/netbackup/bin/libobk.so.1 libobk.so.1 ln -s libobk.so.1 libobk.so
76 Installing the agent About the Oracle recovery catalog
Troubleshooting the linking procedure

If you run into problems and are unable to re-link Oracle with the NetBackup API library, you can roll back what you have done. For example, if you are using 32-bit Oracle software and you moved libobk.so to libobk.so.orig during the linking process, you can enter the following commands to roll back what you have done: cd $ORACLE_HOME/bin cp oracle0 oracle cd $ORACLE_HOME/lib mv libobk.so.orig libobk.so If you are using 64-bit Oracle software, enter the following: cd $ORACLE_HOME/bin cp oracle0 oracle cd $ORACLE_HOME/lib64 mv libobk.so.orig libobk.so
About the Oracle recovery catalog

The recovery catalog is a repository of information. The Oracle recovery manager (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:

Datafile and archive log backup sets and backup pieces. Datafile copies. Archived redo logs and their copies. Tablespaces and datafiles 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 datafiles. 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.
Chapter
Configuration
This chapter contains the following topics:

User interface terminology notes on page 77 Configuring the Maximum jobs per client on page 78 Configuring a backup policy for a database on page 78 Configuring the runtime environment on page 89 Creating templates and shell scripts on page 94 Testing configuration settings on page 106
Before attempting to configure NetBackup for Oracle, complete the installation procedure. See Installing the agent on page 37. After you complete the installation, follow the procedures in this chapter to configure your environment.
User interface terminology notes

You can perform many of the configuration steps in this chapter 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 Windows and UNIX master servers. In addition, NetBackup supports a Windows interface for Windows master servers. The Java and Windows interfaces are nearly identical. If interface differences exist in the configuration procedures, this manual uses the following headings to identify the interface being described: From the Windows interface: From the Java interface:
78 Configuration Configuring the Maximum jobs per client
Configuring the Maximum jobs per client

The following procedure shows how to set the Maximum jobs per client attribute. To configure the maximum jobs per client 1 2 3 4 5 In the left pane of the NetBackup administration console, expand Host Properties. Select Master Server. In the right pane, double-click the server icon. Click Global Attributes. Change the Maximum jobs per client value to 99. The Maximum jobs per client specifies the maximum number of concurrent backups that are allowed per client. The default is 1. You can use the following formula to calculate a smaller value: Maximum jobs per client = number_of_streams X number_of_policies
number_of_streams The number of backup streams between the database server and NetBackup. Each separate stream starts a new backup job on the client. The number of policies of any type that can back up this client at the same time. This number can be greater than one. For example, a client can be in two policies in order to back up two different databases. These backup windows can overlap.
number_of_policies
For Oracle backups and restores, the number of jobs is difficult to determine. This difficulty exists because Oracle internally determines when and how many streams to run in parallel to optimize performance. Tip: Enter a large enough value for the Maximum jobs per client attribute to meet the number of jobs that Oracle runs. You might need to experiment with different values at your site.
Configuring a backup policy for a database

A backup policy for a database defines the backup criteria for a specific group of one or more clients. These criteria include:
Storage unit and media to use
Configuration Configuring a backup policy for a database
79
Policy attributes Backup schedules Clients to be backed up Backup templates or script files to be run on the clients
To back up a database environment, you need to define at least one Oracle policy with the appropriate schedules. A configuration can have a single policy that includes all clients, or there can be many policies, some of which include only one client. Most requirements for database policies are the same as for file system backups. In addition to the policy attributes for this database agent, other attributes are available that you should consider. For configuration instructions and information on all the attributes available, see the NetBackup Administrators Guide, Volume I.
Adding a new policy

These instructions describe how to add a new backup policy for a database. To configure a backup policy for databases 1 2 3 4 Log on to the master server as administrator (Windows) or root (UNIX). Start the NetBackup Administration console. If your site has more than one master server, choose the one on which you want to add the policy. From the Windows interface: In the left pane, right-click Policies and choose New Policy. From the Java interface: In the left pane, click Policies. In the All Policies pane, right-click the master server, and click New Policy. In the Add a New Policy dialog box, in the Policy name field, type a unique name for the new policy. Click OK. In the Add a New Policy or Change Policy dialog box, in the Policy type list, select the Oracle policy type. The database agent policy type does not appear in the drop-down list unless your master server has a license key for the database agent. Complete the entries on the Attributes tab. For more information, see Description of attributes, which follows this procedure. Add other policy information.
5 6 7
80 Configuration Configuring a backup policy for a database
To add schedules, see Adding schedules on page 80. To add clients, see Adding clients on page 86. To add templates or scripts to the backup selections list, see Adding backup selections on page 87.
10 When you have added all the schedules, clients, and backup selections you need, click OK.
Description of attributes
With a few exceptions, NetBackup manages a database backup like a file system backup. Table 4-2 shows the policy attributes that are different for Oracle backups. This information is used when you add a new policy. Other policy attributes vary according to your specific backup strategy and system configuration. For more information on policy attributes, see the NetBackup Administrators Guide, Volume I. Table 4-2 Attribute
Policy type
Policy attribute descriptions Description

Determines the types of clients that can be in the policy. In some cases the policy type determines the types of backups that NetBackup can perform on those clients. To use the database agent, you must define at least one policy of type that is Oracle. For NetBackup for Oracle, the Keyword phrase entry is ignored. For information about how to configure advanced backup methods, see NetBackup for Oracle with Snapshot Client on page 147.
Keyword phrase Snapshot Client
Adding schedules
Each policy has its own set of schedules. These schedules initiate automatic backups and specify when a user can initiate operations. A database backup has two types of schedules: Application Backup and Automatic Backup.
Tips for configuring schedules
For an XML Export backup to be used for database archiving purposes, set the Retention to infinity.
81
Set the window for the Application Backup schedule for 24 hours per day, seven days per week. This window ensures that your operations are never locked out due to the Application Backup schedule.
Configuring an Application Backup schedule

A database backup requires an Application Backup schedule. You cannot perform backups if this type of schedule is not included in the policy. The database agent automatically creates this schedule, named Default-Application-Backup, when you configure a new database policy. To configure an Application Backup schedule 1 In the Policy dialog box, click the Schedules tab. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console. Double-click the schedule that is named Default-Application-Backup. Specify the other properties for the schedule. See Schedule properties on page 84. The backup window for an Application Backup schedule must encompass the time period during which all scheduled jobs and unscheduled jobs can occur. This window is necessary because the Application Backup schedule starts the processes that are required for all database backups, including those started automatically. For example, assume the following:
2 3
Users perform database backup operations during business hours, 08:00 to 13:00.
The Automatic backups that use this policy start between 18:00 and 22:00. In this scenario, the Application Backup schedule must have a start time of 0800 and a duration of 14 hours. Table 4-3 on page 81 shows this example schedule.
Table 4-3 Type of backup

Application Backup
Example settings for an Application Backup schedule Schedule settings

Retention
Description
Settings
The length of time the backup images 2 weeks are retained in the NetBackup catalog for restore. The time during which a NetBackup operation can be initiated. Sunday through Saturday 00:08:00 - 22:00:00
Backup Window
Configuring Automatic Backup schedules

You also need one or more automatic backup schedules if you plan to have NetBackup perform automatic backups, or if you use Snapshot Client features. To configure an Automatic Backup schedule 1 2 3 4 5 On the Policy dialog box, click the Schedules tab. Click New. Specify a unique name for the schedule. Select the Type of backup. See Types of backup schedules on page 83. Specify the other properties for the schedule. See Schedule properties, which follows this procedure. Table 4-4 shows example settings for an automatic backup schedule. When an automatic schedule runs, NetBackup sets the environment
Table 4-4 Type of backup

Automatic Full Backup
Example settings for an Automatic Backup schedule Schedule settings

Retention
Description
The length of time to store the record of a backup, which NetBackup uses to determine if the schedule needs to be run. Frequency determines how often a backup should be performed. The time during which a NetBackup operation can be initiated. The length of time to store the record of a backup, which NetBackup uses to determine if the schedule needs to be run. Frequency determines how often a backup should be performed. The time during which a NetBackup operation can be initiated.
Settings
2 weeks
Frequency
every week
Backup Window
Sunday, 18:00:00 22:00:00 1 week
Automatic Differential Incremental Backup
Retention
Frequency
every day
Backup Window
Sunday through Saturday 18:00:00 - 22:00:00
variables that are based on the type of automatic backup schedule selected. You can use these environment variables to initiate a backup conditionally. See Environment variables set by NetBackup for Oracle on page 92.
83
If this schedule is the last schedule, click OK. To add other schedules, repeat step 1 through step 6.
Types of backup schedules

Table 4-5 shows the backup schedules you can specify. Table 4-5 Backup type
Application Backup
Oracle backup types Description

The Application Backup schedule enables user-controlled NetBackup operations from the client. These operations include those initiated from the client and those initiated by an automatic schedule on the master server. NetBackup uses the Application Backup schedule when the user starts a backup manually. Configure at least one Application Backup schedule for each database policy. The Default-Application-Backup schedule is configured automatically as an Application Backup schedule. An Automatic Full Backup copies all blocks into the backup set. It skips only the data file blocks that have never been used. The Automatic Full Backup schedule enables scheduled NetBackup operations to be performed on the client. It is used to run a backup or XML export template or script automatically. NetBackup backs up all blocks that have changed since the most recent full or incremental backup at level n or lower. For example, in a differential level 2 backup, NetBackup backs up all the blocks that have been modified since the last level 2, level 1, or level 0 backup. Incremental backups are differential by default. Do not use an Automatic Differential Incremental Backup schedule for Oracle XML Exports.
Automatic Full Backup
Automatic Differential Incremental Backup
Automatic Cumulative Incremental Backup
NetBackup backs up all blocks that have changed since the most recent full backup at level n-1 or lower. For example, in a cumulative level 2 backup, NetBackup backs up all blocks that have changed since the most recent level 1 or level 0 backup. Cumulative incremental backups reduce the work that is needed for a restore. You need only one cumulative incremental backup from any particular level at restore time. Cumulative backups typically require more space and time than Differential Incremental Backups, however. They they duplicate the information in previous backups at the same level. Do not use an Automatic Cumulative Incremental Backup schedule for Oracle XML Exports.
Using backup schedules, templates, and scripts

Later in this chapter you configure templates or scripts to use when you perform backups and restores. Be aware that when an automatic schedule invokes a script that a user authored, NetBackup does not provide safeguards to prevent unusual behavior. For example, if an automatic backup schedule runs a restore or recovery script.
To help guard against such mistakes, use a template instead of a script whenever possible. When a template runs, it detects the backup type on the schedule. You are responsible for specifying a template with the correct operation type (backup or restore) in the policy.
Backup schedules and Snapshot Client features

The information in Types of backup schedules on page 83 pertains to stream-based backups. If you use the Snapshot Client option, be aware that some of the information in that table may differ if you use certain Snapshot Client features. For more information about backup schedules and Snapshot Client features, see NetBackup for Oracle with Snapshot Client on page 147.
Schedule properties
Some of the schedule properties have a different meaning for database backups than for a regular file system backup. Table 4-6 explains the schedule properties. Table 4-6 Property
Type of backup
Description of schedule properties Description

Specifies the type of backup that this schedule controls. The selection list shows only the backup types that apply to the policy you want to configure. For more information, see Types of backup schedules on page 83.
Frequency
This setting is used only for scheduled backups and not for user-directed backups. Frequency specifies the period of time that can elapse until the next backup or archive operation begins on this schedule. For example, assume that the frequency is seven days and a successful backup occurs on Wednesday. The next full backup does not occur until the following Wednesday. Typically, incremental backups have a shorter frequency than full backups. This setting is used only for scheduled backups. It is not used for user-directed backups. The Calendar option allows you to schedule backup operations that are based on specific dates, recurring week days, or recurring days of the month.
Calendar
85
Table 4-6 Property

Retention
Description of schedule properties (continued) Description

The retention period for an Application Backup schedule refers to the length of time that NetBackup keeps backup images. The retention period for an Automatic Full Backup, Automatic Differential Incremental Backup, or Automatic Cumulative Incremental Backup schedule controls how long NetBackup keeps records of when scheduled backups have occurred. Frequency-based scheduling Set a retention period that is longer than the frequency setting for the schedule. For example, if the frequency setting is set to one week, set the retention period to be more than one week. The NetBackup scheduler compares the latest record of the Automatic Backup schedule to the frequency of that Automatic Backup schedule to determine whether a backup is due. This means that if you set the retention period to expire the record too early, the scheduled backup frequency is unpredictable. However, if you set the retention period to be longer than necessary, the NetBackup catalog accumulates unnecessary records. Note: Oracle is not notified when NetBackup expires a backup image. Use Oracle RMAN repository maintenance commands to periodically delete expired backup sets from the Oracle RMAN repository. Oracle XML export operations create archives for long-term storage and recovery. Set the retention level to a period of years or to infinity. Calendar-based scheduling The retention period setting is not significant for calendar-based scheduling.
Multiple copies
If you want to specify multiple copies of a backup for the policy, configure Multiple copies on the Application Backup schedule.
Other schedule properties vary according to your specific backup strategy and system configuration. For more information on schedule properties, consult the NetBackup Administrators Guide, Volume I.
Managing expired backup images

NetBackup and Oracle each maintain a repository of RMAN-initiated backup image information. Automatic expiration of backup images from both repositories is not supported. To manage expired backup images, use the Retention setting in the NetBackup Application Backup schedule to expire the
Oracle backup images and then synchronize the NetBackup and Oracle repositories. To manage expired backup images from the NetBackup repository
In the Retention setting of the Application Backup Schedule, specify the length of time before NetBackup expires a backup image. Note that the retention setting has a slightly different meaning for an Application Backup schedule versus an automatic backup schedule. For more information, see Schedule properties on page 84.
To manually remove references to backup images from the Oracle RMAN repository
Use RMAN repository maintenance commands to remove references to backup files. You can use these commands to delete backup image information from both the Oracle RMAN repository and the NetBackup repository. For more information on the RMAN repository maintenance commands, refer to Maintaining the RMAN repository on page 109. When a request is issued to delete a backup file from the RMAN repository, RMAN sends the request to NetBackup to delete the corresponding image from the NetBackup repository, regardless of the retention level.
Adding clients
The client list enumerates the clients on which your NetBackup for Oracle template or shell scripts can run during an automatic backup. A NetBackup client must be in at least one policy but can be in more than one. NetBackup attempts to run each template in the backup selections list for each client in the client list. If a template is not valid on a particular client, for example, if the Oracle home specified in the template does not exist on that client, the template is skipped. A policy can contain multiple clients and multiple templates. Only a subset of the templates needs to be valid on each client. If the valid templates are successful, the entire backup is successful. For a database policy, clients you want to add must have the following software installed:

Oracle NetBackup client or server NetBackup for Oracle The backup or XML export archive shell script(s)(unless, for Oracle, you are using templates)
87
To add clients to a policy 1 In the Policy dialog box, click the Clients tab. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console. Click New. Enter the name of the client you want to add. If Oracle is installed in a NetBackup cluster, specify the virtual Oracle name as the client name. From the Windows interface
2 3
Type the name of the client and press Enter. If NetBackup cannot detect the hardware and operating system, a dialog box displays so you can specify this information. OR
Click the Browse for Computer button to choose the client from the network. From the Java interface
a b 4 5
In the Client name field, type the name of the client you want to add. Choose the Hardware and operating system type and click Add.
To add another client, repeat step 2 and step 3. If this client is the last client, click OK.
Adding backup selections

The backup selections list in a database policy has a different meaning than for non-database policies. For example, in a Standard or Windows-NT policy, the list contains files and directories to be backed up. In a database policy, you specify templates or scripts to be run.
Rules for templates or scripts

Observe the following when using templates or scripts:
Make sure the scripts reside on each client in the client list. Scripts can reside in any location. Make sure that NetBackup can access the location you choose and that NetBackup can run the scripts. Note that templates do not reside on the clients. Templates reside on the NetBackup master server. NetBackup installs sample scripts when you install the software, and you can modify these scripts for your own use. Write the scripts to a location
outside of the original installation location. This way future NetBackup installations do not overwrite your sites scripts.
If you use NetBackup for Oracle in a NetBackup server cluster, make sure that the scripts reside in a location that is available after a failover.
Add templates or scripts to the backup selections list only if you want to set up a policy for automatic backups. These templates or scripts are run for manual backups and for Automatic Full Backup, Automatic Differential Incremental Backup, or Automatic Cumulative Incremental Backup schedules as specified under the Schedules tab. NetBackup runs the templates or scripts in the order that the templates or scripts appear in the backup selections list. For more information on backup templates and scripts, see Creating templates and shell scripts on page 94.
Adding templates or scripts to the backup selections list

The following procedures describe how to add templates or scripts to the backup selections list using the Java interface and using the Windows interface. Caution: Be sure to specify the correct template and script names in the backup selections list to prevent an error or possibly a wrong operation. Make sure that the template or script resides on the client before you try to add it to the backup selections list.
To add templates or scripts to the backup selections list from the Java interface 1 Open the Policy dialog box. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console. Click the Backup Selections tab. Click New. Specify the names of the templates that you want NetBackup to use. a b From the Template Set list, choose the template type by operation. Choose a template from the drop-down Script or Template list or type the name of a template. Include the .tpl extension. Do not include the full path. For example: weekly_full_backup.tpl Click Add.
2 3 4
Configuration Configuring the runtime environment
89
d 5
Repeat step a, step b, and step c to add any other templates.
Specify the names of the scripts that you want NetBackup to use. a In the Script: box, type the full path name of a script on the client. For example:
/backup_scripts/db/cold_backup.sh
b c 6
Click Add to add the script to the list. Repeat step a and step b to add any other scripts.
Click OK.
To add templates or scripts to the backup selections list from the Windows interface 1 In the Policy dialog box, click the Backup Selections tab. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console. Click New. Specify the names of the templates you want NetBackup to use. Use one of the following methods:
2 3
Type the name of the template with the .tpl extension. Do not include the full path. For example: weekly_full_backup.tpl Click the Template button. From the Template set list, choose the template type by operation. From the Template list, choose the correct template. Click OK.
Specify the names of the scripts you want NetBackup to use. Use one of the following methods:
Type the full path name of the script on the client. For example:
/backup_scripts/db/cold_backup.sh
Click the Remote Folder button. Navigate to and select the script file. Click OK.
Click OK.
Configuring the runtime environment

The order of precedence for runtime configuration is slightly different for scheduled backups using templates than for all other types of backups. The lists
90 Configuration Configuring the runtime environment
below show the order of precedence for each situation. The following is the order of precedence for the runtime configuration variable settings. Scheduled backups with templates: 1 Environment variables set by NetBackup. For more information, see Environment variables set by NetBackup for Oracle on page 92. Environment variables set by the user.
For RMAN backups, these are set by the user with the Oracle RMAN send command and parms operand. For more information, see Oracle RMAN environment on page 91. For XML export archives, environment variables are set by the user in the XML export parameter file. For more information, see Environment variables set by a user in the XML export parameter file on page 92.
3 4
User bp.conf. For more information, see Creating a bp.conf file on page 93. Master bp.conf. For more information, see Creating a bp.conf file on page 93.
All other Oracle backups: 1 Environment variables set by the user.
For RMAN backups, these are set by the user with the Oracle RMAN send command and parms operand. For more information, see Oracle RMAN environment on page 91.
For XML export archives, environment variables are set by the user in the XML export parameter file. For more information, see Environment variables set by a user in the XML export parameter file on page 92. The user can also set these variables on the Configuration Variables screen of the template generation wizards. However, variables set in this manner apply only for templates run from the client (through the wizard, or through Template Administration). When the scheduler runs these templates on the NetBackup master server, NetBackup overrides these variables.
Environment variables set by NetBackup. For more information, see Environment variables set by NetBackup for Oracle on page 92. User bp.conf For more information, see Creating a bp.conf file on page 93.
91
Master bp.conf For more information, see Creating a bp.conf file on page 93.
Oracle RMAN environment

Table 4-7 shows how to define the RMAN environment. The method to use depends on the version of Oracle you are using. Table 4-7 RMAN commands that define the environment Connected using TNS (SQL*Net)
Oracle 8.1 or later Oracle 8 send command Not Applicable
Local connection
send command or parms operand parms operand
When connected to a database through a LISTENER using SQL*Net, RMAN takes on the environment of the LISTENER. Therefore, the environment defined at the system level is not visible when RMAN is running. In this case, the send command is used to modify the runtime environment.
Templates
With templates, NetBackup for Oracle environment variables are specified on the NetBackup for Oracle configuration variables wizard page. For more information, see Creating RMAN templates using the NetBackup for Oracle RMAN template generation wizard on page 95.
Shell scripts
Use the send command or the parms operand to specify NetBackup for Oracle environment variables for use during a backup or restore. Example 1. This example uses the send command to specify the policy and server to use for a database backup. As this example shows, specify the variables in the string in the RMAN script after all channels have been allocated and before the backup command.
run { allocate channel t1 type 'SBT_TAPE'; allocate channel t2 type 'SBT_TAPE'; send 'NB_ORA_POLICY=your_policy, NB_ORA_SERV=your_server; backup (database format 'bk_%U_%t'); }
92 Configuration Configuring the runtime environment
Example 2. This example uses the parms operand to specify the policy and server to use for a database backup. parms is set with each allocate channel command in the shell script.
run { allocate channel t1 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=your_pol, NB_ORA_SERV=your_server)"; allocate channel t2 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=your_pol, NB_ORA_SERV=your_server)"; backup (database format 'bk_%s_%p_%t'); }
Environment variables set by a user in the XML export parameter file

You can set the NetBackup for Oracle variables that Table 4-8 shows in the XML export parameter file in the Oracle users environment. If you are using templates, use the template generation wizard to set these variables. Table 4-8 Environment variables that you can set Purpose
Specifies the name of NetBackup master server. Specifies the name of the Oracle client. Specifies the name of the policy to use for the Oracle backup. Specifies the name of the Application Backup schedule to use for the Oracle backup.
Environment variable
NB_ORA_SERV NB_ORA_CLIENT NB_ORA_POLICY NB_ORA_SCHED
For more information, see Creating XML export templates using the NetBackup for Oracle wizard on page 101.
Environment variables set by NetBackup for Oracle

When a schedule runs, NetBackup sets environment variables for templates and shell scripts to use when performing a NetBackup operation. These variables can be used to perform conditional operations. These variables are set only if the backup is started from the server, either automatically by the NetBackup
93
scheduler or manually through the administrator interface. Table 4-9 shows the variables. Table 4-9 Variables that NetBackup for Oracle sets Purpose
Name of the NetBackup Server. Name of the Oracle policy. Name of the NetBackup client that hosts the Oracle database. Set to 1 for Automatic Full Backups. Set to 1 for Automatic Differential Incremental Backups. Set to 1 for Automatic Cumulative Incremental Backups.
NB_ORA_SERV NB_ORA_POLICY NB_ORA_CLIENT NB_ORA_FULL NB_ORA_INCR NB_ORA_CINC
Creating a bp.conf file

A NetBackup for Oracle user can create an Oracle client bp.conf file in the Oracle users home directory on the NetBackup for Oracle client host. When a NetBackup for Oracle operation is started, the users bp.conf file is searched before the master configuration file (/usr/openv/netbackup/bp.conf) on the client. Any option found at the user level overrides the same options setting at the master level. Table 4-10 shows the options you can set in the users bp.conf file. Table 4-10 Option
BPBACKUP_POLICY
Options for the user bp.conf file Purpose

This option specifies the name of the policy to use for the Oracle backup. This option specifies the name of the Application Backup type of schedule to use for the Oracle backup. This option specifies the name of the Oracle client. It is especially useful for a redirected restore operation. Use this option to increase the number of seconds that the Oracle client initially waits for a response from the NetBackup server. The default is the greater of 900 or CLIENT_READ_TIMEOUT. This option specifies the name of the NetBackup master server.
BPBACKUP_SCHED
CLIENT_NAME
CLIENT_READ_TIMEOUT
SERVER
94 Configuration Creating templates and shell scripts
Table 4-10 Option

VERBOSE
Options for the user bp.conf file (continued) Purpose

This option causes NetBackup to include more information in its logs.
For more information, see the NetBackup System Administrators Guide, Volume I. The following shows example bp.conf entries for an Oracle user:
SERVER=jupiter CLIENT_READ_TIMEOUT=900 VERBOSE=1
Creating templates and shell scripts

RMAN templates and scripts contain commands that run NetBackup RMAN backup and recovery jobs. XML export and import templates and shell scripts contain commands that run NetBackup XML export backup and XML import restore jobs. Templates and scripts must be created before NetBackup can perform scheduled backups. These are the template files or shell scripts that are specified in policy configuration on the NetBackup server.
Recovery Manager (RMAN)

Then following sections describe the RMAN templates and shell scripts.
RMAN templates and shell scripts

The templates and scripts are as follows:
Templates. The NetBackup for Oracle backup wizard creates backup templates. You can launch this wizard from the NetBackup Backup, Archive, and Restore interface. For more information, see Creating RMAN templates using the NetBackup for Oracle RMAN template generation wizard on page 95. The NetBackup for Oracle backup wizard does not support all of the RMAN commands and options provided by Oracle. Write a shell script if a template does not provide all the functionality you require. Shell scripts. Shell scripts are written by the user and must conform to RMAN and operating system shell syntax. Sample backup and recovery shell scripts are installed on the client with the NetBackup for Oracle agent. Modify these scripts to meet your individual requirements.
Configuration Creating templates and shell scripts
95
For more information on sample scripts, see Creating RMAN scripts manually on page 98. NetBackup for Oracle also provides a utility, bpdbsbora, that can generate a shell script from a backup wizard template. This allows a user to create a template with the wizard and generate a shell script from the template. The user can then run the shell script or modify the shell script further. For more information, see Creating an RMAN script from a template on page 97.
Creating RMAN templates using the NetBackup for Oracle RMAN template generation wizard
The NetBackup for Oracle backup wizard stores information about desired RMAN backup operations. The wizard uses the information to create a template that you can run immediately or you can save in a NetBackup location on the master server for later use. For information on backup strategies and RMAN functionality, see your Oracle documentation. To launch the NetBackup backup, archive, and restore interface
Use the procedure called To log into the client and invoke the backup wizard on page 33 to bring up the NetBackup Backup, Archive, and Restore interface.
To use the backup wizard 1 In the Backup, Archive, and Restore interface, expand an Oracle instance and select the database object(s) (data files, tablespaces, archived redo logs)
to back up. Selecting the Oracle instance backs up the whole database using RMAN.
Click Backup. The NetBackup for Oracle RMAN template generation wizard displays the following screens for you to enter information about the backup operation you want to perform:

Welcome Target Database Logon Credentials Recovery Catalog Logon Credentials Archived Redo Logs Configuration Options Backup Options Database State NetBackup Configuration Variables
Backup Limits If you need an explanation of any of the fields on the wizard screens, or more details, click Help on the wizard screen.
97
After you complete the wizard, the Template Summary screen displays the summary of the backup template:
You can choose to run the template immediately after the wizard finishes, save the template to the master server, or both. For explanations of your choices, click Help. To save, run, or save and run the template, click Finish.
Creating an RMAN script from a template

You can use the bpdbsbora command to create a script from a backup template. This command generates RMAN shell scripts from templates created by the backup wizard. At the command prompt, type this command in the following format:
bpdbsbora -backup -g script_file -t templ_name -S server_name
where:
-backup -g script_file Specifies the template type. Specifies the name of the file to which you want bpdbsbora to write the script. Enclose script_file in quotation marks if it contains blanks. This option cannot be used with the -r (run) option. Specifies the name of the template that you want to use as the basis for the script. Make sure the template exists. bpdbsbora retrieves backup templates from a known location on the master server, so specify only the template file name.
-t templ_name
-S server_name
Specifies the master server upon which the template resides. When specified, the bpdbsbora command retrieves backup templates from the specified master server.
Creating RMAN scripts manually

RMAN supports the following different types of backups:

Full Backup Level 0 Backup (Level 0 Incremental) Level n Backup (Differential Incremental Backup) Level n Backup (Cumulative Incremental Backup)
When generating a data file backup set, you can make either an incremental backup or a full backup. An incremental backup is a backup of one or more data files that contain only those blocks that have been modified since a previous backup. A full backup is a non-incremental backup of one or more data files that contain all blocks of the data files. When NetBackup for Oracle was installed, the installation software wrote example scripts to the following directory:
install_path/netbackup/ext/db_ext/oracle/samples/rman
The Oracle example scripts installed are as follows:

pit_database_restore.sh hot_tablespace_backup.sh hot_database_backup.sh database_restore.sh cold_duplex_database_backup_full.sh cold_database_backup.sh
To use sample scripts provided by NetBackup for Oracle 1 2 3 Copy the example scripts to a different directory on your client. Oracle scripts can be located anywhere on the client. Modify each script for your environment. Make sure the su command logs into the correct user. If you do not include an su - user (user is Oracle administrator account) in your Oracle scripts, they do not run with the proper permissions and
99
environment variables. This creates problems with your database backups and restores. Table 4-11 explains some of the sample scripts provided with NetBackup for Oracle. Table 4-11 Script
cold_database_backup.sh
NetBackup for Oracle sample scripts Purpose

This script sets the environment and calls RMAN with the appropriate commands to perform a whole database backup. It is used for both full backups and incremental backups. When a schedule runs, NetBackup sets environment variables that the script uses to perform a backup. This script sets up the environment and calls RMAN with the appropriate commands to perform a whole database backup. It is used for both full backups and incremental backups. When a schedule runs, NetBackup sets environment variables that the script uses to perform the backup. With the proper schedules, you can use this script to run a backup every week on Friday night and an incremental backup each night for the rest of the week automatically. This script sets up the environment and calls RMAN to run commands that make two copies of a cold (consistent) database backup.
hot_database_backup.sh
cold_duplex_database_backup_full.sh
Oracle8i and later versions of RMAN provide an API that allows you to make up to four backup sets simultaneously, each an exact duplicate of the others. Using NetBackup, for example, you can back up each copy to a different tape to protect against disaster, media damage, or human error. Use the set duplex and the send commands to take advantage of this feature. The set duplex command specifies the number of copies of each backup piece to create. The set duplex command affects all channels allocated after issuing the command, and it remains in effect until explicitly disabled or changed
during the session. You cannot issue the set duplex command after allocating a channel. The command syntax is:
set duplex = {ON | OFF | 1 | 2 | 3 | 4}
By default, duplex is OFF (a single backup set is produced). If you specify ON, it produces two identical backup sets. Observe the following with regard to file names:
Each output file must have a unique name. Use the %U format specifier to satisfy this restriction. %U is equivalent to %u_%p_%c, and it guarantees the uniqueness of the backup set name in all circumstances. Put %t at the end of the backup file name format. NetBackup uses the timestamp as part of its search criteria for catalog images. Without this timestamp, performance might degrade as the NetBackup catalog grows.
Note that you must enable the BACKUP_TAPE_IO_SLAVES initialization parameter to perform duplexed backups. RMAN configures as much media as needed for the number of backup copies you request. For more information on BACKUP_TAPE_IO_SLAVES, see your Oracle documentation. Use the send command to specify the policy and/or schedule to use with each backup. Because NetBackup uses the policy or schedule to determine what media to use, this information is required for each copy, or an error occurs. The command syntax is as follows:
send 'keyword=value [, keyword=value,...]';
The keywords used to specify a policy are CPF1_POLICY, CPF2_POLICY, CPF3_POLICY, and CPF4_POLICY, which specify the backup policy for duplexed file 1 through duplexed file 4. The keywords used to specify a schedule are CPF1_SCHED, CPF2_SCHED, CPF3_SCHED, and CPF4_SCHED, which specify the Application Backup schedule for duplexed file 1 through duplexed file 4.
XML export archive

The following sections describe XML export templates and shell scripts.
XML export templates and shell scripts

The templates and scripts are as follows:
Templates. The NetBackup for Oracle XML export wizard creates XML export templates. This wizard is initiated from the NetBackup Backup, Archive, and Restore interface.
101
The NetBackup for Oracle XML export wizard does not support all of the parameters provided by the command line utility, bporaexp. You can write a shell script if a template does not provide all of the required functionality.
Shell scripts. Shell scripts are written by the user and must conform to the operating systems shell syntax. Sample XML export and import shell scripts are installed on the client with the NetBackup for Oracle agent. Modify these scripts to meet your individual requirements. NetBackup for Oracle also provides a utility, bpdbsbora, that can generate a shell script from an XML export or import wizard template. This allows a user to create a template with the wizard and generate a shell script from it. The user can run or modify the shell script.
Creating XML export templates using the NetBackup for Oracle wizard
NetBackup for Oracle provides a wizard that solicits information about desired XML export operations. The wizard uses the information to create a template that can be run immediately or saved in a NetBackup specific location on the current master server for later use. To launch the NetBackup backup, archive, and restore interface
Use the procedure called To log into the client and invoke the backup wizard on page 33 to bring up the NetBackup Backup, Archive, and Restore interface.
To use the XML export wizard 1 In the left pane of the Backup, Archive, and Restore interface, select the Oracle instance. Database objects that can be exported are listed under the Users node. Only the schema owners and objects accessible by the current user login displays. Expand the Users list to the schema owners of the objects to be exported. In the right pane, select the Oracle objects to export. Figure 4-1 shows this.
2 3
Figure 4-1
View showing objects to export
Click Backup to start the wizard. The NetBackup for Oracle XML export wizard displays the following screens for you to enter information about the export operation you want to perform:

Welcome Target Database Logon Credentials Configuration Options Archive Export Options
NetBackup Archive Destination Options If you need an explanation of any of the fields on the wizard screens, or more details, click Help on the wizard screen. 5 When you have completed the wizard, the Template Summary screen displays the summary of the XML export template. Figure 4-2 shows this.
103
Figure 4-2
Template summary
You can choose to run the template immediately after the wizard finishes, save the template to the master server, or both. For explanations of your choices, click Help. To save, run, or save and run the template, click Finish.
Creating an XML export script from a template

You can use the bpdbsbora command to create a script from an XML export template. This command generates XML export shell scripts from templates created by the XML export wizard. At the command prompt, type this command using the following options: bpdbsbora -export -g script_file -t templ_name -S server_name where:
-export -g script_file Specifies the template type. Specifies the name of the file to which you want bpdbsbora to write the script. Enclose script_file in quotation marks if it contains blanks. This option cannot be used with the -r (run) option.
-t templ_name
Specifies the name of the template that you want to use as the basis for the script. Make sure the template exists. bpdbsbora retrieves XML export templates from a known location on the master server, so specify only the template file name. Specifies the master server upon which the template resides. When specified, the bpdbsbora command retrieves XML export templates from the specified master server.
-S server_name
Creating XML export scripts manually

When the database agent was initially installed, the installation software wrote example scripts to the following locations:
For export:
/usr/openv/netbackup/ext/db_ext/oracle/samples/bporaexp
For import:
/usr/openv/netbackup/ext/db_ext/oracle/samples/bporaimp
The example export scripts installed in bporaexp are as follows:

data_archiver_export.sh data_archiver_export64.sh bporaexp_help.param bporaexp_partitions.param bporaexp_table_to_files.param bporaexp_tables.param bporaexp_tables_rows.param
The example import scripts installed in bporaimp are as follows:

data_archiver_import.sh data_archiver_import64.sh bporaimp_archive.param bporaimp_archive_schema_to_files.param bporaimp_archive_to_users.param bporaimp_bfile_table.param bporaimp_help.param bporaimp_ignore_rows_table.param bporaimp_large_table.param
105
bporaimp_list.param bporaimp_old_archive.param bporaimp_partitions.pram bporaimp_table_from_files.param bporaimp_table_to_files.param bporaimp_table_to_user.param bporaimp_tables.param
To use the example scripts 1 2 3 Copy the example scripts to a different directory on your client. Oracle scripts can be located anywhere on the client. Modify each script for your environment. Make sure the su command logs into the correct user. If you do not include an su - user (user is Oracle administrator account) in your Oracle scripts, they do not run with the proper permissions and environment variables. The result is problems with your database backups and restores.
Storing templates and shell scripts

The following sections describe how to store templates and scripts.
Templates
The NetBackup for Oracle backup and XML export wizards save a template to a NetBackup specific location on the current NetBackup master server. A backup or XML export template is retrieved from the master server as part of a backup (server-directed, scheduled, or user-directed) and is run on the client. Backup or XML export templates are associated with a policy by specifying its name in the policy backup Selections list. Because backup or XML export templates are stored on the server in a known location, server-directed and scheduled backups or XML exports use the same copy of the template for each client in the policy client list. Before running a template on a NetBackup for Oracle client, NetBackup verifies the validity of the template for that client by checking the Oracle installation information stored in that template. Only valid templates are run on each client.
106 Configuration Testing configuration settings
The NetBackup for Oracle recovery and XML import wizards save a template to a user-specified location on the client. The location specified should include a fully qualified path to a directory where the user has write access. Templates store encrypted passwords that are decrypted at runtime.
Shell scripts
Shell scripts must reside on the NetBackup client. Backup or XML export shell scripts are associated with a policy by specifying the file name (including path) in the policy backup selections list. This means that for server-directed or scheduled backups or XML exports, each client in the policy's client list must have a copy of the script with the same name in the same location. For more information, see Adding backup selections on page 87. The backup and recovery processes sometimes require passwords for Oracle database access and/or system user accounts. Shell scripts, because a shell interprets them, store passwords in clear text.
Testing configuration settings

After you configure the master server for NetBackup for Oracle, test the configuration settings. Perform a manual backup (or backups) with the automatic backup schedules you created. For a description of status codes and other troubleshooting information, see the NetBackup Troubleshooting Guide. To test the configuration settings 1 2 3 Log onto the master server as administrator (Windows) or root (UNIX). Start the NetBackup administration console. In the left pane, click Policies. From the Windows interface: The policy list appears in the right pane. From the Java interface: The right pane splits into an All Policies pane and a details pane. Click the policy you want to test. Choose Actions > Manual Backup. The Schedules pane contains the name of an automatic schedule (or schedules) configured for the policy that you want to test. The Clients pane contains the name of the client(s) listed in the policy that you want to test. Follow the directions in the Manual Backup dialog box. Click Activity Monitor on the NetBackup administration console.
4 5
6 7
Configuration Testing configuration settings
107
When the Activity Monitor indicates job completion, check the output of the script(s) indicated in the policy you tested. The script shows the location to which the output is written. It is usually in the same directory as the original script, and it is similarly named. The Activity Monitor and the script output indicates the status of the backup operation. If the manual backup does not exit with a successful status, see Troubleshooting on page 179.
108 Configuration Testing configuration settings
Chapterf
Using NetBackup for Oracle


Maintaining the RMAN repository on page 109 Querying the RMAN repository on page 112 Performing a backup on page 113 Browsing backups on page 116 Performing a restore on page 117 Performing other RMAN actions on page 126 Performing an XML export archive on page 126 Browsing XML export archives on page 133 Restoring an XML export archive on page 135
The NetBackup graphical user interfaces and command line interfaces allow you to perform Oracle backup and recovery operations using Oracles RMAN utilities and to perform Oracle archives and restores using NetBackups XML export (bporaexp) and import (bporaimp) utilities. You can also use the Oracle Enterprise Manager to perform Oracle backup and recovery operations. The Oracle RMAN command line interface is also used to maintain and query the RMAN repository.
Maintaining the RMAN repository

The RMAN repository is the collection of metadata about your target databases that RMAN uses to conduct its backup, recovery, and maintenance operations. You can either create a recovery catalog in which to store this information or let RMAN store it exclusively in the target database control file. Although RMAN
110 Using NetBackup for Oracle Maintaining the RMAN repository
can conduct all major backup and recovery operations using just the control file, some RMAN commands function only when you use a recovery catalog. Table 5-1 shows tasks and the commands needed to accomplish the tasks. It shows a subset of the repository maintenance commands provided by RMAN. Some of these commands might not be available with all versions of RMAN. Table 5-1 Task
Registering a database with the recovery catalog
Tasks and commands Commands used to accomplish the task

Before using RMAN with a recovery catalog, register the target database in the recovery catalog. To do this, start and mount the target database but do not open it. At the RMAN prompt, issue a register database command. The reset database command directs RMAN to create a new database incarnation record in the recovery catalog. Because NetBackup can mark backup images as expired, the RMAN repository can contain outdated information. To ensure that data in the recovery catalog or control file is in sync with data in the backup image catalog, perform a cross check. Use the cross check feature to accomplish the following:

Resetting the incarnation in the recovery catalog Cross checking the information in the RMAN repository
Determine whether a backup set is available or expired. Delete any expired backup sets. Call Media Manager about the status of a backup piece and then mark it as available or expired.
Use either the change ... crosscheck or crosscheck backup command to check the specified files. Note that these commands do not delete images or repository records. You must use separate commands for these operations. The change ... crosscheck command queries Media Manager to determine if a backup piece is available. If a backup piece is unavailable, RMAN marks the backup piece as expired. If it was expired but is now available, RMAN marks the backup piece as available. The command syntax is as follows: change backuppiece {primary_key_list|filename_list|tag} crosscheck; change backupset {primary_key_list} crosscheck; The crosscheck backupset command operates on available and expired backup pieces. RMAN updates their status with the result (available or expired). To cross-check a database, start RMAN and connect to the target database. Also connect to the recovery catalog if one is being used. At the rman command prompt, type the following commands: allocate channel for maintenance type 'SBT_TAPE'; crosscheck backupset of database;
Using NetBackup for Oracle Maintaining the RMAN repository
111
Table 5-1 Task
Tasks and commands (continued) Commands used to accomplish the task

The delete expired backup command operates only on expired backup pieces found in the recovery catalog. RMAN removes them from the recovery catalog. To delete expired backup sets of a database from the recovery catalog, start RMAN and connect to the target and recovery catalog databases. At the RMAN command prompt, type the following commands: allocate channel for maintenance type 'SBT_TAPE'; delete expired backupset of database; The crosscheck and delete backupset commands let you restrict the list of objects operated on to the specified Oracle device type (disk or SBT tape), object type (archived logs or database files), and date range.
Deleting expired backups
Resynchronizing the recovery RMAN compares the recovery catalog to either the current control file of the target catalog database or a backup control file. It subsequently updates the catalog with information that is missing or changed. If you are running in ARCHIVELOG mode, resynchronize the recovery catalog regularly since the recovery catalog is not updated automatically when a log switch occurs or when a redo log is archived. You must also resynchronize the recovery catalog after making any change to the physical structure of the target database. As with log archive operations, the recovery catalog is not automatically updated when a physical schema change is made. The RMAN backup, copy, restore, and switch commands update the recovery catalog automatically when the target database control file is available, and the recovery catalog database is available when any of these commands are executed. If the recovery catalog is unavailable when you issue backup or copy commands, you should resynchronize it manually. To resynchronize the recovery catalog, start RMAN and issue the resync catalog command.
112 Using NetBackup for Oracle Querying the RMAN repository
Table 5-1 Task
Tasks and commands (continued) Commands used to accomplish the task

Periodically, you might need to notify RMAN that the status of a backup set, backup piece, data file copy, or archived redo log has changed. The RMAN change command enables you to make a variety of useful record changes. The change ... uncatalog command removes references to a backup piece, data file copy, or archive log from the recovery catalog. This command works only with a recovery catalog. The change ... delete command removes references to a backup piece, data file copy, or archive log from the control file and recovery catalog. It physically deletes the file. This command works with or without a recovery catalog. The change ... crosscheck command removes references to a backup piece, data file copy, or archive log from the control file and recovery catalog when that file no longer exists. This command works with or without a recovery catalog. The change ... unavailable command marks a backup piece, data file copy, or archive log as unavailable. This command works only with a recovery catalog.
Changing the availability of a backup set or file copy
Validating the restore of backups
A restore validation executes a restore test run without restoring the files. Test the restore of the entire database or individual tablespaces, data files, or control files. Use restore ... validate when you want RMAN to choose the backups to test. Use validate backupset when you want to specify the backup sets to test.
Querying the RMAN repository

RMAN lets you generate a number of reports relevant for backup and recovery using the report and list commands. The list command lists the contents of the recovery catalog or control file, and the report command performs a more detailed analysis. Use the report and list commands to determine what you have backed up and what you need to back up. The information is available whether or not you use a recovery catalog. You can use the report command to answer questions such as the following:

Which files need a backup? Which files have not had been backed up in awhile? Which files are not recoverable due to unrecoverable operations? Which backup files can be deleted?
Using NetBackup for Oracle Performing a backup
113
What was the physical schema of the database at some previous point in time?
The list command queries the recovery catalog and control file and produces a listing of its contents. The primary purpose of the list command is to determine the backups that are available. You can list the following information:

Backup sets containing a backup of a specified list of data files. Backup sets containing a backup of any data file that is a member of a specified list of tablespaces. All backup sets or copies of all data files in the database. Backup sets containing a backup of any archive logs with a specified name and/or within a specified range. Incarnations of a specified database or of all databases known to the recovery catalog.
For more information on querying the RMAN repository, see your Oracle documentation.
Performing a backup
This section describes how to perform several different types of backups.
Automatic backups
The most convenient way to back up your database is to set up schedules for automatic backups. When the NetBackup scheduler invokes a schedule for an automatic backup, the NetBackup for Oracle backup templates or shell scripts run as follows:

In the same order as they appear in the file list On all clients in the client list
The NetBackup for Oracle backup templates or shell scripts start the database backup by running the rman command. When the backup is started through NetBackup, RMAN performs error checking. The rman command generates an error if it considers a command invalid, but it allows any of the commands it typically considers valid to proceed. This means that by specifying the wrong script file name, you could start an unintended operation.
114 Using NetBackup for Oracle Performing a backup
Manual backups
The administrator can use the NetBackup server software to manually run an automatic backup schedule for the Oracle policy. For more information, see the NetBackup Administrators Guide, Volume I. For information on initiate a manual backup of an Oracle policy, see Testing configuration settings on page 106.
Performing a user-directed backup from the client

This section describes how to perform several types of user-directed backups.
Running NetBackup for Oracle templates

The Oracle template administration interface is available in the NetBackup Backup, Archive, and Restore interface. Use this dialog to run, edit, delete, rename, and view existing backup templates. These are the templates created by the NetBackup for Oracle RMAN template generation wizard and stored in a predetermined location on the master server. For more information, see Creating RMAN templates using the NetBackup for Oracle RMAN template generation wizard on page 95. To use Oracle template administration 1 In the Backup, Archive, and Restore interface, choose Actions > Administer Database Templates > Oracle.
The Select Template list shows the names and descriptions of the RMAN backup templates stored on the current master server. 2 Select the name of the backup template you want to run.
Using NetBackup for Oracle Performing a backup
115
Click Run. You can use the View Status tool to see the status of the backup. Click Actions > View Status.
The Oracle template administration window provides the following functions: Function name
Run Edit
Purpose
Runs the selected template. Changes the contents of an existing template. The selected backup template is loaded into the NetBackup for Oracle RMAN template generation wizard. Removes the selected template. You must be the root user or the template creator to delete a template. Changes the name of the selected template. You must be the root user or the template creator to rename a template. Displays a summary of the selected template.
Delete
Rename
View
Using bpdbsbora to run a backup template

The bpdbsbora command lets you run a backup template created by the NetBackup for Oracle RMAN template generation wizard. At the command prompt, type this command using the following options:
bpdbsbora -backup -r -t templ_name [-S server_name] [-L prog_file]
where:
-backup -r -t templ_name Specifies the template type. Runs the template. Specifies the name of the template that you want to use. bpdbsbora retrieves backup templates from a known location on the master server, so specify only the template file name. Optional. Specifies the master server upon which the templates reside. When specified, the bpdbsbora command retrieves backup templates from the specified master server. Optional. Specifies a runtime progress log. Enclose prog_file in quotation marks ( ) if it contains space characters.
-S server_name
-L prog_file
For example:
bpdbsbora -backup -r -t ORCLMonfull.tpl -S my_mast -L my_prog_log
116 Using NetBackup for Oracle Browsing backups
Running the NetBackup for Oracle shell script

When you run a NetBackup for Oracle shell script on a client to initiate a backup from the operating systems command prompt, specify the full path name to the file that contains the script. For example:
/oracle/scripts/db_full_backup.sh
The shell starts the database backup by running the Oracle shell script. The Oracle shell script contains commands to run rman. The NetBackup installation script installs sample scripts in the following location:
/usr/openv/netbackup/ext/db_ext/oracle/samples/rman
Running RMAN
As an Oracle user, you can run the rman command from the operating systems command prompt with the RMAN command file as a parameter. This section describes how to set the master server to hag and the Oracle policy to obk before starting the backup. If you are connecting to a database using a TNS alias, use the RMAN send command to specify the environment variables. At the command prompt, type the following:
rman target internal/oracle@ORCL rcvcat rman/rman@RCAT send "NB_ORA_POLICY=obk,NB_ORA_SERV=hag" cmdfile /oracle/scripts/db_full_backup.rcv
For more information, see Creating a bp.conf file on page 93.
Browsing backups
This section describes procedures for browsing backup images.
Using the RMAN repository to browse backups

You can use the RMAN report and list commands to browse Oracle backups. See Maintaining the RMAN repository on page 109.
Using bplist to browse backups

You can use the bplist command to browse Oracle backups. The command returns a list of backup file names. Before using the bplist command, log into either the master server or to the client as follows:

Log in as root to the master server Log in as root to the client with the appropriate altnames entry.
Using NetBackup for Oracle Performing a restore
117
The following example uses bplist to search all Oracle backups for a client named jupiter:
/usr/openv/netbackup/bin/bplist -C jupiter -t 4 -R / /exb_n2bm5bco_1_1392342936 /exb_mabm02ko_1_1392170136 /exb_lqbltds6_1_1392083334
The -t 4 on this command specifies the Oracle backups. The -R specifies the default number (999) of directory levels to search. For more information on this command, see the bplist(1M) man page.
Performing a restore
Make sure a backup has completed successfully before you attempt a restore. An error occurs if a backup history does not exist. The following sections describe how to perform user-directed restores.
Running the NetBackup for Oracle recovery wizard on the client

NetBackup for Oracle includes a recovery wizard that solicits information from the user about the desired RMAN restore and recovery operations. The wizard uses the information to create a template.
Limitations
The recovery wizard has several limitations:
The database is displayed only in its current state. If objects have been deleted from the database since the last backup, these objects do not appear among the objects you can select for restore. In order to restore the objects that have been deleted, you need to restore the entire database point in time before the objects were deleted. Data is restored to the original location. The wizard does not provide a way for the user to specify alternate file names. The wizard does not restore control files.
How the recovery wizard works

The recovery wizard saves a recovery template locally in a user-specified location on the NetBackup client. Recovery templates are not stored on the master server because recovery is always user directed, not scheduled. Typically, you run the recovery template immediately and then delete it.
118 Using NetBackup for Oracle Performing a restore
The recovery process sometimes requires passwords for Oracle database access and system user accounts. Templates store the encrypted passwords that are decrypted at runtime. Because recovery can be a complex process, it might be necessary to perform manual steps as part of the operation. For more information, see your Oracle documentation. The restore browser is used to display database objects. A hierarchical display is provided where objects can be selected for recovery. The top database node expands to show all of the installed databases. The oratab file is read to get the names and location of each database. The objects (tablespaces and datafiles) that make up an Oracle database are displayed by expanding an individual database node. This information is gathered from various database tables and views. Since you must be connected to the database before you can access its tables or views, logon criteria must be provided. When a user selects or expands a database node the wizard first tries to logon to the database using OS authentication. If the authentication fails the user is solicited for a user name and password. Optionally, the user is prompted for the Net Service Name if the connection is through SQL-Net, which is then used to logon to the database. This user must have a sysdba privilege since the logon credentials that are also used to perform the RMAN restore. The logon fails if the database is not in a mount or open state. The GUI uses the bpubsora utility to access and query the database. If there is a problem when NetBackup attempts to connect or browse a database this utility can be run from the command line to debug the issue.
Starting the NetBackup Backup, Archive, and Restore interface

To start the NetBackup Backup, Archive, and Restore interface You start the NetBackup for Oracle recovery wizard from the Backup, Archive, and Restore interface. You can start the Backup, Archive, and Restore interface from the NetBackup administration console. Or you can start it from the command line.
To start the Backup, Archive, and Restore interface from the NetBackup administration console, do one of the following:
From the Java interface, click Backup, Archive, and Restore in the left pane of the console. From the Windows interface, click File > Backup, Archive, and Restore.
To start the Backup, Archive, and Restore interface from the command line, run the following command: /usr/openv/netbackup/bin/jbpSA &
119
Starting the recovery wizard

To start the recovery wizard 1 (Conditional) Change the policy type. Perform this step if the Oracle node is not visible. Your NetBackup for Oracle client may not have the appropriate policy type specified. Change the policy type with the following steps: a b c 2 3 On the Actions menu, select Specify NetBackup Machines and Policy Type for the restore. In the Specify NetBackup Machines and Policy Type dialog box, select Oracle from the Policy Type drop-down list. Click OK.
From the Restore Files tab, expand the Oracle node in the left pane to view an Oracle instance hierarchy. Select a node in the left pane to view details in the right pane.
Using the recovery wizard

When you are ready to perform a recovery, follow these steps to create and run a template with the recovery wizard. To use the recovery wizard 1 In the Backup, Archive, and Restore interface, choose the Restore Files tab. Ensure that the Restore Type drop down is set to Normal Backups (the default choice). Expand an Oracle instance. Select the database object(s) (data files, tablespaces) you want to recover. If you select the Oracle instance, the wizard recovers the entire database using RMAN. Figure 5-1 shows selections.
2 3
Figure 5-1
Object selections
Click Restore. Enter information about the recovery operation you want to perform in the screens that the NetBackup for Oracle recovery wizard displays. The screens are as follows:

Welcome Target Database Logon Credentials Recovery Catalog Logon Credentials Recovery Options Restore Options Recover Limits
Database State If you need an explanation of any of the fields on the wizard screens, click Help on the wizard screen. 5 Review the summary. When you have completed the wizard, the Selection Summary screen displays the summary of the recovery template. You can choose to run the template immediately after the wizard finishes or save the template locally, or both. If you need an explanation of any of the fields on the wizard panels, click Help on the wizard panel. Click Finish to run, save, or run and save the recovery template.
121
Using bpdbsbora
The bpdbsbora command lets you run a recovery template created by the NetBackup recovery wizard. At the command prompt, type this command and the following options:
bpdbsbora -restore -r -t templ_name [-L progress_file]
where:
-restore -r -t templ_name Specifies the template type. Runs the template. Specifies the full-path name of the template you want to use. Unlike backup templates, restore templates do not reside in a predetermined location on the master server. They are considered to be temporary in nature and should reside on the client. If the full path is not specified as part of the restore template name, the file might not be found. -L progress_file Optional. Specifies a run-time process log. Enclose progress_file in quotation marks ( ) if it contains space characters.
For example:
bpdbsbora -restore -r -t /oracle/restore_templs/ORCL_MON_Full.tpl
Running a NetBackup for Oracle recovery shell script on the client

You can initiate a database recovery from the operating system command prompt by typing the full path to the shell script that performs an Oracle recovery. For example: oracle/scripts/database_restore.sh The operating system shell starts the database restore by running the Oracle shell script file. The Oracle shell script file contains commands to run RMAN. The NetBackup installation script writes sample scripts to the following location: /usr/openv/netbackup/ext/db_ext/oracle/samples/rman
Running RMAN on the client

You can run the rman command from acommand line on the client. Use the appropriate RMAN command file as a parameter. The following example assumes that you are logged on as an Oracle administrator. To run the rman command on the client
At the command prompt, type the following:
rman target internal/oracle@ORCL rcvcat rman/rman@RCAT / cmdfile /oracle/scripts/database_restore.rcv
Redirecting a restore to a different client

With NetBackup for Oracle you have the option to restore a database to a client other than the one that originally performed the backup. The process of restoring data to another client is called a redirected restore. Figure 5-2 shows a redirected restore. Figure 5-2 Redirected restore
1. Cl ient A
gets back ed up
Server
.
2. Clien t B re q uests r client A esto image to clien re of t B.
t s clien restore r e . v B r t e s lien 3. The ge t o c up ima A back
The user on client A cannot initiate a redirected restore to client B. Only the user on client B, which is the client receiving the backup image, can initiate the redirected restore.
123
Note: For Oracle backups performed with NetBackup 6.0x or earlier, only the user who performed the backup can restore that backup. For any Oracle backup that is performed with NetBackup 6.5, any user who belongs to the database group that performed the backup can restore it. This ability will be added to future patches of NetBackup releases earlier than 6.5. The following sections describe how to perform a redirected restore using Oracle RMAN.
Server configuration
Ensure that the NetBackup server is configured to allow a redirected restore. The administrator can remove restrictions for all clients by creating the following file on the Netbackup master server: /usr/openv/netbackup/db/altnames/No.Restrictions Or, to restrict clients to restore only from certain other clients, create the following file: /usr/openv/netbackup/db/altnames/client_name Where client_name is the name of the client allowed to do the redirected restore (the destination client). Then, add the name of the NetBackup for DB2 source client to that file. For more information about redirected restores, see the NetBackup Administrators Guide, Volume I.
Using RMAN to perform a redirected restore

Note: For Oracle backups performed with NetBackup 6.0x or earlier, only the user who performed the backup can restore that backup. For any Oracle backup that is performed with NetBackup 6.5, any user who belongs to the database group that performed the backup can restore it. This ability will be added to future patches of NetBackup releases earlier than 6.5. Perform the following procedure on the destination client host if you want to restore any RMAN backups that another client owns.
To perform a redirected restore 1 Enable a network connection to the RMAN catalog database that the source client used.
Note: If the RMAN catalog database has been lost, restore the catalog database first before continuing with the redirected restore. 2 3 Set the NB_ORA_CLIENT environment variable to the source client. Check the bp.conf files on the source client. Make sure that the CLIENT_NAME variable either is not set or is set to the hostname of the source client. Make the init.ora file of the source client available to the destination client. Copy the file to the destination client or modify the file on the destination client. Change all location-specific parameters. Grant write permission to the directory to which you want to restore the data files. Set up a password file for the destination client database. Start up the database in the nomount state. Start RMAN, connecting to the catalog. Set dbid to be the DBID of the source client database.
5 6 7 8 9
10 Connect to the target database without using a userid and password. 11 Run an RMAN restore script or type the RMAN commands for the restore.
Example
For example, assume the following:

Source client is camel Destination client is giraffe Master server is lion ORACLE_SID is test The user is connected to the Oracle database using a local connection, not SQL*Net UNIX user is ora on both camel and giraffe
125
Create the following file on server lion and edit it to contain the name camel:
/usr/openv/netbackup/db/altnames/giraffe
2 3 4 5 6
Log in to giraffe as ora. Set SERVER=lion in $ORACLE_HOME/bp.conf. This server must be the first server that is listed in the bp.conf file. Modify the network tnsnames.ora file to enable RMAN catalog connection. Set the environment variables ORACLE_SID to test and NB_ORA_CLIENT to camel. Make sure the destination database directory exists and has appropriate access permissions. The data files are restored to the directory path with the same name they had when they were backed up. Create an inittest.ora file. Start up the database in a nomount state.
SVRMGR> startup nomount pfile=$ORACLE_HOME/dbs/inittest.ora %rman rcvcat rman/rman@rcat RMAN> set dbid=<dbid of source database on camel RMAN> connect target/ RMAN> run { RMAN> ALLOCATE CHANNEL CH00 TYPE 'SBT_TAPE'; RMAN> SEND 'NB_ORA_SERV=lion, NB_ORA_CLIENT=camel'; RMAN> restore controlfile; RMAN> } SVRMGR> alter database mount; %orapwd file=$ORACLE_HOME/dbs/orapwtest password=<oracle> %rman rcvcat rman/rman@RCVCAT RMAN>set dbid=<Saved dbID of Source Target> RMAN>connect target/ RMAN>run { RMAN> ALLOCATE CHANNEL CH00 TYPE 'SBT_TAPE'; RMAN> ALLOCATE CHANNEL CH01 TYPE 'SBT_TAPE'; RMAN> SEND 'NB_ORA_SERV=lion, NB_ORA_CLIENT=camel'; RMAN> restore database; RMAN> restore archivelog all; RMAN> } SVRGMR>recover database until cancel using backup controlfile;
7 8
Now apply the archived logs. Type cancel when you decide to stop recovery.
126 Using NetBackup for Oracle Performing other RMAN actions
Performing other RMAN actions

To run script files for database operations other than backups or restores, Symantec recommends that you run the rman command directly rather than using NetBackup. For rman command script syntax and examples, see your Oracle documentation.
Performing an XML export archive

The following sections describe how to perform an XML export archive.
Automatic backup of an Oracle policy

As with Oracle backups using RMAN, the most convenient way to create Oracle archives that consist of XML exports of data from your database is to set up schedules for automatic backups. The Oracle policy runs NetBackup for Oracle templates or shell scripts. For a backup using RMAN, a backup template is used, and for an XML export, an XML export template is used. When the NetBackup scheduler invokes a schedule for an automatic backup, the NetBackup for Oracle XML export templates or shell scripts run as follows:

In the same order as they appear in the file list On all clients in the client list
The NetBackup for Oracle XML export template or shell scripts start the XML export by running NetBackups bporaexp utility.
Manual backup of an Oracle policy

The administrator can use the NetBackup server software to manually run an automatic backup schedule for the Oracle policy. For more information, see the NetBackup Administrators Guide, Volume I. For information on initiating a manual backup of an Oracle policy, see Testing configuration settings on page 106.
User-directed XML exports from the client

The following sections describe procedures for performing user-directed XML exports.
Running NetBackup for Oracle XML export templates

The Template Administration interface is available in the NetBackup Backup, Archive, and Restore interface.
Using NetBackup for Oracle Performing an XML export archive
127
Use this dialog to run, edit, delete, rename, and view existing XML export templates. These are the templates created by the NetBackup for Oracle XML Export Wizard and stored in a predetermined location on the master server. To use Oracle template administration 1 In the Backup, Archive, and Restore interface, click Actions > Administer Database Templates > Oracle. The Oracle template administration window appears. The Select Template list shows the names, descriptions, and types of the Oracle templates stored on the current master server. Select the name of the XML export template you want to run. Click Run.
2 3
The Oracle template administration window provides the following functions: Function name
Run Edit
Purpose
Runs the selected template. Changes the contents of an existing template. The selected XML export template is loaded into the NetBackup for Oracle XML export template generation wizard. Removes the selected template. You must be the root user or the template creator to delete a template. Changes the name of the selected template. You must be the root user or the template creator to rename a template. Displays a summary of the selected template.
Delete
Rename
View
Using bpdbsbora to run an XML export template

The bpdbsbora command lets you run an XML export template created by the NetBackup for Oracle XML export wizard. At the command prompt, type this command using the following options:
bpdbsbora -export -r -t templ_name [-S server_name] [-L prog_log]
where:
-export -r -t templ_name Specifies the template type. Runs the template. Specifies the name of the template that you want to use. bpdbsbora retrieves XML export templates from a known location on the master server, so specify only the file name.
128 Using NetBackup for Oracle Performing an XML export archive
-S server_name
Optional. Identifies the master server. bpdbsbora retrieves XML export templates from a specific master server when you specify this option. Optional. Specifies a runtime process log. Enclose prog_log in quotation marks ( ) if it contains space characters.
-L prog_log
For example:
bpdbsbora -export -r -t sales_arch.tpl -S my_server -L my_progress_log
Running the NetBackup for Oracle XML export script on the client
You can initiate a database XML export from the operating system command prompt by typing the full path to the shell script that performs the export. For example:
/oracle/scripts/data_archiver_export.sh
The operating system shell starts the database XML export archive by running the XML export script. The XML export script contains commands to run bporaexp. The NetBackup for Oracle installation script installs sample scripts in the following location: /usr/openv/netbackup/ext/db_ext/oracle/samples/bporaexp/
Running bporaexp on the client as an Oracle user

As an Oracle user you can also run the bporaexp command from the operating system command prompt and specify a parameter file. Note: Be sure to configure the runtime environment as specified in Configuration on page 77 because this method does not call the full script that includes the runtime configuration. Check the sample scripts for runtime environment details. bporaexp creates a set of XML schema and instance documents that can be used to archive Oracle table data. For each archive, one master XML schema (.xsd) document is generated. In addition, for each table, bporaexp generates a table-specific schema (.xsd) document and a table specific instance (.xml) document. Additional files are created if the table contains LONG or LOB columns.
129
The bporaexp parameter file

Before you run the bporaexp command, create a parameter file. This parameter file lets you specify settings that determine how the backup is to be performed. The following example command shows how to specify the parameter file on the bporaexp command:
bporaexp [username/password] parfile = filename | help=y
Writing to a directory versus writing to a storage unit

One important aspect of the parameter file is the DIRECTORY parameter. If you specify the DIRECTORY parameter, the bporaexp command writes the backup files to the operating system directory you specify. NetBackup does not write the files to a storage unit. For example, the archive test1 contains one table, USER1. If the following parameter is specified, NetBackup creates the files shown in Table 5-2 when you run the bporaexp command: DIRECTORY=/db/netbackup/xml
Table 5-2 File
NetBackup files for example table USER1 Content

Master XML schema for table USER1
/db/netbackup/xml/test1/test1.xsd
/db/netbackup/xml/test1/USER1/TEST1.xsd Table schema for table USER1 /db/netbackup/xml/test1/USER1/TEST1.xml XML document for table USER1
If the DIRECTORY parameter is not specified, NetBackup writes the backup images to a storage unit. A NetBackup backup set is created and cataloged under the name /Oracle/XMLArchive. All NetBackup for Oracle bporaexp backups are cataloged using this convention. Alternatively, if the parameter file does not contain the DIRECTORY parameter, NetBackup creates and catalogs the following files:
/Oracle/XMLArchive/test1/test1.xsd /Oracle/XMLArchive/test1/USER1/TEST1.xsd /Oracle/XMLArchive/test1/USER1/TEST1.xml
In production, do not use the DIRECTORY parameter in the bporaexp parameter file. When you write to a storage unit, NetBackup offers features that include searching and cataloging with the NetBackup catalog and automatic handling of output that exceeds file system limits. With the DIRECTORY parameter, file system limits, such as a 2 GB maximum, can cause an error.
To run bporaexp on the client
At the command prompt, type:

bporaexp [username/password] parfile = filename | help=y
Note: On 64-bit platforms, the bporexp64 command is also available. Table 5-3 shows the available bporaexp parameters with their default values. Note: Use the NetBackup parameters NB_ORA_SERV, NB_ORA_CLIENT, NB_ORA_POLICY, and NB_ORA_SCHED to specify the NetBackup runtime configuration. Otherwise, the order of precedence for the runtime configuration variable settings is used. Some parameters are valid only when writing to a storage unit. Other parameters are valid only when writing to a directory. In the following table, the right-most column contains either Storage Unit or Directory to indicate whether the parameter in that row is applicable for either writing to a storage unit or to a directory. Parameters that are recognized when writing to a directory are ignored when writing to a storage unit. Table 5-3 Parameter
CONSISTENT
bporaexp parameters and default values Required?

N
Default
N
Description
Target location
Directory Specifies whether or not bporaexp uses the SET TRANSACTION READ ONLY statement to ensure that the data from all tables is consistent to a single point in time and does not change during the execution of the bporaexp command. If the default of CONSISTENT = N is used, each table is exported as an independent transaction. Optionally specifies a directory for the output of the bporaexp utility. Displays a help message with descriptions of bporaexp parameters. Does not export data if HELP=Y. Directory
DIRECTORY
no default
HELP
Directory
131
Table 5-3 Parameter

KEYWORD
bporaexp parameters and default values (continued) Required?

N
Default
no default
Description
Optionally specifies a keyword phrase that NetBackup associates with the image being created by the archive operation. Values for KEYWORD must be in double quotes.
Target location
Storage Unit
LOG
no default
Directory Optionally specifies a file name to receive informational and error messages. If this parameter is specified, messages are logged in the log file and not displayed to the terminal display. The name of the master XML schema file. Optionally specifies the name of the NetBackup master server. Directory
NAME
no default
NB_ORA_SERV
default master server
Storage Unit
NB_ORA_CLIENT
default client Optionally specifies the name of the NetBackup for Oracle client. default Optionally specifies the name of the Oracle policy NetBackup for Oracle policy. default backup policy schedule no default Optionally specifies the name of the backup policy schedule to use.
Storage Unit
NB_ORA_POLICY
Storage Unit
NB_ORA_SCHED
Storage Unit
OWNER
Lists the Oracle schema owners to export. For each owner, the tables, partitions, and views owned by that Oracle account are exported by default. The PARTITIONS and VIEWS parameters can be used to exclude partitions and views.
Directory
PARTITIONS
Optionally specifies whether or not Directory table partitions are included. Only valid when used with the OWNER parameter.
Table 5-3 Parameter

QUERY

N
Default
no default
Description
Target location
This parameter lets you select a subset Directory of rows from a set of tables. The value of the query parameter is a string that contains a WHERE clause for a SQL select statement that is applied to all tables and table partitions listed in the TABLES parameter. For example, if TABLES = emp, bonus and QUERY = where job = SALESMAN and sal < 1600, two SQL statements are run:
SELECT*FROM emp where job=SALESMAN and sal<1600; SELECT*FROM bonus where job=SALESMAN and sal<1600;
Note that each query that runs refers to a single table at a time in the FROM clause, so it is illegal to have a join in the WHERE clause. ROW_BUFFER N 1000 Specifies the size, in rows, of the buffer used to fetch rows. Tables with LONG columns are fetched one row at a time. The maximum value allowed is 32767. Lists the table names, view names, and partition names to export. The USERID must have SELECT privilege on the tables and views. The syntax used is: schema.table: partition name or schema.view name USERID Y no default Specifies the username/password (and Directory optional connect string) of the user initiating the export. If a connect string is not provided, the ORACLE_SID environment variable is used. Directory
TABLES
no default
Directory
Using NetBackup for Oracle Browsing XML export archives
133
Table 5-3 Parameter

VIEWS

N
Default
Y
Description
Optionally specifies whether or not views are included. Only valid when used with the OWNER parameter.
Target location
Directory
Browsing XML export archives

The following sections describe procedures for browsing XML export archive images created using bporaexp. Note: Only XML export archives created using NetBackup mode are searched. Exports stored in an operating system directory using the DIRECTORY parameter are not searched.
Using bporaimp parameters to browse XML export archives

To use the bporaimp command to browse XML export archives created using bporaexp, create a parameter file with the desired search criteria. First, set the variables LIST=Y and USERID=username/. Only the archives created using the Oracle USERID are listed. The Oracle password is not required. The operating system account that is running bporaimp has access only to archives that were created using the same account. Use the NB_ORA_SERV and NB_ORA_CLIENT parameters to specify the NetBackup server and client. Otherwise, the order of precedence for the runtime configuration variable settings is used. You can also include the LOG parameter. Information is available on the LIST, LOG, NB_ORA_CLIENT, NB_ORA_SERV, and USERID parameters. See To run bporaexp on the client on page 130. Table 5-4 shows other parameters you can include in the parameter file. Table 5-4 Parameter
ARCHIVE_DATE_FROM
Parameters you can include in a parameter file Default

no default
Description
Optionally specifies a start date for the archive search. Used with ARCHIVE_DATE_TO to specify a range. The date format is mm/dd/yyyy [hh:mm:ss].
134 Using NetBackup for Oracle Browsing XML export archives
Table 5-4 Parameter
Parameters you can include in a parameter file (continued) Default

no default
Description
Optionally specifies an end date for the archive search. Used with ARCHIVE_DATE_FROM to specify a range. The date format is mm/dd/yyyy [hh:mm:ss]. Optionally specifies a keyword phrase for NetBackup to use when searching for archives. The name of the master XML schema file. Optionally specifies a comma-separated list of table owners. Optionally specifies a list of table and partition names that were included in an archive.
ARCHIVE_DATE_TO
KEYWORD
no default
NAME FROMUSER TABLES
no default no default no default
For example, assume you named the list parameter file bporaimp_list.param. At the command prompt, type the following:
bporaimp parfile = bporaimp_list.param
Note: On 64-bit platforms, the bporaimp64 command is also available.
Using bplist to browse XML export archives

For a higher level view of the Oracle XML export archive list, you can use the bplist command. The result is the list of XML schema and instance document file names. The following example uses bplist to search all Oracle archives for a client named jupiter. The sample output is produced for two archives, test1 and little_sales, where each archive has one Oracle table (test1 has USER1.TEST1 and little_sales has USER1.LITTLE_SALES).
/usr/openv/netbackup/bin/bplist -C jupiter -t 4 -R /Oracle/XMLArchive/ /Oracle/XMLArchive/test1/test1.xsd /Oracle/XMLArchive/test1/USER1/TEST1.xsd /Oracle/XMLArchive/test1/USER1/TEST1.xml /Oracle/XMLArchive/little_sales/little_sales.xsd /Oracle/XMLArchive/little_sales/USER1/LITTLE_SALES.xsd /Oracle/XMLArchive/little_sales/USER1/LITTLE_SALES.xml /exb_n2bm5bco_1_1392342936 /exb_mabm02ko_1_1392170136 /exb_lqbltds6_1_1392083334
The -t 4 on this command specifies the Oracle backups or archives. The -R specifies the default number of directory levels to search, 999. For more information on this command, see the bplist(1M) man page.
Using NetBackup for Oracle Restoring an XML export archive
135
Restoring an XML export archive

Make sure an XML export archive has completed successfully before attempting a restore. Use the procedures for browsing XML export archives as described in the previous section to identify the correct archive to restore. NetBackup generates an error if an archive backup history does not exist. The following sections describe procedures for performing user-directed restores.
Running the XML import wizard on the client

NetBackup for Oracle includes an XML import wizard that solicits information from the user about the desired import operations. The wizard uses the information to create a template. You can use the template immediately, or you can save it for later use. The NetBackup for Oracle XML import wizard saves an XML import template locally in a user-specified location on the NetBackup client. XML import templates are not stored on the server because a restore is always user directed, not scheduled. Typically, you run an XML import template immediately and then delete it. The restore process requires a password for Oracle database access. Templates store encrypted passwords that are decrypted at runtime. To start the NetBackup Backup, Archive, and Restore interface You start the NetBackup for Oracle XML import wizard from the Backup, Archive, and Restore interface. You can start the Backup, Archive, and Restore interface from the NetBackup administration console. Or you can start it from the command line on the client.
To start the NetBackup Backup, Archive, and Restore interface from the NetBackup administration console, do one of the following:
From the Java interface, click Backup, Archive, and Restore in the left pane of the console. From the Windows interface, click File > Backup, Archive, and Restore.
To start the NetBackup Backup, Archive, and Restore interface from the command line, run the following command: /usr/openv/netbackup/bin/jbpSA &
To start the XML import wizard 1 (Conditional) Change the policy type. Perform this step if the Oracle node is not visible.
136 Using NetBackup for Oracle Restoring an XML export archive
It is possible that your NetBackup for Oracle client does not have the appropriate policy type specified. Change the policy type with the following steps: a b c 2 3 On the Actions menu, select Specify NetBackup Machines and Policy Type. In the Specify NetBackup Machines and Policy Type dialog box, in the Policy type drop-down list, select Oracle. Click OK.
Click the Restore Files tab. Expand the Oracle node in the left pane to view an Oracle instance hierarchy in the right pane.
To use the XML import wizard When you are ready to perform an import, follow these steps to create and run a template with the XML import wizard. 1 In the left pane of the Backup, Archive, and Restore interface, select the Oracle instance. Database objects that can be imported are listed under the Users node. The tool displays only the schema owners and objects accessible by the current user login. Expand the Users list to the schema owners of the objects to be imported. In the right pane, select database objects that exist in the archive to be restored. Click Restore. Enter information about the restore operation you want to perform in the screens that the NetBackup for Oracle XML import wizard displays. The screens are as follows:

2 3 4 5
Welcome Target Database Logon Credentials Archive Import Options
NetBackup Archive Source Options If you need an explanation of any of the fields on the wizard screens, or more details, click Help on the wizard screen. 6 Review the summary. When you have completed the wizard, the Selection Summary screen displays the summary of the XML import template.
137
You can choose to run the template immediately after the wizard finishes, save the template locally, or both. For explanations of your choices, click Help.
Using bpdbsbora
The bpdbsbora command allows you to run an XML import template created by the NetBackup XML import wizard. At the command prompt, type this command with the following options:
bpdbsbora -import -r -t template_name [-L progress_file]
where:
-import -r Specifies the template type. Runs the template.
-t template_name Specifies the full path name of the template you want to use. Unlike backup templates, XML import templates do not reside in a predetermined location on the master server. They are considered to be temporary in nature and should reside on the client. If the full path is not specified as part of the XML import template name, it must reside in the current directory. -L progress_file Optional. Specifies a run-time progress log. Enclose progress_file in quotation marks ( ) if it contains space characters.
For example:
bpdbsbora -import -r -t /oracle/imp_tpls/sales_imp.tpl -L prog_file
Running an XML import script on the client

You can initiate a restore from the operating system command prompt by typing the full path to the XML import script that initiates the restore. For example:
/oracle/scripts/data_archiver_import.sh
The operating system shell starts the database restore by running the XML import script file. The XML import script file contains commands to run bporaimp. The NetBackup for Oracle installation script writes sample scripts to the following location: /usr/openv/netbackup/ext/db_ext/oracle/samples/bporaimp/
Running bporaimp on the client

Run the bporaimp command from the operating system command line on the client using the appropriate parameter file. The UNIX account that is running bporaimp has access only to XML export archives that were created using the same UNIX account. Note: Be sure to configure the runtime environment as specified in Configuration on page 77 because this method does not call the full script that includes the runtime configuration. Check the sample scripts for runtime environment details.
To run bporaimp on the client
At the command prompt, type the bporaimp command in the following format:
bporaimp [username/password] parfile = filename | help=y
On 64-bit platforms, the bporaimp64 command is also available. Table 5-5 shows the available bporaimp parameters with their default values. Note: Use the NetBackup parameters NB_ORA_SERV and NB_ORA_CLIENT to specify the NetBackup runtime configuration. Otherwise, the order of precedence for the runtime configuration variable settings is used. Some parameters are valid only when writing to a storage unit. Other parameters are valid only when writing to a directory. In the following table, the right-most column contains either Storage Unit or Directory to indicate whether the parameter in that row is applicable for either writing to a storage unit or to a directory. Parameters that are recognized when writing to a directory are ignored when writing to a storage unit.
139
Table 5-5 Parameter
bporaimp parameters and default values Required?

N
Default
no default
Description
Optionally specifies a start date for the archive to be imported. Used with ARCHIVE_DATE_TO to specify a range. If not used, the most recent archive is imported. If the range used results in more than one archive, the most recent from the range is used. The date format is mm/dd/yyyy [hh:mm:ss].
Target location
Storage Unit
ARCHIVE_DATE_FROM
ARCHIVE_DATE_TO
no default
Storage Unit Optionally specifies an end date for the archive to be imported. Used with ARCHIVE_DATE_FROM to specify a range. If not used, the most recent archive is imported. If the range used results in more than one archive, the most recent from the range is used. The date format is mm/dd/yyyy [hh:mm:ss]. Specifies a directory for the Directory output of any BFILE columns being imported. Oracles CREATE DIRECTORY command can be used to create the DIRECTORY in Oracle, and the name should match the name used in the export file.
BFILE_DIRECTORY
Y (if any no default table being imported has BFILE columns)
Table 5-5 Parameter

COMMIT
bporaimp parameters and default values (continued) Required?

N
Default
N
Description
Target location
Directory Specifies whether bporaimp should commit after each array insert. The size of the array is determined by ROW_BUFFER. By default, bporaimp commits only after loading each table, and performs a rollback when an error occurs, before continuing with the next object. Optionally specifies a directory Directory for the input of the bporaimp utility. Optionally specifies a comma-separated list of users to import from an archive containing multiple users tables. If not specified, all of the tables are imported. Displays a help message with descriptions of bporaimp parameters. Directory
DIRECTORY
no default
FROMUSER
no default
HELP
Directory
141
Table 5-5 Parameter

IGNORE_ROWS

N
Default
N
Description
Specifies whether or not rows should be inserted into a table that is not empty. The default is that the table already exists and that it is empty. If it is not empty, IGNORE_ROWS = N causes an error to be reported, and the table is skipped with no rows inserted. IGNORE_ROWS = Y causes rows to be inserted with errors reported in the log file. If IGNORE_ROWS = Y and an error such as a primary key constraint violation occurs, no data is inserted if COMMIT = N. However, if COMMIT = Y, the array of rows (size determined by ROW_BUFFER) is not inserted, but bporaimp continues to process additional row arrays in the order in which they were exported. To cause all rows that do not violate a primary key constraint to be inserted, set COMMIT = Y, ROW_BUFFER = 1, and IGNORE_ROWS = Y.
Target location
Directory
KEYWORD
no default
Optionally specifies a keyword phrase for NetBackup to use when searching for archives from which to restore files. LIST = Y queries the NetBackup catalog and lists the archives available. Does not import the data if LIST = Y.
Storage Unit
LIST
Storage Unit
Table 5-5 Parameter

LOG

N
Default
no default
Description
Target location
Optionally specifies a file name Directory to receive informational and error messages. If this parameter is specified, messages are logged in the log file and not displayed to the terminal display. The name of the master XML schema file. This parameter is required if LIST = N. Optionally specifies the name of the NetBackup master server. Optionally specifies the name of the NetBackup for Oracle client. Used with RESTORE_TO_DIRECTORY to restore the XML schema files only to a directory. Directory
NAME
no default
NB_ORA_SERV
default master server default client
Storage Unit
NB_ORA_CLIENT
Storage Unit
RESTORE_SCHEMA_ONLY
Storage Unit
RESTORE_TO_DIRECTORY
no default
Optionally specifies a directory Storage Unit for the output of the bporaimp utility. If used, the XML data is not parsed and inserted into Oracle. Specifies the size, in rows, of the buffer used to insert rows. Tables with LONG or LOB columns are inserted one row at a time. The maximum value allowed is 32767. Directory
ROW_BUFFER
1000
143
Table 5-5 Parameter

TABLES

N
Default
no default
Description
Target location
Directory Optionally specifies a list of table, view, and partition names to import. If not used, all objects in the archive are imported. The objects must already exist, and the USERID must have INSERT privilege on the objects. The object names cannot be qualified with owner names, and the FROMUSER parameter is used to specify a particular owner. If a partition name is specified, it indicates the exported partition only and the rows are inserted according to the partitioning scheme of the target table. If the export contains partitions, and the import does not specify them, all are inserted. Optionally specifies a comma-separated list of users to import to that can be used with the FROMUSER parameter to change the table owners. The TOUSER Oracle accounts must already exist, and the USERID must have INSERT privilege on the tables that must also exist. Specifies the username/password (and optional connect string) of the user initiating the import. If a connect string is not provided, the ORACLE_SID environment variable is used. Directory
TOUSER
no default
USERID
no default
Directory
Redirecting a restore of an XML export archive to a different client

With NetBackup for Oracle you have the option to restore an XML export archive to a client other than the one that originally performed the XML export. The process of restoring data to another client is called a redirected restore. Figure 5-3 illustrates a typical redirected restore. Figure 5-3 Redirected restore
1. Cl ient A
gets back ed up
Server
.
2. Clien t B re q uests r client A esto image to clien re of t B.
nt res clie er resto ent B. v r e s e li 3. Th ge to c up ima A back
The user on client A cannot initiate a redirected restore to client B. Only the user on client B, the client receiving the backup image, can initiate the redirected restore. Note: For Oracle backups performed with NetBackup 6.0x or earlier, only the user who performed the backup can restore that backup. For any Oracle backup that is performed with NetBackup 6.5, any user who belongs to the database group that performed the backup can restore it. This ability will be added to future patches of NetBackup releases earlier than 6.5.
Server configuration
Ensure that the NetBackup server is configured to allow a redirected restore. The administrator can remove restrictions for all clients by creating the following file on the Netbackup master server: /usr/openv/NetBackup/dbaltnames/No.Restrictions Or, to restrict clients to restore only from certain other clients, create the following file: /usr/openv/NetBackup/dbaltnames/client_name
145
For client_name, specify the name of the client allowed to do the redirected restore (the destination client). Then, add the name of the NetBackup for Oracle source client to that file.
Client configuration
For Oracle backups performed with NetBackup 6.0x or earlier, only the user who performed the XML export archive can restore that archive. For any Oracle XML export archive that is performed with NetBackup 6.5, any user who belongs to the database group that performed the archive can restore it. This ability will be added to future patches of NetBackup releases earlier than 6.5. To use bporaimp for a redirected restore Perform the following on the new client host if you want to restore XML export archives that are owned by another client. 1 2 Set environment variables for bporaimp on the new client, including ORACLE_HOME and ORACLE_SID. In the bporaimp parameter file, include the following lines:
nb_ora_serv = NetBackup_server nb_ora_client = original_client_where_XML_export_occurred. 3 4 Specify other bporaimp parameters. For more information, see Running bporaimp on the client on page 138. Run bporaimp.
Example
For example, assume the following:

Original client is jupiter New client is saturn Server is jupiter ORACLE_SID is test on both saturn and jupiter UNIX user is ora on both jupiter and saturn Archive name is sales Create the following file on server jupiter:
/usr/openv/netbackup/db/altnames/saturn
1 2 3 4
Edit the preceding file to contain the name jupiter. Log on to saturn as ora. Create file bporaimp.param.
Include the following parameters:

NAME = sales NB_ORA_SERV = jupiter NB_ORA_CLIENT = jupiter USERID = orauser/orapasswd
Run bporaimp parfile=bporaimp.param to restore sales archive to saturn and to import the data into the test database on saturn.
Chapter
NetBackup for Oracle with Snapshot Client

The chapter describes the following topics:

Installation and licensing requirements on page 147 NetBackup for Oracle with Snapshot Client overview on page 148 How does NetBackup for Oracle with Snapshot Client work? on page 151 Configuring snapshot backups on page 158 Restoring data from a snapshot backup on page 165 Snapshot Client effects on page 173
This chapter explains how to use NetBackup for Oracle with NetBackup Snapshot Client to perform snapshot backups and block-level incremental backups of your Oracle database. To use NetBackup for Oracle with Snapshot Client, you must have both NetBackup Snapshot Client and NetBackup for Oracle licensed and installed.
Installation and licensing requirements

To use NetBackup for Oracle with Snapshot Client, you must have the following licensed and installed:

NetBackup for Oracle 6.5 NetBackup Snapshot Client 6.5
No additional NetBackup software is required. You might need to modify other hardware and software configurations. For more information about the following, see the NetBackup Snapshot Client Administrators Guide:
148 NetBackup for Oracle with Snapshot Client NetBackup for Oracle with Snapshot Client overview
How to install and configure the NetBackup Snapshot Client Configuration requirements for specific snapshot methods
NetBackup for Oracle with Snapshot Client overview

The following sections describe the NetBackup Snapshot Client features that are available for use with NetBackup for Oracle.
Snapshot backup
A snapshot is a disk image of the client's data made almost instantaneously. When used in conjunction with NetBackup Snapshot Client, NetBackup for Oracle can back up Oracle objects by taking snapshot images of the component files. Later, it backs up the snapshot version to the storage unit. Snapshot backup captures the data at a particular instant without causing significant client downtime. Client operations and user access continue without interruption during the backup. The resulting capture or snapshot can be backed up without affecting the performance or availability of the database.
Instant recovery
This feature makes backups available for instant recovery from disk. Instant recovery combines snapshot technology with the ability to do rapid disk-based restores. NetBackup creates the image without interrupting user access to data. Optionally, the image is retained on disk as well as backed up to storage. Instant recovery makes it possible to perform block-level restores.
Off-host backup
An off-host backup shifts the burden of backup processing onto a separate backup agent, such as an alternate client. This reduces the effect on the client's computing resources ordinarily caused by a local backup. The backup agent reads the data from the client disk and writes it to storage. An off-host backup can also be directed to a NetBackup media server, or third-party copy device
Block-level incremental backup

A block-level incremental (BLI) backup uses the change tracking capabilities of the VxFS Storage Checkpoint feature. In a BLI backup, only the changed blocks of data are backed up not the entire file or file system. A BLI backup saves
NetBackup for Oracle with Snapshot Client NetBackup for Oracle with Snapshot Client overview
149
time, decreases the amount of backup media required, and significantly reduces CPU and network overhead during backups. You can perform a BLI backup with, or without, RMAN.
Proxy copy
A proxy copy is a special type of backup in which the control of the data transfer is managed by the NetBackup for Oracle agent. During the backup and restore operations, proxy copy enables the agent to manage the entire data movement between the disks that contain the data files and the storage devices managed by NetBackup. With proxy copy, RMAN provides a list of files that require backup or restore to the NetBackup for Oracle agent. The agent determines how the data is moved and when to move the data. Proxy copy is an extension to Oracles Media Management API. Backups and restores remain tightly integrated with RMAN and its catalog, greatly simplifying administration tasks.
File-based operations
Standard NetBackup for Oracle backups and restores are stream-based. When Snapshot Client is enabled, the operations are file-based. The following sections illustrate the differences between these operation types.
Stream-based operations
Stream-based operations are the standard NetBackup implementation of conventional RMAN backup and restores. In a stream-based backup, NetBackup moves the data provided by the server process. NetBackup captures the data stream content provided by RMAN. If the user has specified multiple streams, then RMAN opens multiple streams and NetBackup catalogs them as separate images. Figure 6-1 on page 150 represents a stream-based backup or restore.
150 NetBackup for Oracle with Snapshot Client NetBackup for Oracle with Snapshot Client overview
Figure 6-1
NetBackup for Oracle RMAN stream-based backup or restore
Oracle Server Oracle database disk Control commands Data Oracle database disk
NetBackup
File-based operations
File-based operations are the NetBackup for Oracle with Snapshot Client implementation of Oracle proxy copy backups and restores. In a file-based operation, RMAN provides the list of files that require backup or restore to NetBackup for Oracle with Snapshot Client. NetBackup for Oracle with Snapshot Client performs the data movement. Figure 6-2 on page 151 represents a file-based backup or restore.
NetBackup for Oracle with Snapshot Client How does NetBackup for Oracle with Snapshot Client work?
151
Figure 6-2
NetBackup for Oracle with Snapshot Client file-based backup or restore
Oracle Server
Oracle database disk
Control commands
Oracle database disk
List of files
Data NetBackup
Data
How does NetBackup for Oracle with Snapshot Client work?

NetBackup users or schedules start database backups or restores by specifying a template or shell script in the backup selections list of the Oracle policy. The template or shell script specifies backup or restore commands for the Oracle Recovery Manager (RMAN) to use when performing the backup or restore on the client. The RMAN backup proxy command initiates a proxy copy backup of the specified objects. The objects that can be backed up using the proxy copy functionality depend on the Oracle version. RMAN translates the objects into the physical file names and provides a list of file names to NetBackup for Oracle. See Database objects supported by advanced backup methods on page 152.
152 NetBackup for Oracle with Snapshot Client How does NetBackup for Oracle with Snapshot Client work?
The agent checks that the policy it is using for the backup is configured with the appropriate Snapshot Client attributes. The agent then initiates file-based backups of the Oracle files and uses the NetBackup Snapshot Client interface to perform the data movement. When Oracle performs proxy copy backups, it puts the data files being backed up into backup mode. NetBackup then creates a snapshot of the files. After the snapshot has been created, the NetBackup for Oracle agent signals back to Oracle to take the data files out of backup mode. The data files that are being backed up are in backup mode only for the period of time necessary to capture a snapshot of the data.
Sequence of operation: Backup

For a backup operation, the NetBackup for Oracle agent performs the following steps: 1 Receives a list of files to back up from RMAN. Each file is identified by a unique backup file name in the NetBackup catalog. To ensure this, use the format operand to give each data file a unique name. Queries the policy to check whether the Snapshot Client policy attributes are specified. Initiates a configured number of Snapshot Client backups and waits until the jobs are completed. See Multistreaming on page 153.
2 3
Sequence of operation: Restore

For a restore operation, the NetBackup for Oracle agent performs the following steps: 1 2 3 Receives a list of files to restore from RMAN. Sends a restore request to the NetBackup server for all files in the list. Waits for all files in the file list to be restored by NetBackup.
Database objects supported by advanced backup methods

Oracle controls the kinds of database objects that can be backed up by proxy copy and, therefore, what NetBackup can back up using Snapshot Client backup methods. Oracle allows proxy copy backups of databases, tablespaces, and data files. With Oracle 10g releases and later, Oracle also allows proxy copy backups of archived redo logs. As a result, NetBackup can use file-based Snapshot Client backup methods to back up these objects.
153
For control files and archived redo logs, Oracle RMAN performs only conventional stream-based backups. This means that NetBackup for Oracle must use stream-based backups for control files and archived redo logs even when using Snapshot Client methods for the other database objects. Note: Oracle 10g and later releases support proxy copy backups for archived redo logs. Control files, however, must still be included in a stream-based backup schedule. If you are using an Oracle 10g or later release, you can include archived redo logs in your database proxy file backups, and you can ignore the instructions in this chapter that direct you to back up the archived redo logs in a stream-based backup schedule. File-based and stream-based backups require different configurations. When configuring your NetBackup for Oracle with Snapshot Client backups, be sure to configure a policy that allows both kinds of backups. For information on configuring such a policy, seeSnapshot Client effects on page 173.
Multistreaming
On the initial call, NetBackup for Oracle with Snapshot Client returns a special entry to RMAN indicating that it supports proxy copy. It also indicates to RMAN that it supports an unlimited number of files to be proxy copied in a single proxy copy session. This means that the number of channels allocated for the RMAN backup proxy command does not control the degree of parallelism for proxy backups. RMAN uses only one channel for proxy copy backups except when a specific configuration is used. The NB_ORA_PC_STREAMS variable controls the number of proxy copy backup streams to be started. By default, the agent initiates one backup job for all files. If the RMAN send command passes NB_ORA_PC_STREAMS, NetBackup for Oracle splits the files into the number of groups specified by the variable based on the file size. The agent attempts to create streams of equal size.
RMAN multiple channels

If you allocate multiple channels for an RMAN proxy copy backup session, RMAN uses only one channel to perform a proxy backup of all objects. All other channels could be used for a stream-based (non-proxy) backup of the control file or archived redo logs. For examples, see Proxy backup examples on page 155.
Restoring data files to a new location

NetBackup for Oracle with Snapshot Client can restore data files backed up by proxy to a new location. The new location can be specified by using the RMAN
set newname command or ALTER DATABASE RENAME DATAFILE statement before initiating a restore. For example, to restore a data file for tablespace TEST to a new location, you can use the following RMAN commands:
RUN { allocate channel t1 'SBT_TAPE'; sql 'alter tablespace TEST offline immediate' # restore the datafile to a new location set newname for datafile '/oradata/test.f' to '/oradata_new/test.f'; restore tablespace TEST; # make the control file recognize the restored file as current switch datafile all; recover tablespace TEST; release channel t1; }
The RMAN procedure for data files backed up by proxy is the same as for conventionally backed up data files. RMAN knows that the data files were backed up by proxy, and it issues a proxy restore request to NetBackup for Oracle, which restores the data files to the new location. For more information on the required procedure, see your Oracle documentation.
Redirecting a restore to a different client

The procedure for restoring a proxy backup to a different destination client is the same as the procedure for stream-based, non-proxy backups. See Using NetBackup for Oracle on page 109.
Symbolic links and raw data files

NetBackup for Oracle with Snapshot Client backs up and restores data files that consist of symbolic links and regular files. Both the symbolic link and the file are backed up and restored. However, if you selected Retain snapshots for instant recovery, the symbolic link must reside on the same file system as the data file. When you use instant recovery, if the symbolic link resides on a different file system than the data file it points to, the restore fails. NetBackup for Oracle with Snapshot Client backs up and restores data files created on raw partitions.
Quick I/O data files

NetBackup for Oracle with Snapshot Client backs up and restores Quick I/O Oracle data files. A Quick I/O file consists of two components: a hidden file with space allocated for it and a link that points to the Quick I/O interface of the hidden file.
155
On the backup, NetBackup for Oracle with Snapshot Client follows the symbolic link and backs up both components of the Quick I/O file: the symbolic link and the hidden file. On the restore, NetBackup for Oracle with Snapshot Client restores both components from the backup image. If one or both of the components are missing, NetBackup for Oracle with Snapshot Client creates the missing component(s).
RMAN incremental backups

You can use proxy copy backups as a part of the incremental strategy with conventional non-proxy RMAN backups. RMAN allows you to create a proxy copy incremental level 0 backup. This backup can be the base for subsequent RMAN traditional incremental backups (level 1-n). To accomplish this, perform a snapshot proxy copy (file-based) level 0 incremental backup and follow with an RMAN traditional (stream-based) level 1-n incremental backup. In the following example, the first run command initiates a proxy copy backup of tablespace tbs1. NetBackup for Oracle uses a snapshot file-based backup to perform a full tablespace backup. RMAN designates this backup as eligible for incremental level 1-n backups. The second run command initiates a traditional non-proxy level 1 incremental backup of the same tablespace tbs1. In this case, NetBackup for Oracle performs a stream-based backup.
run { allocate channel t1 type 'SBT_TAPE'; backup incremental level 0 proxy format bk_%U_%t tablespace tbs1; release channel t1; } run { allocate channel t1 type 'SBT_TAPE'; backup incremental level 1 format bk_%U_%t tablespace tbs1; release channel t1; }
Proxy backup examples

The following examples show how to use multiple channels in RMAN scripts with proxy backups.
Example 1
This RMAN sample script initiates a whole database backup, which includes the control file. RMAN starts one proxy copy backup session by sending a list of all data files to the NetBackup for Oracle agent on channel t1. The agent splits the files into 3 streams and initiates a file-based backup for each stream. After the proxy backup is done, RMAN starts a non-proxy conventional backup of the control file on channel t1.
run { allocate channel t1 type 'SBT_TAPE'; send 'NB_ORA_PC_STREAMS=3'; backup proxy format 'bk_%U_%t' (database); release channel t1; }
Example 2
This RMAN sample script initiates a whole database backup, which includes the control file. RMAN starts one proxy copy backup session by sending a list of all data files to the NetBackup for Oracle agent on channel t1. The agent splits the files into 3 streams and initiates a file-based backup for each stream. At the same time, RMAN starts a non-proxy conventional backup of the control file on channel t2.
run { allocate channel t1 type 'SBT_TAPE'; allocate channel t2 type 'SBT_TAPE'; send 'NB_ORA_PC_STREAMS=3'; backup proxy format 'bk_%U_%t' (database); release channel t1; release channel t2; }
Note that if the RMAN recovery catalog is not used, then the version of the control file being backed up does not contain the information about the current backup. To include the information about the current backup, back up the control file as the last step in the backup operation. This step is not necessary if the recovery catalog is used.
Run { allocate channel t1 type 'SBT_TAPE'; backup format 'cntrl_%s_%p_%t' current controlfile; release channel t2; }
157
Example 3
In this sample script, RMAN initiates two proxy copy backups sequentially on channel t1. It starts a proxy backup of tablespace tbs1 data files. After the backup is done, it starts another proxy backup of tablespace tbs2 data files.
run { allocate channel t1 type 'SBT_TAPE'; backup proxy format 'bk_%U_%t' (tablespace tbs1); backup proxy format 'bk_%U_%t' (tablespace tbs2); release channel t1; }
This configuration can cause problems if the sequential backups create snapshots on the same volumes. In such a situation, issue a single backup command such as the following, which specifies both tablespaces, rather than two separate backup commands:
run { allocate channel t1 type 'SBT_TAPE'; backup proxy format 'bk_%U_%t' (tablespace tbs1, tbs2); release channel t1; }
Example 4
In this example, RMAN distributes proxy copy backups over two channels. It creates two proxy copy backup sessions sending tbs1 data files on channel t1 and tbs2 data files on channel t2. Such a method is useful if you want to specify different NetBackup configurations for each channel. In this example, each send command specifies a different policy to be sent and used by each proxy backup.
run { allocate channel t1 type 'SBT_TAPE'; send NB_ORA_POLICY=policy1; allocate channel t2 type 'SBT_TAPE'; send NB_ORA_POLICY=policy2; backup proxy format 'bk_%U_%t' (tablespace tbs1 channel t1); (tablespace tbs2 channel t2); release channel t1; release channel t2; }
158 NetBackup for Oracle with Snapshot Client Configuring snapshot backups
Configuring snapshot backups

You can combine two NetBackup features, snapshot backup and instant recovery, to enable fast database backups and recoveries. These features are as follows:
A snapshot backup occurs when NetBackup creates a point-in-time disk image of the database and copies that image to disk. This process is nearly instantaneous, so user access to the database is not interrupted during the backup. An instant recovery occurs when NetBackup restores the on-disk snapshot copy of the database.
Another feature, off-host backup, can reduce the I/O processing load on the client that hosts the database. To use off-host backup, specify an alternate client (UNIX and Windows clients) or a data mover (UNIX clients only) to assume the I/O processing load.
Configuration requirements
Each agent has its own hardware requirements, software requirements, compatibility with certain features, and snapshot methods that are supported. There are also special requirements for specific types of backups. Refer to the NetBackup Snapshot Client Administrators Guide and the Symantec Support Web site for more information. Familiarize yourself with this information before you configure any snapshot backups. The following list highlights some of the requirements that pertain to database agents:
The user identification and group identification numbers (UIDs and GIDs) associated with the files to be backed up must be available to both the primary client and the alternate backup client. You should allocate at least two different volumes or file systems for database activities, as follows:

Allocate one or more volumes or file systems to the database data files.
Allocate a different set of volumes or file systems to the Oracle executables, configuration files, and the archive redo logs. One reason for to have two different volumes is to separate the data files from the other files. If the logs are configured on the same volumes (or file systems) as the data files, the logs are temporarily frozen while NetBackup takes the snapshot. The process cannot access the logs when the database is active, so the database activity might freeze until the logs become accessible again. Another reason for writing the data files to their own repository is because it is required for an instant recovery point-in-time
NetBackup for Oracle with Snapshot Client Configuring snapshot backups
159
rollback. Only data files may exist on the volume or file system being restored.
The hardware and software that is required for the appropriate snapshot method must be installed and configured correctly. NetBackup Snapshot Client must be installed and configured correctly, and the license key for this option must be registered. To perform off-host backups, perform any special configuration that is required.
Configuring the Oracle policy with Snapshot Client backup methods

This section explains how to configure snapshot and instant recovery backups for the Oracle policy. For information on how a snapshot method is automatically selected and details on the types of backup methods, see the NetBackup Snapshot Client Administrators Guide. Snapshot backups do not back up all database objects. Your backup configuration must include policies to perform file-based and stream-based backups. This configuration ensures that the entire database can be restored successfully. For snapshot or instant recovery backups, configure the following Oracle policy and schedules:
Snapshot methods for the file systems (logical volumes) on which the data files reside. Snapshot methods for the file systems (raw partitions or logical volumes) on which the data files reside. A backup method on the policy attributes dialog box. An Automatic Full Backup schedule to perform file-based snapshot and off-host backups of the data files. An Application Backup schedule to perform the stream-based backup of control files and archived redo logs. Oracle does not support proxy backups of database control files and archived redo logs. These files are backed up using standard RMAN operations.
Configuring a snapshot policy

The following procedure shows how to configure a snapshot policy with optional instant recovery, snapshot retention, and off-host backup. To configure a snapshot policy 1 Open the policy you want to configure.
2 3
Click on the Attributes tab. Select the Oracle policy type. Figure 6-3 on page 160 shows the interface that lets you configure a snapshot policy. Snapshot policy interface
Figure 6-3
Select the policy type Select appropriate storage unit or storage unit group
Click Perform snapshot backups (Optional) Click Retain snapshots for instant recovery (Optional) Click Perform off-host backup and specify a method
Select a policy storage unit from the Policy storage unit list. Select a policy storage unit in this step even if you plan to select Instant Recovery Snapshots Only later in this procedure. NetBackup uses this storage unit for the stream-based backups of the control files and the archived redo logs that are included in this policy. NetBackup also uses this storage unit if you select Third Party Copy Device when you configure the schedule. Any_available is not supported for the following data movers: NetBackup Media Server or Third-party Copy Device. Click Perform snapshot backups.
161
(Optional) Click Advanced Snapshot Options to choose a snapshot method. By default NetBackup chooses a snapshot method for you. To choose a snapshot method, click auto (the default) or click one of the methods that are presented in the list. The snapshot method you can use depends on your hardware environment and software environment. Only certain snapshot methods are supported in certain environments. See the NetBackup Snapshot Client Administrators Guide or the supported platforms matrix on the Symantec Support Web site for more information. You can configure only one snapshot method per policy. For example, assume you want one snapshot method for clients a, b, and c, and a different method for clients d, e, and f. Then you need to create two policies for each group of clients and select one method for each policy. (Optional) Select Retain snapshots for instant recovery. When this option is selected, NetBackup retains the snapshot backup image on disk for later use in recovery. (Optional) Select Perform off-host backup. By default, the client that hosts the database performs the backup. If you want to reduce the I/O processing load on the client that hosts the database, specify an alternate client to perform the backup. Select an off-host backup method by specifying the following:
Use alternate client (UNIX and Windows clients). If you click Use alternate client, also specify the name of the client to perform the backup. This option might require additional configuration. The alternate client must be a client that shares the disk array. Use data mover (UNIX clients only). If you click Use data mover, also select one of the possible data movers:

NetBackup Media Server Third-Party Copy Device Network Attached Storage
Click the Schedules tab.
10 Click New. Configure both an Automatic schedule and an Application Backup schedule, as follows:
The Automatic schedule is for the database files. If you want to create only disk images, in the Destination panel, under Instant Recovery, select Snapshots only. This suppresses NetBackups default behavior, which is to copy the snapshot to a storage unit. When you select Snapshots only, NetBackup creates the on-disk snapshot copy of the database, but it does not copy the snapshot to a storage
unit. The on-disk snapshot becomes the only backup copy. Note that the on-disk snapshot is not considered to be a replacement for a traditional backup.
(Conditional) The Application Backup schedule is for the control files and archived redo logs. NetBackup uses this storage unit for the stream-based backups of the control files and the logs that are included in this policy. NetBackup copies the databases control files and archived redo logs to the storage unit you selected. For UNIX clients, if you selected Third-Party Copy Device as an off-host backup method, click Override policy storage unit. Then select a non-SAN Media Manager or other storage unit type that is appropriate to back up the control files and archived redo logs.
11 Click the Clients tab. Specify the clients to be included in this policy. 12 Click the Backup Selections tab. Specify a backup template or script. For information about using templates and scripts with a NetBackup for Oracle policy with Snapshot Client, see Snapshot Client effects on page 173. 13 Configure other attributes and add any additional schedules and backup selections.
NAS snapshot policy with optional SnapVault capabilities

To use NAS snapshot with NetBackup for Oracle, the Oracle database must be installed and configured to work in a NAS environment. NAS snapshot for Oracle backup is only supported in Solaris (SPARC) environments. NetBackup does not support multi-streamed backups for a NetBackup for Oracle snapshot policy that uses NAS. If you want to use a SnapVault storage unit, make sure the storage unit is configured before you start to configure the NAS snapshot policy. For more information about NAS snapshot and SnapVault, see the NetBackup Snapshot Client Administrators Guide. To configure a NAS snapshot policy 1 2 3 Open the policy you want to configure. Click on the Attributes tab. Select the Oracle policy type.
163
Figure 6-4 on page 163 shows the interface to use when you define a NAS snapshot policy. Figure 6-4 NAS snapshot policy interface
Select the policy type Select appropriate storage unit or storage unit group
Click Perform snapshot backups Click Retain snapshots for instant recovery Click Perform off-host backup
Click Use data mover and specify Network Attached Storage
Decide on a storage unit. a If you do not want to use a SnapVault storage unit, from the Policy storage unit list, select an appropriate non-SnapVault storage unit. Although the policy cannot run without a specified storage unit, NetBackup does not use the storage unit for NAS snapshot backups. NetBackup creates the snapshot on disk regardless of which storage unit you select. The policy storage unit is used for stream-based backups of control files and archived redo logs unless you override it in the Application Backup schedule.
If you want to use a SnapVault storage unit, make sure you have defined a disk storage unit. Select the disk storage unit you have configured for SnapVault in the Policy storage unit list.
5 6 7
Select Perform snapshot backups and Retain snapshots for instant recovery. Select Perform off-host backup and Use data mover. From the pull-down menu under Use data mover, select Network Attached Storage. When the policy runs, NetBackup automatically selects the NAS_Snapshot method for creating the snapshot. As an alternative, you can manually select the NAS_Snapshot method using the Advanced Snapshot Options dialog from the policy display. For information about the Maximum Snapshots (Instant Recovery only) parameter, see the policy configuration chapter of the NetBackup Snapshot Client Administrators Guide. Click the Schedules tab. Click New. Configure both an Automatic Backup schedule and an Application Backup schedule, as follows:
8 9
The Automatic Backup schedule is for the database files. In the Destination panel, under Instant recovery, select Snapshots only. This suppresses NetBackups default behavior, which is to copy the snapshot to a storage unit. If you use SnapVault, the level you specify in the Retention field determines the retention period for the SnapVault copies on the SnapVault secondary. The Application Backup schedule is for the archived redo logs and the control files. If you use SnapVault, override the policy storage unit and specify a storage unit that is appropriate for the control files and archive logs.
10 Click the Clients tab. Specify clients to be backed up by this policy. 11 Click the Backup Selections tab. Specify a backup template or script. For information about using templates and scripts with a NetBackup for Oracle with Snapshot Client policy, seeSnapshot Client effects on page 173. 12 Configure other attributes and add any additional schedules and backup selections.
NetBackup for Oracle with Snapshot Client Restoring data from a snapshot backup
165
Restoring data from a snapshot backup

The following sections describe how to restore files, volumes, and file systems from a snapshot backup.
Restoring individual files

Data that was backed up with Snapshot Client methods is restored in the same way as data that was backed up without Snapshot Client methods. You can use the procedure in Performing a restore on page 117 to restore data from a snapshot backup. Use this procedure for the files that were backed up with, or without, instant recovery enabled. In all cases, NetBackup determines the files that were backed up, and it initiates a corresponding restore request to the database agent. If instant recovery is enabled, NetBackup attempts to restore the file by using the unique restore methods available with the instant recovery feature. The type of restore method that NetBackup uses depends on your environment and the type of backup performed. If NetBackup is unable to use any of the instant recovery methods, it restores the file in the typical manner. Data is copied from the snapshot to the primary file system. For information on the instant recovery methods that NetBackup uses, see the NetBackup Snapshot Client Administrators Guide.
Restoring volumes and file systems using snapshot rollback

You can request that an entire volume or an entire file system be restored from an instant recovery Snapshot backup. This type of a restore is called a point in time rollback. All the data in the snapshot is restored; single file restore is not available in a rollback. You can perform a snapshot rollback from an instant recovery backup that was made with the following methods:

NAS_Snapshot VxFS_Checkpoint snapshot vxvm snapshot FlashSnap snapshots
The NetBackup Snapshot Client Administrators Guide contains more information on snapshot rollbacks.
166 NetBackup for Oracle with Snapshot Client Restoring data from a snapshot backup
The following considerations are relevant for NetBackup for Oracle restores:

Snapshot rollback overwrites the entire volume. With NetBackup for Oracle, snapshot rollback always performs file verification. The agent checks for the following:
The requested files (number and names) are identical to those in the snapshot The primary volume does not contain any files that were created after the snapshot was made
RMAN only requests those files that have changed since the point in time indicated. This behavior can cause file verification to fail because the number of files requested does not match the number of files in the snapshot. To prevent this error, run the restore command with a shell script and use the FORCE option. If verification fails, the rollback aborts with 249.
Snapshot rollback should be used with database files only. Database files and archived redo logs should exist on different file systems or volumes.
Notes on SnapVault restores

When a Point in Time Rollback restore is selected from a SnapVault backup, the entire subvolume (qtree) is restored to a new subvolume (qtree) on the primary host. The restore does not overwrite the existing subvolume. File verification is not performed. The format of the new subvolume name is as follows:
mountpointname_restore.timestamp
For example: subvol1_restore.2005.05.19.10h49m04s To use the restored and new subvolume 1 2 3 4 Unmount the original subvolume, which is the subvolume that the restore process did not overwrite. Rename the original subvolume. Rename the new subvolume with the name of the original. Mount the new subvolume on the client. Use the ALTER DATABASE RENAME DATAFILE command to point to the restored data file on the newly created subvolume.
Restoring volumes and file systems using block-level restore

The procedure for specifying a snapshot rollback restore depends on the method you choose to perform the restore. Use one of the following methods:
NetBackup for Oracle with Snapshot Client Configuring block-level incremental backups
167
To specify a snapshot rollback restore from the Java or Windows interface 1 2 Go to the NetBackup Backup, Archive, and Restore Interface. Click the Restore Files tab.
Note: If the data file you want to restore has not changes since it was backed up, the rollback may fail. Initiate the restore from a script and use the FORCE option. 3 4 5 Set the Restore Type to Point in Time Rollback. Use the NetBackup for Oracle recovery wizard for the restore. Follow the restore procedure for typical backups. See Performing a restore on page 117.
To specify a snapshot rollback restore using a script or RMAN command
If you want to use a shell script or RMAN command, set a new variable, NB_PC_ORA_RESTORE=rollback.
Note: If the data file you want to restore has not changes since it was backed up, the rollback may fail. Initiate the restore from a script and use the FORCE option. For example:
RUN { allocate channel t1 'SBT_TAPE'; send 'NB_ORA_PC_RESTORE=rollback'; sql 'alter tablespace TEST offline immediate' restore tablespace TEST; recover tablespace TEST; release channel t1; }
Troubleshooting
If the rollback restores fails, it might be because Oracle still has a file open. Shut down and restart the database to try to correct this problem.
Configuring block-level incremental backups

If only a small portion of a database changes on a daily basis, full database backups are costly in terms of time and media. The block-level incremental (BLI)
168 NetBackup for Oracle with Snapshot Client Configuring block-level incremental backups
backup interface extends the capabilities of NetBackup to back up only changed data blocks. A database BLI backup is done at the file system block level, which means only changed blocks are backed up. Changed files are not backed up. VxFS Storage Checkpoint facility identifies changed blocks in real time. BLI backup does not need to search the entire database for the modified blocks. BLI backup saves time, decreases the amount of backup media that is required, and significantly reduces CPU and network overhead during backups. In addition, BLI backup allows more frequent backups, so backup images are more up-to-date. BLI backup is particularly useful for any large databases that are sized in terms of hundreds of gigabytes or terabytes. Using most traditional methods for database backup, any change in the databaseno matter how smallrequires that the entire database is backed up. Using BLI backup, only modified data blocks need to be backed up. The recommended method for performing BLI backups is the proxy BLI agent with RMAN. This method supports the other features of NetBackup for Oracle, including the policy types and schedules and the convenience of the RMAN template generation wizard. It also remains tightly integrated with RMAN and its catalog, which greatly simplifies administration tasks. Note: Symantec recommends that Snapshot Client users who want to perform BLI backups use BLI with RMAN. NetBackup for Oracle also provides a method for BLI backup without RMAN that uses scripts to put tablespaces into, and take them out of, backup mode. This method is not recommended, and it requires a significantly different configuration. For instructions on using the script-based BLI method without RMAN, see Script-based block-level incremental (BLI) backups without RMAN on page 203.
How does BLI work?

NetBackup supports BLI full backups and BLI incremental backups of Oracle databases. BLI backup supports two types incremental backups: differential and cumulative. Full, differential incremental, and cumulative incremental backups are specified as part of the backup schedule. When performing a restore, NetBackup restores an appropriate full backup, then it applies the changed blocks from the incremental backups. Restoring any of the incremental backup images requires NetBackup to restore the last full backup image and all the subsequent incremental backups until the specified incremental backup image is restored. NetBackup performs this restore process automatically, and it is completely transparent. The media that
169
stored the last full backup and the subsequent incremental backups must be available, or the restore cannot proceed. Note that restoring a file rewrites all blocks in that file. The first subsequent differential incremental backup and all subsequent cumulative incremental backups back up all the blocks in the restored file. After restoring an entire database, the first subsequent backup results in a full backup. The restore destination can be a VxFS, UFS (Solaris), JFS (AIX), or HFS (HP-UX) file system. The destination VxFS file system does not need to support the Storage Checkpoint feature to restore files, but a VxFS file system with the Storage Checkpoint feature is needed to perform BLI backups of the restored data. This section uses the following terms to describe BLI backups:
Full Backup. A backup in which NetBackup backs up the entire database file, not just data blocks changed since the last full or incremental backup. Cumulative BLI Backup. This is a backup of all the data blocks of database files that changed since the last full backup. A cumulative BLI backup image contains only the data blocks of database files that changed since the last full backup, but a cumulative BLI backup can reduce the number of incremental backup images that must be applied to a restore operation. This speeds up the restore process. Differential BLI backup. This is a backup in which NetBackup performs a backup of only those data blocks of database files that changed since the last backup of any type (full, cumulative incremental, or differential incremental backup) was performed.
When NetBackup initiates full database backups, followed by BLI backups, it creates, manages, and uses the appropriate Storage Checkpoints of the Oracle data file file systems.
Storage Checkpoint
The BLI backup methodology uses the Storage Checkpoint facility in the Veritas File System (VxFS). This facility is available through the Storage Foundation for Oracle. The VxFS Storage Checkpoint facility keeps track of data blocks modified by the database since the last backup. NetBackup with BLI backup leverages this facility to back up only changed blocks, not the entire database, for an incremental backup. VxFS Storage Checkpoint is a disk- and I/O-efficient snapshot of file systems. A Storage Checkpoint provides a consistent, stable view of a file system at the instant when the file system was snapped or checkpointed. Instead of making a physically separate copy of the file system, a Storage Checkpoint identifies and
maintains only changed file system blocks, saving disk space and significantly reducing I/O overhead. By keeping track of changed blocks, the VxFS Storage Checkpoint enables BLI backups. VxFS Storage Checkpoint facility provides a consistent view of file systems, allowing BLI backup to freeze the database image during database backups. The Storage Checkpoint operation is similar to the snapshot file system mechanism. However, unlike a snapshot, the Storage Checkpoint persists after a system reboot. Also, the Storage Checkpoint operation is totally transparent to administrators. The Checkpoint image is managed and available only through NetBackup or through the VxDBA utility for database backup available with the Veritas Storage Foundation. For more information on Storage Checkpoints, see the Veritas Storage Foundation documentation. You can take a Storage Checkpoint while the database is online or offline. To take a Storage Checkpoint while the database is online, you must enable archive log mode. During the creation of the Storage Checkpoint, all tablespaces are placed in backup mode.
Nodata Storage Checkpoint

The Nodata Storage Checkpoint sets a bit to indicate that a block has changed. When using Nodata Storage Checkpoints, the data files are left in backup mode for the duration of the backup. The amount of redo logs generated depends on the number of changes made during the backup. To support BLI backup, the VxFS file systems need extra disk space to keep track of the block change information. The space required depends on the database workload while the backup is running. For Nodata Storage Checkpoints, the additional space required by each file system is about 1% of the file system size. The default option used by NetBackup for Oracle with Snapshot Client for backups is to use Fulldata Storage Checkpoint. By using this option, the NetBackup for Oracle agent keeps Oracle data files in backup mode only for the time needed to create a Storage Checkpoint.
Fulldata Storage Checkpoint

The Fulldata Storage Checkpoint makes a copy of the original data block before making a change. When using Fulldata Storage Checkpoints, the tablespaces and data files are in backup mode for only a few seconds while the Storage Checkpoint is created, so the extra archived redo log space used is very small. Space in the file system, however, is needed to keep a copy of the original block of data that was changed. If the workload is light during the backup or if the
171
backup window is relatively short (such as for incremental backups), an additional 10% of the file system size is usually sufficient. If the database has a heavy workload while a full backup is running, the file systems might require more space. While archive log mode is required when the database is online, this mode provides the best recoverability for taking offline Storage Checkpoints, too.
Storage Checkpoint configuration on the client

By default, the NetBackup for Oracle with Snapshot Client for proxy BLI backups uses the Fulldata Storage Checkpoint. When Fulldata Storage Checkpoint is in effect, the NetBackup for Oracle agent keeps the Oracle data files in backup mode only for the time needed to create a Storage Checkpoint. To change the default option to use Nodata Storage Checkpoint, a user must create the following file, which can remain empty: /usr/openv/netbackup/ext/db_ext/NODATA_CKPT_PROXY If the agent finds this file during run time, it uses Nodata Storage Checkpoint, and it keeps the data files in backup mode for the duration of the backup.
Configuration requirements
Before configuring BLI backups, make sure your configuration meets the following requirements:

NetBackup for Oracle is installed, licensed, and configured. NetBackup Snapshot Client is installed and configured, and the license key for this option has been registered. Veritas Storage Foundation for Oracle must be installed and configured. Veritas File System must have Storage Checkpoint licensed.
For more information on requirements, see the NetBackup Snapshot Client Administrators Guide.
Configuring policies for BLI backups

This section explains how to configure BLI backups for Oracle policies. BLI backups do not back up all database objects. Include policies to perform file-based and stream-based backups. Your backup configuration must ensure that the entire database can be successfully restored. To configure a policy for BLI backups, configure the following:
The BLI backup method on the policy attributes dialog box.
An Automatic Backup schedule to perform full and incremental file-based backups of the data files. An Application Backup schedule to perform a stream-based backup of control files and archived redo logs. These files are backed up using standard RMAN operations.
The following procedure describes how to configure a NetBackup for Oracle policy with BLI backups. To configure a policy for BLI backups 1 2 3 4 5 6 Open the policy you want to configure. Click the Attributes tab. From the Policy Type list, choose Oracle. Select a Policy storage unit. Select Perform block level incremental backups. To configure schedules, click the Schedules tab. Oracle does not support proxy backups of database control files and archived redo logs. To perform a whole database proxy backup, which automatically includes a backup of the control file, configure the following:
One or more automatic backup schedules to perform proxy BLI backups of the data files. An Application Backup schedule type to back up the control files and archived redo logs.
7 8
On the Clients tab, specify clients to be backed up with this policy. On the Backup Selections tab, specify the template or script.
Types of BLI backups

Proxy BLI backups are performed by Automatic Full Backup, Automatic Differential Incremental Backup, and Automatic Cumulative Incremental Backup schedules. If a user initiates a backup and the proxy schedule name is not specified on the request using the NB_ORA_PC_SCHED environment variable, the NetBackup server starts an Automatic Full Backup schedule by default. NetBackup for Oracle checks that a full backup has been performed before proceeding with an incremental backup. If the NetBackup scheduler or user initiates an incremental backup, and NetBackup for Oracle finds no record of a full backup using the same policy, it performs a full backup.
NetBackup for Oracle with Snapshot Client Snapshot Client effects
173
To ensure that it has a proper set of images to restore, NetBackup performs a full backup when it encounters the following situations:
If the number of backup streams specified has changed from the previous backup. This can be accomplished by changing the NB_ORA_PC_STREAMS environment variable. If NetBackup does not have a valid full backup image for the same policy in its database. This can occur, for example, if images were expired. If a new file was added to or deleted from the list of files for an incremental backup.
NetBackup for Oracle always initiates a full backup under these conditions, even if you want to perform an incremental backup.
Snapshot Client effects

The following sections describe the ways in which the Snapshot Client software affects backup types, schedule properties, and templates. Snapshot Client also affects scripts and environment variables.
Types of backups
The backup types available on the Schedules tab of the policy play a different role for NetBackup for Oracle with Snapshot Client backups. Table 6-1 on page 173 explains these roles.
Table 6-1 Backup type
Backup types for Oracle Description

The Application Backup schedule enables stream-based NetBackup operations. The Default-Application-Backup schedule is automatically configured as an Application Backup schedule. On UNIX clients, if you are using Third-party Copy Device or NetBackup Media Server as your data mover, override the policy storage unit by specifying a non-SAN media manager or other storage unit type for the Application Backup schedule to back up control files and archived logs.
Application Backup
174 NetBackup for Oracle with Snapshot Client Snapshot Client effects
Table 6-1 Backup type
Backup types for Oracle (continued) Description

For file-based proxy copy backups, the automatic backup schedule types serve two purposes:

Automatic Full Backup, Automatic Differential Incremental Backup, Automatic Cumulative Incremental Backup
Automatic backup schedules automatically start the backups by running the NetBackup for Oracle RMAN scripts or templates. Automatic backup schedules control file-based snapshot backups of the database objects.
Note: Snapshot backups do not support BLI functionality. Oracle always updates the data file headers when performing a checkpoint of the database. This means that an incremental backup that copies each changed file in its entirety is likely to include all of a databases files, effectively performing a full backup. For snapshot backups, specifying any of the automatic backup types results in a full backup.
Schedule properties
Some schedule properties have a different meaning for Snapshot Client database backups than for a regular database backup. Table 6-2 on page 174 explains these properties.
Table 6-2 Property

Retention
Schedule properties Description

Frequency based scheduling: The retention period for an Application Backup schedule refers to the length of time that NetBackup keeps stream-based, non-proxy backup images. For proxy backups, NetBackup for Oracle uses the Automatic Full Backup, Automatic Differential Incremental Backup, or Automatic Cumulative Incremental Backup retention period to specify how long to keep proxy file-based backup images. Calendar based scheduling: The retention period for an Application Backup schedule refers to the length of time that NetBackup keeps non-proxy backup images. For proxy backups, NetBackup for Oracle with Snapshot Client uses the Automatic Full Backup, Automatic Differential Incremental Backup, or Automatic Cumulative Incremental Backup retention period to specify how long to keep proxy file-based backup images.
175
Table 6-2 Property

Multiple copies
Schedule properties (continued) Description

If you are using Multiple copies and want to specify multiple copies of non-proxy stream-based backups for your Oracle policy, configure Multiple copies on the Application Backup schedule. For proxy file-based backups, configure Multiple copies on the automatic backup schedule.
Schedule properties on page 84 describes other schedule properties that are specific to database agent backups.
Templates and scripts

You can use a template created by the RMAN template generation wizard to perform backups with Snapshot Client. After they are created, templates reside on the NetBackup master server and are available for use by other [NetBackup Product] clients. See Creating templates and shell scripts on page 94. In the RMAN template generation wizard, the Specify Maximum Limits selection options on the backup limits screen are not applicable for proxy backups. RMAN uses these options only for conventional stream-based backups. If the template includes archived redo logs, NetBackup uses this option to back up the logs. Whether you use a template or script, you must enable the advanced backup method for your clients by configuring the Snapshot Client methods on the Attributes tab of the policy. At run time, the template checks the policy attributes to determine if an Snapshot Client backup method is configured, and it initiates the proxy file-based backup. If you use a script, the script must reside on each client included in the policy. Include the Oracle backup proxy command in the script to perform the advanced backup method. Sample scripts are included with the installation.
Environment variables
You can use environment variables to change the number of streams used for a proxy copy session or to specify an alternate backup schedule. For information on specifying these variables, see Configuring the runtime environment on page 89.
The following list shows variables that you can to set that are specific to the NetBackup for Oracle Snapshot Client: Environment variable
NB_ORA_PC_SCHED
Description
NetBackup for Oracle schedule used for a proxy copy file-based backup (Automatic Full, Automatic Differential Incremental, or Automatic Cumulative Incremental backup type). For scheduled backups, this variable is passed from the scheduler. When creating an RMAN template using the NetBackup for Oracle RMAN template generation wizard, this variable is automatically created in the template.
NB_ORA_PC_STREAMS
Specifies the number of backup streams that the NetBackup for Oracle Snapshot Client starts simultaneously in each proxy copy session. When a backup starts, NetBackup for Oracle Snapshot Client groups all data files into a specified number of backup streams based on the file size. NetBackup for Oracle Snapshot Client attempts to create streams of equal size. The default value for NB_ORA_PC_STREAMS is 1. Only a user can set this variable. When creating an RMAN template using the NetBackup for Oracle RMAN template generation wizard, this variable is automatically created in the template when you provide a value for the Number of parallel streams.
For NetBackup for Oracle with Snapshot Client, the order of precedence for environment variables is the same as for standard NetBackup for Oracle. Configuring the runtime environment on page 89 contains instructions for configuring variables set by NetBackup and variables set by a user. NetBackup for Oracle installs sample scripts in the following location:
/usr/openv/netbackup/ext/db_ext/oracle/samples/rman
The following are the NetBackup for Oracle with Snapshot Client sample scripts that show how to configure the required variables:
hot_database_backup_proxy.sh This script sets the environment and calls RMAN with the appropriate command to perform a whole database proxy backup. When NetBackup runs a schedule, it sets the environment variables that NetBackup for Oracle with Snapshot Client uses. The script shows how to use the RMAN send command to pass the NetBackup for Oracle with Snapshot Client variables with a vendor-specific quoted string. This script sets the environment and calls RMAN with the appropriate command to perform a tablespace proxy backup.
hot_tablespace_backup_proxy.sh
177
If you use scripts, use the send command to pass the environment variables to the agent. The following example uses the send command to specify the values for NB_ORA_PC_SCHED and NB_ORA_PC_STREAMS:
run { allocate channel t1 type 'SBT_TAPE'; send 'NB_ORA_PC_SCHED= sched, NB_ORA_PC_STREAMS= number; backup proxy (database format 'bk_%U_%t'); }
For more information, see the sample scripts provided with the agent.
Chapter
Troubleshooting

General troubleshooting procedure on page 179 NetBackup reports on page 181 Setting the debug level on page 184 Troubleshooting backup or restore errors on page 185 Troubleshooting XML export or XML import errors on page 188 Troubleshooting the browser interface and wizards on page 191 Troubleshooting NetBackup for Oracle with Snapshot Client on page 192 Minimizing timeout failures on large database restores on page 193
NetBackup, NetBackup for Oracle, and the Oracle Recovery Manager (RMAN) all provide reports on database backup, archive, and restore operations. These reports are useful for finding errors associated with those applications.
General troubleshooting procedure

Note: For brevity, this chapter refers to the libobk module as API. Many media manager vendors also call the libobk module DMO (Database Module). To perform this procedure, the following products must be properly installed and configured:

NetBackup 6.5. Oracle RDBMS 8.0.4 or later. XML export and XML import require Oracle RDBMS 8.1.5 or later. NetBackup for Oracle 6.5.
180 Troubleshooting General troubleshooting procedure
To perform initial troubleshooting steps 1 When verifying your installation, ensure that the following NetBackup for Oracle binaries exist. These are located in /usr/openv/netbackup/bin.
bphdb. This binary resides on the client and is used by both the NetBackup scheduler and the graphical interface to start backups. The main purpose of bphdb is to run an Oracle template or shell script that in turn calls rman, bporaexp, or bporaimp. libobk is a shared library module that contains functions callable by RMAN. This library is loaded when RMAN is started. The name of this binary depends on the operating system.

libobk.so on NCR, SGI, Sequent, Linux, and Data General libobk.so.1 on Solaris Opteron (64-bit Oracle) libobk.so.1 on Solaris SPARC, Tru64 and Digital UNIX (32-bit Oracle) libobk.so64.1 on Solaris SPARC (64-bit Oracle) libobk.sl on HP-UX (32-bit Oracle) libobk.sl64 on HP-UX (64-bit Oracle) libobk.a on AIX libobk.a64 on AIX (64-bit Oracle) libobk.so64 on SGI (64-bit Oracle)
For XML export and XML import, verify that the following binaries exist.
For 32-bit Oracle

/usr/openv/netbackup/bin/bporaexp /usr/openv/netbackup/bin/bporaimp /usr/openv/lib/libbpora.so.8.0 (libbpora.sl.8.0 on HP-UX) /usr/openv/lib/libbpora.so.9.0 (libbpora.sl.9.0 on HP-UX) /usr/openv/netbackup/bin/bporaexp64 /usr/openv/netbackup/bin/bporaimp64 /usr/openv/lib/libbpora64.so.8.0 (libbpora64.sl.8.0 on HP-UX) /usr/openv/lib/libbpora64.so.9.0 (libbpora64.sl.9.0 on HP-UX)
For 64-bit Oracle:

Troubleshooting NetBackup reports
181
For the Backup, Archive, and Restore interface, verify that the following binaries exist.

/usr/openv/netbackup/bin/bpdbsbora /usr/openv/netbackup/bin/bpubsora /usr/openv/lib/libdbsbrman.so (libdbsbrman.sl on HP-UX) /usr/openv/lib/libnbberman.so (libnbberman.sl on HP-UX)
Check that both the NetBackup server and client software are working properly. That is, check that normal operating system files can be backed up and restored from the client. The NetBackup client must be running the same version of software as the NetBackup server. Check that the following NetBackup log directories exist.
On the client: bpdbsbora, bporaexp (or boraexp64), bporaimp (or boraimp64), dbclient, bphdb, and bpcd. On the master server: bprd and bpdbm.
On the host with the storage unit: bpbrm and bptm. These directories must have 777 permissions. The VERBOSE level must be 5.
Note: The logs can become very large, especially bpdbm. Ensure that enough free disk space exists in the log directory disk partition.
NetBackup reports
The NetBackup server and client software allow you to enable detailed debugging logs. The information in these log files can help you troubleshoot problems that occur outside of either the database agent or RMAN. Note the following with regard to these logs:
These logs do not reveal errors that occur when RMAN is running unless those errors also affect NetBackup. Oracle might (or might not) write to the NetBackup logs for errors in the application. Your best sources for Oracle error information are the logs provided by Oracle. Generally, each debug log corresponds to a NetBackup process and executable. However, for an RMAN backup, the debug log is created in the dbclient directory, which has no corresponding executable.
For information about the debugging log files, see the NetBackup Troubleshooting Guide and the /usr/openv/netbackup/logs/README.debug file.
182 Troubleshooting NetBackup reports
Enabling logging
To enable the database agent logs 1 Create the following directories on the client:
/usr/openv/netbackup/logs/bpbackup /usr/openv/netbackup/logs/bpbkar /usr/openv/netbackup/logs/bpdbsbora /usr/openv/netbackup/logs/bphdb /usr/openv/netbackup/logs/bporaexp /usr/openv/netbackup/logs/bporaimp /usr/openv/netbackup/logs/bprestore /usr/openv/netbackup/logs/tar /usr/openv/netbackup/logs/dbclient
For example:
cd /usr/openv/netbackup/logs mkdir bphdb
For 64-bit, also create the following directories

/usr/openv/netbackup/logs/bporaexp64 /usr/openv/netbackup/logs/bporaimp64
Set the access permissions to 777 on these log directories. For example:
chmod 777 bphdb
Enable logging for the nbpem, nbjm, and nbrb scheduling processes, which use unified logging. NetBackup writes unified logs to /usr/openv/logs. You do not need to create log directories for processes that use unified logging. For information on using logs and reports, see the NetBackup Troubleshooting Guide.
Accessing the log files

The following sections describe the logs created when you create the log directories. Use a text editor to view the contents of the logs.
bphdb directory on the client

The /usr/openv/netbackup/logs/bphdb directory contains the following types of logs: obk_stdout.mmddyy Unless redirected elsewhere, NetBackup writes NetBackup for Oracle template or shell script output to this file.
Troubleshooting NetBackup reports
183
obk_stderr.mmddyy Unless redirected elsewhere, NetBackup writes NetBackup for Oracle template or shell script errors to this file. log.mmddyy bphdb is the NetBackup database backup binary. This log contains debugging information for the bphdb process. NetBackup for Oracle uses this client process for NetBackup for Oracle template or shell script execution. It is invoked when an automatic backup schedule is run.
dbclient directory on the client

The /usr/openv/netbackup/logs/dbclient directory contains the following execution log: log.mmddyy This log contains debugging information and execution status for the Oracle NetBackup client processes linked to the library program provided with NetBackup for Oracle. (This library program is, libobk.)
bpdbsbora directory on the client

The /usr/openv/netbackup/logs/bpdbsbora directory contains the following execution log: log.mmddyy This log contains debugging information and execution status for the NetBackup for Oracle backup and recovery wizards and for the bpdbsbora command line utility. This log also contains the debugging information and execution status information that is generated when an Oracle template is run from an automatic schedule (when bphdb invokes bpdbsbora to run the template).
bporexp64 and bporaexp directories on the client

The /usr/openv/netbackup/logs/bporaexp (bporaexp64) directory contains the following execution log: log.mmddyy.log This log contains debugging information and execution status for the bporaexp (bporaexp64) program that performs XML exports.
184 Troubleshooting Setting the debug level
bporaimp and bporaimp64 directories on the client

The /usr/openv/netbackup/logs/bporaimp (bporaimp64) directory contains the following execution log: log.mmddyy This log contains debugging information and execution status for the bporaimp (bporaimp64) program that performs XML imports.
Setting the debug level

You can control the amount of information written to the debugging logs in the /usr/openv/netbackup/logs/ directories by changing the debug level. Typically, the default value of 0 is sufficient. However, Technical Support might ask you to set the value higher when a problem is being analyzed. You can set a debug level to a value ranging from 0 to 5. A level of 5 provides the most detail. To enable detailed logging
Enable detailed logging by entering the following line in the bp.conf file:
VERBOSE = 5
NetBackup server reports

NetBackup provides other reports that are useful in isolating problems. One such report is All Logs Entries on the server. For information on server reports, see the NetBackup Administrators Guide.
RMAN utility logs

RMAN uses a command language interpreter, and it can be run in interactive or batch mode. You can use the following syntax to specify a log file on the command line to record significant RMAN actions: msglog logfile_name
Additional XML export and import logs

The bporaexp and bporaimp utilities perform error logging and tracing in the file specified by the LOG parameter. The log files contain Oracle errors and other errors that are not related to NetBackup. When bporaexp and bporaimp are used and the backup images are written to a storage unit, these errors are also logged in the NetBackup debug logs. These logs appear in the following directories: /user/openv/netbackup/logs/bporaexp
Troubleshooting Troubleshooting backup or restore errors
185
/user/openv/netbackup/logs/bporaimp When bporaexp and bporaimp are being used and the backup images are written to an operating system directory, the file specified by the LOG= parameter is the only source of error logging and tracing.
Troubleshooting backup or restore errors

An RMAN backup error can originate from NetBackup or from Oracle, as follows:
On the NetBackup side, an error can be from the API, from the NetBackup server or client, or from Media Manager. On the Oracle side, an error can be from RMAN or from the target database.
Symantec suggests that you use the following steps when troubleshooting a failed operation: 1 2 Check the logs to determine the source of the error. Troubleshoot each stage of the backup or restore.
The following sections describe these steps in detail.
Checking the logs to determine the source of the error

Determine whether the error is from NetBackup or the RMAN. If the error came from NetBackup, go to Troubleshooting each stage of the backup or restore on page 186. The majority of the problems setting up NetBackup and RMAN concern the linking process not working, an error with the RMAN script that is being run, problems with the NetBackup policy being set up incorrectly, or problems allocating backup media. Note: Ensure that server and user-directed regular file system backups work for the client prior to debugging the Oracle RMAN backups. Try backing up the Oracle binaries.
The first place to start is to run rman from the command line rather than having the NetBackup scheduler run a script. These troubleshooting steps assume you are running rman from the command line. If NetBackup and RMAN are communicating, look for a log in /usr/openv/netbackup/logs/dbclient. If a log file exists and you are having problems, this usually indicates a configuration problem within the NetBackup policy or media availability. For example:
186 Troubleshooting Troubleshooting backup or restore errors
cd /usr/openv/netbackup/logs/dbclient ls log.123098
The preceding example shows how to check for a log files presence. The presence of a log file indicates that NetBackup and Oracle RMAN are linked correctly.
If NetBackup and Oracle rman are not communicating, you do not see a log in /usr/openv/netbackup/logs/dbclient. Logs are not created in this directory if the permissions are not set correctly for the Oracle user to write to the directory. A full permission setting is best. Type chmod 777 to open up all permissions. If you receive an error such as one of the following, it often means that the link step (oracle_link) failed:
RMAN-00571:============================================================ RMAN-00569:=============== ERROR MESSAGE STACK FOLLOWS: =============== RMAN-00571:============================================================ RMAN-03009: failure of allocate commands on t1 channel at 05/11/2005 09:29:37 ORA-19554: error allocating device, device type: SBT_TAPE, device name: ORA-27211: Failed to load Media Management Library Additional information: 25
If you suspect a link failure, refer to Linking the library on page 52.
Use the following procedure to verify that the RMAN script works correctly:
To verify the RMAN script 1 2 3 4 Use RMAN to make a backup directly to disk. Do not use NetBackup. Use RMAN with NetBackup to create a backup. Check the /usr/openv/netbackup/logs/dbclient directory permissions. They should be set to 777. Look for a log file in /usr/openv/netbackup/logs/dbclient If no log file exists, libobk is not linked into Oracle properly. For the relinking procedure, see Linking the library on page 52.
Troubleshooting each stage of the backup or restore

The following explains the sequence of events for an action initiated by RMAN and suggests solutions for problems that can occur at each point in the sequence. 1 rman starts. A backup or restore can be started in any of the following ways:
From an RMAN backup or restore initiated from the operating system prompt such as:
Troubleshooting Troubleshooting backup or restore errors
187
rman target user/pwd[@TNS_alias] \ rcvcat user/pwd[@TNS_alias]\ cmdfile RMAN_script_file_name where the RMAN_script_file_name is fully qualified.
Using a template run from the NetBackup client interface or from bpdbsbora. Manually from the administrator interface on the master server.
Automatically by an automatic backup schedule. If an error occurs at this point, check the RMAN log. 2 RMAN verifies its environment and then issues requests to the API. Some information, such as the NetBackup version, API versions, trace file name, and NetBackup signal handlers, is registered with RMAN. An error at this point is usually due to a problem with client and server communication. Check the messages in the bprd and bpcd logs for clues. Also verify the bp.conf entries on the client. RMAN issues a backup or restore request. The API gathers necessary parameters and sends the backup or restore request to the NetBackup server. The API waits until both the server and client are ready to transfer data before returning. The API then sends this information to the master servers bprd process. To troubleshoot a problem in this part of the first sequence, examine the following file: /usr/openv/netbackup/logs/dbclient/log.mmddyy If the bprd process failed, check the logs for bprd and bpbrm. A failure at this point is frequently due to bad NetBackup server or Oracle policy configuration parameters. NetBackup can usually select the correct Oracle policy and schedules, but NetBackup can select a policy or schedule in error if there are several Oracle policies in its database. Try setting the SERVER and POLICY values in the bp.conf file on the client or by setting environment variables. For example, the following C Shell setenv commands specify the Oracle policy, schedule, and server for NetBackup to use: setenv NB_ORA_POLICY policyname setenv NB_ORA_SCHED application_backup_schedule_name setenv NB_ORA_SERV NetBackup_server 4 RMAN issues read or write requests to the API, which then transfers data to or from the NetBackup server. A failure here is probably due to NetBackup media, network, or timeout errors.
188 Troubleshooting Troubleshooting XML export or XML import errors
RMAN tells the API to close the session. The API waits for the server to complete its necessary actions (for example, it verifies the backup image) and then exits. An error can originate from either NetBackupor RMAN.
RMAN aborts if it encounters an error while reading a data file during the backup (for example, if Oracle blocks are out of sequence). It also aborts if NetBackup sends a bad backup image during the restore. NetBackup might return an error code to the API if for some reason it could not complete the backup successfully.
Troubleshooting XML export or XML import errors

An XML export or import error can originate from NetBackup or from Oracle, as follows:
On the NetBackup side, an error can be from the bporaexp or bporaimp programs, the NetBackup server or client, or Media Manager. On the Oracle side, an error can be from the target database.
Symantec suggests that you use the following steps when troubleshooting a failed operation: 1 2 Check the logs to determine the source of the error. Troubleshoot each stage of the XML export or XML import.
The following sections describe these steps in detail. These sections describe the log files from the bporaexp and bporaimp commands. For 32-bit Oracle, the logs are created in /usr/openv/netbackup/logs/bporaexp or /usr/openv/netbackup/logs/bporaimp. For 64-bit Oracle, the logs are created in /usr/openv/netbackup/logs/bporaexp64 and /usr/openv/netbackup/logs/bporaimp64. The following sections reference the bporaexp and bporaimp directories. If you are using 64-bit Oracle, look in the bporaexp64 and bporaimp64 directories.
Checking the logs to determine the source of the error

To check the logs 1 Check the bporaexp or bporaimp log. If the LOG parameter is specified in the bporaexp or bporaimp commands parfile, the commands write logs to the file specified as the argument to the LOG parameter. The commands write log information to the screen if LOG is not specified.
Troubleshooting Troubleshooting XML export or XML import errors
189
For example, the following common problems are caused by incorrect installation or configuration:

The ORACLE_HOME environment variable was not set.
The bporaexp or bporaimp program was unable to connect to the target database. When bporaexp and bporaimp are being used and the backup images are being written to an operating system directory, these logs are the only source of error logging and tracking. 2 Check the NetBackup logs. The first NetBackup log to check is /usr/openv/netbackup/logs/bporaexp/log.mmddyy or /usr/openv/netbackup/logs/bporaimp/log.mmddyy. Examine these logs for messages that show how to determine the source of an error. These logs are written by the NetBackup client and contain the following:
Requests from bporaexp and bporaimp
Activities between bporaexp and bporaimp and NetBackup processes If /usr/openv/netbackup/logs/bporaexp/log.mmddyy /usr/openv/netbackup/logs/bporaimp/log.mmddyy do not contain any messages, the following conditions could be present:
bporaexp or bporaimp terminated before requesting service from NetBackup.
bphdb (if started by the scheduler or graphical user interface) did not start the template or shell script successfully. Check the bphdb logs for stderr and stdout files. Try to run the XML export or XML import template or script file from the command line to determine the problem. Usually, the error is due to a file permission problem for bphdb itself or for the export or import script file. Ensure that the full XML export or import script file name is entered correctly in the Backup Selections list of the Oracle policy configuration, or for templates, that the name is correct. Logs are not created in this directory if the permissions are not set for the Oracle user to write to the directory. The full permissions setting, chmod 777, is best.
Troubleshooting each stage of the XML export or XML import

The information in this section does not apply to you if DIRECTORY is specified in bporaexp or bporaimp commands parfile. The following explains the sequence of events for an action initiated by bporaexp or bporaimp in NetBackup mode; that is, when DIRECTORY is not
190 Troubleshooting Troubleshooting XML export or XML import errors
specified in the bporaexp or bporaimp commands parfile. It suggests solutions for problems that can occur at each point in the sequence. To troubleshoot by stage 1 bporaexp or bporaimp starts. An export or import can be started in any of the following ways:
Command line from the system prompt. For example: bporaexp parfile = parameter_filename bporaimp parfile = parameter_filename Using a template run from the NetBackup client GUI or bpdbsbora. Manually from the NetBackup administration console on the master server.
Automatically by an automatic export schedule. If an error occurs at this point, check the bporaexp or bporaimp log.
bporaexp or bporaimp verifies its environment and then connects to Oracle and NetBackup. Oracle connect errors can be caused by an Oracle environment problem, a database problem, an incorrect userid, or an incorrect password. A NetBackup error at this point is usually due to a problem with client and server communication. Check the messages in the bprd and bpcd logs for clues. Also verify the bp.conf entries on the client. bporaexp or bporaimp issues a backup or restore request. bporaexp or bporaimp gathers necessary parameters, sends the backup or restore request to the NetBackup server, and waits until both the server and client are ready to transfer data before proceeding. The NetBackup client interfaces gather information from the following places:
The environment, including bporaexp and bporaimp parameter files. If you are using templates, the parameter files are generated from the template. If you are using scripts, you have to generate the parameter file manually.
The users bp.conf and /usr/openv/netbackup/bp.conf files on the client. This information is sent to the master servers bprd process. To troubleshoot a backup problem in this part of the sequence, examine the following file: /usr/openv/netbackup/logs/bporaexp/log.mmddyy If the bprd process failed, check the bprd and bpbrm logs.
Troubleshooting Troubleshooting the browser interface and wizards
191
Frequently, incorrect NetBackup server or Oracle policy configuration parameters cause failures at this point. NetBackup can usually select the correct Oracle policy and schedules, but NetBackup can select a policy or schedule in error if there are several Oracle policies in its database. Try setting the SERVER and POLICY values in the bp.conf file on the client or by setting the following bporaexp parameters:
NB_ORA_POLICY=policyname NB_ORA_SCHED=schedule NB_ORA_SERV=NetBackup_server NB_ORA_CLIENT=NetBackup_client
To troubleshoot a restore, examine the following log file: /usr/openv/netbackup/logs/bporaimp/log.mmddyy Make sure that the correct NetBackup server and NetBackup client values are being used by setting the following bporaimp parameters:
NB_ORA_SERV=NetBackup_server NB_ORA_CLIENT=NetBackup_client
Set these parameters to the same values that were used for the XML export operation. 4 bporaexp or bporaimp issues read or write requests to the NetBackup client, which then transfers data to or from the NetBackup server. bporaexp builds an SQL query for each table being archived, and it uses the Oracle Call Interface (OCI) to run the query. The query results are translated into XML. The XML output is passed to the NetBackup client interfaces. The reverse process is used by bporaimp. That is, XML data is restored, parsed, and inserted into the database. A failure here is probably due to an Oracle error, or to a NetBackup media, network, or timeout error. bporaexp or bporaimp tells the NetBackup client to close the session and disconnects from the Oracle database. The NetBackup client waits for the server to complete its necessary actions (backup image verification and so on) and then exits.
Troubleshooting the browser interface and wizards

If you do not see the Oracle instance in your Backup, Archive and Restore interface, verify the following:

A NetBackup for Oracle license is installed on the master server. For browsing in the restore window, the policy type must be set to Oracle. Perform the following actions to change the client policy type:
192 Troubleshooting Troubleshooting NetBackup for Oracle with Snapshot Client
a b c
On the Actions menu, select Specify NetBackup Machines and Policy type. In the Policy type drop down list, select Oracle. Click OK.
The oratab file is in the correct location (/etc/oratab or /var/opt/oracle/oratab) and contains all of the available Oracle SIDs.
If you have trouble connecting to the Oracle database, verify the following:

Make sure the database is in a mount or open state. Make sure that your login ID and password have Oracle SYSDBA privileges. Initially, NetBackup for Oracle attempts OS Authentication to log on. If that fails, you are prompted for a user name, password, and an optional Transparent Network Substrate (TNS) alias. The user name and password you enter must have SYSDBA privileges. In a clustered environment, failure to connect to the database can mean a problem with the network configuration. The browser must connect locally. However, in some environments, all connections are considered to be remote connections, even a connection to a local database. This is true, for example, in an Oracle Real Application Clusters (RAC) environment. In such cases, you must make the connection using a TNS alias.
In a Linux environment, Oracle backups and restores fail if the Linux login is not the Oracle user. In such cases, Oracle generates the following message:
INF - ORA-19554: error allocating device, device type: SBT_TAPE, device name: INF - ORA-27211: Failed to load Media Management Library
If you want to start an Oracle job as someone other than an Oracle user, augment the default shared library search path. Use the Linux ldconfig(8) command to add $ORACLE_HOME/lib to the search path.
Troubleshooting NetBackup for Oracle with Snapshot Client

In addition to the debug logs used for troubleshooting problems that occur with NetBackup and NetBackup for Oracle described in the previous sections, additional debug logs are used for troubleshooting NetBackup for Oracle with Snapshot Client. Snapshot Client backup and debug messages are written to the following subdirectories of: /usr/openv/netbackup/logs/
bpbrm on the NetBackup media server
Troubleshooting Minimizing timeout failures on large database restores
193
bptm/bpdm on the NetBackup media server online_util on the NetBackup client and alternate client bpbkar on the NetBackup client and alternate client bpfis on the NetBackup client and alternate client bppfi on the NetBackup client or alternate client
Snapshot Client restore and debug messages are written to the following subdirectories on the NetBackup master server:

bprestore. This is almost always a client log. bprd. bpbrm. This is always a media server log. bptm/bpdm. This is always a media server log. tar. This is always a client log.
Additional troubleshooting information, including troubleshooting installation problems, is available in the NetBackup Snapshot Client Administrator's Guide.
Minimizing timeout failures on large database restores

Large database restores sometimes fail when multiple restore sessions compete for resources. In this situation, a restore session can be delayed while waiting for media or device access. If the delay is too long, the restore session times out. Use the following procedures to minimize session timeouts and to allow the restores to complete successfully. To minimize database session timeouts 1 2 In the NetBackup administration console, expand NetBackup Management > Host Properties > Clients Set the Client read timeout property to a large value. The default for the Client read timeout setting is 300 seconds (5 minutes). For database agent clients, increase the value significantly from the value recommended in the NetBackup Administrators Guide, Volume 1. For example, change this setting to 30-60 minutes to minimize timeout errors. Click OK for each client.
To minimize loading and unloading of tapes You can minimize excessive unloading and reloading of tapes between multistreamed backups by making changes on the NetBackup media server.
194 Troubleshooting Minimizing timeout failures on large database restores
In the /usr/openv/netbackup/bp.conf file on the NetBackup media server, add the following options:

MEDIA_UNMOUNT_DELAY. MEDIA_REQUEST_DELAY. Use this variable only with non-robotic drives, such as tape stackers.
Appendix
Oracle 9i and 10g Real Application Clusters

This appendix includes the following topics:

Virtual names on page 195 Archiving schemes on page 196 Backing up a database on page 199 Restoring a database on page 200 Restoring archive logs on page 201
In an Oracle9i or Oracle 10g Real Application Clusters (RAC) environment, many Oracle instances exist on separate servers, each with direct connectivity to a single Oracle database. All the servers can run transactions concurrently against the same database. Should any single server or instance fail, processing continues on the surviving servers. RAC supports all Oracle backup features that are available in exclusive mode, including both online and offline backups of either an entire database or individual tablespaces.
Virtual names
A virtual name is a network host name resource (mapped to a IP address) that is associated with an application. If it is possible, virtual names should be used for the client and server nodes. Using a virtual node name for the client allows you to specify a single client entity for all of the Oracle backups. This allows NetBackup to perform a restore to any physical node. If a virtual client name is not used, a regular restore can only be performed from the node associated to the client name specified on the backup. Another possible solution in this environment is to use an alternate client restore.
196 Archiving schemes
Archiving schemes
The preferred RAC configuration uses a cluster file system archiving scheme. In this scheme, each node writes to a single Cluster File System (CFS) archived log destination and can read the archived log files of the other nodes. Figure A-1 on page 196 depicts a CFS archiving scheme. Figure A-1 CFS archiving scheme
CFS archive destination
Node 1
Database data files
Node 2
If the CFS solution is not available, Oracle recommends a scheme like that in Figure A-2 on page 197. In that figure, each node archives to a local directory and writes a copy to each of the other nodes archive directories. The locations are shared between the nodes (with read and write permissions) by NFS mounting the directory (UNIX) or sharing the locations (Windows). Figure A-2 Non-CFS local archiving scheme with archive sharing
Archive destination 1
Database data files
Node 1 NFS mount or Shared location read and write access Physically attached Logically attached
Node 2
A scheme similar to the previous one exists if each node archives to a local directory, as in Figure A-3 on page 198, and the locations are shared (read-only) with the other nodes in the cluster. These locations are shared between the nodes by NFS-mounting the directory (UNIX) or sharing the locations (Windows). Therefore, each node can read each archive destination. Figure A-3 Non-CFS local archiving scheme with archive read-only sharing
Database data files
Node 1 NFS mount or Shared location read and write access Physically attached Logically attached
Node 2
199 Backing up a database
The simplest archiving scheme is local archiving with no sharing, as shown in Figure A-4 on page 199. Each node writes only to the local destination, and no access is given to the other nodes in the cluster. Figure A-4 Non-CFS local archiving scheme with no archive sharing
Database data files
Node 1
Node 2
For more information, including configuration and additional archiving scheme examples, see your Oracle documentation.
Backing up a database
If you are in a RAC environment and you chose one of the archive log schemes described in the previous section, you can perform a backup and a restore using typical RMAN scripts. In the following example, RMAN backs up the database, including all of the archive logs. This example assumes that the archive logs are accessible by each node in the cluster. If they are not, then the archive logs need to be backed up separately on each node.
200 Restoring a database
RUN { ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; SEND 'NB_ORA_CLIENT=$NB_ORA_CLIENT, NB_ORA_SERV=$NB_ORA_SERV'; BACKUP DATABASE; sql 'alter system archive log current'; RELEASE CHANNEL ch00; ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; SEND 'NB_ORA_CLIENT=$NB_ORA_CLIENT, NB_ORA_SERV=$NB_ORA_SERV'; BACKUP ARCHIVELOG ALL ; RELEASE CHANNEL ch00; }
Restoring a database
Restoring the database using a virtual name or restoring from the node where the backup was performed is straightforward and identical to a typical RMAN restore.
Example
In this example, the client is saturn and the server is jupiter. The names saturn and jupiter can be either the physical names or the virtual names of the nodes in the cluster. The following example restores the entire database from any node:
RUN { ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; SEND 'NB_ORA_CLIENT=saturn, NB_ORA_SERV=jupiter'; RESTORE DATABASE; RECOVER DATABASE; RELEASE CHANNEL ch00; }
Troubleshooting
An RMAN restore to one node of a cluster can fail with a status code 39. This happens when the following situation is present:
The NB_ORA_CLIENT environment variable is set to the virtual host name of the cluster. and The CLIENT_NAME variable in the user or master bp.conf file on the client is set to the virtual host name of the cluster.
201 Restoring archive logs
To remedy this, set the CLIENT_NAME variable to the node name. For more information on restores and redirected restores, see Performing a restore on page 117.
Restoring archive logs

You can use the typical RMAN script to restore the archive logs under the following circumstances:
If the remote archived log destinations allow write access. See Figure A-2 on page 197. If the archive logs reside on a CFS. See Figure A-1 on page 196.
In the examples that follow, the client is saturn and the server is jupiter. The names jupiter and saturn can be either the physical names or the virtual names of the nodes in the cluster. The following example restores all of the archive logs:
RUN { ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; SEND 'NB_ORA_CLIENT=saturn, NB_ORA_SERV=jupiter'; RESTORE ARCHIVELOG ALL; RELEASE CHANNEL ch00; }
If the remote archive logs destinations do not allow write access, use a script such as the following to restore the archive logs:
RUN { ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; SEND 'NB_ORA_CLIENT=saturn, NB_ORA_SERV=jupiter'; SET ARCHIVELOG DESTINATION TO <directory>; RESTORE ARCHIVELOG ALL; RELEASE CHANNEL ch00; }
where <directory> is the directory into which you copied the archive logs. Use a script like the preceding one if your configuration is like that shown in Figure A-3 on page 198 and Figure A-4 on page 199.
202 Restoring archive logs
Appendix
Script-based block-level incremental (BLI) backups without RMAN

This appendix contains the following topics:

Script-based BLI backup overview on page 204 Installation requirements on page 206 Configuring script-based BLI backups on page 207 Performing backups and restores on page 217 Troubleshooting on page 220
NetBackup for Oracle with Snapshot Client extends the capabilities of NetBackup to back up only changed data blocks of Oracle database files. NetBackup recommends using RMAN-based BLI backups, which allow the use of templates and remain tightly integrated with Oracle administration. For more information on BLI backups, see NetBackup for Oracle with Snapshot Client on page 147. If you choose to use script-based BLI backups without RMAN, this chapter describes the necessary configuration.
204 Script-based BLI backup overview
Script-based BLI backup overview

A BLI backup backs up only the changed data blocks of Oracle database files. NetBackup for Oracle script-based BLI performs backups using the Storage Checkpoint facility in the Veritas File System (VxFS) available through the Veritas Storage Foundation for Oracle. For more information on BLI backups, see Configuring block-level incremental backups on page 167.
Terms
The following list contains terms that might be new to you: Term Definition
cold database backup A cold database backup is taken while the database is offline or closed. BLI backup shuts down the database and performs either full or block-level incremental backups. This backup method is also referred to in Oracle documentation as a consistent whole database backup or a closed backup. The data from a cold backup is consistent, resulting in easier recovery procedures. hot database backup A hot database backup allows the database to be online and open while the backup is performed. With the Storage Checkpoint facility, this backup method runs database backups in parallel so a database does not need to be in backup mode for a long time. To use hot backups, the database must be in ARCHIVELOG mode. BLI backup uses the alter tablespace begin backup command and the alter tablespace end backup command to put the database into and take it out of backup mode. This method is also referred to in Oracle documentation as an inconsistent whole database backup or open backup. Unlike the cold database backup method, the data in hot backups is fuzzy or inconsistent until the appropriate redo log files (online and archived) are applied after the restore operation to make the data consistent.
205 Script-based BLI backup overview
Term
Definition
quick freeze database A quick freeze database backup is a combination of the traditional backup cold and hot database backup. A quick freeze database backup initially shuts down the database to create a Fulldata Storage Checkpoint for a consistent database backup. Because the VxFS Fulldata Storage Checkpoint is a snapshot of the database image, an Oracle instance can be brought back online as soon as the Fulldata Storage Checkpoint is created. The Oracle instance can remain online while NetBackup is backing up the database using the Fulldata Storage Checkpoint. A quick freeze database backup is different from the traditional Oracle online backup. Quick freeze database backup is also an online database backup, but it requires the database to be brought down briefly to take a snapshot or Fulldata Storage Checkpoint of the database image. The Fulldata Storage Checkpoint is created in a few seconds and the database can be restarted immediately after the Fulldata Storage Checkpoint is taken. A backup image from a quick freeze database backup is equivalent to a backup image from a cold database backup. You can choose to use this backup method when configuring BLI notify scripts. See Creating notify scripts on page 213.
How BLI backups and restores work

A BLI backup performs database backups by obtaining the changed blocks identified by the Storage Checkpoints. BLI backups can also be performed while the database is online or offline. As with Storage Checkpoints, you must enable archive log mode to perform online BLI backups. A BLI backup places the tablespaces in backup mode, takes a Storage Checkpoint, and then performs the backup. You specify how and when to back up the database when configuring the NetBackup notify scripts. For example, suppose at 4:00 p.m. you lost a disk drive and its mirrored drive. There are a number of user tablespaces on the disk drive, and you want to recover all committed transactions up to the time you lost the drive. Because the BLI backup facility lets you perform more frequent backups, you did an online differential incremental backup at 1:00 p.m. You recover by shutting down the database, installing new replacement disk drives, and restoring all the datafiles with NetBackup. Then you apply the archive logs to recover the tablespaces on the failed drive. If you used Fulldata Storage Checkpoints, the extra redo logs generated during an online backup are small, the media recovery part of the database recovery takes very little time. Moreover, because you have a recent backup, the entire recovery is accomplished quickly.
206 Installation requirements
Installation requirements
To verify the installation requirements 1 Make sure that the following products are properly installed and configured:

NetBackup 6.5 A supported level of Oracle NetBackup for Oracle 6.5 Veritas Storage Foundation for Oracle
Verify licensing. The products must have valid licenses. To check for licenses, enter the following commands based on your version: For VxFS versions earlier than 3.5:
# vxlicense -p
For VxFS versions 3.5 or later:

# vxlicrep
The command displays all the valid licenses installed on the system. If you have valid licenses, the Storage Checkpoint feature and the Veritas Storage Foundation for Oracle appear in the list. 3 Verify that both the NetBackup server (master and media) and client software are working properly. Particularly, verify that you can back up and restore typical operating system files from the client.
File system and Storage Checkpoint space management

To support BLI backups, the VxFS file systems need extra disk space to keep track of the block change information. The space required depends on the database workload while the backup is running. If the database is offline during the entire backup window (a cold database backup) or you are using Nodata Storage Checkpoints, the additional space required by each file system is about 1% of the file system size. If the database is online while the backup is running (a hot database backup or quick freeze database backup using Fulldata Storage Checkpoints), the additional space required by each file system depends on the duration of the backup and the database workload. If the workload is light during the backup or the backup window is relatively short (such as for incremental backups), an additional 10% of the file system size is usually sufficient. If the database has a heavy workload while a full backup is running, the file systems may require more space.
207 Configuring script-based BLI backups
Configuring script-based BLI backups

The following sections describe the configuration process.
Creating NetBackup policies for script-based BLI backup

To allow full and incremental backups, you must add at least one Standard type policy to NetBackup and define the appropriate schedules for that policy. Use the NetBackup administration console to add policies. NetBackup policies define the criteria for the backup. These criteria include the following:

Policy attributes Clients and the files or directories to be backed up on the client Storage unit to use Backup schedules
Most database NetBackup BLI backup policy requirements are the same as for file system backups. The differences or special requirements, where they exist, are defined in the following sections.
Number of policies required

A database BLI backup requires at least one Standard type policy. This policy usually includes the following:

One full backup schedule One incremental backup schedule One user-directed backup schedule for control files and archive logs
Only one backup stream is initiated for each backup policy during automatic backups. To enable multiple backup streams, define multiple policies for the same database. If you have more than one database SID, configure policies for each SID. If you intend to do simultaneous backups of more than one SID on the same file system, use Nodata Storage Checkpoints. Set the METHOD to NODATA_CKPT_HOT. For example, to back up file systems F1, F2, F3, and F4 with two streams, you need to define two policies (P1 and P2) with F1 and F2 backed up in P1, and F3 and F4 backed up in P2. If you have one large file system that needs to be backed up with multiple streams, divide the files in the file system between different policies. After a file is added to a policy, it should stay in that policy. If you must rearrange the file list, do so only prior to a full backup.
If you have more than one policy defined for an Oracle instance, the instance is grouped by the NetBackup keyword phrase. Identify one of the policies as the POLICY_IN_CONTROL in the NetBackup notify scripts. This is the policy that performs database shutdowns and restarts. All policies with the same keyword phrase need to be configured to start simultaneously. Caution: Care must be taken when specifying the keyword phrase. A multistream backup is attempted if the backup process finds more than one policy with the following characteristics: each policy has the BLI attribute set, each policy is active, each policy contains the same client, and each policy has an identical keyword phrase. Typical failure status is 74 - timeout waiting for bpstart_notify to complete. For more information, see Troubleshooting on page 220. You can check the file systems on the backup client to see if they are included in one of the NetBackup policies on the server. To see if you need to add any new file systems to the NetBackup policies, run the following commands from the server on a regular basis, perhaps as a cron(1) job:
# cd /usr/openv/netbackup/bin/goodies/ # ./check_coverage -coverage -client mars -mailid \nbadmin
The preceding command generates the following output and mails it to the specified mailid:
File System Backup Coverage Report (UNIX only) ----------------------------------------------Key: * - Policy is not active UNCOVERED - Mount Point not covered by an active policy MULTIPLE - Mount Point covered by multiple active policies CLIENT: mars Mount Point ----------/ /home /oradata1 /oradata2 /oradata3 /opt /oracle /stand /usr /var
Device -----/dev/vg00/lvol3 /dev/vg00/lvol5 /dev/dsk/c1t0d0 /dev/dsk/c1t0d0 /dev/nbuvg/nbuvol /dev/vg00/lvol6 /dev/vg00/oracle /dev/vg00/lvol1 /dev/vg00/lvol7 /dev/vg00/lvol8
Backed Up By Policy ------------------production_servers production_servers block_incr1 block_incr1 UNCOVERED production_servers production_servers production_servers production_servers production_servers
Notes -----
If there is an UNCOVERED file system that is used by Oracle, add it to one of the NetBackup policies so that all the necessary file systems are backed up at the same time.
Note: After a file system is added to a policy, it is a good idea to keep the file system in that policy. If you change the policy, NetBackup performs a full backup the next time backups are run even if an incremental backup is requested.
Policy attributes
NetBackup applies policy attribute values when it backs up files. Certain attributes must be set for BLI backup:

Policy Type. Set to Standard. Perform block level incremental backups. Select to enable BLI backups. If the BLI attribute is not enabled, NetBackup uses the standard method to back up the files in the file list. Job Priority. Set so that the BLI backup policies run before other policies. Keyword phrase. Define as the Oracle instance name ($ORACLE_SID) in each of the policies for the same instance. Multistream backups start when all the policies with a particular keyword phrase complete their respective startup scripts. If you have multiple Oracle instances (SIDs) use a separate set of policies for each SID. If the SIDs are backed up simultaneously and any share a common file system for data files, use Nodata Storage Checkpoints. Set the METHOD to NODATA_CKPT_HOT.
Note: Do not change a keyword phrase after it is set in a policy. The keyword phrase is used in naming Storage Checkpoints. Changing the keyword phrase necessitates a full backup even if an incremental backup is requested. The NetBackup Administrators Guide, Volume I describes other policy attributes and how to configure them.
Client list
The client list specifies the clients upon which you configured a BLI backup. For a database backup, specify the name of the machine upon which the database resides. Specify the virtual hostname if clustered.
Backup selections list

The backup selections list specifies a list of directories and files to back up. The list must contain all the database files or their directory names. Using directory names, rather than file names, ensures that new database files added to an
existing configuration are backed up without having to update the file list. Use the check_coverage script to make sure all file systems are backed up. If you are using the Quick I/O interface, you need to specify both the Quick I/O file name and the associated hidden file in the file list (for example, dbfile and .dbfile), or you need to specify the directory that contains both files. NetBackup does not follow the symbolic links to automatically back up the hidden file if you enumerate only the dbfile explicitly in the backup selections list. They are both included if you enumerate their common directory. When the NetBackup scheduler invokes an automatic backup schedule, it backs up the files one at a time, in the same order they appear in the backup selection list. Oracle does not recommend backing up the online redo log, so it is recommended that you place online redo log files in a different file system than datafiles, archive log files, or database control files. Do not include the online redo log files in the file list.
Schedules
The NetBackup server starts these schedule types:

Full Backup Differential Incremental Backup Cumulative Incremental Backup
Each BLI backup policy must include one full backup schedule and at least one incremental backup schedule. In addition, you must designate one of the BLI backup policies as the POLICY_IN_CONTROL. The policies for each stream must have the same types of schedules. The NetBackup Administrators Guide, Volume I describes other schedule attributes and how to configure them.
Schedule types
You can configure the following types of schedules:
User-directed backup schedule. The user-directed backup schedule encompasses all the days and times when user-directed backups are allowed to occur. Set the backup window as described in Schedule times on page 211. The policies for each stream must have the same types of schedules. Automatically initiated backup schedules. Include server-initiated backup schedules to specify the days and times for NetBackup to automatically start backups of the files specified in the policy file list. Set the backup window as described in Schedule times on page 211.
Schedule times
For server-initiated full and incremental backup schedules, set the start times and durations to define the appropriate windows for the backups. Follow the same procedure used to define backup schedules for other policies. For more information on these procedures, see the NetBackup Administrators Guide, Volume I. The backups are started by the scheduler only within the backup window specified. For the POLICY_IN_CONTROL, include in the user-directed backup schedule the time periods when the BLI backup policies complete.
Retention
Set the retention level and periods to meet user requirements.
Example Oracle BLI backup policy

The following example shows attributes and schedules for an Oracle BLI backup policy. Use the NetBackup Administration Console to add policies.
Policy Name: oracle_backup1 Policy Type:Standard Active:yes Block level incremental:yes Job Priority:0 Max Jobs/Policy:1 Residence:oracle_tapes Volume Pool:NetBackup Keyword:ORA1 Client List: Sun4 Solaris2.6 mars HP9000-800 HP-UX11.00 mars Backup Selections List: /oradata/oradata1 Schedule: full Type: Full Backup Frequency: 1 week Retention Level: 3 (one month) Daily Windows: Sunday 18:00:00 --> Monday 06:00:00 Monday 18:00:00 --> Tuesday 06:00:00 Tuesday 18:00:00 --> Wednesday 06:00:00 Wednesday 18:00:00 --> Thursday 06:00:00 Thursday 18:00:00 --> Friday 06:00:00 Friday 18:00:00 --> Saturday 06:00:00 Saturday 18:00:00 --> Sunday 06:00:00 Schedule: incr Type: Differential Incremental Backup Frequency: 1 day Retention Level: 3 (one month) Daily Windows: Sunday 18:00:00 --> Monday 06:00:00
18:00:00 --> 18:00:00 --> 18:00:00 --> 18:00:00 --> 18:00:00 --> 18:00:00 --> Schedule: userbkup Type: User Backup Retention Level: 3 (one month) Daily Windows: Sunday 00:00:00 --> Monday 00:00:00 --> Tuesday 00:00:00 --> Wednesday 00:00:00 --> Thursday 00:00:00 --> Friday 00:00:00 --> Saturday 00:00:00 -->
Monday Tuesday Wednesday Thursday Friday Saturday
Tuesday Wednesday Thursday Friday Saturday Sunday
06:00:00 06:00:00 06:00:00 06:00:00 06:00:00 06:00:00
Sunday Monday Tuesday Wednesday Thursday Friday Saturday
24:00:00 24:00:00 24:00:00 24:00:00 24:00:00 24:00:00 24:00:00
In this example, the oracle_backup1 policy backs up all the files in /oradata/oradata1. The policy specifies a weekly full backup, a daily differential incremental backup, and a user-directed backup schedule. The archive logs and the control file are backed up using the user-directed schedule at the completion of the full or incremental backup.
Setting the maximum jobs per client global attribute

Set the Maximum Jobs per Client to the number of policies that have the same keyword phrase. This number can be greater than one when multiple job policies are defined to back up multiple file systems.
Creating directories for logging NetBackup activity

As a troubleshooting aid, enable the bpbkar, tar, and bpbackup debugging logs on the client as explained in NetBackup debug logs on page 221. You can delete these directories after completing testing.
Selecting a backup method

You can choose from the following backup methods when configuring BLI notify scripts:
Cold database backup. Set METHOD to SHUTDOWN_BKUP_RESTART. An offline backup where all database files are consistent to the same point in time. For example, when the database was last shutdown using typical methods. The database must stay shut down while the backup is running. Hot database backup. Set METHOD to ALTER_TABLESPACE.
An online backup of an open database. Hot backups are required if the database must be up and running 24 hours a day, 7 days a week.
Nodata Storage Checkpoint Hot. Set METHOD to NODATA_CKPT_HOT. A backup where the tablespaces are in backup mode for the duration of the backup and a Nodata Storage Checkpoint is used to reduce the amount of file system space consumed. Use this method if all of the following conditions are present:

You are backing up multiple Oracle instances. More than one instance shares the file system. The backup of the instances can overlap in time.
Quick freeze backup. Set METHOD to SHUTDOWN_CKPT_RESTART. A backup where all database files are consistent to the same point in time when the database was last shut down to take a Fulldata Storage Checkpoint. Unlike a cold backup, a quick freeze database backup requires only a brief offline period during the creation of the Fulldata Storage Checkpoint. After the Fulldata Storage Checkpoint is created, the database is online while the backup is running.
If the database is in ARCHIVELOG mode, you can use all four methods to back up the database. If the database is in NOARCHIVELOG mode, you can only select the cold backup or quick freeze backup. When using the cold and quick freeze database backups, the default shut down command used in the bpstart_notify.oracle_bli script is shutdown or shutdown normal. These commands wait for all users to log off before initiating the shut down. In some circumstances, even after all interactive users are logged off, processes such as the Oracle Intelligent Agent (Oracle dbsnmp account) can still be connected to the database, preventing the database shut down. Attempt to use the default shut down commands to shut down the database cleanly. Alternatively, you can use shutdown immediate to initiate the database shut down immediately.
Creating notify scripts

Create notify scripts that run on the clients to synchronize the backup operation and the database operation. You need a set of three notify scripts for each policy that is performing BLI backups. The scripts are named as follows and must be in the /usr/openv/netbackup/bin directory on the NetBackup client:

bpstart_notify.POLICY post_checkpoint_notify.POLICY bpend_notify.POLICY
To create the notify scripts, run the following script as root:
/usr/openv/netbackup/ext/db_ext/oracle/bin/setup_bli_scripts This script copies the sample notify script templates to /usr/openv/netbackup/bin and makes the necessary changes based on the information you provide. The notify script templates are located on the local machine in the following location: /usr/openv/netbackup/ext/db_ext/oracle/samples The following sections describe the information you need to supply when running setup_bli_scripts. For more information about using the notify scripts to back up your Oracle database, see Manual backups on page 218.
Identify the POLICY_IN_CONTROL

If you have more than one policy defined on the server for one Oracle instance, identify one of the policies as the POLICY_IN_CONTROL. This is the policy that initiates the database shutdown, startup, or alter tablespace commands. The POLICY_IN_CONTROL can be any policy (for example, the first policy defined). This variable is stored in the notify scripts.
Oracle environment variables

If you create notify scripts, or if you run setup_bli_scripts, you need to provide values for the following Oracle environment variables: Environment variable
ORACLE_DBA
Purpose
User name of the Oracle database administrator. Typically, oracle. $ORACLE_BASE of the Oracle instance. $ORACLE_HOME of the Oracle instance. Oracle instance ID ($ORACLE_SID) if it is different from the keyword. Directory in which the Oracle archive logs reside. Location to which a copy of the Oracle control file is written so that it can be backed up. sqldba, svrmgrl, or sqlplus command to start up or shut down the database. Path name for the Oracle startup parameter file (INIT.ORA). If you are using an Oracle SPFILE as your parameter file, do not set the ORACLE_INIT environment variable.
ORACLE_BASE ORACLE_HOME ORACLE_SID
ORACLE_LOGS ORACLE_CNTRL
SQLCMD
ORACLE_INIT
ORACLE_CONFIG
Purpose
Path name for the Oracle configuration file (CONFIG.ORA). Some database configurations use the CONFIG.ORA file to specify values for the database parameters that usually do not change. The CONFIG.ORA file can be called by the INIT.ORA file using an include statement.
Select a backup method

You must select a backup method to use when creating the notify scripts:
Cold backup. Set METHOD to SHUTDOWN_BKUP_RESTART. NetBackup shuts down the database, backs up the database, and then restarts the database. Hot backup. Set METHOD to ALTER_TABLESPACE. NetBackup uses the alter tablespace begin backup command to change the tablespaces to online backup mode, take a Fulldata Storage Checkpoint of the database file, and then use the alter tablespace end backup command to change the tablespaces back to normal mode. Nodata Storage Checkpoint Hot backup. Set METHOD to NODATA_CKPT_HOT. NetBackup uses the alter tablespace end backup command to change the tablespaces to online backup mode, take a Nodata Storage Checkpoint, and back up the tablespaces while in the backup mode. The tablespaces are taken out of backup mode by using the alter tablespace end backup command when the backup is complete. Quick freeze backup. Set METHOD to SHUTDOWN_CKPT_RESTART. NetBackup shuts down the database, creates the Fulldata Storage Checkpoint, and then restarts the database before the database backup starts.
Notify scripts for other policies

If you have more than one policy defined to support multiple backup streams, create a copy of the notify scripts for each policy defined. For example, assume that you have two policies defined, oracle_backup1 and oracle_backup2. Also assume that POLICY_IN_CONTROL is set to oracle_backup1. You also need to create notify scripts for policy oracle_backup2. The setup_bli_scripts script performs this step automatically.
Sample setup_bli_scripts session

The following sample session shows how to use setup_bli_scripts to create the notify scripts.
#/usr/openv/netbackup/ext/db_ext/oracle/bin/setup_bli_scripts
Please enter the user name of your Oracle administrator? orac901 ORACLE_BASE is the Oracle enviroment variable that identifies the directory at the top of the Oracle software and administrative file structure. The value of this variable is typically /MOUNTPOINT/app/oracle Please enter your ORACLE_BASE? /dbhome/oracle/orac901 ORACLE_HOME is the Oracle enviroment variable that identifies the directory containing the Oracle software for a given Oracle server release. The value of this variable is typically /dbhome/oracle/orac901/product/RELEASE Please enter your ORACLE_HOME? /dbhome/oracle/orac901 sqlplus will be used. The default "connect" statement that will be used to connect to the database is: "connect / as sysdba" Would you like to modify the connect and use a specific login? (y/n) n "connect / as sysdba" will be used.
Please enter the Oracle instance (ORACLE_SID) you want to back up? orac901 If you are using a CONFIG.ORA file, you need to specify where it is, so that it can be backed up. If this does not apply apply to your configuration, hit ENTER to go on. If this does apply to your configuration, specify the file path. Typically this would be: /dbhome/oracle/orac901/admin/orac901/pfile/configorac901.ora but this file could not be found. Enter your Oracle config file path or hit ENTER: To back up a copy of the Oracle control file, you need to specify a file path where Oracle can write a copy of the control file. Please enter the file path where Oracle is to write a copy of your control file? /dbhome/oracle/orac901/admin/orac901/pfile/cntrlorac901.ora To back up the Oracle archive logs, you need to specify their location.
Enter the directory path to your Oracle archive logs? /dbhome/oracle/orac901/admin/orac901/arch Do you have more archive log locations? (y/n): n
217 Performing backups and restores
Do you want the output of successful executions of the NetBackup scripts mailed to you? y Please enter the mail address to send it to? jdoe@company.com Do you want the output of unsuccessful executions of the NetBackup scripts mailed to you? y Please enter the mail address to send it to? jdoe@company.com There are 4 backup methods to choose from: ALTER_TABLESPACE - Use alter tablespace begin backup method NODATA_CKPT_HOT - Use alter tablespace begin backup with nodata ckpts SHUTDOWN_CKPT_RESTART - Shutdown, create the ckpt clones, and restart SHUTDOWN_BKUP_RESTART - Shutdown the DB, backup, and then restart If one of the methods requiring DB shutdown are selected, you may experience problems with timeouts if the database can't be shut down in a timely manner. You may want to change the shutdown command in the notify scripts to shutdown immediate, or you may have to increase the BPSTART_TIMEOUT value in the bp.conf file on the master server, or you may want to change the backup method to ALTER_TABLESPACE or NODATA_CKPT_HOT. Note: the default BPSTART_TIMEOUT value is 300 seconds. Do you want to use the ALTER_TABLESPACE method? y You now need to decide on how many NetBackup policies you will have backing up simultaneously. The first one you enter will be known as the POLICY_IN_CONTROL in the scripts and will perform any needed DB operations. When you create the policies on the NetBackup server, you will have to divide the filesystems between these policies. Please Please Please Please Please Please Please enter enter enter enter enter enter enter the the the the the the the name name name name name name name of of of of of of of the policy that will be the POLICY_IN_CONTROL? BLI_1 another policy or DONE to stop? BLI_2 another policy or DONE to stop? BLI_3 another policy or DONE to stop? BLI_4 another policy or DONE to stop? BLI_5 another policy or DONE to stop? BLI_6 another policy or DONE to stop? DONE
Performing backups and restores

After the installation and configuration is complete, you can use the NetBackup interfaces to start Oracle backups and restores.
Performing backups
Note: You must be the root user to perform all operations using the BLI backup software.
Automatic backups
The best way to back up databases is to set up schedules for automatic backups. To add a new schedule or change an existing schedule, follow the guidelines in Creating NetBackup policies for script-based BLI backup on page 207.
Manual backups
You can also run an Automatic Backup schedule manually using the NetBackup Administration Console. For information about performing manual backups of schedules, see the NetBackup Administrators Guide, Volume I. To perform a cold (offline) backup, set the environment variable METHOD in the bpstart_notify script on the client to SHUTDOWN_BKUP_RESTART. The bpstart_notify script shuts down the database before the backup begins and the bpend_notify script restarts the database after the backup completes. To perform a hot (online) backup using Fulldata Storage Checkpoints, make sure the database is running in ARCHIVELOG mode and set the variable METHOD to ALTER_TABLESPACE. The bpstart_notify script changes the tablespaces to online backup mode before the backup begins, and the post_checkpoint_notify script changes the tablespaces back to normal mode after the Fulldata Storage Checkpoints are created. To perform a Nodata Storage Checkpoint Hot (online) backup, make sure the database is running in ARCHIVELOG mode and set the environment variable METHOD in the bpstart_notify script to NODATA_CKPT_HOT. The bpstart_notify script changes the tablespaces to online backup mode before the backup begins. The bpend_notify script changes the tablespaces back to normal mode after the backup completes. To perform a quick freeze backup, set the environment variable METHOD in the bpstart_notify script to SHUTDOWN_CKPT_RESTART. The bpstart_notify script shuts down the database and the post_checkpoint_notify script restarts it immediately after the Fulldata Storage Checkpoints are created. Taking VxFS Fulldata Storage Checkpoints is very fast (within a minute), and with the NetBackup queueing delay for scheduling the backup jobs, the database down time is typically only a few minutes.
Backing up quick I/O files

A Quick I/O file consists of two components: a hidden file with the space allocated for it, and a link that points to the Quick I/O interface of the hidden file. Because NetBackup does not follow symbolic links, you must specify both the Quick I/O link and its hidden file in the list of files to be backed up. For example:
ls -la /db02 total 2192 drwxr-xr-x 2 root root 96 drwxr-xr-x 9 root root 8192 -rw-r--r-- 1 oracle dba 1048576 lrwxrwxrwx 1 oracle dba 22 .cust.dbf::cdev:vxfs:
Jan Jan Jan Jan
20 20 20 20
17:39 17:39 17:39 17:39
. .. .cust.dbf cust.dbf ->\
The preceding example shows that you must include both the symbolic link cust.dbf and the hidden file .cust.dbf in the backup file list. If you want to backup all Quick I/O files in a directory, you can simplify the process by just specifying the directory to be backed up. In this case, both components of each Quick I/O file is properly backed up. In general, you should specify directories to be backed up unless you only want to back up some, but not all, files in those directories.
Restoring backups
Restoring the backup images created by a BLI backup is no different than restoring the backup images created using the default NetBackup configuration. Restoring to any of the incremental backup images requires NetBackup to restore the last full backup image and all the subsequent incremental backups until the specified incremental backup image is restored. NetBackup does this automatically. The media that stored the last full and the subsequent incrementals must be available, or the restore cannot proceed. You can start the restores from the NetBackup client by using the Backup, Archive, and Restore interface. To restore the latest copy of each file, select either the files or parent directories with the latest backup date, and click Restore. For more information on restoring, see the NetBackup Backup, Archive, and Restore Getting Started Guide. If the operation is to restore files from an incremental backup image, NetBackup issues multiple restore operations beginning from the last full backup image and the subsequent incremental backup images until the selected date. The activity of multiple restores is logged in the Progress Log. If you plan to restore files backed up by another client or to direct a restore to another client, start the restore from the NetBackup server using the Backup, Archive, and Restore interface. Before initiating a restore, a backup must have successfully completed or an error occurs during the execution. For Solaris, the restore destination can be a VxFS or UFS file system. The destination file system does not need to support the Storage Checkpoint feature, but to be able to perform BLI backups of the restored data, a VxFS file system with the Storage Checkpoint feature is required. For HP-UX, the restore destination can be a VxFS or HFS file system. The destination file system does not need to support the Storage Checkpoint feature
220 Troubleshooting
to restore files, however, a VxFS file system with the Storage Checkpoint feature is required to perform BLI backups of the restored data. For AIX, the restore destination can be a VxFS or JFS file system. The destination file system does not need to support the Storage Checkpoint feature to restore files, however, a VxFS file system with the Storage Checkpoint feature is required to perform BLI backups of the restored data. Note that restoring a file causes all blocks in that file to be rewritten. Thus, all the blocks in the file are considered to have been modified. This means that the first subsequent differential incremental backup and all subsequent cumulative incremental backups will back up all of the blocks in the restored file. If you are restoring an entire database and/or file system, note that the first subsequent backup backs up all blocks that are restored. To restore a Quick I/O file, if both the symbolic link and the hidden file already exist, NetBackup restores both components from the backup image. If either one of the two components is missing, or both components are missing, NetBackup creates or overwrites as needed. Oracle database recovery might be necessary after restoring the files. See the Oracle documentation for more information on doing database recovery.
Troubleshooting
This section provides tips on troubleshooting common issues with script-based BLI backups.
Checking logs
NetBackup provides logs on the database backup and restore operations. These logs are useful for finding problems associated with those operations.
NetBackup progress logs

For user-directed backups and restores performed with Backup, Archive, and Restore interface, the most convenient log to use for NetBackup is the progress log. The progress log file is written to the user's home directory, by default in /usr/openv/netbackup/logs/user_ops/username/logs. This log indicates whether NetBackup was able to complete its part of the operation. You can view the progress log from the Backup, Archive, and Restore interface, or you can use a file editor such as vi(1).
221 Troubleshooting
NetBackup debug logs

The NetBackup server and client software provide debug logs for troubleshooting problems that occur outside of BLI backups. To enable these debug logs on the server or client, create the appropriate directories under the following directory:
/usr/openv/netbackup/logs
For more information on debug logs, see the NetBackup Troubleshooting Guide for UNIX and Windows or see the /usr/openv/netbackup/logs/README.debug file.
NetBackup reports
In addition to logs, NetBackup provides a set of reports that help isolate problems. One report is All Log Entries on the server. For a description of this and other reports, see the NetBackup Administrators Guide, Volume I.
Troubleshooting backup or restore errors

A backup or restore error can originate from NetBackup for Oracle, from the NetBackup server or client, from the Media Manager, or from VxFS. This section describes typical errors that can occur while running a database backup, and it provides suggestions on how to correct the underlying problem.
Troubleshooting stages of the operation
A backup or restore can be started in either of the following ways:

Manually from the administrator interface on the master server
Automatically by a NetBackup server using a full or incremental schedule If an error occurs during the start operation, examine the Java reports window for the possible cause of the error.
If the backup or restore started successfully, but eventually failed, one of the following could be the cause:

Server/Client communication problem Schedule error Media-related error
VxFS errors For more information, see the NetBackup Troubleshooting Guide for UNIX and Windows.
222 Troubleshooting
There can be insufficient disk space for the VxFS Fulldata Storage Checkpoints to keep track of changed block information. Check the All Log Entries report for errors. If there is a file system out-of-space condition, increase the size of the file system so it is large enough for Fulldata Storage Checkpoints or use the Nodata Storage Checkpoint Hot backup method. This error does not affect the integrity of the backup images because a full backup of the affected file system will occur after the condition is fixed. If an incremental backup is intended, but the whole file system is backed up instead, one of the following conditions might be present:

Storage Checkpoints that keep track of changes have been removed The Block level incremental attribute is not selected
Other errors with a nonzero status code The most common cause of this problem is the Storage Checkpoint that keeps track of the block changes was removed by the file system. This might happen if the file system runs out of space, and there are no volumes available to allocate to the file system. This does not affect the integrity of the backup images because a full backup of the file system will occur at the next backup opportunity after NetBackup detects that a Storage Checkpoint is missing.
Status codes
The status codes and their meanings are as follows:
Status Code 9. An extension package is needed but was not installed. The client does not have the NetBackup binaries required to do BLI backups. Use update_clients on the server to push out new binaries. Also, use vxlicense -p to verify that the Storage Checkpoint feature [83] and the Veritas Storage Foundation for Oracle [100] are installed. Status Code 69. Invalid file list specification. Look for a message such as the following in the error log on the server:
FTL - /oradata is not in a VxFS file system. A block incremental backup of it is not possible.
This indicates that there was an attempt to back up a file system that is not a VxFS file system with the Block level incremental attribute. This error can also occur if the file system is not mounted.
Status Code 73. bpstart_notify failed. When running the notify scripts, the bpstart_notify script exited with a nonzero status code, or the permission bits are set wrong on the bpstart_notify script. The script must have execute permission. If the permission bits are set, check the
223 Troubleshooting
bpstart_notify_output.ORACLE_SID file in the /usr/openv/netbackup/bin/BLOCK_INCR directory.
Status Code 74. Client timed out waiting for bpstart_notify to complete. Check the BPSTART_TIMEOUT setting on the NetBackup server. The BPSTART_TIMEOUT specified did not allow enough time for the script to complete. The shutdown database operation might be taking too long, or the script might be waiting for other streams to start. Check the bpstart_notify_output.ORACLE_SID file and the post_checkpoint_notify_output.ORACLE_SID file in the /usr/openv/netbackup/bin/BLOCK_INCR directory. Make sure that the policies and schedules are configured with appropriate multiplexing factors and that the required storage units that allow all streams to start at the same time are configured. Check to see if all needed tape drives are working and available. Make sure that the database is not processing transactions so that the instance cannot be shut down immediately (if you are using one of the backup methods where the database is shut down). Finally, make sure that the priority on the BLI policies is higher than other policies, so they get access to the tape drives before the other policies. Status Code 75. Client timed out waiting for bpend_notify to complete. Check the BPEND_TIMEOUT setting on the NetBackup server. The BPEND_TIMEOUT specified did not allow enough time for the script to complete. The restart database operation might be taking too long, or the script might be waiting for other streams to call the bpend_notify script. Check the bpend_notify_output.ORACLE_SID file and the post_checkpoint_notify_output.ORACLE_SID file in the /usr/openv/netbackup/bin/BLOCK_INCR directory. Make sure that the policies and schedules are configured with appropriate multiplexing factors and that the required storage units that can allow all streams to be started at the same time are configured. Verify that all needed tape drives are working and available during backup. Status Code 77. Execution of the specified system command returned a nonzero status code. Check the post_checkpoint_notify_output.KEYWORD file in the /usr/openv/netbackup/bin/BLOCK_INCR directory for the possible cause. The post_checkpoint_notify script exited with a nonzero status code. Status Code 143. Invalid command protocol. Check to see if the Block level incremental policy attribute is selected without a keyword specified. Set the Keyword phrase in the policies to the Oracle instance name ($ORACLE_SID).
224 Troubleshooting
Improving netbackup backup performance

If backups are running slowly, check to see if the database has an excessive workload. BLI backups allow hot database backups and quick freeze database backups. Because the database is running during both of these backup methods while NetBackup is backing up the database files, Oracle I/O can affect the backup performance. If the database is not running with a high transaction volume, troubleshoot NetBackup. If the incremental backup takes a long time to finish, it could mean that there are more changed blocks since the last incremental backup. Verify whether the size of the incremental backup image has increased, and consider increasing the frequency of incremental backups. Finally, you can improve the speed at which backup is performed by using multiplexed backups. Assigning multiple policies to the same backup device is helpful when devices are not writing at their maximum capacity.
Database recovery
A BLI backup does not perform automatic database recovery. This process includes restoring the database files from NetBackup images and applying the Oracle redo log files to the database files. Follow the Oracle documentation to perform database recovery after a restore.
Index
Symbols
.xml 128 .xsc 128 /Oracle/XMLArchive 134
B
backup automatic using scripts 113, 126 errors 221 methods 213, 215 methods or types of 212 performing 218 wizard, invoking 175 Backup Selections list adding selections 88, 89 overview 87 backups manual 106 BFILE_DIRECTORY 139 binaries, pushing out 222 BLI Backup restores 219 BLI no RMAN adding policies 207 backup example 211 cold backup 204 goodies directory 208 hot backup 204 improving performance 224 mailid 208 requirements 206 schedule types 210 schedules 205 standard policy type 207 workload 224 Block level incremental 222 Block-level Incremental backup, see Snapshot Client boraexp64 181 boraimp64 181 bp.conf 93 administrator 194 troubleshooting 187, 191 BPBACKUP 93 BPBACKUP_POLICY 93 BPBACKUP_SCHED 93
A
Advanced Client for Oracle 147 ALTER_TABLESPACE 212, 215, 218 API error 185, 188 libobk module 179 Application Backup schedule backup window 81 configuring 81 for Block-level Incremental backups 172 overview 81, 83 retention 81 with Snapshot Client 159 archive 15, 24 ARCHIVE_DATE_FROM 133, 139 ARCHIVE_DATE_TO 134, 139 ARCHIVELOG 213, 218 attributes Block level incremental 222 automatic archive 126 automatic backup policy 113, 126 schedule manual backup 114, 126 schedules, configuring 82 automatic backups 218 Automatic Cumulative Incremental Backup schedule Snapshot Client effects 174 Automatic Differential Incremental Backup schedule overview 83 Snapshot Client effects 174 Automatic Full Backup schedule 82, 83 Snapshot Client effects 174 with Snapshot Client 159
226
bpbrm log verbose mode 181 bpcd 181 verbose mode 181 bpdbm daemon 46 bpdbm log verbose mode 181 bpdbsbora for XML import 137 bpend_notify 213, 223 BPEND_TIMEOUT 223 bphdb 180, 181 description 180 log 183 bphdb log verbose mode 181 bplist 116 browsing for backups 116 browsing for XML export archives 134 example 116 bplist log verbose mode 181 bporaexp 15, 23, 128, 130, 181 bporaexp64 130, 180 bporaimp 16, 25, 133, 134, 181 performing a restore 138 bporaimp64 134, 138, 180 bpplclients command 39, 46 bprd log verbose mode 181 bpsched verbose mode 181 bpstart_notify 213, 218 bpstart_notify.oracle_bli 213 BPSTART_TIMEOUT 223 bptm log verbose mode 181 bpubsoraarc 181 browsing archives 133
command bplist 116 bporaexp 128 commands allocate channel 21 backup 21, 111 bplist 116, 134 bporaexp 15, 23, 130 bporaimp 25, 133, 134 bporexp64 130 bpplclients 39, 46 change 112 copy 111 crosscheck 110 crosscheck backupset 110 delete expired backupset 111 get_license_key 40, 48 initbpdbm 46 install_dbext 45, 49 list 112 register database 110 report 112 reset database 110 restore 111 resync catalog 111 rman execute scripts 126 performing restore 122 script syntax 126 send 99 set duplex 99 switch 111 update_dbclients 39, 43, 47 COMMIT 140 compatibility information 37 configuration database debug level 184 Media Manager 38 CONSISTENT 130 correcting errors 221
C
check_coverage 210 client list for installation 43 client read timeout property 193 CLIENT_NAME 93 CLIENT_READ_TIMEOUT 93 cluster software prerequisites 39 cluster_config script 39, 47, 49
D
daemons, see processes database software prerequisites for installation 38 debug logs 221 accessing 182 enabling 181 in /usr/openv/netbackup/logs 182 troubleshooting with log files 181
227
debugging level 184 DIRECTORY 130, 140 DIRECTORY parameter 129
E
environment variables 175 environmental variable user-directed backup 116 error checking 113 errors, correcting 221 example bplist 116 RMAN script 98 examples parameter files 105 scripts 105 execution log 183
local 47 platform compatibility 37 prerequisites 37 prerequisites in a cluster 39 remote 39 requirements for NetBackup software 38 instant recovery, see Snapshot Client
J
Java interface 77 jbpSA 135
K
KEYWORD 131, 134, 141
L
libbpora.so.8.0 180 libbpora.so.9.0 180 libbpora64.so.8.0 180 libbpora64.so.9.0 180 libobk,shared library module 180 license keys 28 licensing information 40, 48 LIST 141 LIST parameters 133 local installation procedure 47 LOG 131, 142 log files enabling 182 logs NetBackup progress 220
F
failed operation troubleshooting 185, 188 file system growing 222 UNCOVERED 208 file-based operations 149, 150 FlashSnap snapshots 165 FROMUSER 134, 140 Fulldata Storage Checkpoint 170
G
get_license_key 28 get_license_key command 40, 48
H
HELP 130, 140 hot backup 212
M
manual archive 126 manual backups 114, 126, 218 maximum jobs per client 78 Media Manager configuring backup media 38 multiple copies feature 85, 175 multiplexing overview 12 multi-streamed backups 193
I
IGNORE_ROWS 141 INIT.ORA 215 initbpdbm command 46 install script 41, 48 install_dbext 29 install_dbext command 45, 49 installation database software prerequsites 38
N
NAME 131, 142 NAS Snapshot 162
228
configuring a policy for 162 NAS_Snapshot 165 NAS_Snapshot method 164 NB_ORA_CLIENT 92, 130, 131, 133, 138, 142 NB_ORA_POLICY 92, 130, 131 NB_ORA_SCHED 92, 130, 131 NB_ORA_SERV 92, 130, 131, 133, 138, 142 NB_PC_ORA_RESTORE variable 167 nbjm scheduling process 182 nbpem scheduling process 182 nbrb scheduling process 182 NetBackup 14 logs and reports 220 NetBackup mode 129 Nodata Storage Checkpoint 170
scheduling (nbpem, nbjm, nbrb) 182 Progress Log 219 proxy copy 149
Q
QUERY 132
R
Recovery Wizard use with Snapshot Client 175 redirected restores 122, 144 redo log 210 remote folder button 89 remote installation procedure 39 reports All Log Entries report 184 database operations 179 NetBackup server reports 184 reports See also log files restore 16, 24 to a different client 122, 144 user-directed 137 restore errors 221 RESTORE_SCHEMA_ONLY 142 RESTORE_TO_DIRECTORY 142 restores snapshot rollback 165, 167 with Snapshot Client methods 165, 167 retention period for frequency-based schedules 85 for Snapshot Client 174 rman change command 86 RMAN script example 98 robust logging 182 ROW_BUFFER 132, 142
O
offhost backup, See Snapshot Client Oracle environment variables 214 Intelligent Agent 213 Oracle Advanced Client 147 Oracle Recovery Manager errors 185 example RMAN script 98 OWNER 131
P
parameter file 24, 25, 128 parms operand 92 PARTITIONS 131 permission bits 222 platform compatibility 37 point in time rollback 165 policy configuration adding clients 87 attributes 80 backup selections list 87 for databases 79 for Snapshot Client 159, 171 overview 78 schedules 80 testing 106 POLICY_IN_CONTROL 214, 215 post_checkpoint_notify 213, 223 processes bpdbm 46 log files for NetBackup processes 182
S
schedule automatic backup 113, 126 schedules adding 80 frequency 84 properties 84 properties for Snapshot Client 174 retention 85 retention for Snapshot Client 174
229
types of schedules 80 scripts bpend_notify 223 bpstart_notify.oracle_bli 213 cautions for using 83 check_coverage 210 cluster_config 39, 47, 49 install 41, 48 notify 218 RMAN 19, 20 scheduler 113, 126 XML export 101 SERVER 93 setup_bli_scripts contents of 214 sample of 215 Shared library module, libobk 180 SHUTDOWN_BKUP_RESTART 212, 215, 218 SHUTDOWN_CKPT_RESTART 213, 215, 218 skipped clients 43 snapshot backup 148, 158, 159, 165 Snapshot Client Block-level Incremental backup configuring a policy 171 overview 148, 167 configuring policies 159 effect on backup schedules 84 effects on policies and schedules 173 file-based operations 149, 150 instant recovery configuration requirements 158 overview 148 policy configuration 159 restore method 165 offhost backup configuration 158 configuring 161 overview 148 overview 148 proxy copy 149 snapshot backup configuration 158 configuration requirements 158 database objects included 159 overview 148 policy configuration 159 restore method 165 stream-based operations 149 snapshot rollback 165, 167
SnapVault 166 Storage Checkpoint 169 backup 213 removing 222 stream-based operations 149
T
TABLES 132, 134, 143 templates administration 126 advantages over scripts 83 button on Backup Selections tab 89 creating for XML export 101 overview 13 XML export 100 testing policy configuration 106 timeout failures, minimizing 193 TOUSER 143 transaction logs see archive logs
U
UNCOVERED file system 208 Unicode 14 unified logging 182 update_clients 222 update_dbclients command 39, 43, 47 user-directed archive 126 user-directed restore 137 USERID 132, 133, 143 UTF-8 14
V
VERBOSE 94 Verifying installation 180 Veritas Storage Foundation 171 VIEWS 133 VxFS_Checkpoint snapshot 165 vxvm snapshot 165
W
Windows interface 77 wizard overview 13 use with Snapshot Client 175
230
X
XML 14 XML export 15 XML Export Wizard 101 XML import 16 XML Import Wizard 136 XML instance 15, 23, 25, 128 XML schema 14, 23, 25, 128

NBU-290216-Netbackup For Oracle Admin Guide

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

NBU-290216-Netbackup For Oracle Admin Guide

Caricato da

Copyright:

Formati disponibili

Veritas NetBackup for Oracle Administrators Guide

for UNIX and Linux

Veritas NetBackup for Oracle Administrators Guide

Third-party legal notices

Licensing and registration

NetBackup for Oracle QuickStart

Installing the agent

Using NetBackup for Oracle

NetBackup for Oracle with Snapshot Client

Oracle 9i and 10g Real Application Clusters

Script-based block-level incremental (BLI) backups without RMAN

NetBackup for Oracle features

Table 1-1 Feature

NetBackup for Oracle features and descriptions Description

12 Introduction NetBackup for Oracle features

Table 1-1 Feature

NetBackup for Oracle features and descriptions (continued) Description

Graphical user interfaces

Introduction NetBackup for Oracle features

Table 1-1 Feature

NetBackup for Oracle features and descriptions (continued) Description

Parallel backup and restore operations

14 Introduction NetBackup for Oracle terminology

Self-identifying archive format

Flexible archive image searches

NetBackup for Oracle terminology

XML export and XML import terms

Introduction NetBackup for Oracle terminology

XML export archives

XML Format OS Directory

The archive activity includes the following actions: Activity

A directory A storage unit

Archive bporaexp command

16 Introduction NetBackup for Oracle terminology

XML import restores

XML Format OS Directory

The restore activity includes the following actions: Activity

Introduction NetBackup for Oracle terminology

Multilevel incremental backup

18 Introduction NetBackup for Oracle terminology

Cumulative incremental backup

Oracle RMAN terms

Introduction NetBackup for Oracle overview

NetBackup for Oracle overview

20 Introduction NetBackup for Oracle overview

NetBackup for Oracle on a sample network

System containing Oracle database Recovery Catalog

How does RMAN work?

Introduction NetBackup for Oracle overview

How does NetBackup for Oracle work?

Linking with NetBackup Generating unique file names

22 Introduction NetBackup for Oracle overview

Incremental backups of Oracle databases

About the Oracle recovery catalog

NetBackup for Oracle XML export and XML import

Introduction NetBackup for Oracle overview

Sequence of operation: XML export archive

XML schema(s), XML instance(s) XML schema(s), XML instance(s)

XML generator Option to create XML files on disk

Table(s) metadata, Table(s) data Query processor

24 Introduction NetBackup for Oracle overview

Sequence of operation: XML import restore