VERITAS NetBackup 6[1].0 on Unix-Oracle

VERITAS NetBackup 6.0 for OracleSystem Administrators Guidefor UNIX and Linux

N15262B 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 Administrators Guide for UNIX and Linux

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Finding NetBackup Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Accessing the VERITAS Technical Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . xiv Contacting VERITAS Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv Comment on the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 NetBackup for Oracle Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 NetBackup for Oracle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 XML Export and XML Import Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Oracle Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 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 Installing NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Performing the NetBackup for Oracle Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Linking NetBackup for Oracle with RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Configuring a NetBackup for Oracle Policy and Schedule . . . . . . . . . . . . . . . . . . . . . . . 19 Invoking the NetBackup Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Creating an Oracle Policy and Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Backing Up the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Chapter 3. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Verifying the Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Operating System and Platform Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 NetBackup Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Cluster Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Installing NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Remote Installation of NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Loading the NetBackup for Oracle Files onto the Server . . . . . . . . . . . . . . . . . . 30 Pushing the Software to All Clients Currently Specified in an Oracle Policy Type 33 Pushing the Software to New or Selected Clients . . . . . . . . . . . . . . . . . . . . . . . . . 36 Local Installation of NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Linking the Oracle Recovery Manager (RMAN) With NetBackup . . . . . . . . . . . . . . . . 42 Verifying Environment Variables and Shutting Down Oracle . . . . . . . . . . . . . . . . . 43 Linking the Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Manually Linking AIX (32-bit or 64-bit) Using 32-bit Oracle8 or Oracle8i Software 46 Manually Linking AIX (64-bit) Using 64-bit Oracle8i Software . . . . . . . . . . . . . 48 Manually Linking HP-UX (32-bit or 64-bit) Using 32-bit Oracle8 or Oracle8i Soft- ware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Manually Linking HP-UX (64 bit) Using 64-bit Oracle8 or Oracle8i Software . 51

iv


Manually Linking IRIX (64-bit) Using 64-bit Oracle8i Software . . . . . . . . . . . . . 53 Manually Linking Linux Using Oracle8i Software . . . . . . . . . . . . . . . . . . . . . . . . 55 Manually Linking Solaris (32-bit or 64-bit) Using 32-bit Oracle8 or Oracle 8i Soft- ware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Manually Linking Solaris (64 bit) Using 64-bit Oracle 8i Software . . . . . . . . . . . 58 Manually Linking Tru64/Digital UNIX (OSFI) Using Oracle8 or Oracle8i Soft- ware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Manually Linking AIX Using 64-bit Oracle9i or Later Software . . . . . . . . . . . . . 62 Manually Linking HP-UX (64-bit) Using 64-bit Oracle9i or Later Software . . . 63 Manually Linking Linux Using Oracle9i or Later Software . . . . . . . . . . . . . . . . . 64 Manually Linking Solaris (32-bit or 64-bit) Using 32-bit Oracle9i or Later Soft- ware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Manually Linking Solaris (64-bit) Using 64-bit Oracle9i or Later Software . . . 66 Manually Linking Tru64/Digital UNIX (OSFI) Using Oracle9i or Later Software 67 Troubleshooting the Linking Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 About the Oracle Recovery Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Chapter 4. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 User Interface Terminology Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configuring the Maximum Jobs Per Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Configuring Backup Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Adding a New Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Description of Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Adding Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Types of Backup Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Schedule Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Managing Expired Backup Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Adding Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Adding Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Configuring the Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Oracle RMAN Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Contents v

Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Shell scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Environment Variables Set by a User in the XML Export Parameter File . . . . . . . 86 Environment Variables Set by NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . 87 Creating a bp.conf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Creating Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Recovery Manager (RMAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 RMAN Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Creating RMAN Templates Using the NetBackup for Oracle RMAN Template Generation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Creating an RMAN Script From a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Creating RMAN Scripts Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 XML Export Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 XML Export Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Creating XML Export Templates Using the NetBackup for Oracle Wizard . . . 95 Creating an XML Export Script From a Template . . . . . . . . . . . . . . . . . . . . . . . . 97 Creating XML Export Scripts Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Storing Templates and Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Testing Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Chapter 5. Using NetBackup for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Maintaining the RMAN Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Querying the RMAN Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Performing a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Automatic Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Manual Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Performing a User-directed Backup From the Client . . . . . . . . . . . . . . . . . . . . . . . 109 Running NetBackup for Oracle Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Using bpdbsbora to Run a Backup Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Running the NetBackup for Oracle Shell Script . . . . . . . . . . . . . . . . . . . . . . . . . 111 Running RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

vi NetBackup for Oracle System Administrators Guide for UNIX and Linux

Browsing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Using the RMAN Repository to Browse Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Using bplist to Browse Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Performing a Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Running the NetBackup for Oracle Recovery Wizard on the Client . . . . . . . . . . . 113 Using bpdbsbora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Running a NetBackup for Oracle Recovery Shell Script on the Client . . . . . . . . . . 116 Running RMAN on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Using RMAN to Perform a Redirected Restore . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Performing Other RMAN Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Performing an XML Export Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Automatic Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Manual Backup of an Oracle Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 User-directed XML Exports From the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Running NetBackup for Oracle XML Export Templates . . . . . . . . . . . . . . . . . . 122 Using bpdbsbora to Run an XML Export Template . . . . . . . . . . . . . . . . . . . . . . 123 Running the NetBackup for Oracle XML Export Script on the Client . . . . . . . 124 Running bporaexp on the Client as an Oracle User . . . . . . . . . . . . . . . . . . . . . . 124 Browsing XML Export Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Using bporaimp Parameters to Browse XML Export Archives . . . . . . . . . . . . . . . 131 Using bplist to Browse XML Export Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Performing a Restore of an XML Export Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Running the XML Import Wizard on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Using bpdbsbora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Running an XML Import Script on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Running bporaimp on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Redirecting a Restore of an XML Export Archive to a Different Client . . . . . . . . . 144

Contents vii

Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Chapter 6. NetBackup for Oracle with Advanced Client . . . . . . . . . . . . . . . . . . . . 147 Installation and Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 NetBackup for Oracle with Advanced Client Overview . . . . . . . . . . . . . . . . . . . . . . . . 149 Snapshot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Instant Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Offhost Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Block-level Incremental Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Proxy Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 File-based Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Stream-based Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 File-based Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 How Does NetBackup for Oracle with Advanced Client Work? . . . . . . . . . . . . . . . . . 153 Sequence of Operation: Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Sequence of Operation: Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Database Objects Supported by Advanced Backup Methods . . . . . . . . . . . . . . . . 154 Multistreaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 RMAN Multiple Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Restoring Datafiles to a New Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Symbolic Links and Raw Datafiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Quick I/O Datafiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 RMAN Incremental Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Examples: Using Multiple Channels in RMAN Scripts with Proxy Backups . . . 157 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

viii


Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Configuring Snapshot Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Configuring an Oracle Policy with Advanced Client Backup Methods . . . . . . . . 161 Configuring a Snapshot Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 NAS Snapshot Policy with Optional SnapVault Capabilities . . . . . . . . . . . . . . 164 Restoring Data from a Snapshot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Restoring Individual Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Restoring Volumes and File Systems Using Snapshot Rollback . . . . . . . . . . . . . . . 167 Notes on SnapVault Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Configuring Block-level Incremental Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 How Does BLI Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Storage Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Nodata Storage Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Fulldata Storage Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Storage Checkpoint Configuration on the Client . . . . . . . . . . . . . . . . . . . . . . . . 173 Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Configuring Oracle Policies for BLI Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Types of BLI Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Advanced Client Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Types of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Schedule Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Templates and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Chapter 7. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 General Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 NetBackup and NetBackup for Oracle Logs and Reports . . . . . . . . . . . . . . . . . . . . . . . 184 NetBackup for Oracle Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Contents

ix

Enabling Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Accessing the Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 bphdb Directory on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 dbclient Directory on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 bpdbsbora Directory on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 bporaexp and bporexp64 Directories on the Client . . . . . . . . . . . . . . . . . . . . . . 186 bporaimp and bporaimp64 Directories on the Client . . . . . . . . . . . . . . . . . . . . 186 Setting the Debug Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 NetBackup Server Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Oracle Recovery Manager Utility Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Additional XML Export and Import Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Troubleshooting Backup or Restore Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Check the Logs to Determine the Source of the Error . . . . . . . . . . . . . . . . . . . . . . . 188 Troubleshoot Each Stage of the Backup or Restore . . . . . . . . . . . . . . . . . . . . . . . . . 189 Troubleshooting XML Export or XML Import Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Checking the Logs to Determine the Source of the Error . . . . . . . . . . . . . . . . . . . . 192 Troubleshoot Each Stage of the XML Export or XML Import . . . . . . . . . . . . . . . . 193 Troubleshooting the Browser Interface and Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Troubleshooting NetBackup for Oracle with Advanced Client . . . . . . . . . . . . . . . . . . 197 Minimizing Timeout Failures on Large Database Restores . . . . . . . . . . . . . . . . . . . . . 197 Appendix A. Oracle 9i and 10g Real Application Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 How Does NetBackup Fit into a RAC Environment? . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Virtual Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Archiving Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Backing Up a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Restoring a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

x NetBackup for Oracle System Administrators Guide for UNIX and Linux

Restoring Archive Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Appendix B. Script-based Block-level Incremental (BLI) Backups Without RMAN . . 207 Script-based BLI Backup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 How BLI Backups and Restores Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 File System and Storage Checkpoint Space Management . . . . . . . . . . . . . . . . . . . . 210 Configuring Script-based BLI Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Creating NetBackup Policies for Script-Based BLI Backup . . . . . . . . . . . . . . . . . . . 212 Number of Policies Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Policy Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Client List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Backup Selections List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Schedule Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Schedule Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Example Oracle BLI Backup Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Setting the Maximum Jobs per Client Global Attribute . . . . . . . . . . . . . . . . . . . . . . 217 Creating Directories for Logging NetBackup Activity . . . . . . . . . . . . . . . . . . . . . . . 218 Selecting a Backup Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Creating Notify Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Identify the POLICY_IN_CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Oracle Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Select a Backup Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Notify Scripts for Other Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Sample setup_bli_scripts Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Performing Backups and Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Performing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Contents xi

Automatic Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Manual Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Backing Up Quick I/O Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Restoring Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Checking Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 NetBackup Progress Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 NetBackup Debug Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 NetBackup Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Troubleshooting Backup or Restore Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Troubleshooting Stages of the Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Improving NetBackup Backup Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Database Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

xii


Preface

This guide describes how to install, configure, and use NetBackup for Oracle on UNIX and Linux platforms. Throughout the NetBackup for Oracle documentation, the term UNIX refers to both UNIX and Linux platforms. For information about the NetBackup server software, see one of the following platform-specific manuals:

NetBackup System Administrators Guide for UNIX and Linux, Volumes I and II NetBackup System Administrators Guide for Windows, Volumes I and II

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

Finding NetBackup DocumentationA 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.

xiii

Getting Help

Accessing the VERITAS Technical Support Web SiteThe 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.

xiv


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

xv

Comment on the Documentation

Comment on the DocumentationLet 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.

xvi


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

1

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 FeaturesThe following list shows NetBackup for Oracles 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 Media and device management Scheduling facilities

Description All devices supported by Media Manager are available to NetBackup for Oracle. NetBackup scheduling facilities on the master server can be used to schedule automatic and unattended Oracle backups. This also lets you choose the times when these operations can occur. For example, to prevent interference with normal daytime operations, you can schedule your database backups to occur only at night.

Multiplexed backups and restores

NetBackup for Oracle lets you take advantage of NetBackups multiplexing capabilities. Multiplexing directs multiple data streams to one backup device, thereby reducing the time necessary to complete the operation. All backups and restores run simultaneously and transparently without any action from the NetBackup administrator. The database administrator can run database backup and restore operations through NetBackup. Alternatively, you can use Oracles Recovery Manager (RMAN) as if NetBackup were not present. An administrator or any other authorized user can use NetBackup to run database backups and restores.

Transparent execution of both Oracle and regular file system backup and restore operations

Sharing the same Media Manager and disk storage units used for other file backups

It is possible to share the same devices and media used for other backups or to give Oracle exclusive use of certain devices and media.

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 Features

Feature Graphical user interfaces

Description 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 format The XML Schema standard is used to describe the table data that is included in an archive. In this way, the archive contains the key to understanding the format of the data as well as the data itself.

Chapter 1, Introduction

3

NetBackup for Oracle Terminology

Feature Command line interfaces that allow export and import at row-level granularity Restore destination option

Description Parameter files specify the table data to include in an archive and the table data to extract from an archive for import into an Oracle database.

NetBackup for Oracle can either restore XML data to an Operating System directory or import the data back into the Oracle database. The NetBackup catalog contains information on the contents of the archive that can be searched using flexible search criteria, such as tablename or user.

Flexible archive image searches

NetBackup for Oracle TerminologyThis section explains important terms that might be new to an Oracle database administrator or a NetBackup administrator.

XML Export and XML Import TermsThis 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.

4



Archives

XML export

Archive

NetBackup

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

XML export Archive bporaexp command

NetBackup for Oracle converts Oracle table data to XML format (XML schema, or metadata, and XML instance, or data). NetBackup stores the XML data on a NetBackup storage unit. NetBackup for Oracles XML export utility converts Oracle database table data into a self-identifying XML schema document and instance document that can be archived by NetBackup or redirected to an OS directory.


5


Restores

OS DirectoryXML import restore

NetBackup

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. NetBackup retrieves the XML-formatted data from the storage unit. NetBackup for Oracle parses XML-formatted Oracle table data and inserts data into the Oracle database. NetBackup for Oracles XML import utility can parse the XML-formatted data for re-insertion into the database or can redirect the data to an OS directory.

Restore XML import bporaimp command

Oracle TermsFull 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. NetBackup for Oracle System Administrators Guide for UNIX and Linux

6


Multilevel Incremental Backup

RMAN allows you to create multilevel backups. An integer identifies each level; for example, 0, 1, 2, and so on. A level 0 incremental backup, which is the base of subsequent incremental backups, copies all blocks containing data. When you generate a level n incremental backup in which n is greater than 0, you back up the following:

All blocks that have been modified since the most recent backup at a level n or lower. This is the default type of incremental backup. It is called a differential incremental backup. All blocks that have been modified since the most recent backup at level n-1 or lower. This is called a cumulative incremental backup.

The benefit to performing multilevel incremental backups is that you do not back up all of the blocks all of the time. Incremental backups at a level greater than 0 only copy blocks that were modified, which means that the backup size can be significantly smaller and the backup might require much less time. The size of the backup file depends solely upon the number of blocks modified and the incremental backup level. Differential Incremental Backup In a differential level n incremental backup, you back up all blocks that have changed since the most recent backup at level n or lower. For example, in a differential level 2 backup, you back up all blocks modified since the last level 2, level 1, or level 0 backup. Incremental backups are differential by default. In a cumulative level n incremental backup, you back up all blocks that have changed since the most recent backup at level n-1 or lower. For example, in a cumulative level 2 backup, you back up all blocks changed since the most recent level 1 or level 0 backup. Cumulative incremental backups reduce the work needed for a restore by ensuring that you only need one incremental backup from any particular level at restore time. Cumulative backups require more space and time than Differential Incremental Backups, however, because they duplicate the work done by previous backups at the same level.

Cumulative Incremental Backup


7


Oracle RMAN TermsRMAN RMAN backs up, restores, and recovers database files. RMAN starts Oracle server processes on the target database. These Oracle server processes perform the backup and restore. RMAN performs backup and recovery procedures, and it greatly simplifies the tasks administrators perform during these processes. However, RMAN cannot directly manage the storage devices and media used in its backups, so it must be integrated with an application that has these capabilities. NetBackup for Oracle provides device and media management capabilities by integrating RMAN with NetBackup and its media management software. Other advantages are access to NetBackups automatic scheduling facilities and the graphical interfaces. An RMAN recovery catalog or the database control file is a repository for information that is used and maintained by RMAN. RMAN uses this information to determine how to run requested backup and restore actions. For a description of the recovery catalog, see the Oracle Server Backup and Recovery Guide. rman command RMAN script The rman command starts an RMAN backup or restore. This command is described in the Oracle Server Backup and Recovery Guide. 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

RMAN Repository

/usr/openv/netbackup/ext/db_ext/oracle/samples /rman directory. These example scripts run RMAN commands andare 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 Overview

NetBackup for Oracle OverviewThe 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 installed.System hosting the Oracle database NetBackup for Oracle supplies: Oracle database to back up or restore Sample configuration program Sample script files VERITAS I/O Library (libobk) bporaimp and bporaexp Additional required NetBackup software: NetBackup Client

System containing Oracle database Recovery Catalog

Oracle database software supplies: Oracle Recovery Manager (RMAN) Oracle Call Interface (OCI)

Network (TCP/IP)

NetBackup master server or remote media server NetBackup software: NetBackup Master Server NetBackup Media Server (if system is a media server)

Media Manager or disk storage unit

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


9


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: Linking with NetBackup Generating unique file names

NetBackup for Oracle includes a library of functions that enable RMAN to use NetBackup. To link with this library, see Linking the Library on page 44. 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



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


11


Sequence of Operation: XML Export Archive

XML schema(s), XML instance(s) XML generator Option to create XML files on disk XML schema(s), XML instance(s)

NetBackup

Table(s) metadata, Table(s) data Oracle DBMS OCI Table list WHERE clause Script or template (bporaexp) (Parameter file) Query processor

Command line 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. Oracles OCI API executes the queries on the Oracle instance to be archived.12 NetBackup for Oracle System Administrators Guide for UNIX and Linux


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 Parser

XML schema(s), XML instance(s)

NetBackup

Table(s) metadata, Table(s) data

Archive name Keyword Table name

OCI Oracle DBMS XML data loader

Script or template (bporaimp) (Parameter file)

Command line or Backup, Archive, and Restore interface


13


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 Oracles OCI API to insert the data into the database. Optionally, bporaimp allows the XML data stream to bypass the XML parser and be sent to an operating system directory. In addition, users can restore the table metadata only into an operating system directory. bporaimp also allows import from an operating system directory into Oracle.

14


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 147. For more detailed instructions, see the following chapters:

Installation on page 27 Configuration on page 69 Using NetBackup for Oracle on page 103

15

Installing NetBackup for Oracle

Installing NetBackup for OracleTo install NetBackup for Oracle, ensure the following: The NetBackup version on the local machine must be the same as the NetBackup for

Oracle version. For example, 6.0. The local machine can be a client or a NetBackup server that also happens to be a client. The local machine must have adequate disk space.

Reserve a minimum of two megabytes of disk space in the /usr/openv/netbackup directory. More disk space might be necessary at run time. NetBackup version 6.0 client or server software is installed and operational.

This also means that the /usr/openv/netbackup directory already exists. For a more comprehensive list of installation prerequisites, see Verifying the Installation Prerequisites on page 27.

Performing the NetBackup for Oracle InstallationDuring a local installation, the NetBackup for Oracle files are extracted and installed. The instructions that follow are for an initial, local installation on the NetBackup client upon which the Oracle database resides. To install NetBackup for Oracle

1. Log in as the root user on the machine. If you are already logged in, but are not the root user, run the following command. su - root If the local machine is a client, go to step 3. If the local machine is a server, go to step 2. 2. Make sure a valid license key for NetBackup for Oracle has been registered. To view or add license keys, perform one of the following: un the command R /usr/openv/netbackup/bin/admincmd/get_license_key.

Open the NetBackup Administration Console and choose Help > License Keys. 3. Insert the CD-ROM into the drive. 4. Change to the working directory to the CD-ROM directory.

16



cd /CD_mount_point 5. Load and install the software by running the install script../install

a. Select the NetBackup Database Agent Software option. The following prompt appears:

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

b. Answer y. You are presented with a menu of all database agents available on the CD-ROM. c. Select the NetBackup for Oracle option. d. Enter q to quit selecting options. A prompt appears asking if the list is correct. e. Answer y. The following actions occur: The version file, compressed tar file, and install_dbext script are loaded to directory /usr/openv/netbackup/dbext. he install script automatically runs the install_dbext script. T

If the receiving client is configured as an HP-UX11.00, HP-UX11.11, Solaris7, or Solaris8, IRIX65, AIX4.3.3, or AIX5 machine, both the 32-bit and 64-bit versions of NetBackup for Oracle are installed. f install_dbext completes successfully, there is a version file in directory I /usr/openv/netbackup/ext/ that contains the version of NetBackup for Oracle that was installed and an installation timestamp.

Linking NetBackup for Oracle with RMANBefore writing to sequential devices such as tape, you must link the Oracle server software with the media management API library installed by NetBackup for Oracle. Oracle uses this library when it needs to write to, or read from, devices.

Chapter 2, NetBackup for Oracle QuickStart

17

Installing NetBackup for Oracle To link Oracle with NetBackup for Oracle

1. Become the Oracle user.su - oracle

2. (Conditional) Shut down all of the Oracle instances (SIDs). Perform this step if you are using an Oracle8 release. Oracle releases 9 and later do not need to perform this step. The user must connect as the SYSDBA, either using OS Authentication or Oracle Authentication (set up in the Oracle password file). The following example is for Oracle9i. a. Set the $ORACLE_SID environment variable to the first SID. b. Connect as SYSDBA in one of the following ways: Using OS Authentication: sqlplus /nolog connect / as sysdba shutdown immediate exit Using Oracle Authentication (via password file): sqlplus /nolog connect userid/password as sysdba shutdown immediate exit c. Change the $ORACLE_SID environment variable to any other SID that uses this Oracle installation, and repeat the preceding commands. 3. Set up automatic linking. a. Change directory to /usr/openv/netbackup/bin/ b. Run the oracle_link script: ./oracle_link This script determines the Oracle version level and then links Oracle to NetBackup. All output from this script is written to /tmp/make_trace.pid. To change the trace file location, change the MAKE_TRACE variable in the oracle_link script.

18


Configuring a NetBackup for Oracle Policy and Schedule

4. Restart the Oracle instances.

Configuring a NetBackup for Oracle Policy and ScheduleTo 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 ConsoleYou configure an Oracle policy from the NetBackup Administration Console on the master server. Depending on your master servers platform, the console is available in one or two forms. NetBackup supports a Java interface for both UNIX and Windows master servers. In addition, NetBackup supports a Windows interface for Windows master servers. Use one of the following procedures to invoke the NetBackup Administration Console:

To invoke the NetBackup Administration Console on a UNIX master server 1. Log on to the NetBackup master server as root. 2. Start the NetBackup Administration Console by typing the following command: /usr/openv/java/jnbSA &

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 SchedulesThe following procedures use the NetBackup Policy wizard to help you create a NetBackup for Oracle policy. In most cases, you can accept the default entries.


19

Configuring a NetBackup for Oracle Policy and Schedule 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: 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 20 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.20 NetBackup for Oracle System Administrators Guide for UNIX and Linux

Backing Up the Oracle Database

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. ultiplexing is 1. M

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. 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 DatabaseNetBackup for Oracle includes a Backup Wizard that solicits information about desired RMAN backup operations. The wizard uses this information to create a template that can back up the Oracle database. You can run this template immediately, or you can save it to run later.Chapter 2, NetBackup for Oracle QuickStart 21


To back up an Oracle database, perform the following procedures: To log into the client and invoke the Backup Wizard on page 22 To back up the Oracle database using the Backup Wizard on page 24 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 running the following command: /usr/openv/java/jbpSA & 4. Provide the information requested by the login dialog box. For the Host name, type the name of the client upon which the Oracle database and NetBackup for Oracle reside. Type your user name and password in the other fields. You can log in as a regular user. You do not have to log in as root or as the Oracle administrator. After NetBackup accepts your login information, the NetBackup Administration Console appears. 5. Click the Backup Files tab.

22



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. o back up an entire Oracle T 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: Net service name (TNS alias): c. Select the data files or tablespaces in the instance that you want to back up by clicking in the checkbox to the left of each instance data files name. d. Proceed to step 10 10. Click Backup.


23


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 databases archiving mode is set to ARCHIVELOG. 1. Invoke the Backup Wizard. The procedure in To log into the client and invoke the Backup Wizard on page 22 describes how to invoke this wizard. If you just completed that procedure, the Backup Wizard is displayed on your screen at this time. 2. Click Next. The Target Database Logon Credentials dialog box displays. Fill in the fields in this dialog box, as follows: If you use OS authentication for Oracle, select OS Authentication. If you use Oracle authentication via a password file, select Oracle_Authentication and supply the following: A User name A Password with Oracle SYSDBA privileges (Optional) A Net service name (TNS alias)

Optional) Select Use Oracle RMAN recovery catalog. This is not required. If this ( is your first NetBackup for Oracle backup, you can leave this option unselected.

If you did not choose to use the recovery catalog, skip to step 4. 3. Click Next. If you chose to use the recovery catalog, you see the Recovery Catalog Logon Credentials screen. Supply the appropriate User name and Password for the recovery catalog. 4. Click Next. The Archived Redo Logs screen displays. 5. Click Next to accept all defaults. The Configuration Options screen displays. 6. Click Next to accept all defaults. The Backup Options screen displays. 7. Click Next to accept all defaults. The Database State screen displays.

24



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.


25


26


InstallationThis chapter describes how to perform the following tasks: Verifying the installation prerequisites for NetBackup for Oracle. Perform this task

3

before installing this agent. Installing NetBackup for Oracle. Enabling functions specific to NetBackup for Oracle.

Verifying the Installation PrerequisitesBefore installing 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 CompatibilityVerify 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.

27

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 SoftwareVerify that the following requirements are met for the NetBackup server and client software: The NetBackup server software is installed and operational on the NetBackup server. The NetBackup server platform can be any 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. The version of the NetBackup client and the version of NetBackup for Oracle to be installed must be the same (for example, 6.0). There must be adequate disk space on each machine upon which you are installing NetBackup for Oracle. Less than two megabytes of additional disk space is required in the /usr/openv/netbackup directory. However, more disk space might be needed at run time. Make sure that you 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 Administrators Guide.

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

28


Verifying the Installation Prerequisites

Oracle vendor software must be installed and operational. One or more Oracle instances must exist. For all Oracle 8 releases, make sure you have shut down the Oracle database. For more information about when you need to perform this step, see your Oracle documentation. For information on installing Oracle and creating instances, see your Oracle documentation.

Cluster SoftwareVerify the following requirements if you are installing 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, including running the cluster_config script after the NetBackup server software has been installed. You only need to run the cluster_config script after you install the NetBackup server software. You do not need to run cluster_config after installing NetBackup for Oracle on a NetBackup server that is part of a NetBackup cluster. The following additional information also pertains to cluster environments: Make sure you install the NetBackup client software and the NetBackup for Oracle software on each node to which NetBackup can failover. Run commands such as bpplclients and update_dbclients from the active NetBackup master or media server. If you plan to perform a remote installation, in which you push the database agent software to clients located in a cluster, specify the individual node names, not the virtual names, in the client list.

Chapter 3, Installation

29


Installing NetBackup for OracleYou can install the database agent software in one of the following ways: A remote installation. The user loads the software onto a master server or a media

server and then pushes the database software out to the clients. You can perform an initial or upgrade remote installation in this manner. Remote Installation of NetBackup for Oracle on page 30 describes this procedure. A local installation. The user loads and installs the software onto the local machine

only. Local Installation of NetBackup for Oracle on page 38 describes this procedure.

Remote Installation of NetBackup for OracleDuring a remote installation, you load the NetBackup for Oracle files onto either a UNIX master server or media server, and then you push the software to the clients to install it.

Loading the NetBackup for Oracle Files onto the Server To load the NetBackup for Oracle files on a UNIX server

1. Review Verifying the Installation Prerequisites on page 27. If you are installing NetBackup for Oracle on a clustered NetBackup server, be sure to read Cluster Software on page 29. 2. (Conditional) Perform this step only if you are installing on a server that is part of a NetBackup cluster. a. Freeze the active NetBackup node. When you install NetBackup for Oracle, install the software on all the inactive nodes first, then install on the active node. For information on how to freeze the active node in your specific cluster environment, see the NetBackup High Availability System Administrators Guide. b. Decide which of the inactive nodes to install the software on first. In the next step, you log in to the first machine and commence the installation process. Because you need to perform the installation on all inactive nodes first, make sure that the first machine you select is an inactive node. 3. Log in as the root user on the master or media server. If you are already logged in, but are not the root user, run the following command:30 NetBackup for Oracle System Administrators Guide for UNIX and Linux


su - root

4. Verify that a registered and valid license key for NetBackup for Oracle resides on the master server. You can obtain master server license information from either the master server or the media server. To view or add license keys, perform one of the following actions: From the master or media server, run the following command:

/usr/openv/netbackup/bin/admincmd/get_license_key When the system prompts you, type the host name of the NetBackup master server. Open the NetBackup Administration Console and choose Help > License Keys.

If the NetBackup master server is part of a NetBackup cluster, the license key must be registered on each node. 5. Mount the CD-ROM. For more information on how to mount a CD-ROM, see the NetBackup Installation Guide. 6. Change the working directory to the CD-ROM directory. For example: cd /CD_mount_point 7. Invoke the install script to load and install the software. For example: ./install a. Select the NetBackup Database Agent Software option. The following prompt appears: Do you want to do a local installation? (y/n) [n] b. Answer n. A menu of all database agents available on the CD-ROM displays. c. Select the NetBackup for Oracle option. d. Type q to quit selecting options. A prompt appears asking if the list is correct.

Chapter 3, Installation 31


e. Answer y. The install script identifies the types of client software loaded during the installation of the NetBackup server. By default, any matching NetBackup for Oracle software is automatically loaded. If there are more platforms available, the script displays a menu that gives you the opportunity to add more client types to the default list. After the list is complete, the installation script copies database agent version files, tar(1) files compressed with gzip(1), and the install_dbext script to directory /usr/openv/netbackup/dbext. 8. (Conditional) Select another node upon which to install the software. Perform this step under the following circumstances: If you are installing the NetBackup for Oracle software on a server that is part of a

NetBackup cluster. and If you have nodes that still need to have the software installed.

If there are inactive nodes that do not yet have the software installed upon them, select one of these inactive nodes, and repeat step 3 through step 8 for that node. If you have installed the software on all the inactive nodes, select the active node and repeat step 3 through step 8 for that node. If you have installed on all the nodes, proceed to step 9. 9. (Conditional) Unfreeze the active node. Perform this step if you are installing the NetBackup for Oracle software on a server that is part of a NetBackup cluster. Unfreezing the active node is the last step in the installation process. Unfreeze the active node only after all the software has been installed on all nodes. For information on how to unfreeze the active node in your specific cluster environment, see the NetBackup High Availability System Administrators Guide. 10. Decide how you want to distribute the NetBackup for Oracle software to the clients. Regardless of whether you are upgrading clients in an existing environment or you are performing a new installation, use one of the following methods: Distribute to all clients currently specified in an Oracle policy type. This method

distributes the NetBackup for Oracle software to all clients that are currently included in an Oracle policy type. You can use this method only if you are pushing from a master server. For information on this method, see Pushing the Software to All Clients Currently Specified in an Oracle Policy Type on page 33.

32


Installing NetBackup for Oracle Distribute to selected clients. This method distributes the NetBackup for Oracle

software to selected clients only. If you are performing a new installation, and you plan to add clients to an Oracle policy type after you install the software, you can install the software on such clients now and configure the policy later. This method also allows you to skip clients that you do not want to upgrade to 6.0 at this time. You can use this method whether you are pushing from a master server or from a media server. For information on this method, see Pushing the Software to New or Selected Clients on page 36. Note Make sure that the NetBackup for Oracle version is the same version as the NetBackup client software.

Pushing the Software to All Clients Currently Specified in an Oracle Policy TypeUse the following procedure if you want to install or upgrade the NetBackup for Oracle software on all clients currently configured in an Oracle policy type. You can use this procedure only from a master server. To push the software to all clients specified in an Oracle policy type

Note If you are pushing the NetBackup for Oracle software from a server that is part of a NetBackup cluster, type all commands in this procedure from the active NetBackup node. 1. Run the update_dbclients command to launch the installation script. Type the following command: /usr/openv/netbackup/bin/update_dbclients Oracle ALL ALL 2. Examine the client list that the update_dbclients command returns. a. Locate the client list. The update_dbclients command compiles a list of clients that it detects are included in an Oracle policy type. It presents this list to you. If 9 or fewer clients are in the client list, update_dbclients displays all the client names. If 10 or more clients are on the client list, update_dbclients writes the first 9 to standard output and writes the entire list to $TMPDIR/NB_DBCLIENT_LIST.identifier, where identifier is a mix of date, time, and process identifier information. If the TMPDIR environment variable is not set, the default is /tmp. b. Check the client list.Chapter 3, Installation 33


The host names of the clients must be the clients individual node names. They cannot be virtual names. The correct value for the individual node names is returned by the hostname(1) and the domainname(1) commands. The format can be either hostname or hostname.domainname. If the client list contains virtual names, you cannot complete this procedure. Do one of the following: To exit this procedure if there are two or more clients, press the Enter key and

then type n to stop the upgrade and exit from this installation dialog. To install the software in this situation, use Pushing the Software to New or Selected Clients on page 36. To exit this procedure if there is only one client, type n. To install the software

in this situation, use Pushing the Software to New or Selected Clients on page 36. If the client list contains only individual node names, proceed to the following step. c. Check the skipped client list, if any. If update_dbclients detects that it cannot update a particular client, it does not include the name of that client in the client list. Such clients are skipped for one or more of the following reasons: The client is a PC client. You cannot install or

VERITAS NetBackup 6[1].0 on Unix-Oracle

Documents

Transcript of VERITAS NetBackup 6[1].0 on Unix-Oracle