VERITAS NetBackup™ 6.

0
for Oracle

System Administrator’s Guide

for Windows

N152628

September 2005
Disclaimer
The information contained in this publication is subject to change without notice. VERITAS Software
Corporation makes no warranty of any kind with regard to this manual, including, but not limited to,
the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software
Corporation shall not be liable for errors contained herein or for incidental or consequential damages
in connection with the furnishing, performance, or use of this manual.

VERITAS Legal Notice

Copyright © 2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo,
and NetBackup are trademarks or registered trademarks of VERITAS Software 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.
VERITAS Software Corporation
350 Ellis Street
Mountain View, CA 94043
USA
Phone 650-527-8000
Fax 650-527-2908
www.veritas.com

Third-Party Copyrights
For a list of third-party copyrights, see the NetBackup Release Notes appendix.

ii NetBackup for Oracle System Administrator’s Guide for Windows

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Finding NetBackup Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Accessing the VERITAS Technical Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . .xii

Contacting VERITAS Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Comment on the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

NetBackup for Oracle Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

NetBackup for Oracle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

XML Export and XML Import Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Oracle Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Oracle RMAN Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

NetBackup for Oracle Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

How Does RMAN Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

How Does NetBackup for Oracle Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Incremental Backup of Oracle Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

NetBackup for Oracle XML Export and XML Import . . . . . . . . . . . . . . . . . . . . . . . . 11

Sequence of Operation: XML Export Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Sequence of Operation: XML Import Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

iii
 Chapter 2. NetBackup for Oracle QuickStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Enabling NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuring a NetBackup for Oracle Policy and Schedule . . . . . . . . . . . . . . . . . . . . . . . 16

Invoking the NetBackup Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Creating an Oracle Policy and Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Backing Up the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3. Verifying Installation Requirements and Registering a License Key . . 23

Verifying the Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Operating System and Platform Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

NetBackup Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Cluster Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Registering the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Oracle Recovery Catalog Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

User Interface Terminology Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the Maximum Jobs Per Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring Backup Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Adding a New Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Description of Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Adding Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Types of Backup Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Schedule Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Managing Expired Backup Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Adding Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Adding Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring the Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Oracle RMAN Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

iv NetBackup for Oracle System Administrator’s Guide for Windows

 Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Environment Variables Set by a User in the XML Export Parameter File . . . . . . . . 46

Environment Variables Set by NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . 46

Creating Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Recovery Manager (RMAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

RMAN Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Creating RMAN Templates Using the NetBackup for Oracle RMAN Template

Generation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Creating an RMAN Script From a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Creating RMAN Scripts Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

XML Export Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

XML Export Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Creating XML Export Templates Using the NetBackup for Oracle Wizard . . . 53

Creating an XML Export Script From a Template . . . . . . . . . . . . . . . . . . . . . . . . . 55

Creating XML Export Scripts Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Storing Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Database User Authentication and Server-directed Backups . . . . . . . . . . . . . . . . . . . . . 57

Testing Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 5. Using NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Maintaining the RMAN Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Querying the RMAN Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Performing a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Automatic Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Manual Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

User-directed Backup From the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Running NetBackup for Oracle Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Using bpdbsbora to Run a Backup Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Running the NetBackup for Oracle Shell Script . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Running RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Browsing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Contents
v
 Using the RMAN Repository to Browse Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Using bplist to Browse Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Performing a Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Running the NetBackup for Oracle Recovery Wizard on the Client . . . . . . . . . . . . 70

Using bpdbsbora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Running the NetBackup for Oracle Recovery Shell Script on the Client . . . . . . . . 74

Running RMAN on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Using RMAN to Perform a Redirected Restore . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Performing Other RMAN Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Performing an XML Export Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Automatic Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Manual Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

User-directed XML Exports From the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Running NetBackup for Oracle XML Export Templates . . . . . . . . . . . . . . . . . . . 79

Using bpdbsbora to Run an XML Export Template . . . . . . . . . . . . . . . . . . . . . . . 80

Running the NetBackup for Oracle XML Export Script on the Client . . . . . . . . 80

Running bporaexp on the Client as an Oracle User . . . . . . . . . . . . . . . . . . . . . . . 81

Browsing XML Export Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Using bporaimp Parameters to Browse XML Export Archives . . . . . . . . . . . . . . . . 87

Using bplist to Browse XML Export Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Performing a Restore of an XML Export Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Running the XML Import Wizard on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Using bpdbsbora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Running an XML Import Script on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Running bporaimp on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Redirecting a Restore of an XML Export Archive to a Different Client . . . . . . . . 100

Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

vi NetBackup for Oracle System Administrator’s Guide for Windows

 Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Using NetBackup for Oracle in a Microsoft Cluster Server Environment . . . . . . . . . 102

Automatic Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Manual Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

User-directed Backup or Restore from the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Chapter 6. NetBackup for Oracle with Advanced Client . . . . . . . . . . . . . . . . . . . . .105

Installation and Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

NetBackup for Oracle with Advanced Client Overview . . . . . . . . . . . . . . . . . . . . . . . . 107

Snapshot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Instant Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Offhost Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Proxy Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

File-based Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Stream-based Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

File-based Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

How Does NetBackup for Oracle with Advanced Client Work? . . . . . . . . . . . . . . . . . 111

Sequence of Operation: Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Sequence of Operation: Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Database Objects Supported by Advanced Backup Methods . . . . . . . . . . . . . . . . . 112

Multistreaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

RMAN Multiple Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Restoring Datafiles to a New Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

RMAN Incremental Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Examples: Using Multiple Channels in RMAN Scripts with Proxy Backups . . . . 115

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Contents vii

 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configuring Snapshot Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Configuring an Oracle Policy with Advanced Client Backup Methods . . . . . . . . 119

Configuring a Snapshot Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Restoring Data from a Snapshot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Restoring Individual Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Restoring Volumes and File Systems Using Snapshot Rollback . . . . . . . . . . . . . . 123

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Advanced Client Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Types of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Schedule Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Templates and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Chapter 7. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

General Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

NetBackup and NetBackup for Oracle Logs and Reports . . . . . . . . . . . . . . . . . . . . . . . 132

NetBackup for Oracle Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Enabling Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Accessing the Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

bphdb Folder on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

dbclient Folder on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

bpdbsbora Folder on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

bporaexp Folder on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

bporaimp Folder on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Setting the Debug Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

NetBackup Server Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Oracle Recovery Manager Utility Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Additional XML Export and Import Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

viii NetBackup for Oracle System Administrator’s Guide for Windows

 Troubleshooting Backup or Restore Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Check the Logs to Determine the Source of the Error . . . . . . . . . . . . . . . . . . . . . . . 136

Troubleshoot Each Stage of the Backup or Restore . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Troubleshooting XML Export or XML Import Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Checking the Logs to Determine the Source of the Error . . . . . . . . . . . . . . . . . . . . . 138

Troubleshoot Each Stage of the XML Export or XML Import . . . . . . . . . . . . . . . . . 139

Troubleshooting NetBackup for Oracle with Advanced Client . . . . . . . . . . . . . . . . . . 141

Minimizing Timeout Failures on Large Database Restores . . . . . . . . . . . . . . . . . . . . . . 142

Appendix A. Oracle 9i and 10g Real Applications Clusters . . . . . . . . . . . . . . . . . . 143

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

How Does NetBackup Fit into a RAC Environment? . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Virtual Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Archiving Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Backing Up a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Restoring a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Restoring Archive Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Contents
ix
x NetBackup for Oracle System Administrator’s Guide for Windows
Preface

This guide describes how to install, configure, and use NetBackup for Oracle on a
Windows platform. For information about the NetBackup server software, see one of the
following platform-specific manuals:
◆ NetBackup System Administrator’s Guide for UNIX and Linux, Volumes I and II
◆ NetBackup System Administrator’s Guide for Windows, Volumes I and II

Getting Help
You can find answers to questions and get help from the NetBackup documentation and
from the VERITAS technical support web site.

Finding NetBackup Documentation

A list of the entire NetBackup documentation set appears as an appendix in the NetBackup
Release Notes. All NetBackup documents are included in PDF format on the NetBackup
Documentation CD.
For definitions of NetBackup terms, consult the online glossary.

▼ To access the NetBackup online glossary

1. In the NetBackup Administration Console, click Help > Help Topics.

2. Click the Contents tab.

3. Click Glossary of NetBackup Terms.

Use the scroll function to navigate through the glossary.

xi
Getting Help

Accessing the VERITAS Technical Support Web Site

The address for the VERITAS Technical Support Web site is http://support.veritas.com.
The VERITAS Support Web site lets you do any of the following:
◆ Obtain updated information about NetBackup for Oracle, including system

requirements, supported platforms, and supported peripherals

◆ Contact the VERITAS Technical Support staff and post questions to them
◆ Get the latest patches, upgrades, and utilities
◆ View the NetBackup for Oracle Frequently Asked Questions (FAQ) page
◆ Search the knowledge base for answers to technical support questions
◆ Receive automatic notice of product updates
◆ Find out about NetBackup for Oracle training
◆ Read current white papers related to NetBackup for Oracle
From http://support.veritas.com, you can complete various tasks to obtain specific types
of support for NetBackup for Oracle:

1. Subscribe to the VERITAS Email notification service to be informed of software alerts,

newly published documentation, Beta programs, and other services.

a. From the main http://support.veritas.com page, select a product family and a

product.

b. Under Support Resources, click Email Notifications.

Your customer profile ensures you receive the latest VERITAS technical
information pertaining to your specific interests.

2. Locate the telephone support directory at http://support.veritas.com by clicking the

Phone Support icon. A page appears that contains VERITAS support numbers from
around the world.

Note Telephone support for NetBackup for Oracle is only available with a valid
support contract. To contact VERITAS for technical support, dial the
appropriate phone number listed on the Technical Support Guide included in
the product box and have your product license information ready for quick
navigation to the proper support group.

3. Contact technical support using e-mail.

xii NetBackup for Oracle System Administrator’s Guide for Windows

 Accessibility Features

a. From the main http://support.veritas.com page, click the E-mail Support icon.
A wizard guides you to do the following:
◆ Select a language of your preference
◆ Select a product and a platform
◆ Provide additional contact and product information, and your message
◆ Associate your message with an existing technical support case

b. After providing the required information, click Send Message.

Contacting VERITAS Licensing

For license information, you can contact us as follows:
◆ Call 1-800-634-4747 and select option 3
◆ Fax questions to 1-650-527-0952
◆ In the Americas, send e-mail to [email protected].
In the Asia and Pacific areas, send email to [email protected].
In all other areas, send email to [email protected].

Accessibility Features
NetBackup contains features that make the user interface easier to use by people who are
visually impaired and by people who have limited dexterity. Accessibility features
include:
◆ Support for assistive technologies such as screen readers and voice input (Windows
servers only)
◆ Support for keyboard (mouseless) navigation using accelerator keys and mnemonic
keys
For more information, see the NetBackup Installation Guide.

Preface xiii
Comment on the Documentation

Comment on the Documentation

Let us know what you like and dislike about the documentation. Were you able to find the
information you needed quickly? Was the information clearly presented? You can report
errors and omissions or tell us what you would find useful in future versions of our
manuals and online help.
Please include the following information with your comment:
◆ The title and product version of the manual on which you are commenting
◆ The topic (if relevant) on which you are commenting
◆ Your comment
◆ Your name
Email your comment to [email protected].
Please only use this address to comment on product documentation. See “Getting Help”
in this preface for information on how to contact Technical Support about our software.
We appreciate your feedback.

xiv NetBackup for Oracle System Administrator’s Guide for Windows

Introduction 1
NetBackup for Oracle 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 for Oracle. It includes the following topics:
◆ NetBackup for Oracle features
◆ NetBackup for Oracle terminology
◆ NetBackup for Oracle overview
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 15.

1
NetBackup for Oracle Features

NetBackup for Oracle Features

The following list shows NetBackup for Oracle’s main features and introduces some terms
used in the NetBackup for Oracle documentation. For more information on general
NetBackup terminology, see the NetBackup System Administration Guide, Volume I.

Feature Description

Media and device All devices supported by Media Manager are available to NetBackup
management for Oracle.

Scheduling facilities NetBackup scheduling facilities on the master server can be used to
schedule automatic and unattended Oracle backups.

This also lets you choose the times when these operations can occur.

For example, to prevent interference with normal daytime operations,

you can schedule your database backups to occur only at night.

Multiplexed backups and NetBackup for Oracle lets you take advantage of NetBackup’s
restores multiplexing capabilities. Multiplexing directs multiple data streams
to one backup device, thereby reducing the time necessary to
complete the operation.

Transparent execution of All backups and restores run simultaneously and transparently
both Oracle and regular file without any action from the NetBackup administrator.
system backup and restore The database administrator can run database backup and restore
operations operations through NetBackup. Alternatively, you can use Oracle’s
Recovery Manager (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 Media It is possible to share the same devices and media used for other
Manager and disk storage backups or to give Oracle exclusive use of certain devices and media.
units used for other file
backups

Centralized and networked From the NetBackup master server, you can schedule database
backup operations 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.

2 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle Features

Feature Description

Graphical user interfaces NetBackup provides the following graphical user interfaces for client
users and administrators:
◆ Backup, Archive, and Restore user interface
◆ NetBackup Administration Console for Java
◆ NetBackup Administration Console for Windows
A database administrator or NetBackup administrator can start
backup or restore operations for Oracle from the NetBackup
graphical user interface on the master server.

Parallel backup and restore NetBackup for Oracle supports the parallel backup and restore
operations 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.

Templates The NetBackup for Oracle database wizards can create backup and
recovery templates. You can launch the Backup Wizard and the
Recovery Wizard from the NetBackup Backup, Archive, and Restore
interface. The wizards generate platform-independent templates that
contain configuration information that the software uses when
performing backups and restores. Because the wizard-generated
templates do not support all the features 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.

The following list describes the NetBackup for Oracle XML Export and XML Import
archiving features:

Feature Description

System- and database- NetBackup for Oracle uses the eXtensible Markup Language (XML)
independent archive format standard to represent relational database table data extracted from an
Oracle database.

Self-identifying archive The XML Schema standard is used to describe the table data that is
format 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.

Chapter 1, Introduction 3
NetBackup for Oracle Features

Feature Description

Command line interfaces Parameter files specify the table data to include in an archive and the
that allow export and table data to extract from an archive for import into an Oracle
import at row-level database.
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.

Flexible archive image The NetBackup catalog contains information on the contents of the
searches archive that can be searched using flexible search criteria, such as
tablename or user.

4 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle Terminology

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 Export and Import terms. The graphics illustrate the
relationships of the terms as they apply to both XML export archives and restores.

eXtensible Markup Language XML 1.0 is a universal format for structured documents and data. The
(XML) XML 1.0 standards are produced by the World Wide Web Consortium
and include the XML Schema standard.
Unicode UTF-8 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.

Archives

XML Archive NetBackup

export
XML
Format

OS
Directory

Oracle XML Archive NetBackup for Oracle extracts database table data, converts it into
XML format, and stores XML data to either of the following types of
repositories:
◆ A directory
◆ A NetBackup Media Manager storage unit or disk storage unit

Chapter 1, Introduction 5
NetBackup for Oracle Terminology

XML export NetBackup for Oracle converts Oracle table data to XML format (XML
schema, or metadata, and XML instance, or data).
Archive NetBackup stores the XML data on a NetBackup storage unit.
bporaexp command NetBackup for Oracle’s 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.

Restores

OS
Directory

XML restore NetBackup

import
XML
Format

OS
Directory

Oracle XML Restore NetBackup for Oracle manages the retrieval of archived database
table data, the parsing of the XML format, and the insertion of the
data back into the Oracle database.
Restore NetBackup retrieves the XML-formatted data from the storage unit.
XML import NetBackup for Oracle parses XML-formatted Oracle table data and
inserts data into the Oracle database.
bporaimp command NetBackup for Oracle’s XML import utility can parse the
XML-formatted data for re-insertion into the database or can redirect
the data to an OS directory.

6 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle Terminology

Oracle Terms

Full Backup A full backup copies all blocks into the backup set, skipping only
datafile 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 datafiles, 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.
Multilevel Incremental RMAN allows you to create multilevel backups. An integer identifies
Backup each level; for example, 0, 1, 2, and so on. A level 0 incremental
backup, which is the base of subsequent incremental backups, copies
all blocks containing data.
When you generate a level n incremental backup in which n is greater
than 0, you back up the following:
◆ All blocks that have been modified since the most recent backup at
a level n or lower. This is the default type of incremental backup. It
is called a differential incremental backup.
◆ All blocks that have been modified since the most recent backup at
level n-1 or lower. This is called a cumulative incremental backup.
The benefit to performing multilevel incremental backups is that you
do not back up all of the blocks all of the time. Incremental backups at
a level greater than 0 only copy blocks that were modified, which
means that the backup size can be significantly smaller and the
backup might require much less time. The size of the backup file
depends solely upon the number of blocks modified and the
incremental backup level.
Differential Incremental In a differential level n incremental backup, you back up all blocks
Backup 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.

Chapter 1, Introduction 7
NetBackup for Oracle Terminology

Cumulative Incremental In a cumulative level n incremental backup, you back up all blocks
Backup 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.

Oracle RMAN Terms

RMAN RMAN backs up, restores, and recovers database files. RMAN starts
Oracle server processes on the target database. These Oracle server
processes perform the backup and restore. RMAN performs backup
and recovery procedures, and it greatly simplifies the tasks
administrators perform during these processes. However, RMAN
cannot directly manage the storage devices and media used in its
backups, so it must be integrated with an application that has these
capabilities. NetBackup for Oracle provides device and media
management capabilities by integrating RMAN with NetBackup and
its media management software. Other advantages are access to
NetBackup’s automatic scheduling facilities and the graphical
interfaces.
RMAN Repository An RMAN recovery catalog or the database control file is a repository
for information that is used and maintained by RMAN. RMAN uses
this information to determine how to run requested backup and
restore actions.
For a description of the recovery catalog, see the Oracle Backup and
Recovery Guide.
rman command The rman command starts an RMAN backup or restore. This
command is described in the Oracle Backup and Recovery Guide.
RMAN script The RMAN script specifies the commands for RMAN to perform (for
example, backups, and restores). For information on RMAN
commands and script files, see your Oracle documentation.
There are example RMAN shell scripts in the
install_path\NetBackup\dbext\Oracle\samples\rman

directory. 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.

8 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle Overview

NetBackup for Oracle Overview

The following example network shows the major components in a NetBackup for Oracle
configuration. The server that is hosting the Oracle database must be a NetBackup client,
and it must have NetBackup for Oracle licensed.

System hosting the Oracle database

System containing Oracle

database Recovery Catalog

NetBackup for Oracle supplies:
Oracle database
– Sample configuration program
to back up or
– Sample script files
restore
– VERITAS I/O Library (libobk)
– bporaimp and bporaexp
Oracle database software supplies:
Additional required NetBackup software:
– Oracle Recovery Manager (RMAN)
– Oracle Call Interface (OCI) – NetBackup Client

Network (TCP/IP)

NetBackup master server Media Manager or

or remote media server disk storage unit

NetBackup software:
– NetBackup Master Server
– NetBackup Media Server

(if system is a media server)

RMAN

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 DOS script, or an application
such as NetBackup. The RMAN script is used as a parameter to the rman command and

Chapter 1, Introduction 9
NetBackup for Oracle Overview

specifies the operations to be performed (for example, backup or restore). The RMAN
script also defines other 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 Media Manager or disk storage
units:
◆ Access to the NetBackup library
◆ Generating unique file names
NetBackup for Oracle includes a library of functions that enable RMAN to use
NetBackup. This library is in install_path\NetBackup\bin.
When using the RMAN backup command, each resulting backup set contains at least one
backup piece (datafile, datafile 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 having that name is deleted. In Oracle 8i or later, the RMAN backup fails
with a file already exists in catalog error. For information on generating
unique file names, see your Oracle documentation.
Either NetBackup users or automatic schedules start database backups by specifying a
template or shell script in the file list of the Oracle policy. The template or shell script
specifies the backup commands that RMAN will perform on the client.
For a backup:

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

2. When the process requires media to store backup data, RMAN starts a user-directed
backup by issuing a backup request.

3. The NetBackup media server connects to NetBackup for Oracle on the client and
transfers the database data to secondary storage.

10 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle Overview

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 Backup of Oracle Databases

The RMAN provides true incremental backups. An incremental backup backs up datafiles
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.

NetBackup for Oracle XML Export and XML Import

While Oracle RMAN performs backup, restore, and recovery of physical Oracle database
objects (datafiles, 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).
The XML format is used to provide a self-identifying and system-independent format
ideal for database archiving.

Chapter 1, Introduction 11
NetBackup for Oracle Overview

Sequence of Operation: XML Export Archive

XML schema(s),
XML instance(s)

XML generator XML schema(s),

Option to XML instance(s) NetBackup
create XML
files on disk

Table(s) metadata, Table(s) data

Oracle DBMS Query processor

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. The NetBackup for Oracle script or template calls the bporaexp utility with a
specified parameter file.

2. The Query Processor uses the parameters in the specified file to build an SQL query
for each table.

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

12 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle Overview

4. The Query Processor passes the output (including metadata and data for a single table
or multiple tables) to the XML Generator.

5. For each table passed, the XML Generator builds one or more sets of XML Schema
and XML Instance documents.

6. XML data streams are backed up by NetBackup.

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

Sequence of Operation: XML Import Restore

XML schema(s),
XML instance(s)

Option to
restore XML
files on disk

XML schema(s),
XML Parser XML instance(s) NetBackup

Table(s) metadata, Archive name

Table(s) data Keyword
Table name
OCI
Oracle DBMS XML data loader Script or template
(bporaimp)
(Parameter file)

Command line or

Backup, Archive, and Restore interface

Chapter 1, Introduction 13
NetBackup for Oracle Overview

NetBackup for Oracle users start database XML import restores by invoking a NetBackup
for Oracle script or template at the client command line or by invoking an XML import
restore template through the Backup, Archive, and Restore interface.
For an XML import restore:

1. The NetBackup for Oracle script or template calls the bporaimp utility with a
specified parameter file.

2. The input parameters that identify the XML Archive to restore are passed to
NetBackup.

3. NetBackup locates and reads the set of XML schema and instance documents from the
NetBackup storage unit.

4. The XML data stream is passed to an XML parser, which passes the data to the XML
Data Loader.

5. The XML Data Loader uses Oracle’s 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.

14 NetBackup for Oracle System Administrator’s Guide for Windows

NetBackup for Oracle QuickStart 2
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 Advanced Client
options, see “NetBackup for Oracle with Advanced Client” on page 105.
For more detailed instructions, see the following chapters:
◆ “Verifying Installation Requirements and Registering a License Key” on page 23

◆ “Configuration” on page 29

◆ “Using NetBackup for Oracle” on page 61

15

Enabling NetBackup for Oracle

Enabling NetBackup for Oracle

NetBackup for Oracle is installed automatically when you install the NetBackup client. If
you are planning your NetBackup for Oracle installation on a machine that is not yet a
NetBackup client, use the NetBackup for Windows install CD to install NetBackup. A
wizard will guide you through the installation.
When the NetBackup client is installed, you must enable NetBackup for Oracle by
registering the license key on the NetBackup master server for that client.

▼ To enable NetBackup for Oracle

1. Stop Oracle services on the client.

2. In the NetBackup Administration Console on the master server, click Help > License
Keys.

3. Add the license key for NetBackup for Oracle.

4. Restart Oracle services on the client.

For a more comprehensive list of installation prerequisites, see “Verifying the Installation
Prerequisites” on page 23.

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 69.

Invoking the NetBackup Administration Console

You configure an Oracle policy from the NetBackup Administration Console on the
master server. Depending on your master server’s 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:

16 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring a NetBackup for Oracle Policy and Schedule

▼ To invoke the NetBackup Administration Console on a UNIX master server

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

2. Start the NetBackup Administration Console by typing the following command:

/usr/openv/java/jnbSA &

▼ 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 System Administration Guide for Windows, Volume I.

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

2. Start the NetBackup Administration Console by clicking Start > All Programs >
VERITAS NetBackup > NetBackup Administration Console.

Creating an Oracle Policy and 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. If necessary, use File > Change Server to select the master server upon which you
want to create the policy.

2. In the left pane, click Policies.

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

The Add a New Policy dialog displays.

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

b. Click in the box to the right of Use add policy wizard to use the Backup Policy
Configuration Wizard. Click OK.

c. Click Next.

4. Complete the Backup Policy Configuration Wizard by supplying the following

information:

Chapter 2, NetBackup for Oracle QuickStart 17

Configuring a NetBackup for Oracle Policy and Schedule

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

b. On the Client List screen, click Add. Add the name of the NetBackup for Oracle
client. Select the hardware and operating system. Click OK. Click Next.

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

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

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

f. Click Finish to create the policy.

5. Proceed to “To create schedules” on page 18 for information on creating schedules for
this policy.

▼ 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.

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

2. Click the Schedules tab.

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

By default, the NetBackup sets the following:

◆ The retention period is 1 month.

◆ Multiplexing is 1.
◆ The schedule is seven days per week and 24 hours per day. This ensures that your
backups can always commence.
Examine the properties for the Default-Application-Backup schedule and change
them if needed.

4. Click OK.

5. Click New to create another schedule.

18 NetBackup for Oracle System Administrator’s Guide for Windows

 Backing Up the Oracle Database

6. Specify a unique name for the schedule.

7. Select Automatic Full Backup as the Type of Backup.

8. Click the Start Window tab.

9. Follow the instructions on the Start screen to specify a time for this schedule.
You must specify a time and a duration for the Automatic Full Backup schedule.
Depending on the size of the database and your site conditions, an Automatic Full
Backup can take a long time to complete. Choose a time when your system is not
likely to be in use. For example, you might 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.

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 19
◆ “To back up the Oracle database using the Backup Wizard” on page 21

▼ To log into the client and invoke the Backup Wizard

1. Use operating system methods to log into the client upon which NetBackup for Oracle
is installed.

2. Make sure that the Oracle database is in the mount or open state.
If this is not the case, this procedure fails.

3. Start the NetBackup Backup, Archive, and Restore interface on the NetBackup client
by clicking Start > All Programs > VERITAS NetBackup > Backup, Archive, and
Restore.

4. Provide the information requested by the login dialog box.

Chapter 2, NetBackup for Oracle QuickStart 19

Backing Up the Oracle Database

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 the administrator or as
the Oracle administrator.
After NetBackup accepts your login information, the NetBackup Administration
Console appears.

5. Click the Backup Files tab.

6. 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.

7. Decide whether you want to back

up an entire Oracle instance or an
individual Oracle instance data
file.
◆ To back up an entire Oracle

instance, go to step 8.

Click here to expand the Oracle node

◆ To back up an individual

Oracle instance data file, go to

step 9.

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

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

b. Proceed to step 10.

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

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

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

Information dialog box appears. Type the Oracle administrator authentication
information into the following fields:
◆ User name: (must have SYSDBA priviledge)
◆ Password:

20 NetBackup for Oracle System Administrator’s Guide for Windows

 Backing Up the Oracle Database

◆ Net service name (TNS alias):

c. Select the data files or tablespaces in the instance that you want to back up by
clicking in the checkbox to the left of each instance data file’s name.

d. Proceed to step 10.

10. Click Actions > Start Backup of Marked Files.

The NetBackup for Oracle Backup Wizard Welcome screen displays.

▼ 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 database’s 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 19
describes how to invoke this wizard. If you just completed that procedure, the Backup
Wizard is displayed on your screen at this time.

2. Click Next.
The Target Database Logon Credentials dialog box displays. Fill in the fields in this
dialog box, as follows:
◆ If you use OS authentication for Oracle, select OS Authentication.
◆ If you use Oracle authentication via a password file, select

Oracle_Authentication and supply the following:

◆ A User name
◆ A Password with Oracle SYSDBA privileges
◆ (Optional) A Net service name (TNS alias)
◆ (Optional) Select Use Oracle RMAN recovery catalog. This is not required. If this
is your first NetBackup for Oracle backup, you can leave this option unselected.
◆ If you did not choose to use the recovery catalog, skip to step 4.

3. Click Next.
If you chose to use the recovery catalog, you see the Recovery Catalog Logon
Credentials screen. Supply the appropriate User name and Password for the recovery
catalog.

4. Click Next. The Archived Redo Logs screen displays.

Chapter 2, NetBackup for Oracle QuickStart 21

Backing Up the Oracle Database

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

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

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

8. Click Next to accept all defaults. The NetBackup Configuration Variables screen
displays.
In the Backup policy name field, enter the name of the Oracle policy you created on
the NetBackup master server.

9. Click Next. The Backup Limits screen displays.

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

11. Click Perform backup immediately after wizard finishes.

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.

22 NetBackup for Oracle System Administrator’s Guide for Windows

Verifying Installation Requirements and
Registering a License Key 3
This chapter describes how to perform the following tasks:
◆ Verifying the installation prerequisites for NetBackup for Oracle. Perform this task
before enabling this agent.
The NetBackup for Oracle software is installed when you install NetBackup, so verify
these prerequisites before enabling NetBackup for Oracle.
◆ Registering the license key for NetBackup for Oracle.
◆ Enabling functions specific to NetBackup for Oracle.

Verifying the Installation Prerequisites

Before enabling NetBackup for Oracle, verify that you are installing the agent on a
supported operating system or platform and that requirements are met for the NetBackup
software, the database agent, and, if applicable, the cluster software. These requirements
apply for remote and local installations.

Operating System and Platform Compatibility

Verify that NetBackup for Oracle will be installed on an operating system or platform
supported by NetBackup. A compatibility list for database agents is available on the
Technical Support web site.

▼ To verify compatibility

1. Go to the Technical Support web page: http://support.veritas.com.

2. From the Select Product Family list, click NetBackup Products.

3. From the Select Product list in the right pane, click NetBackup Enterprise Server.

4. Under Support Resources, click Compatibility and Reference.

23
Verifying the Installation Prerequisites

5. In the list of documents, click NetBackup Enterprise Server (tm)/ Server x.x Database
Agent Compatibility (updated date).
For x.x, look for the current release. For date, look for the most recent date.
For information on supported cluster environments for NetBackup for Oracle, see
NetBackup (tm) x.x Cluster Compatibility (updated date).

6. Click on the link for the PDF document, which is a downloadable file that enables you
to view the supported database spreadsheet for this release.

7. Read the document and verify that the software in your environment is compatible
with the NetBackup and NetBackup for Oracle software.

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 of those that NetBackup supports. For
installation information, see the NetBackup Installation Guide.
❏ The NetBackup client software is installed on the client where you will be backing up
the databases. This step also installs NetBackup for Oracle.
In addition, the install_path\NetBackup directory must exist on the client. On
Windows platforms, the NetBackup for Oracle software is installed along with the
server and client software. For installation information, see the NetBackup Installation
Guide.
❏ Make sure that you have configured backup media in a Media Manager or disk
storage unit. The amount of backup media required depends on the devices used, the
sizes of the databases that you are backing up, the amount of data that you are
archiving, the size of your backups, and the frequency of backups or archives. For
information on using Media Manager, see the NetBackup Media Manager System
Administrator’s Guide.

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.

24 NetBackup for Oracle System Administrator’s Guide for Windows

 Verifying the Installation Prerequisites

❏ For all Oracle 8 releases, make sure you have stopped Oracle services. For more
information about when you need to perform this step, see your Oracle
documentation.
For information on installing Oracle and creating instances, see your Oracle

documentation.

Cluster Software
Verify the following requirements if you are enabling the NetBackup for Oracle 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.
The NetBackup server installation procedure installs the NetBackup for Oracle
software along with the server and client software. After all other prerequisites are
met, you only need to register the license key for the agent on each NetBackup server
in order to enable the agent.

Chapter 3, Verifying Installation Requirements and Registering a License Key 25

Registering the License Key

Registering the License Key

NetBackup for Oracle is installed with the server and client software. To use this agent,
register a valid license key for it on the master or media server. In a NetBackup cluster,
register the key on each node on which the NetBackup server is installed.

▼ To register a license key

1. On the master or media server, open the NetBackup Administration Console.

2. Choose Help > License Keys.

3. Click the New button.

4. Type in the license key and click Add.

For information on adding license keys, see the NetBackup System Administrator’s
Guide, Volume I.

5. Restart Oracle services on the client.

26 NetBackup for Oracle System Administrator’s Guide for Windows

 Oracle Recovery Catalog Information

Oracle Recovery Catalog Information

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 3, Verifying Installation Requirements and Registering a License Key 27

Oracle Recovery Catalog Information

28 NetBackup for Oracle System Administrator’s Guide for Windows

Configuration 4
Before attempting to configure NetBackup for Oracle, complete the installation procedure
as described in the Installation chapter.
The configuration procedure is as follows:

1. Configuring the Maximum Jobs Per Client

2. Configuring Backup Policies

3. Configuring the Runtime Environment

4. Creating Templates and Shell Scripts

5. Database User Authentication and Server-directed Backups

6. Testing Configuration Settings

The following subsections describe these steps.

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 server’s
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, but when there are interface
differences in the configuration procedures, this manual uses the following headings to
identify the interface being described:
From the Windows interface:
From the Java interface:

29
Configuring the Maximum Jobs Per Client

Configuring the Maximum Jobs Per Client

▼ To configure the Maximum jobs per client

1. In the left pane of the NetBackup Administration Console, expand Host Properties.

2. Select Master Server.

3. In the right pane, double-click on the server icon.

The Master Server Properties dialog box displays.

4. In the Master Server Properties dialog box, click Global Attributes.

5. Change the Maximum jobs per client value to 99.

The Maximum jobs per client specifies the maximum number of concurrent backups
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.

number_of_policies 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.

For Oracle backups and restores, the number of jobs is hard to determine 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 executed by Oracle. You might need to experiment with different
values at your site.

30 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Backup Policies

Configuring Backup Policies

A NetBackup policy defines the backup criteria for a specific group of one or more clients.
These criteria include:
◆ Storage unit and media to use
◆ Policy attributes
◆ Backup schedules
◆ Clients to be backed up
◆ Backup templates or shell script files to be run on the clients
To use NetBackup for Oracle, 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 Oracle policies are the same as for file system backups. In addition
to the attributes described here, there are other attributes for a policy to consider. For
configuration instructions and information on all the attributes available, see the
NetBackup System Administrator’s Guide, Volume I.

Adding a New Policy

▼ To add a new policy

1. Log on to the master server as administrator (Windows) or root (UNIX).

2. Start the NetBackup Administration Console.

3. If your site has more than one master server, choose the one on which you want to
add the policy.

4. 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.
The Add a New Policy dialog box displays.

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

6. Click OK.
A dialog box displays in which you can specify the general attributes for the policy.

Chapter 4, Configuration 31
Configuring Backup Policies

7. From the Policy Type box, select the Oracle policy type.

Note The Oracle policy type does not appear in the drop-down list unless your master
server has a license key for NetBackup for Oracle.

8. Complete the entries on the Attributes tab. For more information, see “Description of
Attributes”, which follows this procedure.

9. Add other policy information.

◆ To add schedules, see “Adding Schedules” on page 33.
◆ To add clients, see “Adding Clients” on page 40.
◆ To add templates or shell scripts to the Backup Selections list, see “Adding
Backup Selections” on page 41.

10. When you have added all the schedules, clients, and Backup Selections you need,
click OK. The new policy is created.

Description of Attributes
With a few exceptions, NetBackup manages a database backup like a file system backup.
The following table shows the policy attributes that are different for Oracle backups. This
information is used when you are adding 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 System
Administrator’s Guide, Volume I.

Description of Policy Attributes

Attribute Description

Policy type Determines the types of clients that can be in the policy and, in some cases,
the types of backups that NetBackup can perform on those clients. To use
NetBackup for Oracle, you must define at least one policy of type Oracle.

Keyword phrase For NetBackup for Oracle, the Keyword phrase entry is ignored.

Advanced Client See “Using NetBackup for Oracle with Advanced Client” for information
on configuring policies for advanced backup methods.

32 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Backup Policies

Adding Schedules
Each policy has its own set of schedules. These schedules initiate automatic backups and
specify when a user can initate operations.
An Oracle backup or XML export requires an Application Backup schedule, which is
created automatically when you create an Oracle policy. The Application Backup
schedule manages the backup operation. You also need one or more automatic backup
schedules if you plan to have NetBackup perform automatic scheduled backups or if you
are using Advanced Client features.

▼ To configure an Application Backup schedule

1. In the Policy dialog, click the Schedules tab.

To access the Policy dialog, double-click the policy name in the Policies list in the
NetBackup Administration Console.

2. Double-click on the schedule named Default-Application-Backup.

A dialog box displays. The title bar shows the name of the policy to which you are
adding the schedule.
All Oracle backup operations are performed through NetBackup for Oracle using an
Application Backup schedule. This includes backups that start automatically.
Configure an Application Backup schedule for each Oracle policy you create. If you
do not do this, you cannot perform a backup. To help satisfy this requirement, an
Application Backup schedule named Default-Application-Backup is automatically
created when you configure a new Oracle policy.

3. Specify the other properties for the schedule as explained in “Schedule Properties” on
page 37.
The backup window for an Application Backup schedule must encompass the time
period during which all NetBackup for Oracle jobs, scheduled and unscheduled, can
occur. This is necessary because the Application Backup schedule starts processes that
are required for all NetBackup for Oracle backups, including those started
automatically.

Tip For an XML Export backup to be used for database archiving purposes, set the
Retention to infinity.

For example, assume the following:

◆ Users perform Oracle backup operations during business hours, 0800 to 1300.
◆ Automatic backups that use this policy commence between 1800 and 2200.

Chapter 4, Configuration 33
Configuring Backup Policies

The Application Backup schedule must have a start time of 0800 and a duration of 14
hours.

Example Settings for an Application Backup schedule

Type of Backup Schedule settings Description Settings

Application Retention The length of time the backup 2 weeks
Backup images are retained in the
NetBackup catalog for restore.
Backup Window The time during which a NetBackup Sunday through Saturday
operation can be initiated. 00:00:00 - 24:00:00

Tip Set the time period for the Application Backup schedule for 24 hours per day, seven
days per week. This ensures that your NetBackup for Oracle operations are never
locked out due to the Application Backup schedule.

▼ To configure an automatic backup schedule

1. On the Policy dialog, click the Schedules tab.

2. Click New.
A dialog box displays. The title bar shows the name of the policy to which you are
adding the schedules.

3. Specify a unique name for the schedule.

4. Select the Type of backup.

For information on the types of backups available for this policy, see “Types of Backup
Schedules” on page 36.

Tip For an XML Export backup to be used for database archiving purposes, set the
Retention to infinity.

5. Specify the other properties for the schedule as explained in Schedule Properties,
which follows this procedure.

34 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Backup Policies

The following table shows example settings for an automatic backup schedule:

Type of Backup Schedule settings Description Settings

Automatic Full Retention The length of time to store the 2 weeks
Backup record of a backup, which
NetBackup uses to determine if
the schedule needs to be run.
Frequency Frequency determines how often every week
a backup should be performed.
Backup Window The time during which a Sunday, 18:00:00 - 22:00:00
NetBackup operation can be
initiated.
Automatic Retention The length of time to store the 1 week
Differential record of a backup, which
Incremental Backup NetBackup uses to determine if
the schedule needs to be run.
Frequency Frequency determines how often every day
a backup should be performed.
Backup Window The time during which a Sunday through Saturday
NetBackup operation can be 18:00:00 - 22:00:00
initiated.
Automatic Retention The length of time to store the 1 week
Cumulative record of a backup, which
Incremental Backup NetBackup uses to determine if
the schedule needs to be run.
Frequency Frequency determines how often every day
a backup should be performed.
Backup Window The time during which a Sunday through Saturday
NetBackup operation can be 18:00:00 - 22:00:00
initiated.

When an automatic schedule is run, NetBackup sets environment variables based on

the type of automatic backup schedule selected. You can use these environment
variables to initiate a backup conditionally. For more information, see “Environment
Variables Set by NetBackup for Oracle” on page 46.

6. If this is the last schedule, click OK. To add other schedules, repeat step 1 through
step 6.

Chapter 4, Configuration 35
Configuring Backup Policies

Types of Backup Schedules

You can perform backups with the following types of schedules:

Oracle Backup Types

Application Backup The Application Backup schedule enables user-controlled NetBackup

operations from the client, both those initiated from the client and those
initiated by an automatic schedule on the master server. NetBackup uses the
Application Backup schedule when the Oracle user starts a backup
manually. Configure at least one Application Backup schedule for each
Oracle policy. The Default-Application-Backup schedule is configured
automatically as an Application Backup schedule.

Automatic Full An Automatic Full Backup copies all blocks into the backup set, skipping
Backup only datafile blocks that have never been used. The Automatic Full Backup
schedule enables scheduled NetBackup operations performed on the client.
It is used to run a backup or XML export template or script automatically.

Automatic In a differential level n incremental datafile backup, you back up all blocks
Differential that have changed since the most recent full or incremental backup at level n
Incremental Backup 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.
Do not use an Automatic Differential Incremental Backup schedule for
Oracle XML Exports.

Automatic In a cumulative level n incremental backup, you back up all blocks that have
Cumulative changed since the most recent full backup at level n-1 or lower. For example,
Incremental Backup 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 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, because
they duplicate the work done by 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 performing backups
and restores. Be aware that when an automatic schedule invokes a script authored by a
user, NetBackup does not provide safeguards to prevent unusual behavior, such as an
automatic backup schedule running a restore or recovery script.

36 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Backup Policies

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 Advanced Client Features

The information in “Types of Backup Schedules” on page 36 pertains to stream-based
backups. If you are using the NetBackup Advanced Client, be aware that some of the
information in that table might differ depending on the Advanced Client features that you
are using. For more information about backup schedules and Advanced Client features,
see “NetBackup for Oracle with Advanced Client” on page 105.

Schedule Properties
Some of the schedule properties have a different meaning for database backups than for a
regular file system backup. The following table explains the schedule properties:

Description of Schedule Properties

Property Description

Type of backup Specifies the type of backup that this schedule controls. The selection list
shows only the backup types that apply to the policy you are configuring.
For more information, see “Types of Backup Schedules” on page 36.

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, if
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.

Calendar 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 based on specific dates, recurring week days, or recurring days of
the month.

Chapter 4, Configuration 37
Configuring Backup Policies

Description of Schedule Properties (continued)

Property Description

Retention Frequency-based scheduling

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.
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 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. However, this setting is not significant for
calendar-based scheduling.

Multiple copies If you want to specify multiple copies for your Oracle 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 System
Administrator’s Guide, Volume I.

38 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Backup Policies

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 37.

▼ 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 62.
When a request is issued to delete a backup file from the RMAN repository, RMAN
sends the request to NetBackup for Oracle to delete the corresponding image from the
NetBackup repository, regardless of the retention level.

Chapter 4, Configuration 39
Configuring Backup Policies

Adding Clients
The client list is the list of clients on which your NetBackup for Oracle templates or shell
scripts are 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.
The following software must be installed on the client:
◆ Oracle
◆ NetBackup client or server
◆ The backup or XML export archive shell script(s) (unless you are using templates)

▼ To add clients to a policy

1. In the Policy dialog, click the Clients tab.

To access the Policy dialog, double-click the policy name in the Policies list in the
NetBackup Administration Console.

2. Click New.

3. 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:

◆ Type the name into the client list 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:

40 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Backup Policies

a. The Add Client dialog box displays. In the Client name field, type the name of
the client you are adding.

b. Choose the Hardware and operating system type and click Add.

4. To add another client, repeat step 2 and step 3.

5. If this 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 an MS-Windows-NT policy, the list contains files
and folders to be backed up. In a NetBackup for Oracle database policy, you specify
templates or shell scripts to be run.
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. As part of the modification process, write the scripts to
a location outside of the original installation location so future NetBackup
installations do not overwrite your site’s scripts.
◆ If you are using 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 shell scripts only if you are setting up a policy for automatic scheduling.
All templates or shell scripts listed in the backup selections list 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 shell scripts in the order that the templates or shell
scripts appear in the Backup Selections list.
For more information on backup templates and scripts, see “Creating Templates and Shell
Scripts” on page 47.

▼ To add templates or shell scripts to the backup selections list

The following steps show how to perform this procedure from both the Java interface and
from the Windows interface.

Chapter 4, Configuration 41
Configuring Backup Policies

Caution Be sure to specify the correct template and shell script names in the Backup
Selections list to prevent an error or possibly a wrong operation. Make sure that
the template or shell script resides on the client before you try to add it to the
Backup Selections list.

From the Java interface:

1. Open the Policy dialog.

To access the Policy dialog, double-click the policy name in the Policies list in the
NetBackup Administration Console.

2. Click the Backup Selections tab.

3. Click New.
A dialog box displays.

4. Specify the names of templates that you want NetBackup to use.

a. From the Template Set list, choose the template type by operation. Then, specify a
specific template by choosing the template from the drop-down Script or
Template list or by typing the correct template file name.
Include the .tpl extension. Do not include the full path.
For example:
weekly_full_backup.tpl

b. Click Add to add the template to the list.

c. Repeat step a and step b until all templates are added.

5. Specify the names of the shell scripts that you want NetBackup to use.

a. In the Script: box, type the full path name of a shell script on the client.

For example:

C:\backup_scripts\db\cold_backup.cmd

b. Click Add to add the shell script to the list.

c. Repeat step a and step b until all shell scripts are added.

6. Click OK.

42 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Backup Policies

From the Windows interface:

1. In the Policy dialog, click the Backup Selections tab.

To access the Policy dialog, double-click the policy name in the Policies list in the
NetBackup Administration Console.

2. Click New.

3. Specify the names of the templates you want NetBackup to use.

Use one of the following methods:
◆ 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. The Select Template dialog displays. From the
Template set list, choose the template type by operation. From the Template list,
choose the correct template. Click OK.

4. Specify the names of the shell scripts you want NetBackup to use.
Use one of the following methods:
◆ Type the full path name of the shell script on the client.

For example:

C:\backup_scripts\db\cold_backup.cmd

◆ Click the Remote Folder button.

The Browse window displays the hosts in the client list. Navigate to and select the
shell script file. Click OK.

5. Click OK.

Chapter 4, Configuration 43
Configuring the Runtime Environment

Configuring the Runtime Environment

The order of precedence for run-time configuration is slightly different for scheduled
backups using templates than for all other types of backups. The lists below show the
order of precedence for each situation. The following is the order of precedence for the
run-time configuration variable settings.

Scheduled Backups with Templates

1. Environment variables set by NetBackup for Oracle

For more informaiton, see “Environment Variables Set by NetBackup for Oracle” on
page 46.

2. 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 45.
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 46.

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 45.
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 46.
These variables can also be set by the user on the Configuration Variables screen of the
template generation wizards. However, they apply only to templates run from the
client (through the wizard or through Template Administration). When templates are
run by the scheduler on the NetBackup master server, NetBackup overrides these
variables.

2. Environment variables set by NetBackup for Oracle

For more information, see “Environment Variables Set by NetBackup for Oracle” on
page 46.

44 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring the Runtime Environment

Oracle RMAN Environment

Because components of RMAN run as services on Windows, special attention should be
given to environment variables. The environment that a service runs in is established
when the service is started, usually when the system is booted. Typically, a service is run
under the SYSTEM account so it can take on the system level environment settings.
Because a Service provides RMAN functionality, an environment variable set at runtime is
not visible during a backup or restore.

Templates
With templates, NetBackup for Oracle on Windows 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 48.

Shell Scripts
Use the send command 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');

Chapter 4, Configuration 45
Configuring the Runtime Environment

Environment Variables Set by a User in the XML Export

Parameter File
The NetBackup for Oracle variables that follow can be set in the XML export parameter
file for use in the Oracle user environment. With templates, these variables are set using
the Template Generation Wizard. For more information, see “Creating XML Export
Templates Using the NetBackup for Oracle Wizard” on page 53.

Environment Variable Purpose

NB_ORA_SERV Specifies the name of NetBackup master server.

NB_ORA_CLIENT Specifies the name of the Oracle client. It is especially useful for
specifying a virtual client name in a cluster.

NB_ORA_POLICY Specifies the name of the policy to use for the Oracle backup.

NB_ORA_SCHED Specifies the name of the Application Backup schedule to use for
the Oracle backup.

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 are set only if the
backup is started from the server, either automatically by the NetBackup scheduler or
manually through the administrator interface. The variables are as follows:

Environment Variable Purpose

NB_ORA_SERV Name of the NetBackup Server.

NB_ORA_POLICY Name of the Oracle policy.

NB_ORA_CLIENT Name of the NetBackup client that hosts the Oracle database.

NB_ORA_FULL Set to 1 for Automatic Full Backups.

NB_ORA_INCR Set to 1 for Automatic Differential Incremental Backups.

NB_ORA_CINC Set to 1 for Automatic Cumulative Incremental Backups.

46 NetBackup for Oracle System Administrator’s Guide for Windows

 Creating Templates and Shell Scripts

Creating Templates and Shell Scripts

RMAN shell scripts and RMAN templates contain commands that run NetBackup for
Oracle RMAN backup and recovery jobs. XML export and XML import templates and
shell scripts contain commands that run NetBackup for Oracle XML export backup and
XML import restore jobs. Scripts and templates must be created before NetBackup for
Oracle can perform scheduled backups. These are the shell scripts or template files that
are specified as Backup Selections in the policy configuration on the NetBackup server.
For more information on scripts, see the Oracle Backup and Recovery Guide.

Recovery Manager (RMAN)

RMAN Templates and Shell Scripts

Templates
The NetBackup for Oracle Backup Wizard creates backup templates. You can invoke this
wizard from the NetBackup Client graphical user interface. For more information, see
“Creating RMAN Templates Using the NetBackup for Oracle RMAN Template
Generation Wizard” on page 48.
The NetBackup for Oracle Backup Wizard does not support all of the RMAN commands
and options provided by Oracle. 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 RMAN and Windows 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.
For more information, see “Creating RMAN Scripts Manually” on page 50.
NetBackup for Oracle also provides the bpdbsbora utility, which 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 it. The user can run the shell script or modify the
shell script further. For more information, see “Creating an RMAN Script From a
Template” on page 49.

Chapter 4, Configuration 47
Creating Templates and Shell Scripts

Creating RMAN Templates Using the NetBackup for Oracle RMAN

Template Generation Wizard
NetBackup for Oracle includes a Backup Wizard that solicits information about needed
RMAN backup operations. The wizard uses the information to create a template that can
be run immediately or saved on the current master server for later use.
For more information on backup strategies and RMAN functionality, see your Oracle
documentation.
If Oracle is installed, the Backup, Archive, and Restore interface on the client displays an
Oracle node in the left pane. From the client, 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.
If your current login does not have Oracle SYSDBA privileges, the system prompts you to
enter your Oracle database login user name and password with SYSDBA privileges to
continue. Optionally, also enter your Net service name (TNS alias).

▼ To use the Backup Wizard

1. In the Backup, Archive, and Restore interface, expand an Oracle instance.

2. Select the Oracle objects (datafiles, tablespaces, archived redo logs) to back up.
Selecting the Oracle instance backs up the whole database using RMAN.

3. Choose Actions>Start Backup of Marked Files.

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:
◆ Target Database Logon Credentials
◆ Recovery Catalog Logon Credentials

48 NetBackup for Oracle System Administrator’s Guide for Windows

 Creating Templates and Shell Scripts

◆ Archived Redo Logs

◆ Configuration Options
◆ Backup Options
◆ Database State
◆ NetBackup for Oracle 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.

4. After you complete the wizard, the Template Summary screen displays the summary
of the backup template.
You can 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

The options are as follows:

-backup Specifies the template type.

-g script_file 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 t
empl_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 backup templates from a known location on
the master server, so specify only the template file 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.

Chapter 4, Configuration 49
Creating Templates and Shell Scripts

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 datafile backup set, you can make either an incremental backup or a
full backup. An incremental backup is a backup of one or more datafiles that contain only
those blocks that have been modified since a previous backup. A full backup is a
nonincremental backup of one or more datafiles that contain all blocks of the datafiles.

When NetBackup for Oracle was initially installed, example scripts were written to the
following directory:
install_path\NetBackup\dbext\Oracle\samples\rman

The Oracle example scripts installed are as follows:

pit_database_restore.cmd

hot_tablespace_backup.cmd

hot_database_backup.cmd

database_restore.cmd

cold_duplex_database_backup_full.cmd

cold_database_backup.cmd

▼ To use sample scripts provided by NetBackup for Oracle

1. Copy the example scripts to a different directory on your client. Oracle scripts can be
located anywhere on the client.

2. Modify each script for your environment.

50 NetBackup for Oracle System Administrator’s Guide for Windows

 Creating Templates and Shell Scripts

The following table explains some of the sample scripts provided with NetBackup for
Oracle.

NetBackup for Oracle Sample Scripts

cold_database_backup.cmd 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.

hot_database_backup.cmd 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 this script could
be used to automatically execute a backup
every week on Friday night and an
incremental backup each night for the rest of
the week.

cold_duplex_database_backup_full.cmd This script sets up the environment and calls

RMAN to run commands that make two
copies of a cold (consistent) database backup.

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
Oracle, 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.

Chapter 4, Configuration 51
Creating Templates and Shell Scripts

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 for Oracle 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

XML Export Templates and Shell Scripts

Templates
The NetBackup for Oracle XML Export Wizard creates XML export templates. This
wizard is initiated from the NetBackup Backup, Archive, and Restore interface.
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.

52 NetBackup for Oracle System Administrator’s Guide for Windows

 Creating Templates and Shell Scripts

Shell Scripts
Shell scripts are written by the user and must conform to the operating system’s 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 start the NetBackup Backup, Archive, and Restore interface on the NetBackup
client, do the following:
From the Start menu, click VERITAS NetBackup > Backup, Archive, and Restore.
Click the Backup Files tab. If Oracle is installed, the Backup, Archive, and Restore
interface on the client displays an Oracle node in the left pane.
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.
If your current login does not have Oracle SYSDBA privileges, enter your Oracle database
login User name and Password with SYSDBA privileges to continue. Optionally, also
enter your Net service name (TNS alias).

▼ 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 display.

2. Expand the User list to the schema owners of the objects to be exported.

3. In the right pane, select the Oracle objects to export.

Chapter 4, Configuration 53
Creating Templates and Shell Scripts

4. From the Actions menu, choose Start Backup of Marked Files to start the wizard.

The NetBackup for Oracle XML Export Template Generation 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. After you complete the wizard, the Selection Summary screen displays the summary
of the XML export template.
You can 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.

54 NetBackup for Oracle System Administrator’s Guide for Windows

 Creating Templates and Shell Scripts

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

The options are as follows:

-export Specifies the template type.

-g script_file 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.

-S server_name Specifies the master server upon which the template resides. When
specified, the bpdbsbora command retrieves XML export templates
from the specified master server.

Creating XML Export Scripts Manually

When NetBackup for Oracle was initially installed, example scripts were written to the
following locations:
For export:
install_path\NetBackup\dbext\Oracle\samples\bporaexp

For import:
install_path\NetBackup\dbext\Oracle\samples\bporaimp

The example export scripts installed in bporaexp are as follows:

data_archiver_export.cmd

bporaexp_help.param

bporaexp_partitions.param

bporaexp_table_to_files.param

bporaexp_tables.param

bporaexp_tables_rows.param

Chapter 4, Configuration 55
Creating Templates and Shell Scripts

The example import scripts installed in bporaimp are as follows:

data_archiver_import.cmd

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

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 sample scripts provided by NetBackup for Oracle

1. Copy the example scripts to a different directory on your client. Oracle scripts can be
located anywhere on the client.

2. Modify each script for your environment.

Storing Templates and Shell 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.
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.

56 NetBackup for Oracle System Administrator’s Guide for Windows

 Database User Authentication and Server-directed Backups

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 41.
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.

Database User Authentication and Server-directed

Backups
Because the NetBackup client service is, by default, started under the SYSTEM account,
special attention must also be given to database user authentication. The SYSTEM account
does not have permission to connect to the target database if you are using OS
Authentication instead of passwords. If you are using OS Authentication, run the
NetBackup client service under an account that has SYSDBA privileges. Use the following
procedure to change the user account.

▼ To change the user account for the NetBackup client services

1. Choose Start > Settings > Control Panel.

2. From the Control Panel, open Services.

3. Highlight NetBackup Client Service, and click Stop.

4. Click Startup.

5. From the Log ON As: pane, select This Account.

6. Type in the account name with SYSDBA privileges.

7. Type in the password.

8. Click OK.

9. Click START to restart the service.

Chapter 4, Configuration 57
Database User Authentication and Server-directed Backups

For more information on OS Authentication, see your Oracle documentation.

58
NetBackup for Oracle System Administrator’s Guide for Windows
 Testing Configuration Settings

Testing Configuration Settings

After configuring the master server for NetBackup for Oracle, test the configuration
settings by performing a manual backup (or backups) using the automatic backup
schedules you have created.

▼ To test the configuration settings

1. Log onto the master server as administrator (Windows) or root (UNIX).

2. Start the NetBackup Administration Console.

3. 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.

4. Click the policy you want to test.

5. Choose Actions > Manual Backup.

The Manual Backup dialog box appears.
The Schedules pane contains the name of an automatic schedule (or schedules)
configured for the policy that you are going to test. The Clients pane contains the
name of the client(s) listed in the policy that you are going to test.

6. Follow the directions in the Manual Backup dialog box.

7. Click Activity Monitor on the NetBackup Administration Console.

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.
If the manual backup does not exit with a successful status (as indicated by the
Activity Monitor and in the script output), see “Troubleshooting” on page 129.
For a description of status codes and other troubleshooting information, see the NetBackup
Troubleshooting Guide.

Chapter 4, Configuration 59
Testing Configuration Settings

60 NetBackup for Oracle System Administrator’s Guide for Windows

Using NetBackup for Oracle 5
The NetBackup graphical user interfaces and command line interfaces allow you to
perform Oracle backup and recovery operations using Oracle’s RMAN utilities and to
perform Oracle archives and restores using NetBackup’s 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.
This chapter contains the following sections:
◆ Maintaining the RMAN Repository
◆ Querying the RMAN Repository
◆ Performing a Backup
◆ Browsing Backups
◆ Performing a Restore
◆ Performing Other RMAN Actions
◆ Performing an XML Export Archive
◆ Browsing XML Export Archives
◆ Performing a Restore of an XML Export Archive
◆ Using NetBackup for Oracle in a Microsoft Cluster Server Environment

61
Maintaining 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 can conduct all major
backup and recovery operations using just the control file, some RMAN commands
function only when you use a recovery catalog.
The following list 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.

Task Commands used to accomplish the task

Registering a Before using RMAN with a recovery catalog, register the target database in
database with the the recovery catalog. To do this, start and mount the target database but do
recovery catalog not open it. At the RMAN prompt, issue a register database
command.
Resetting the The reset database command directs RMAN to create a new database
incarnation in the incarnation record in the recovery catalog.
recovery catalog
Cross checking the Because NetBackup can mark backup images as expired, the RMAN
information in the repository can contain outdated information. To ensure that data in the
RMAN repository 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:
◆ 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:
change backuppiece {primary_key_list|filename_list|tag}

crosscheck;

change backupset {primary_key_list} crosscheck;

62 NetBackup for Oracle System Administrator’s Guide for Windows

 Maintaining the RMAN Repository

Task Commands used to accomplish the task

The crosscheck backupset command operates on available and
expired backup pieces. RMAN updates their status with the result (available
or expired).
To crosscheck 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;

Deleting expired The delete expired backup command operates only on expired
backups 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.
Resynchronizing the RMAN compares the recovery catalog to either the current control file of the
recovery catalog target 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.

Chapter 5, Using NetBackup for Oracle 63

Maintaining the RMAN Repository

Task Commands used to accomplish the task

Changing the Periodically, you might need to notify RMAN that the status of a backup set,

availability of a backup piece, datafile copy, or archived redo log has changed. The RMAN

backup set or file change command enables you to make a variety of useful record changes.

copy The change ... uncatalog command removes references to a backup

piece, datafile 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, datafile 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, datafile 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, datafile

copy, or archive log as unavailable. This command works only with a

recovery catalog.

Validating the restore A restore validation executes a restore test run without restoring the files.

of backups Test the restore of the entire database or individual tablespaces, datafiles, 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.

64 NetBackup for Oracle System Administrator’s Guide for Windows

 Querying the RMAN Repository

Querying the RMAN Repository

RMAN allows you to 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?
◆ 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 datafiles.
◆ Backup sets containing a backup of any datafile that is a member of a specified list of
tablespaces.
◆ All backup sets or copies of all datafiles 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.

Chapter 5, Using NetBackup for Oracle 65

Performing a Backup

Performing a Backup
This section describes how to perform the following types of backups:
◆ Automatic Backup of an Oracle Policy
◆ Manual Backup of an Oracle Policy
◆ User-directed Backup From the Client
◆ Running NetBackup for Oracle Templates
◆ Using bpdbsbora to Run a Backup Template
◆ Running the NetBackup for Oracle Shell Script
◆ Running RMAN

Automatic Backup of an Oracle Policy

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.

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 System
Administrator’s Guide, Volume I.
For information on initiating a manual backup of an Oracle policy, see “Testing
Configuration Settings” on page 59.

User-directed Backup From the Client

This section describes several ways to perform a user-directed Backup.

66 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Backup

Running NetBackup for Oracle Templates

The Oracle Template Administration dialog 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 48.

▼ To use Oracle Template Administration

1. In the Backup, Archive, and Restore interface, choose Actions>Administer Database

Templates>Oracle.
The Oracle Template Administration window appears:

The Select Template list shows the names and descriptions of the Oracle templates
stored on the current master server.

2. Select the name of the backup template you want to run.

3. Click Run.
You can use the View Status tool to see the status of the backup. Click Actions>View
Status.

Chapter 5, Using NetBackup for Oracle 67

Performing a Backup

The Oracle Template Administration window provides the following functions:

Run Runs the selected template.

Edit Changes the contents of an existing template. The selected backup

template is loaded into the NetBackup for Oracle RMAN Template
Generation Wizard.

Delete Removes the selected template. You must be a system administrator

or the template creator to delete a template.

Rename Changes the name of the selected template. You must be a system
administrator or the template creator to rename a template.

View Displays a summary of the selected template.

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]

The options are as follows:

-backup Specifies the template type.

-r Runs the template.

-t templ_name 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.

-S server_name Optional. Specifies the master server upon which the templates reside.
When specified, the bpdbsbora command retrieves backup templates
from the specified master server.

-L prog_file Optional. Specifies a runtime progress log. Enclose prog_file in

quotation marks (" ") if it contains space characters.

For example:
bpdbsbora -backup -r -t ORCLMonfull.tpl -S my_mast -L my_prog_log

68 NetBackup for Oracle System Administrator’s Guide for Windows

 Browsing Backups

Running the NetBackup for Oracle Shell Script

When you run a NetBackup for Oracle shell script on a client to initate a backup from the
operating system’s command prompt, specify the full path name to the file that contains
the script. For example:
N:\oracle\scripts\db_full_backup.cmd

The shell starts the database backup by running the Oracle shell script. The Oracle shell
script contains commands to run rman.
The NetBackup for Oracle installation script installs sample scripts in the following
location:
install_path\NetBackup\dbext\oracle\samples\rman

Running RMAN
As an Oracle user, you can run the rman command from the operating system’s 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.
RMAN functionality executes as a service, so use the send operand to set up the runtime
environment. To start a backup using the rman command from 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

"N:\oracle\scripts\db_full_backup.rcv"

For more information, see “Oracle RMAN Environment” on page 45.

Browsing Backups
This section describes the following procedures for browsing backup images:
◆ Using the RMAN Repository to Browse Backups
◆ Using bplist to Browse Backups

Using the RMAN Repository to Browse Backups

You can use the RMAN report and list commands to browse Oracle backups. For
more information, see “Maintaining the RMAN Repository” on page 62.

Chapter 5, Using NetBackup for Oracle 69

Performing a Restore

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 administrator to the master server
◆ Log in as administrator to the client with the appropriate altnames entry.
The following example uses bplist to search all Oracle backups for a client named
jupiter:
install_path\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
online help.

Performing a Restore
Make sure a backup has been successfully completed before attempting a restore. An
error occurs if a backup history does not exist.
This section describes the following procedures for performing user-directed restores:
◆ Running the NetBackup for Oracle Recovery Wizard on the Client
◆ Using bpdbsbora
◆ Running the NetBackup for Oracle Recovery Shell Script on the Client
◆ Running RMAN on the Client
◆ Redirecting a Restore to a Different Client

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. You can use the template immediately or you can save it
for later use.

70 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore

The NetBackup for Oracle 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.
The recovery process sometimes requires passwords for Oracle database access and
system user accounts. Templates store 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.

▼ 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 from the Start menu on the client.

❖ 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 Start menu, click Start >
All Programs > VERITAS NetBackup > Backup, Archive, and Restore.

▼ To start the Recovery Wizard

1. (Conditional) Change the policy type.

Perform this step if the Oracle node is not visible.
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. On the File menu, select Specify NetBackup Machines and Policy Type for the
restore.

b. In the Specify NetBackup Machines and Policy Type dialog box, select Oracle
from the Policy Type drop-down list.

c. Click OK.

2. From the Select for Restore tab, expand the Oracle node in the left pane to view an
Oracle instance hierarchy.

Chapter 5, Using NetBackup for Oracle 71

Performing a Restore

3. Select a node in the left pane to view details in the right pane.

▼ To use the Recovery Wizard

When you are ready to perform a recovery, follow these steps to create and run a template
with the Recovery Wizard:

1. In the left pane of the Backup, Archive, and Restore interface, select the Oracle
instance.

2. In the right pane, select the database object(s) (datafiles, tablespaces) you want to
recover.
If you select the Oracle instance, the wizard recovers the entire database using
RMAN.

3. On the Actions menu, click Start Restore of Marked Files.

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

72 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore

If you need an explanation of any of the fields on the wizard screens, or more details,
click Help on the wizard screen.

4. 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, or more details,
click Help on the wizard panel.

5. Click Finish to run, save, or run and save the recovery template.

Using bpdbsbora
The bpdbsbora command lets you run a recovery template created by the NetBackup
Recovery Wizard.
At the command prompt, type this command using the following options:
bpdbsbora -restore -r -t templ_name [-L progress_file]

For example:
bpdbsbora -restore -r -t H:\oracle\restore_templs\ORCL_MON_Full.tpl

The options are as follows:

-restore Specifies the template type.

-r Runs the template.

-t templ_name 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.

Chapter 5, Using NetBackup for Oracle 73

Performing a Restore

Running the 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:
H:\oracle\scripts\database_restore.cmd

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 for Oracle installation script writes sample scripts to the following
location:
install_path\Netbackup\dbext\oracle\samples\rman\

Running RMAN on the Client

You can run the rman command from the Windows command prompt on the client using
the appropriate RMAN command file as a parameter.

▼ 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 ‘H:\oracle\scripts\database_restore.rcv’

74 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore

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.
The following illustrates a typical redirected restore process:

1 . Cl
ient A
gets
back Server
e d up
.

2. Clien A
t B requ s client
client A
image
ests res
to r ver restore .
to clien re of 3. The s
e
to clien
t B
t B.
ck up image
ba

Note that 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.
This section describes 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:
install_path\NetBackup\db\altnames\No.Restrictions

Or, to restrict clients to restore only from certain other clients, create the following file:
install_path\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 Oracle source client to that
file.
For more information about redirected restores, see the NetBackup System Administrator’s
Guide, Volume I.

Chapter 5, Using NetBackup for Oracle 75

Performing a Restore

Using RMAN to Perform a Redirected Restore

Perform the following procedure on the destination client host if you want to restore
RMAN backups that are owned by another client.

▼ To perform a redirected restore

1. Enable a network connection to the RMAN catalog database that was used by the
source client.

Note If the RMAN catalog database has been lost, restore the catalog database first before
continuing with the redirected restore.

2. Use the rman parms option to set the NB_ORA_CLIENT environment variable to the
source client.

3. Make the init.ora file of the source client available to the destination client. You
can do this by copying the file to the destination client or by modifying the file on the
destination client. Change all location-specific parameters.

4. Create and start an Oracle service for the previously set ORACLE_SID.

5. Create the folder to which the datafiles will be restored.

6. Set up a password file for the destination client database.

7. Start up the database in the nomount state.

8. Start RMAN, connecting to the catalog and the target database.

9. Run an RMAN restore script.

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

76 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing Other RMAN Actions

1. Create the following file on server lion:

install_path\NetBackup\db\altnames\No.restrictions

2. Modify the network tnsnames.ora file to enable RMAN catalog connection.

3. Create inittest.ora.

4. Using Oracle administration, create and start ORACLESERVICETEST.

5. Set the environment variable ORACLE_SID to test.

6. Make sure the destination database folder exists and has appropriate access
permissions.
The datafiles are restored to the folder path with the same name they had when they
were backed up.

7. Start up the database in a nomount state.

8. Run rman.
rman rcvcat rman/rman@rcat

Recovery Manager: Release 8.0.5.0.0 - Production

RMAN> @restore_database.rcv

where restore_database.rcv is:

run

# Allocates tape channel and sets RMAN environment variable

allocate channel t1 type 'SBT_TAPE'

parms="ENV=(NB_ORA_CLIENT=camel,NB_ORA_SERV=lion)";

restore

(database);

restore

controlfile to 'D:\orant805\database\ctl1TEST.ora';

release channel t1;

Performing Other RMAN Actions

To run script files for database operations other than backups or restores, it is
recommended that you run the rman command directly rather than using NetBackup.
For rman command script syntax and examples, see the Oracle Backup and Recovery
Guide.

Chapter 5, Using NetBackup for Oracle 77

Performing an XML Export Archive

Performing an XML Export Archive

The following sections describe how to perform an XML export archive:
◆ Automatic Backup of an Oracle Policy
◆ Manual Backup of an Oracle Policy
◆ User-directed XML Exports From the Client

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 NetBackup’s 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 System
Administrator’s Guide, Volume I.
For information on initiating a manual backup of an Oracle policy, see “Testing
Configuration Settings” on page 59.

User-directed XML Exports From the Client

This section describes the following procedures for performing user-directed XML
exports:
◆ Running NetBackup for Oracle XML Export Templates
◆ Using bpdbsbora to Run an XML Export Template

78 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing an XML Export Archive

◆ Running the NetBackup for Oracle XML Export Script on the Client
◆ Running bporaexp on the Client as an Oracle User

Running NetBackup for Oracle XML Export Templates

The Template Administration interface is available in the NetBackup Backup, Archive,
and Restore interface.
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.

2. Select the name of the XML Export template you want to run.

3. Click Run.

The Oracle Template Administration window provides the following functions:

Function Name Purpose

Run Runs the selected template.

Edit Changes the contents of an existing template. The selected XML

export template is loaded into the NetBackup for Oracle XML Export

Template Generation Wizard.

Delete Removes the selected template. You must be the administrator or the

template creator to delete a template.

Rename Changes the name of the selected template. You must be the

administrator or the template creator to rename a template.

View Displays a summary of the selected template.

Chapter 5, Using NetBackup for Oracle 79

Performing an XML Export Archive

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]

The options are as follows:

-export Specifies the template type.

-r Runs the template.

-t templ_name 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.

-S server_name Optional. Identifies the master server.

bpdbsbora retrieves XML export templates from a specific master
server when you specify this option.

-L prog_log Optional. Specifies a runtime process log. Enclose prog_log in

quotation marks (" ") if it contains space characters.

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:
N:\oracle\scripts\data_archiver_export.cmd

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:
install_path\NetBackup\dbext\oracle\samples\bporaexp\

80 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing an XML Export Archive

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.
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.

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
DIRECTORY=\db\netbackup\xml parameter is specified, NetBackup creates the
following files when you run the bporaexp command:

NetBackup files for example table USER1

File Content

\db\netbackup\xml\test1\test1.xsd Master XML schema for table USER1

\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
Media Manager or disk 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:

Chapter 5, Using NetBackup for Oracle 81

Performing an XML Export Archive

\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 Media Manager or disk 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

The following table 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 NetBackup Media Manager or
disk 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

82 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing an XML Export Archive

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 Media Manager or disk storage unit.

Target
Parameter Required? Default Description Location

CONSISTENT N N Specifies whether or not Directory

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.

DIRECTORY N no default Optionally specifies a Directory

directory for the output of the
bporaexp utility.

HELP N N Displays a help message with Directory

descriptions of bporaexp
parameters. Does not export
data if HELP=Y.

KEYWORD N no default Optionally specifies a Storage Unit

keyword phrase that
NetBackup associates with
the image being created by
the archive operation. Values
for KEYWORD must be in
double quotes.

Chapter 5, Using NetBackup for Oracle 83

Performing an XML Export Archive

Target
Parameter Required? Default Description Location

LOG N no default Optionally specifies a file Directory

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.

NAME Y no default The name of the master XML Directory

schema file.

NB_ORA_SERV N default Optionally specifies the name Storage Unit

master of the NetBackup master
server server.

NB_ORA_CLIENT N default Optionally specifies the name Storage Unit

client of the NetBackup for Oracle
client.

NB_ORA_POLICY N default Optionally specifies the name Storage Unit

Oracle of the NetBackup for Oracle
policy policy.

NB_ORA_SCHED N default Optionally specifies the name Storage Unit

backup of the backup policy schedule
policy to use.
schedule

OWNER N no default Lists the Oracle schema Directory

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.

84 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing an XML Export Archive

Target
Parameter Required? Default Description Location

PARTITIONS N Y Optionally specifies whether Directory

or not table partitions are
included. Only valid when
used with the OWNER
parameter.

QUERY N no default This parameter lets you select Directory

a subset 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 Directory

the buffer used to fetch rows.
Tables with LONG columns
are fetched one row at a time.
The maximum value allowed
is 32767.

Chapter 5, Using NetBackup for Oracle 85

Browsing XML Export Archives

Target
Parameter Required? Default Description Location

TABLES Y no default Lists the table names, view Directory

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 Directory

username/password (and
optional connect string) of
the user initiating the export.
If a connect string is not
provided, the ORACLE_SID
environment variable is used.

VIEWS N Y Optionally specifies whether Directory

or not views are included.
Only valid when used with
the OWNER parameter.

Browsing XML Export Archives

This section describes the following procedures for browsing XML export archive images
created using bporaexp:
◆ Using bporaimp parameters to browse XML export archives
◆ Using bplist to browse XML export archives

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.

86 NetBackup for Oracle System Administrator’s Guide for Windows

 Browsing XML Export Archives

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.
For information on the LIST, LOG, NB_ORA_CLIENT, NB_ORA_SERV, and USERID
parameters, see “To run bporaexp on the client” on page 82. The following table shows
other parameters you can include in the parameter file:

Parameter Default Description

ARCHIVE_DATE_FROM no default 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].

ARCHIVE_DATE_TO no default 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].

KEYWORD no default Optionally specifies a keyword phrase for NetBackup

to use when searching for archives.

NAME no default The name of the master XML schema file.

FROMUSER no default Optionally specifies a comma-separated list of table

owners.

TABLES no default Optionally specifies a list of table and partition names

that were included in an archive.

For example, assume you named the list parameter file bporaimp_list.param. At the
command prompt, type the following:
bporaimp parfile = bporaimp_list.param

Chapter 5, Using NetBackup for Oracle 87

Browsing XML Export Archives

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 one archive, test.
install_path\NetBackup\bin\bplist -C jupiter -t 4 -R Oracle:\XMLArchive\

Oracle:\XMLArchive\test\test.xsd

Oracle:\XMLArchive\test\SCOTT\BONUS.xsd

Oracle:\XMLArchive\test\SCOTT\BONUS.xml

Oracle:\XMLArchive\test\SCOTT\DEPT.xsd

Oracle:\XMLArchive\test\SCOTT\DEPT.xml

Oracle:\XMLArchive\test\SCOTT\EMP.xsd

Oracle:\XMLArchive\test\SCOTT\EMP.xml

Oracle:\XMLArchive\test\SCOTT\SALGRADE.xsd

Oracle:\XMLArchive\test\SCOTT\SALGRADE.xml

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 online help.

88 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore of an XML Export Archive

Performing a Restore of an XML Export Archive

Make sure an XML export archive has been 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.
This section describes the following procedures for performing user-directed restores:
◆ Running the XML Import Wizard on the Client
◆ Using bpdbsbora
◆ Running an XML Import Script on the Client
◆ Running bporaimp on the Client
◆ Redirecting a Restore of an XML Export Archive to a Different Client

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 from the Start menu 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 Start menu,
click Start > All Programs > VERITAS NetBackup > Backup, Archive, and Restore.

Chapter 5, Using NetBackup for Oracle 89

Performing a Restore of an XML Export Archive

▼ To start the XML Import Wizard

1. (Conditional) Change the policy type.

Perform this step if the Oracle node is not visible.
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. On the File menu, select Specify NetBackup Machines and Policy Type.

b. On the Specify NetBackup Machines and Policy Type dialog box, click the
Clients/Policy type tab.

c. In the Policy type drop down list, select Oracle.

d. Click OK.

2. Click Select for Restore.

3. 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.

2. Expand the Users list to the schema owners of the objects to be imported.

3. In the right pane, select database objects that exist in the archive to be restored.

90 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore of an XML Export Archive

4. From the Actions menu, click Start Restore of Marked Files.

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:
◆ Welcome
◆ Target Database Logon Credentials
◆ Archive Import Options
◆ NetBackup Archive Source Options
◆ NetBackup Import 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. Review the summary.

Chapter 5, Using NetBackup for Oracle 91

Performing a Restore of an XML Export Archive

When you have completed the wizard, the Selection Summary screen displays the
summary of the XML Import template.
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]

The options are as follows:

-import Specifies the template type.

-r 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 H:\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:
H:\oracle\scripts\data_archiver_import.cmd

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.

92 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore of an XML Export Archive

The NetBackup for Oracle installation script writes sample scripts to the following
location:
install_path\NetBackup\dbext\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 Windows account that is running bporaimp
has access only to XML export archives that were created using the same Windows
account.

▼ 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
The following table 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 NetBackup Media Manager or
disk 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

Chapter 5, Using NetBackup for Oracle 93

Performing a Restore of an XML Export Archive

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 Media Manager or disk storage unit.

Target
Parameter Required? Default Description Location

ARCHIVE_DATE_FROM N no Optionally specifies a Storage Unit

default 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].

ARCHIVE_DATE_TO N no Optionally specifies an Storage Unit

default 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].

94 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore of an XML Export Archive

Target
Parameter Required? Default Description Location

BFILE_DIRECTORY Y (if any no Specifies a directory for Directory

table being default the output of any BFILE
imported columns being imported.
has BFILE Oracle’s CREATE
columns) DIRECTORY command
can be used to create the
DIRECTORY in Oracle,
and the name should
match the name used in
the export file.

COMMIT N N Specifies whether Directory

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.

DIRECTORY N no Optionally specifies a Directory

default directory for the input of
the bporaimp utility.

FROMUSER N no Optionally specifies a Directory

default comma-separated list of
users to import from an
archive containing
multiple users’ tables. If
not specified, all of the
tables are imported.

HELP N N Displays a help message Directory

with descriptions of
bporaimp parameters.

Chapter 5, Using NetBackup for Oracle 95

Performing a Restore of an XML Export Archive

Target
Parameter Required? Default Description Location

IGNORE_ROWS N N Specifies whether or not Directory

rows should be inserted
into a table that isn’t
empty. The default is
that the table already
exists and that it is
empty. If it isn’t 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.

KEYWORD N no Optionally specifies a Storage Unit

default keyword phrase for
NetBackup to use when
searching for archives
from which to restore
files.

96 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore of an XML Export Archive

Target
Parameter Required? Default Description Location

LIST N N LIST = Y queries the Storage Unit

NetBackup catalog and
lists the archives
available. Does not
import the data if
LIST = Y.

LOG N no Optionally specifies a file Directory

default 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.

NAME Y no The name of the master Directory

default XML schema file. This
parameter is required if
LIST = N.

NB_ORA_SERV N default Optionally specifies the Storage Unit

master name of the NetBackup
server master server.

NB_ORA_CLIENT N default Optionally specifies the Storage Unit

client name of the NetBackup
for Oracle client.

RESTORE_SCHEMA_ONLY N N Used with Storage Unit

RESTORE_TO_DIRECTO
RY to restore the XML
schema files only to a
directory.

RESTORE_TO_DIRECTORY N no Optionally specifies a Storage Unit

default directory for the output
of the bporaimp utility.
If used, the XML data is
not parsed and inserted
into Oracle.

Chapter 5, Using NetBackup for Oracle 97

Performing a Restore of an XML Export Archive

Target
Parameter Required? Default Description Location

ROW_BUFFER N 1000 Specifies the size, in Directory

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.

TABLES N no Optionally specifies a list Directory

default 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.

98 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore of an XML Export Archive

Target
Parameter Required? Default Description Location

TOUSER N no Optionally specifies a Directory

default 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.

USERID Y no Specifies the Directory

default 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.

Chapter 5, Using NetBackup for Oracle 99

Performing a Restore of an XML Export Archive

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.
The following illustrates a typical redirected restore process:

1 . Cl
ient A
gets
back Server
e d up
.

2. Clien
t
client A B requests res client A
image to r ve r restores B.
to clien re of 3. The s
e client
t B. up i m age to
b ack

Note that the user on client A was not able to initiate a redirected restore to client B. Only
the user on client B, the client receiving the backup image, could initiate the redirected
restore.

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:
install_path\NetBackup\dbaltnames\No.Restrictions

Or, to restrict clients to restore only from certain other clients, create the following file:
install_path\NetBackup\dbaltnames\client_name

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.

100 NetBackup for Oracle System Administrator’s Guide for Windows

 Performing a Restore of an XML Export Archive

Client Configuration
The same user name (Windows account) that was used for the XML export archive must
be used on the client to which you are redirecting the restore.

▼ 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. Set environment variables for bporaimp on the new client, including ORACLE_HOME
and ORACLE_SID.

2. In the bporaimp parameter file, include the following lines:

nb_ora_serv = NetBackup_server
nb_ora_client = original_client_where_XML_export_occurred.

3. Specify other bporaimp parameters.

For more information, see “Running bporaimp on the Client” on page 93.

4. 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
◆ Windows user is ora on both jupiter and saturn
◆ Archive name is sales

1. Create the following file on server jupiter:

install_path\NetBackup\db\altnames\saturn

2. Edit the preceding file to contain the name jupiter.

3. Log on to saturn as ora.

4. Create file bporaimp.param.

Chapter 5, Using NetBackup for Oracle 101

Using NetBackup for Oracle in a Microsoft Cluster Server Environment

Include the following parameters:

NAME = sales

NB_ORA_SERV = jupiter

NB_ORA_CLIENT = jupiter

USERID = orauser/orapasswd

5. Run bporaimp parfile=bporaimp.param to restore sales archive to saturn

and to import the data into the test database on saturn.

Using NetBackup for Oracle in a Microsoft Cluster Server

Environment
To use NetBackup for Oracle in a Microsoft Cluster Server environment, the following
must be installed in the cluster nodes:
◆ NetBackup client or server (6.0)
◆ NetBackup for Oracle on Windows (6.0)
◆ Oracle Database version 8i Release 8.1.7 or greater
◆ Oracle Failsafe 3.11 for Oracle version 8i Release 8.1.7 or greater
NetBackup for Oracle users in a Microsoft Cluster Server Environment must take some
additional steps to prepare for server-directed backups, user-directed backups, and
user-directed restores.

Automatic Backup of an Oracle Policy

The most convenient way to back up your clustered databases is to set up schedules for
automatic backups. NetBackup for Oracle comes with sample scripts for clustered Oracle
databases. The NetBackup for Oracle installation process installs the sample scripts in the
following location:
install_path\NetBackup\dbext\oracle\samples\rman\

Modify the scripts to give values to the following variables:

◆ Oracle SID
◆ Oracle Home
◆ Cluster Name, Domain
◆ Failsafe Home
◆ Failsafe Userid

102 NetBackup for Oracle System Administrator’s Guide for Windows

 Using NetBackup for Oracle in a Microsoft Cluster Server Environment

◆ Failsafe Password
◆ Failsafe Database Resource Name
◆ Virtual Oracle Database Name
For more information on how to back up or restore Microsoft cluster server using
NetBackup, see the NetBackup System Administrator Guide for Windows, Volume I.

Manual Backup of an Oracle Policy

Refer to “Testing Configuration Settings” on page 59 for instructions on initiating a
manual backup of an Oracle policy.

User-directed Backup or Restore from the Client

This section explains the process to prepare a Microsoft Cluster Server environment for a
user-directed backup or restore operation.

1. Take the clustered Oracle database instance offline.

◆ If you are using the Failsafe Graphical User Interface, take the following actions:
◆ Select the Oracle database resource in the Failsafe Graphical User Interface
◆ Choose to bring it offline
◆ If you are using the Failsafe command line (FSCMD), type the following
command:
fscmd offlineresource salesdb /cluster=curly /offline=immediate

/domain=domainname /user=user /pwd=pwd

To bring the resource offline, the preceding command sets offline=immediate.

Alternately, you could specify one of the following, based on your need, as the
argument to offline:

abort Shuts down the database instantaneously by aborting the

database instance.

immediate Shuts down the database immediately by terminating SQL

statements in progress, rolling back uncommitted transactions
and disconnecting users.

Chapter 5, Using NetBackup for Oracle 103

Using NetBackup for Oracle in a Microsoft Cluster Server Environment

normal Shuts down the database and doesn’t allow new connections
after the command was issued. This command waits for the
connected users to disconnect before actually shutting down the
database.

transactional Shuts down the database only after all of the current transactions
have completed.

Because the offline resource operation shuts down the Oracle database service,
enter the following command to start the Oracle database service:
net start OracleService

2. Shut down and start up the database in mount state. This is necessary to perform
administrative tasks like backup and recovery. Use the svrmgrl or sqlplus utility
from Oracle. At the command line, type the following:
Shutdown option [normal, abort, immediate]

startup mount

Note When performing user directed backups, make sure you are on the node that owns
the shared drive where the Oracle database is installed.

3. Perform the backup or recovery according to the directions for “Running the
NetBackup for Oracle Recovery Shell Script on the Client” on page 74.

Note When performing user-directed client restores with different configuration options
of NetBackup failover media servers and a UNIX or Windows master server, refer to
the section “Managing Client Restores” in the NetBackup System Administrator’s
Guide for UNIX or for Windows.

4. Bring the Oracle database online with failsafe after the desired backup/restore is
complete to enable it to fail over between the configured cluster of nodes.
◆ If you are using the Failsafe Graphical User Interface, take the following actions:
◆ Select the resource in the Failsafe Graphical User Interface
◆ Choose to bring it offline
◆ If you are using the Failsafe command line (FSCMD), type the following

command:

fscmd online resource salesdb /cluster=curly /offline=immediate

/domain=domainname /user=user /pwd=pwd

104 NetBackup for Oracle System Administrator’s Guide for Windows

NetBackup for Oracle with Advanced Client 6
This chapter explains how to use NetBackup for Oracle with NetBackup Advanced Client
to perform snapshot backups of your Oracle database.
To use NetBackup for Oracle with Advanced Client, you must have both NetBackup
Advanced Client and NetBackup for Oracle licensed and installed.
The chapter provides information on the following topics:
◆ Installation and Licensing Requirements
◆ NetBackup for Oracle with Advanced Client Overview
◆ How Does NetBackup for Oracle with Advanced Client Work?
◆ Configuring Snapshot Backups
◆ Restoring Data from a Snapshot Backup
◆ Advanced Client Effects

105
Installation and Licensing Requirements

Installation and Licensing Requirements

To use NetBackup for Oracle with Advanced Client, you must have the following licensed
and installed:
◆ NetBackup for Oracle 6.0
◆ NetBackup Advanced Client 6.0
No additional VERITAS NetBackup software is required. You might need to modify other
hardware and software configurations. For more information about the following, see the
NetBackup Advanced Client System Administrator’s Guide:
◆ How to install and configure the NetBackup Advanced Client
◆ Configuration requirements for specific advanced backup methods

106 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle with Advanced Client Overview

NetBackup for Oracle with Advanced Client Overview

The following sections describe the NetBackup Advanced 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 Advanced Client, NetBackup for Oracle can back up Oracle
objects by taking snapshot images of the component files. Later, it backs up the snapshot
version, either to a Media Manager or disk 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.

Offhost Backup
An offhost 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.

Proxy Copy
Proxy copy is an extension to Oracle’s Media Management API. A proxy copy is a special
type of backup in which RMAN turns over control of the data transfer to the NetBackup
for Oracle agent. During RMAN backup and restore operations, proxy copy enables
NetBackup for Oracle to manage the entire data movement between the disks containing
Oracle data files and the storage devices managed by NetBackup.

Chapter 6, NetBackup for Oracle with Advanced Client 107

NetBackup for Oracle with Advanced Client Overview

With proxy copy, RMAN provides a list of files that require backup or restore to the
NetBackup for Oracle agent. The NetBackup for Oracle agent determines how the data is
moved and when to move the data.
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. NetBackup for
Oracle with Advanced Client operations are file-based. The following sections illustrate
the differences between these operation types.

108 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup for Oracle with Advanced Client Overview

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 Oracle 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.

NetBackup for Oracle RMAN stream-based backup or restore

Oracle Server
Oracle Oracle
database disk database disk
Control commands
Data

NetBackup

Chapter 6, NetBackup for Oracle with Advanced Client 109

NetBackup for Oracle with Advanced Client Overview

File-based Operations
File-based operations are the NetBackup for Oracle with Advanced 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 Advanced Client. NetBackup for Oracle with Advanced Client performs the data
movement.

NetBackup for Oracle with Advanced Client file-based backup or restore

Oracle Server

Oracle Oracle
database disk Control commands database disk

List of files

Data Data
NetBackup

110 NetBackup for Oracle System Administrator’s Guide for Windows

 How Does NetBackup for Oracle with Advanced Client Work?

How Does NetBackup for Oracle with Advanced 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. For more information, see “Database Objects
Supported by Advanced Backup Methods” on page 112.
The agent checks that the policy it is using for the backup is configured with the
appropriate Advanced Client attributes. The agent then initiates file-based backups of the
Oracle files and uses the NetBackup Advanced Client interface to perform the data
movement.
When Oracle performs proxy copy backups, it puts the datafiles 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 datafiles out of
backup mode. The datafiles 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 datafile a unique name.

2. Queries the policy to check whether the Advanced Client policy attributes are
specified.

3. Initiates a configured number of advanced client backups and waits until the jobs are
completed. For more information, see “Multistreaming” on page 112.

Sequence of Operation: Restore

For a restore operation, the NetBackup for Oracle agent performs the following steps:

Chapter 6, NetBackup for Oracle with Advanced Client 111

How Does NetBackup for Oracle with Advanced Client Work?

1. Receives a list of files to restore from RMAN.

2. Sends a restore request to the NetBackup server for all files in the list.

3. 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 Advanced Client backup methods. Oracle
allows proxy copy backups of databases, tablespaces, and datafiles. With Oracle 10g
releases and later, Oracle also allows proxy copy backups of archived redo logs. As a
result, NetBackup can use file-based Advanced Client backup methods to back up these
objects.
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 Advanced 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 Advanced Client backups, be sure to configure a policy
that allows both kinds of backups. For information on configuring such a policy, see
“Advanced Client Effects” on page 125.

Multistreaming
On the initial call, NetBackup for Oracle with Advanced 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.

112 NetBackup for Oracle System Administrator’s Guide for Windows

 How Does NetBackup for Oracle with Advanced Client Work?

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 “Examples: Using Multiple Channels in RMAN Scripts with Proxy
Backups” on page 115.

Restoring Datafiles to a New Location

NetBackup for Oracle with Advanced Client can restore datafiles 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 datafile 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 datafiles backed up by proxy is the same as for conventionally
backed up datafiles. RMAN knows that the datafiles were backed up by proxy, and it
issues a proxy restore request to NetBackup for Oracle, which restores the datafiles to the
new location. For more information on the required procedure, see your Oracle
documentation.

Chapter 6, NetBackup for Oracle with Advanced Client 113

How Does NetBackup for Oracle with Advanced Client Work?

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. For information, see “Using
NetBackup for Oracle” on page 61.

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;

114 NetBackup for Oracle System Administrator’s Guide for Windows

 How Does NetBackup for Oracle with Advanced Client Work?

Examples: Using 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 datafiles 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 datafiles 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';

Chapter 6, NetBackup for Oracle with Advanced Client 115

How Does NetBackup for Oracle with Advanced Client Work?

backup

format 'cntrl_%s_%p_%t'

current controlfile;

release channel t2;

Example 3
In this sample script, RMAN initiates two proxy copy backups sequentially on channel
t1. It starts a proxy backup of tablespace tbs1 datafiles. After the backup is done, it starts
another proxy backup of tablespace tbs2 datafiles.
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 datafiles on channel t1 and tbs2 datafiles 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';

116 NetBackup for Oracle System Administrator’s Guide for Windows

 How Does NetBackup for Oracle with Advanced Client Work?

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;

Chapter 6, NetBackup for Oracle with Advanced Client 117

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, offhost backup, can reduce the I/O processing load on the client that hosts
the database. To use offhost 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
The NetBackup Advanced Client System Administrator’s Guide and the VERITAS Technical
Support Web site contain information on hardware requirements, software requirements,
compatibility, snapshot methods supported for your agent, and special requirements for
specific types of backups. Familiarize yourself with this information before you configure
any shapshot backups.
The following list highlights some of the requirements that pertain to database agents:
◆ The user 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.
◆ It is recommended that you 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.
There are several reasons for doing this. One reason for separating the data files from
the other files is that because if the logs are configured on the same volumes (or file
systems) as the datafiles, the logs are temporarily frozen while NetBackup takes the
snapshot. As a result, the Oracle 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 an Instant
Recovery point-in-time rollback requires that there be only data files on the volume or
file system being restored.
◆ The hardware and software required for the appropriate snapshot method must be
installed and configured correctly.

118 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Snapshot Backups

◆ NetBackup Advanced Client must be installed and configured correctly, and the
license key for this option must be registered.
◆ To perform offhost backups, perform any special configuration that is required.

Configuring an Oracle Policy with Advanced Client Backup

Methods
This section explains how to configure snapshot and instant recovery backups for an
Oracle policy. For information about configuring a policy, see “Configuring Backup
Policies” on page 31. For information on how a snapshot method is automatically selected
and details on the types of backup methods, see the NetBackup Advanced Client System
Administrator’s Guide.
Snapshot backups do not back up all database objects. Your backup configuration must
include schedule types to perform file-based and stream-based backups in order to
ensure that the entire database can be successfully restored.
For snapshot or instant recovery backups, configure the following policy and schedules:
◆ An Oracle policy with the following attributes:
◆ Snapshot methods for the file systems (logical volumes) in which the datafiles
reside.
◆ A backup method on the policy attributes dialog.
◆ An Automatic Full Backup schedule to perform file-based snapshot and offhost
backups of the datafiles.
◆ 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.
For information about policy and schedule attributes that differ for a NetBackup for
Oracle with Advanced Client policy, see “Advanced Client Effects” on page 125.

Configuring a Snapshot Policy

The following procedure shows how to configure a snaphot policy with optional instant
recovery, snapshot retention, and offhost backup.

Chapter 6, NetBackup for Oracle with Advanced Client 119

Configuring Snapshot Backups

▼ To configure a snapshot policy

1. Open the policy you want to configure.

2. Click on the Attributes tab.

3. Select the Oracle policy type.

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

Offhost backup and specify a
method

4. 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 control files and archived redo logs that are included in this
policy.

5. Click Perform snapshot backups.

6. (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 presented in the list.

120 NetBackup for Oracle System Administrator’s Guide for Windows

 Configuring Snapshot Backups

The snapshot method you can use depends on your hardware and software
environment. For information about the snapshot methods supported in your
environment, see the NetBackup Advanced Client System Administrator’s Guide or the
supported platforms matrix on the VERITAS technical support website.
You can configure only one snapshot method per policy. For example, if you want one
snapshot method for clients a, b, and c, and a different method for clients d, e, and f,
then create two policies for each group of clients, and select one method for each
policy.

7. (Optional) Select Retain snapshots for instant recovery.

When selected, NetBackup retains the snapshot backup image on disk for later use in
recovery.

8. (Optional) Select Perform offhost 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, you can specify
an alternate client to perform the backup. Select an offhost 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.

9. 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 supresses NetBackup’s default behavior,
which is to copy the snapshot to a Media Manager or disk 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.
◆ The Application Backup schedule is for the control files and archived redo logs.
NetBackup copies the database’s control files and archived redo logs to the Media
Manager or disk storage unit you selected.

Chapter 6, NetBackup for Oracle with Advanced Client 121

Configuring Snapshot Backups

For UNIX clients, if you selected Third-Party Copy Device as an offhost backup
method, click Override policy storage unit and select a non-SAN Media Manager
or disk 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 with Advanced Client policy, see “Advanced
Client Effects” on page 125.

13. Configure other attributes and add any additional schedules and backup selections.

122 NetBackup for Oracle System Administrator’s Guide for Windows

 Restoring Data from a Snapshot Backup

Restoring Data from a Snapshot Backup

Restoring Individual Files

You can use the procedure in “Performing a Restore” on page 70 to restore data from a
snapshot backup. This is the same procedure you use to restore data that is not backed up
with Advanced Client methods. Use this procedure for files backed up with, or without,
Instant Recovery enabled. In all cases, RMAN determines the files that were backed up
with a proxy method, and it initiates a corresponding restore request to the NetBackup for
Oracle 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 by copying the data from the snapshot to the primary file system. For
information on the Instant Recovery methods that NetBackup uses, see the NetBackup
Advanced Client System Administrator’s 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:
◆ vxvm snapshot
◆ FlashSnap snapshots
The NetBackup Advanced Client System Administrator’s Guide contains more information on

snapshot rollbacks.

In addition, 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,
checking for the following:
◆ The requested files (number and names) are identical to those in the snapshot
◆ The primary volume does not contain files created after the snapshot was made

Chapter 6, NetBackup for Oracle with Advanced Client 123

Restoring Data from a Snapshot Backup

If verification fails, the rollback aborts with 249.

◆ Snapshot rollback should be used with database files only. Database files and archive
redo logs should exist on different file systems or volumes.
The procedure for specifying a snapshot rollback restore depends on the method you
choose to perform the restore. Use one of the following methods:

▼ To specify a snapshot rollback restore from the Java or Windows interface

1. Go to the NetBackup Backup, Archive and Restore Interface.

2. Click the Restore Files tab.

3. Set the Restore Type to Point in Time Rollback.

4. Use the NetBackup for Oracle Recovery Wizard for the restore.

5. Follow the restore procedure that is used for typical backups.

For information on restoring from a typical backup, see “Performing a Restore” on
page 70.

▼ To specify a snapshot rollback restore using a script or RMAN command

❖ If using a shell script or RMAN command, set a new variable,

NB_PC_ORA_RESTORE=rollback.

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 restore fails, it might be because Oracle still has a file open. Shutting down
and restarting the database can correct this problem.

124 NetBackup for Oracle System Administrator’s Guide for Windows

 Advanced Client Effects

Advanced Client Effects

The following sections describe the ways in which the Advanced Client software affects
backup types, schedule properties, templates, 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 Advanced Client backups. The following table explains these
roles:

Backup Types for Oracle

Backup Type Description

Application Backup The Application Backup schedule enables stream-based NetBackup

operations. The Default-Application-Backup schedule is automatically
configured as an Application Backup schedule.

Automatic Full Backup, For file-based proxy copy backups, the Automatic backup schedule types
serve two purposes:
Automatic Differential ◆ Automatic backup schedules automatically start the backups by
Incremental Backup, running the NetBackup for Oracle scripts or templates.
◆ Automatic backup schedules control file-based snapshot backups of
Automatic Cumulative
the database objects.
Incremental Backup
Note For snapshot backups, specifying any of the Automatic backup
types results in a full backup.

Chapter 6, NetBackup for Oracle with Advanced Client 125

Advanced Client Effects

Schedule Properties
Some schedule properties have a different meaning for Advanced Client database
backups than for a regular database backup. The following table explains these properties:

Schedule Properties

Property Description

Retention 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 Advanced 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.

Multiple copies 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 37 describes other schedule properties that are specific to
Oracle backups.

Templates and Scripts

You can use a template created by the NetBackup for Oracle Wizard to perform
NetBackup for Oracle with Advanced Client backups. After they are created, templates
reside on the NetBackup master server and are available for use by other NetBackup for
Oracle clients. For information on creating a backup template, see “Creating Templates
and Shell Scripts” on page 47.

126 NetBackup for Oracle System Administrator’s Guide for Windows

 Advanced Client Effects

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 Advanced Client methods on the Attributes tab of the
policy. At run time, the template checks the policy attributes to determine if an Advanced
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.
NetBackup for Oracle provides sample scripts 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 44.
The following list shows variables that you can to set that are specific to the NetBackup
for Oracle Advanced Client:

Environment Variable Description

NB_ORA_PC_SCHED 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
Advanced Client starts simultaneously in each proxy copy session.
When a backup starts, NetBackup for Oracle Advanced Client groups all
datafiles into a specified number of backup streams based on the file
size. NetBackup for Oracle Advanced 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.

Chapter 6, NetBackup for Oracle with Advanced Client 127

Advanced Client Effects

For NetBackup for Oracle with Advanced Client, the order of precedence for environment
variables is the same as for standard NetBackup for Oracle. “Configuring the Runtime
Environment” on page 44 contains instructions for configuring variables set by
NetBackup and variables set by a user.
NetBackup for Oracle installs sample scripts in the following location:
install_path\NetBackup\dbext\oracle\samples\rman

The following are the NetBackup for Oracle with Advanced Client sample scripts that
show how to configure the required variables:
◆ hot_database_backup_proxy.cmd. 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 Advanced Client uses. The script shows how to use the RMAN send
command to pass the NetBackup for Oracle with Advanced Client variables with a
vendor-specific quoted string.
◆ hot_tablespace_backup_proxy.cmd. This script sets the environment and calls
RMAN with the appropriate command to perform a tablespace proxy backup.
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.

128 NetBackup for Oracle System Administrator’s Guide for Windows

Troubleshooting 7
NetBackup, NetBackup for Oracle, and the Oracle Recovery Manager all provide reports
on database backup, archive, and restore operations. These reports are useful for finding
errors associated with those applications.
This chapter contains the following sections.
◆ General Troubleshooting Procedure
◆ NetBackup and NetBackup for Oracle Logs and Reports
◆ Troubleshooting Backup or Restore Errors
◆ Troubleshooting XML Export or XML Import Errors
◆ Troubleshooting NetBackup for Oracle with Advanced Client
◆ Minimizing Timeout Failures on Large Database Restores

129
General Troubleshooting Procedure

General Troubleshooting Procedure

Note For brevity, this chapter refers to the orasbt.dll as API.

To perform this procedure, the following products must be properly installed and
configured:
◆ NetBackup 6.0.
◆ Oracle RDBMS 8.0.4 or later. XML export and XML import require Oracle RDBMS
8.1.5 or later.
◆ NetBackup for Oracle 6.0.

▼ To perform initial troubleshooting steps

1. When verifying your installation, ensure that the following NetBackup for Oracle
binaries exist:
◆ install_path\NetBackup\bin\bphdb.exe, which 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.
◆ \Program Files\Common Files\VERITAS Shared\orasbt.dll, which
provides functions callable by RMAN.

2. For XML export and XML import, verify that the following binaries exist in

install_path\NetBackup\bin:

◆ bporaexp.exe
◆ bporaimp.exe
◆ bpora8.dll
◆ bpora9.dll

3. For the Backup, Archive, and Restore interface, verify that the following binaries exist
in install_path\NetBackup\bin:
◆ bpdbsbora.exe
◆ bpubsora.exe
◆ dbsbrman.dll
◆ nbbedsrman.dll

130 NetBackup for Oracle System Administrator’s Guide for Windows

 General Troubleshooting Procedure

4. 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.

5. Check that the following NetBackup log folders exist and that VERBOSE=5:
◆ On the client: bpdbsbora, bporaexp, bporaimp, dbclient, bphdb, bplist,
and bpcd.
◆ On the master server: bprd and bpdbm.
◆ On the host with the storage unit: bpbrm and bptm.

Note These logs can become very large, especially bpdbm. Ensure that enough free disk
space exists in the log folder disk partition.

Chapter 7, Troubleshooting 131

NetBackup and NetBackup for Oracle Logs and Reports

NetBackup and NetBackup for Oracle Logs and Reports

The following describes troubleshooting logs and reports generated by NetBackup
products.

NetBackup for Oracle Logs

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 NetBackup for Oracle or the Oracle Recovery Manager. To create logs
automatically, run install_path\NetBackup\logs\mklogdir.bat.
Note the following with regard to these logs:
◆ These logs do not reveal errors that occur during the execution of the Oracle Recovery
Manager unless those errors also affect NetBackup for Oracle. Oracle might (or might
not) write to the NetBackup for Oracle 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 install_path\NetBackup\logs\README.debug file.

Enabling Logging
▼ To enable the NetBackup for Oracle logs

1. Create the following folders on the client in a DOS window:

install_path\NetBackup\logs\bpbackup

install_path\NetBackup\logs\bpbkar32

install_path\NetBackup\logs\bphdb

install_path\NetBackup\logs\bprestore

install_path\NetBackup\logs\tar32

install_path\NetBackup\logs\dbclient

install_path\NetBackup\logs\bpdbsbora

install_path\NetBackup\logs\bporaexp

install_path\NetBackup\logs\bporaimp

For example:
cd install_path\NetBackup\logs

mkdir bphdb

132 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup and NetBackup for Oracle Logs and Reports

2. Make sure there is share access to the log folders.

3. Enable logging for the nbpem, nbjm, and nbrb scheduling processes, which use
unified logging.
NetBackup writes unified logs to /usr/openv/logs on UNIX and to
install_path\NetBackup\logs on Windows. 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 Folder on the Client

The install_path\NetBackup\logs\bphdb folder contains the following types of
logs:
oracle_stdout.mmddyy.hhmmss.txt

Unless redirected elsewhere, NetBackup writes NetBackup for Oracle

templates or shell script output to this file.
oracle_stderr.mmddyy.hhmmss.txt

Unless redirected elsewhere, NetBackup writes NetBackup for Oracle

templates or shell script errors to this file.
mmddyy.log

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 templates or shell script execution. It
is invoked when an automatic backup schedule is run.

dbclient Folder on the Client

The install_path\NetBackup\logs\dbclient folder contains the following
execution log:
mmddyy.log

This log contains debugging information and execution status for the Oracle
NetBackup client processes linked to the library program provided with
NetBackup for Oracle.

Chapter 7, Troubleshooting 133

NetBackup and NetBackup for Oracle Logs and Reports

bpdbsbora Folder on the Client

The install_path\NetBackup\logs\bpdbsbora folder contains the following
execution log:
mmddyy.log

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).

bporaexp Folder on the Client

The install_path\NetBackup\logs\bporaexp folder contains the following
execution log:
mmddyy.log

This log contains debugging information and execution status for the
bporaexp program that performs XML exports.

bporaimp Folder on the Client

The install_path\NetBackup\logs\bporaimp folder contains the following
execution log:
mmddyy.log

This log contains debugging information and execution status for the
bporaimp program that performs XML imports.

Setting the Debug Level

You can control the amount of information written to the debugging logs in the
install_path\NetBackup\logs\ folders by changing the database debugging level.
The higher the value, the more information is logged. 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 the debugging levels to 0, 1, 2, 3, 4, or 5. A level of
5 provides the most detail. You can change the amount of debug information in other log
folders by setting other debug levels, including VERBOSE.

134 NetBackup for Oracle System Administrator’s Guide for Windows

 NetBackup and NetBackup for Oracle Logs and Reports

▼ To change the debugging level

1. From the Windows Start menu, choose Programs > VERITAS NetBackup > Backup,
Archive, and Restore.
The Backup, Archive, and Restore interface displays.

2. Choose File > NetBackup Client Properties.

3. In the NetBackup Client Properties dialog, select the Troubleshooting tab.

By default, the setting is 0.

4. Set the database debug level.

Note Information from both settings is logged to the same file, mmddyy.log

5. Stop and start the Oracle database services. This is necessary for orasbt.dll to pick
up the new debug level.

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
System Administrator’s Guide, Volume I.

Oracle Recovery Manager Utility Logs

The Oracle Recovery Manager 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.

Chapter 7, Troubleshooting 135

Troubleshooting Backup or Restore Errors

When bporaexp and bporaimp are being used and the backup images are written to a
storage unit, these errors are also logged in the NetBackup debug logs in
install_path\NetBackup\logs\bporaexp and
install_path\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 Oracle Recovery Manager 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 the Oracle Recovery Manager or from the
target database.
VERITAS suggests that you use the following steps when troubleshooting a failed
operation:

1. Check the logs to determine the source of the error.

2. Troubleshoot each stage of the backup or restore.

The following sections describe these steps in detail.

Check 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 “Troubleshoot Each Stage of the Backup or
Restore” on page 136.

Troubleshoot 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:

136 NetBackup for Oracle System Administrator’s Guide for Windows

 Troubleshooting Backup or Restore Errors

◆ From an RMAN backup or restore initiated from the operating system prompt
such as:
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, and trace file name,
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.

3. 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 server’s bprd process.
To troubleshoot a problem in this part of the first sequence, examine the

install_path\NetBackup\logs\dbclient\mmddyy.log file.

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 client environment.

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.

5. RMAN tells the API to close the session.

Chapter 7, Troubleshooting 137

Troubleshooting XML Export or XML Import Errors

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 NetBackup or 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.
VERITAS suggests that you use the following steps when troubleshooting a failed
operation:

1. Check the logs to determine the source of the error.

2. Troubleshoot each stage of the XML export or XML import.

The following sections describe these steps in detail.

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 command’s
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.
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.

138 NetBackup for Oracle System Administrator’s Guide for Windows

 Troubleshooting XML Export or XML Import Errors

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
install_path\NetBackup\logs\bporaexp\log.mmddyy or
install_path\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 install_path\NetBackup\logs\bporaexp\log.mmddyy or
install_path\NetBackup\logs\bporaimp\log\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.
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.

Troubleshoot 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 command’s 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 specified in the
bporaexp or bporaimp command’s 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:

Chapter 7, Troubleshooting 139

Troubleshooting XML Export or XML Import Errors

◆ 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.

2. 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.

3. 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.
◆ Server configuration parameters.
This information is sent to the master server’s bprd process.
To troubleshoot a backup problem in this part of the sequence, examine the

install_path\NetBackup\logs\bporaexp\log.mmddyy file.

If the bprd process failed, check the bprd and bpbrm logs.
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 client environment or by
setting the following bporaexp parameters:

140 NetBackup for Oracle System Administrator’s Guide for Windows

 Troubleshooting NetBackup for Oracle with Advanced Client

NB_ORA_POLICY=policyname

NB_ORA_SCHED=schedule

NB_ORA_SERV=NetBackup_server

NB_ORA_CLIENT=NetBackup_client

To troubleshoot a restore, examine

install_path\NetBackup\logs\bporaimp\mmddyy.log. 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.

5. 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 NetBackup for Oracle with Advanced

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 Advanced Client.
Advanced Client backup and debug messages are written to the following subdirectories
of install_path\NetBackup\logs:
◆ bpbrm on the NetBackup media server
◆ bptm/bpdm on the NetBackup media server

Chapter 7, Troubleshooting 141

Minimizing Timeout Failures on Large Database Restores

◆ 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
Advanced 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 Advanced Client System 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. In the NetBackup Administration Console, expand NetBackup Management > Host

Properties > Clients

2. 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 System Administrator’s Guide, Volume 1. For example, change this
setting to 30-60 minutes to minimize timeout errors.

3. Click OK for each client.

142 NetBackup for Oracle System Administrator’s Guide for Windows

Oracle 9i and 10g Real Applications
Clusters A
Overview
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 concurrently run transactions against the same database.
Should any single server or instance fail, processing continues on the surviving servers.

How Does NetBackup Fit into a RAC Environment?

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.

143
How Does NetBackup Fit into a RAC Environment?

Archiving Schemes
The preferred configuration for Real Application Clusters is to use 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. The
following figure depicts a CFS archiving scheme.

CFS Archiving Scheme

144 NetBackup for Oracle System Administrator’s Guide for Windows

 How Does NetBackup Fit into a RAC Environment?

If the CFS solution is not available, Oracle recommends a scheme in which each node
archives to a local directory and writes a copy to each of the other nodes’ archive
directories (see the following figure). The locations are shared between the nodes (with
read and write permissions) by NFS mounting the directory (UNIX) or sharing the
locations (Windows). The following figure depicts a non-CFS local archiving scheme with
archive sharing.

Non-CFS Local Archiving Scheme with Archive Sharing

Appendix A, Oracle 9i and 10g Real Applications Clusters 145

How Does NetBackup Fit into a RAC Environment?

A scheme similar to the previous one exists if each node archives to a local directory, as in
the following figure, 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. This figure depicts a non-CFS local archiving scheme with read-only archive
sharing.

Non-CFS Local Archiving Scheme with Archive Read-only Sharing

146 NetBackup for Oracle System Administrator’s Guide for Windows

 How Does NetBackup Fit into a RAC Environment?

The simplest archiving scheme is local archiving with no sharing, as shown in the
following figure. Each node writes only to the local destination, and no access is given to
the other nodes in the cluster. The following figure depicts a non-CFS local archiving
scheme with no archive sharing.

Non-CFS Local Archiving Scheme with no Archive Sharing

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.
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

Appendix A, Oracle 9i and 10g Real Applications Clusters 147

How Does NetBackup Fit into a RAC Environment?

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
For more information on restores and redirected restores, see “Performing a Restore” on
page 70.

Restoring Archive Logs

To restore the archive logs if the remote archived log destinations allow write access (see
the figure “Non-CFS Local Archiving Scheme with Archive Sharing”) or if the archive logs
reside on a CFS (see the figure “CFS Archiving Scheme”), the typical RMAN script can be
used.
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 {

148 NetBackup for Oracle System Administrator’s Guide for Windows

 How Does NetBackup Fit into a RAC Environment?

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 (see the figures “Non-CFS
Local Archiving Scheme with Archive Read-only Sharing” and “Non-CFS Local
Archiving Scheme with no Archive Sharing”), the following example can be used:
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.

Appendix A, Oracle 9i and 10g Real Applications Clusters 149

How Does NetBackup Fit into a RAC Environment?

150 NetBackup for Oracle System Administrator’s Guide for Windows

Index

Symbols overview 33, 36

.xml 81
retention 34

.xsc 81
with Advanced Client 119

/Oracle/XMLArchive 88
archive 6, 12

ARCHIVE_DATE_FROM 87, 94

A
ARCHIVE_DATE_TO 87, 94

accessibility features xiii

automatic archive 78

Advanced Client

automatic backup

configuring policies 119

policy 66, 78, 102

effects on policies and schedules 125

schedule

file-based operations 108, 110

bphdb log 133

instant recovery

manual backup 66, 78

configuration requirements 118

automatic backup schedules

overview 107

configuring 34

policy configuration 119

Automatic Cumulative Incremental Backup

restore method 123

schedule

offhost backup

Advanced Client effects 125

configuration 118

Automatic Differential Incremental Backup

configuring 121

schedule

overview 107

Advanced Client effects 125

overview 107

overview 36

proxy copy 107

Automatic Full Backup schedule

snapshot backup

Advanced Client effects 125

configuration 118

overview 35, 36

configuration requirements 118

with Advanced Client 119

database objects included 119

overview 107
B
policy configuration 119
backup

restore method 123

automatic

stream-based operations 109

using scripts 66, 78, 102

Advanced Client for Oracle 105

wizard, invoking 126

alternate client restore see redirected restore

Backup Selections list

alternate client restoreseeredirected restore

adding selections 41

API
overview 41

error 136, 138

Backup, Archive, and Restore 53

libobk module 130

backups

Application Backup schedule

manual 59

backup window 34
BFILE_DIRECTORY 95

configuring 33
bp.conf

151

 troubleshooting 137, 140

register database 62

bpbrm log
report 65

verbose mode 131

reset database 62

bpcd 131
restore 63

verbose mode 131

resync catalog 63

bpdbm log
rman

verbose mode 131

execute backups 69

bpdbsbora
execute scripts 77

for XML import 92

performing restore 74

bphdb 130, 131

script syntax 77

description 130
send 51

log 132, 133

set duplex 51

bphdb log
switch 63

verbose mode 131

COMMIT 95

bplist 70
compatibility information 23

browsing for backups 70

configuration

browsing for XML export archives 88

database debug level 134

example 70
database user authentication 57

bplist log Media Manager 24

verbose mode 131

CONSISTENT 83

bporaexp 5, 12, 80, 82, 131

D
bporaimp 6, 14, 87, 131

daemons, see processes

performing a restore 93

database software prerequisites for

bprd log

installation 24

verbose mode 131

database user authentication

bpsched

changing 57

verbose mode 131

debug logs

bptm log

description 132

verbose mode 131

in install_path\NetBackup\logs 132

browsing archives 86

debugging level 134

C DIRECTORY 83, 95

changing user authentication 57

directory

client read timeout property 142

debug log 132

command
DIRECTORY parameter 82

bplist 70

E
bporaexp 80

environment variables 127

commands

environmental variable

allocate channel 10

user-directed backup 69

backup 10, 63

error checking 66

bplist 70, 88

example

bporaexp 5, 12, 82

bplist 70

bporaimp 14, 87

RMAN script 50

change 64

examples

copy 63

parameter files 56

crosscheck 62

scripts 56

crosscheck backupset 63

execution log 134

delete expired backupset 63

list 65

152
NetBackup for Oracle System Administrator’s Guide for Windows
 F NB_ORA_POLICY 46, 82, 84

failed operation NB_ORA_SCHED 46, 82, 84

troubleshooting 136, 138

NB_ORA_SERV 46, 82, 84, 87, 93, 97

file-based operations 108, 110

NB_PC_ORA_RESTORE variable 124

FlashSnap snapshots 123

nbjm scheduling process 133

FROMUSER 87, 95
nbpem scheduling process 133

nbrb scheduling process 133

H
NetBackup Client service 57

HELP 83, 95

NetBackup mode 82

O
IGNORE_ROWS 96

offhost backup, see Advanced Client

installation

Oracle Recovery Manager

database software prerequsites 24

errors 136

platform compatibility 23

example RMAN script 50

prerequisites 23

OWNER 84

prerequisites in a cluster 25

registering the license key 26

P
requirements for NetBackup software 24
parameter file 12, 14, 81

instant recovery, see Advanced Client PARTITIONS 85

platform compatibility 23

J
point in time rollback 123

Java interface 29

policy configuration

K adding clients 40

KEYWORD 83, 87, 96

adding new 31

L attributes 32

license keys, registering 26

backup selections list 41

LIST 97
for Advanced Client 119

LIST parameters 87
overview 31

LOG 84, 97
schedules 33

log files
testing 59

accessing 133
processes

also see debug logs

log files for NetBackup processes 133

creating automatically with

scheduling (nbpem, nbjm, nbrb) 133

mklogdir.bat 132
proxy copy 107

enabling 132
Q
troubleshooting with log files 132
QUERY 85

M R
manual archive 78
Recovery Wizard
manual backups 66, 78
use with Advanced Client 126

maximum jobs per client 30

redirected restores 75, 100

Media Manager
remote folder button 43

configuring backup media 24

reports

multiple copies feature 38, 126

All Log Entries report 135

multiplexing
also see log files 132

overview 2
database operations 129

N NetBackup server reports 135

NAME 84, 97
restore 6, 13

NB_ORA_CLIENT 46, 82, 84, 87, 93, 97

to a different client 75, 100

Index 153

 user-directed 92
templates

RESTORE_SCHEMA_ONLY 97
administration 79

RESTORE_TO_DIRECTORY 97
advantages over scripts 36

restores
button on Backup Selections tab 43

snapshot rollback 123, 124

creating for XML export 53

with Advanced Client methods 123

overview 3

retention period
XML export 52

for Advanced Client 126

testing policy configuration 59

for frequency-based schedules 38

timeout failures, minimizing 142

rman change command 39

TOUSER 99

RMAN script
troubleshooting logs 132

example 50

U
robust logging 133

Unicode 5

ROW_BUFFER 85, 98

unified logging 133

S user-directed archive 78

schedule
user-directed restore 92

automatic backup 66, 78, 102

USERID 86, 87, 99

schedules
UTF-8 5

adding 33

frequency 37

Verifying installation 130

properties 37

VIEWS 86

properties for Advanced Client 126

vxvm snapshot 123

retention 38

retention for Advanced Client 126

W
types of schedules 33
Windows interface 29

scripts
wizard

cautions for using 36

overview 3

RMAN 8, 10
use with Advanced Client 126

scheduler 66, 78, 102

X

XML export 53
XML 3, 5

send operand 69
XML export 6

snapshot backup 107, 118, 119, 123

XML Export Wizard 53

snapshot rollback 123, 124

XML import 6

starting 53
XML Import Wizard 90

stream-based operations 109

XML instance 6, 12, 13, 81

T XML schema 3, 5, 12, 13, 81

TABLES 86, 87, 98

154
NetBackup for Oracle System Administrator’s Guide for Windows