300-006-990

EMC® NetWorker® Module for Oracle Release 5.0 Administration Guide P/N 300-006-990 REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.com Copyright © 2003 - 2009 EMC Corporation. All rights reserved. Published June, 2009 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Contents Preface Chapter 1 Introduction Naming conventions used in this guide............................................................... 20 Importance of backups............................................................................................ 20 Product features ....................................................................................................... 20 Scheduled compared to manual backups ..................................................... 21 Deduplication backups and restores ............................................................. 21 Probe-based backups ....................................................................................... 23 Proxy backups and restores ............................................................................ 24 VMware support............................................................................................... 25 Archived redo log backups ............................................................................. 25 Control file autobackup ................................................................................... 25 Automatic channel allocation ......................................................................... 26 Backup and restore optimization ................................................................... 26 Backup copies.................................................................................................... 27 Backup of backup sets...................................................................................... 29 Cluster and RAC backups and restores......................................................... 29 Configuration wizards..................................................................................... 30 Internationalization (I18N) and localization (L10N) ................................... 33 Oracle Data Guard support............................................................................. 36 Parallelism ......................................................................................................... 36 Policy uniformity .............................................................................................. 37 Restartable backups.......................................................................................... 37 Retention policies ............................................................................................. 38 Save set bundling.............................................................................................. 39 Other Oracle features ....................................................................................... 44 Software used in the NMO environment ............................................................. 47 NetWorker software ......................................................................................... 47 NMO software................................................................................................... 48 NetWorker PowerSnap Module software ..................................................... 48 Oracle backup and recovery system .............................................................. 49 NMO components ................................................................................................... 51 NMO backup and restore processes ..................................................................... 52 Regular scheduled backup processes ............................................................ 53 Regular manual backup processes................................................................. 54 Deduplication backup processes.................................................................... 55 Regular restore processes ................................................................................ 57 Deduplication restore processes..................................................................... 58 EMC NetWorker Module for Oracle Release 5.0 Administration Guide 3 Contents Chapter 2 Software Configuration Configuration roadmap.......................................................................................... 62 Verify the Oracle Server configuration................................................................. 63 Verify the NetWorker resources ............................................................................ 63 NetWorker Server resource.............................................................................. 63 NetWorker user group privileges ................................................................... 64 NetWorker Schedule resource......................................................................... 66 NetWorker Device resources ........................................................................... 66 NetWorker volume pools................................................................................. 66 Firewall support ................................................................................................ 67 Configuring I18N support ..................................................................................... 67 Requirements for I18N support ...................................................................... 68 Configure I18N support ................................................................................... 68 Configure L10N support ........................................................................................ 69 Migrating a legacy configuration with the nsrnmoadmin command ..............69 Requirements for using the nsrnmoadmin command for migration ........ 70 Migration command syntax and options ...................................................... 71 Configuring a backup with the NMC wizard......................................................72 About the backup configuration wizard ....................................................... 72 Requirements for using the backup configuration wizard ......................... 73 Configure a backup with the wizard ............................................................. 73 Configuring a backup with the NMC legacy method ........................................75 About backup configuration with the legacy method................................. 75 Create RMAN scripts for backups.................................................................. 75 Customize the nsrnmo script .......................................................................... 79 Configure a Group resource with NMC ........................................................ 86 Configure a Schedule resource with NMC.................................................... 87 Configure a Client resource with NMC ......................................................... 87 Configure save set bundling............................................................................ 91 Configure policy uniformity ........................................................................... 92 Configuring a deduplication backup ................................................................... 93 Requirements for a deduplication backup .................................................... 94 Best practices for a deduplication backup..................................................... 94 Configure a deduplication backup................................................................. 95 Configuring a probe-based backup ...................................................................... 97 Requirements for a probe-based backup ....................................................... 97 Configure a probe-based backup.................................................................... 97 Chapter 3 Backup Procedures Manual backup procedures ..................................................................................104 Requirements for a manual backup ............................................................. 104 Manual backup through the RMAN command line interface ................. 105 Manual backup through Oracle Enterprise Manager Backup Management Tools .................................................................................................................. 105 NetWorker server bootstrap backup ............................................................ 106 Cancel a manual backup ................................................................................ 107 Monitor a manual backup.............................................................................. 108 Scheduled backup procedures .............................................................................110 Test a scheduled backup ................................................................................ 110 Cancel a scheduled backup ........................................................................... 111 Monitor a scheduled backup......................................................................... 112 Automation of NSR_SERVER and NSR_GROUP parameter settings .... 113 Regular backup information in NetWorker indexes .........................................114 Deduplication backup information in NetWorker indexes..............................115 4 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Contents Chapter 4 Data Restore and Recovery About restore and recovery.................................................................................. 118 NetWorker indexes and policies used for restores .................................... 118 Recovery configuration wizard .................................................................... 118 RMAN scripts for restore and recovery ............................................................. 121 Performing an Oracle data restore and recovery .............................................. 123 Requirements for an Oracle data restore..................................................... 123 Restore through the RMAN command line interface ............................... 125 Restore with Oracle Enterprise Manager Backup Management Tools ... 126 Perform an Oracle data recovery ................................................................. 127 Chapter 5 Disaster Recovery About disaster recovery........................................................................................ 130 Preparing an Oracle database for disaster recovery ......................................... 130 Create the DBID text file................................................................................ 131 Set up a postcommand script for backup of Oracle-related files............. 131 Set up RMAN backups of the database and related files ......................... 132 Set up RMAN backups of Recovery Catalog.............................................. 132 Performing a disaster recovery............................................................................ 133 NetWorker server recovery ........................................................................... 133 Oracle disaster recovery to a new host........................................................ 133 Sample postcommand script................................................................................ 134 Chapter 6 Cluster and RAC Systems Considerations for cluster and RAC systems .................................................... 138 Parameters in the RMAN script or session................................................. 138 NetWorker software configuration .............................................................. 139 Backup failover ............................................................................................... 139 Cluster systems ...................................................................................................... 139 Roadmap for backup/restore configuration in a cluster system............. 140 Backup failover ............................................................................................... 140 RAC systems........................................................................................................... 140 RAC terminology............................................................................................ 140 RAC backups and restores ............................................................................ 141 Roadmap for backup/restore configuration in a RAC system................ 141 Setting up RAC nodes to back up to a local storage node........................ 142 Connect-time failover..................................................................................... 144 Creating RMAN backup scripts ................................................................... 146 Creating RMAN restore scripts .................................................................... 146 Archived redo logs ......................................................................................... 147 Chapter 7 Proxy Backups and Restores Overview of proxy backups and restores........................................................... 150 Types of proxy backups ................................................................................. 150 Types of proxy restores .................................................................................. 151 Proxy backup and restore system........................................................................ 151 Proxy backup processes ........................................................................................ 153 Scheduled proxy backup ............................................................................... 154 Proxy restore processes ......................................................................................... 159 Instant restore or rollback.............................................................................. 160 Restore from secondary storage ................................................................... 161 Software configuration roadmap........................................................................ 163 EMC NetWorker Module for Oracle Release 5.0 Administration Guide 5 Contents Basic configurations........................................................................................ 163 Additional configurations for proxy operations ........................................ 163 Proxy backup requirements..................................................................................171 Checking configuration consistency ............................................................ 171 Performing proxy backups ............................................................................ 172 Proxy backup information in the NetWorker indexes ......................................174 Entries in the client file index........................................................................ 175 Entries in the media database ....................................................................... 175 NWORA resource file backup in the NetWorker indexes......................... 176 Proxy restore requirements.................................................................................. 177 Creating RMAN scripts for proxy restores.................................................. 177 Performing proxy restores ............................................................................. 178 Relocating files during proxy restores ......................................................... 179 Restoring to a different host .......................................................................... 180 Point-in-time recoveries without a Recovery Catalog............................... 181 Catalog synchronization for proxy backups ......................................................181 Extra entries in the catalogs........................................................................... 181 Control file versus recovery catalog............................................................. 183 The NWORA resource file ............................................................................. 183 Automatic catalog synchronization with the nsroraclecat program ....... 191 Proxy backups and restores on cluster systems.................................................194 Proxy backup failover .................................................................................... 194 Proxy backups from a virtual cluster client ................................................ 195 Proxy backups from a physical cluster client.............................................. 196 Restores from proxy backups on a cluster system ..................................... 197 Appendix A Parameters in an RMAN Session Setting the NSR* parameters ............................................................................... 200 NSR* parameter definitions................................................................................. 201 Appendix B RMAN Commands The delete expired backup command ................................................................ 210 The change...crosscheck and crosscheck commands ....................................... 210 The pool option of the backup command.......................................................... 210 The send command............................................................................................... 211 Syntax rules...................................................................................................... 211 Two ways to run the send command........................................................... 213 Precedence rules.............................................................................................. 215 The set duplex command..................................................................................... 215 The trace option of the backup command ......................................................... 217 6 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Contents Appendix C Troubleshooting and Error Messages Troubleshooting tips............................................................................................. RMAN error messages ......................................................................................... NMO error messages............................................................................................ Error messages from the libnwora library .................................................. Error messages from the nsrnmoadmin program ..................................... Error messages from the nsrnmoinfo program.......................................... Error messages from the nsrnmoprobe program ...................................... Error messages from the nsrnmostart program......................................... 220 221 222 223 231 233 235 236 Glossary Index EMC NetWorker Module for Oracle Release 5.0 Administration Guide 7 Contents 8 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Figures Title 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Page Regular Oracle backup and recovery system.................................................................... 50 Regular scheduled NMO backup ....................................................................................... 54 Regular manual NMO backup ............................................................................................ 55 Deduplication NMO backup ............................................................................................... 57 Regular NMO restore ........................................................................................................... 58 UNIX Client resource for scheduled backups................................................................... 90 Windows Client resource for scheduled backups............................................................ 91 Oracle backup messages in Sessions tab of Monitoring window ................................ 108 Oracle backup messages in Devices tab of Monitoring window ................................. 109 Oracle backup messages in Log tab of Monitoring window ........................................ 109 Group details for regular scheduled backups................................................................. 113 Proxy backup and restore system..................................................................................... 153 Scheduled instant backup .................................................................................................. 156 Scheduled immediate live backup.................................................................................... 158 Deferred live backup .......................................................................................................... 159 Instant restore or rollback .................................................................................................. 161 Restore from secondary storage........................................................................................ 162 EMC NetWorker Module for Oracle Release 5.0 Administration Guide 9 Figures 10 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Tables Title 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Page NMO components................................................................................................................. 51 NetWorker Server resource attributes ............................................................................... 63 User group privileges required for NMO operations...................................................... 65 Options of the nsrnmoadmin command for migration................................................... 72 NetWorker Client resource attributes ................................................................................ 88 NetWorker Probe resource attributes ................................................................................ 98 PowerSnap parameters ...................................................................................................... 167 NWORA parameter resources .......................................................................................... 184 NWORA SID resource components ................................................................................. 186 Parameters in the RMAN command or script ................................................................ 201 Option values in the send command ............................................................................... 213 Set duplex command values.............................................................................................. 216 Trace option values and conditions traced...................................................................... 217 Error messages from the libnwora library....................................................................... 223 Error messages from the nsrnmoadmin program.......................................................... 231 Error messages from the nsrnmoinfo program .............................................................. 234 Error messages from the nsrnmoprobe program ........................................................... 235 Error messages from the nsrnmostart program ............................................................. 236 EMC NetWorker Module for Oracle Release 5.0 Administration Guide 11 Tables 12 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Examples Title 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Page Using the configure channel command with parms option for automatic channels .. 26 Specifying parameter values per automatic channel ....................................................... 26 Using the set backup copies command in the RMAN script .......................................... 28 Using automatic channels for backup copies .................................................................... 28 Expiring a backup ................................................................................................................. 38 Save set bundling for a one-week scheduled backup cycle of a tablespace ................. 42 Save set bundle join .............................................................................................................. 43 Splitting a save set bundle across volumes ....................................................................... 43 Using save set consolidation to re-unite a save set bundle ............................................. 44 RMAN script for a manual backup .................................................................................... 75 RMAN script for AES encryption during an Oracle backup .......................................... 76 RMAN script for a scheduled backup ................................................................................ 77 RMAN script for a manual deduplication backup ........................................................... 96 Possible Command Options settings for the nsrnmoprobe program ........................... 99 Multiple probes for a probe-based backup ..................................................................... 100 RMAN script to restore a tablespace ................................................................................ 121 RMAN script to restore an AES encrypted backup ....................................................... 122 RMAN script to restore from a specified pool ................................................................ 122 Sample nsrnmoinfo commands for Oracle restores ....................................................... 125 Volume information displayed by the nsrnmoinfo command ..................................... 125 Sample postcommand script on UNIX ............................................................................ 134 Sample postcommand script on Windows ...................................................................... 135 Setting up RAC nodes as storage nodes .......................................................................... 142 RMAN script for a manual Oracle backup on a RAC system ...................................... 146 RMAN script for an Oracle restore on a RAC system ................................................... 146 RMAN scripts with multiple channels ............................................................................ 165 PowerSnap parameter settings .......................................................................................... 168 PowerSnap parameter settings for a Celerra NAS device ............................................ 168 Proxy backup failure ........................................................................................................... 172 Proxy backup entries in the client file index ................................................................... 175 Proxy backup entries in the media database ................................................................... 176 Resource file backup entry in the client file index ......................................................... 176 Resource file backup entry in the media database ......................................................... 176 RESTORE_TYPE_ORDER parameter settings ................................................................ 177 Symbolic link specified in the set newname command ................................................. 180 Relocation of a raw volume ............................................................................................... 180 Default NWORA parameter resources ............................................................................ 186 NWORA SID resource ........................................................................................................ 187 Connection file contents ..................................................................................................... 188 Proxy backup entries in the index of a physical cluster client ...................................... 196 EMC NetWorker Module for Oracle Release 5.0 Administration Guide 13 Examples Title 41 42 43 44 Page Proxy backup entries in the index of a virtual cluster client ......................................... 197 A send command sets the parameters for a specified channel ..................................... 212 An rman send command sets a parameter for all channels .......................................... 214 Order of parameters set according to the precedence rules .......................................... 215 14 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Preface As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. Audience This document is part of the EMC NetWorker Module for Oracle (NMO) documentation set, and is intended for use by system administrators and Oracle database administrators (DBAs) who are responsible for installing software and maintaining the Oracle Server backup and recovery systems. Operators who monitor Oracle database backups may also find this document useful. Readers of this document are expected to be familiar with the following topics: ◆ ◆ ◆ Oracle terminology and concepts, especially those related to Oracle database backup and recovery. Backup and recovery procedures on an Oracle Server. Disaster recovery procedures on an Oracle Server. Related documentation Documentation related to the use of this product can be found at the EMC website, http://Powerlink.EMC.com, including: ◆ The NetWorker Module for Oracle release 5.0 documentation set: • Administration guide • Installation guide • Release notes • Command reference guide The NetWorker documentation set: • Administration guide • Installation guide • Release notes • Command reference guide • Disaster recovery guide Other EMC documentation: • NetWorker PowerSnap Module documentation • Software compatibility guide • UNIX man pages ◆ ◆ EMC NetWorker Module for Oracle Release 5.0 Administration Guide 15 Preface The following additional documentation may be useful: ◆ ◆ Oracle Server documentation Oracle database backup and recovery documentation Conventions used in this document EMC uses the following conventions for special notices. Note: A note presents information that is important, but not hazard-related. ! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment. ! IMPORTANT An important notice contains information essential to software or hardware operation. Typographical conventions EMC uses the following type style conventions in this document: Normal Used in running (nonprocedural) text for: • Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) • Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, utilities • URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications Used in running (nonprocedural) text for: • Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, man pages Used in procedures for: • Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) • What the user specifically selects, clicks, presses, or types Bold Italic Used in all text (including procedures) for: • Full titles of publications referenced in text • Emphasis (for example, a new term) • Variables Used for: • System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Used for: • Specific user input (such as commands) Used in procedures for: • Variables on the command line • User input variables Angle brackets enclose parameter or variable values supplied by the user Square brackets enclose optional values Courier Courier bold Courier italic [] 16 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Preface | {} ... Where to get help Vertical bar indicates alternate selections - the bar means “or” Braces indicate content that you must specify (that is, x or y or z) Ellipses indicate nonessential information omitted from the example EMC support, product, and licensing information can be obtained as follows. Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: http://Powerlink.EMC.com Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to: [email protected] If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing. EMC NetWorker Module for Oracle Release 5.0 Administration Guide 17 Preface 18 EMC NetWorker Module for Oracle Release 5.0 Administration Guide 1 Introduction This chapter includes the following major sections: ◆ ◆ ◆ ◆ ◆ ◆ Naming conventions used in this guide .................................................................... Importance of backups ................................................................................................. Product features............................................................................................................. Software used in the NMO environment .................................................................. NMO components......................................................................................................... NMO backup and restore processes........................................................................... 20 20 20 47 51 52 Introduction 19 Introduction Naming conventions used in this guide Consider the naming conventions used throughout this guide: ◆ “Administrator Microsoft user” and “a member of the Microsoft Windows Administrators group” are used interchangeably. “Oracle Server host” refers to the host where both the Oracle Server and EMC® NetWorker® Module for Oracle (NMO) software are installed. “Proxy backup or restore” refers to an Oracle RMAN proxy copy backup or restore that is implemented by using snapshot technologies through the PowerSnap™ Module software. Unlike the NetWorker software, which uses the term recover for all data retrieval activities, Oracle distinguishes between restoring and recovering a database: • “Restore” refers to retrieving individual datafiles from backup and storing the files on disk. • “Recover” refers to applying the redo logs to make the database consistent. This guide follows the Oracle terminology. “Regular backup or restore” refers to an NMO backup or restore of Oracle data that does not use snapshot technologies through the PowerSnap Module software. "UNIX" refers to both UNIX and Linux operating systems, unless specified otherwise. "Windows" refers to all the supported Microsoft Windows operating systems, unless specified otherwise. ◆ ◆ ◆ ◆ ◆ ◆ Importance of backups The reliability of computer equipment has improved greatly in recent years, but system and hardware failures still occur, sometimes with catastrophic results. In a client/server environment, data can be lost due to hardware failures and user errors. Software bugs, procedural flaws, and simple user errors are common problems that necessitate database restores from backup storage media. A viable backup strategy can help in the recovery from disastrous situations. Database administrators must recognize the importance of performing regular backups of database files and frequent backups of archived redo logs. If all archived redo logs are lost, a database can be recovered only to the time of the last consistent backup. Without backups and archived redo logs, the database cannot be recovered at all. Product features The following sections describe major features of the NMO, Oracle Recovery Manager (RMAN), and Oracle Server software. Certain sections refer to the send command, which is used to set parameters in the RMAN script for an NMO backup, as described in “The send command” on page 211. The Oracle backup and recovery documentation provides more details on RMAN backups and restores and Oracle product features. 20 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Scheduled compared to manual backups An NMO backup can be either a scheduled or manual (unscheduled) backup: ◆ A scheduled NMO backup includes the following features: • The backup is initiated by the NetWorker server. • The backup start time depends on the settings in the NetWorker resources. A regular scheduled backup starts at a time specified in the NetWorker Group resource. A probe-based backup (or event-based backup) is a type of scheduled backup that starts when specified conditions are met, as described in “Probe-based backups” on page 23. A proxy backup is only supported by using a scheduled backup, as described in “Proxy backups and restores” on page 24. ◆ A manual NMO backup includes the following features: • The backup is initiated by a user on the NMO host through an Oracle backup utility, which can be RMAN or Oracle Enterprise Manager. • The backup is performed by running the Oracle utility from the operating system command line. For example, a user starts a manual NMO backup by running an RMAN backup script from the command line. Chapter 2, “Software Configuration,” provides details on the configuration of both scheduled and manual backups. Chapter 3, “Backup Procedures,” provides details on scheduled and manual backup procedures. Deduplication backups and restores NMO 5.0 software provides new support for deduplication backups and restores. The NetWorker Module for Oracle release notes provides details on the NetWorker requirements for the support of deduplication operations. Main features of deduplication operations An EMC Avamar® server (on Linux) interacts with the NetWorker server and NMO software during deduplication backups and restores. The Avamar server is configured as a NetWorker deduplication node, and deduplicates the data from various clients, including the NMO clients. (The Avamar server must also be available when a deduplication client resource is created.) The initial backup to a deduplication node (Avamar server) will be a full backup. During subsequent deduplication backups, the Avamar server identifies redundant data blocks on the NMO client host and backs up only the unique blocks (not entire files) that contain changes. Only a single instance of any unique (atomic in Avamar terminology) data block is maintained on the Avamar server. Since data deduplication is performed on the client host, deduplication backups typically require less time, network bandwidth, and storage space than regular NMO backups. Product features 21 Introduction The Avamar client-side binary, nsravtar, is installed on the NMO client with the NetWorker client software. During a deduplication backup, the nsravtar process sends the deduplicated client data to the Avamar server. A deduplication NMO backup uses a hash cache on the client side. The Avamar and NetWorker documentation provides more details about caches in deduplication backups. The following sections describe the processes involved in deduplication backups and restores: ◆ ◆ “Deduplication backup processes” on page 55 “Deduplication restore processes” on page 58 A deduplication backup can be a manual or scheduled backup, including a probe-based backup. The application of browse and retention policies and the selection of media pools is the same for a deduplication backup as for a regular NMO backup. Since only the backup metadata (hash ID) is stored on the NetWorker backup device (generating a very small save set), the device should be configured as an advanced file type device (AFTD). The NetWorker administration guide provides more information. You must configure a scheduled or manual deduplication backup according to “Configuring a deduplication backup” on page 93. “Deduplication backup information in NetWorker indexes” on page 115 describes the backup information stored in the NetWorker indexes, and how to delete the backups. Features not supported with deduplication operations Deduplication operations do not support the following: ◆ ◆ ◆ ◆ Oracle proxy backups or restores. Cluster or RAC backups or restores. Internet Protocol version 6 (IPv6). AES encryption of deduplicated data through the NSR_AES_ENCRYPTION parameter. Checksumming of deduplicated data through the NSR_CHECKSUM parameter. Compression of deduplicated data through the NSR_COMPRESSION parameter. If NSR_AES_ENCRYPTION, NSR_CHECKSUM, or NSR_COMPRESSION is set for a deduplication backup, NMO applies the AES encryption, checksumming, or compression, respectively, to only the metadata that is stored on the NetWorker storage node. ◆ ◆ ◆ Cloning or staging of deduplicated data on the Avamar server. Only the metadata stored on the NetWorker storage node can be cloned or staged. However, deduplicated save sets on the Avamar server can be replicated to another Avamar server that has been configured as a replication node by EMC Professional Services. Avamar documentation and the NetWorker administration guide provide details on replication of deduplication backups. 22 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Probe-based backups NMO 5.0 software provides new support for probe-based backups (also known as event-based backups). A probe-based backup is a type of scheduled backup: ◆ ◆ The NetWorker server starts a regular scheduled backup based on a time interval. The NetWorker server starts a probe-based backup when specified conditions are met. The NetWorker Module for Oracle release notes provides details on the NetWorker requirements for the support of probe-based backups. Probe-based backups are not supported for proxy backups or cluster/RAC environments. Workflow of probe-based backups A probe-based NMO backup starts when both of the following are true: ◆ (Condition 1) The current time is within a specified window of time (the backup window, defined by the probe start time and probe end time in the probe-enabled backup group resource). One of the following conditions is met: • (Condition 2) A specified amount of time has elapsed since the previous probe-based backup. • (Condition 3) One or all of the probes associated with the backup are successful, depending on the probe success criteria specified in the backup configuration. The probe success criteria can be set in the NetWorker Group resource to the value Any or All. ◆ At specified probe intervals, the NetWorker server performs the following: 1. The server checks for condition 1, to determine if the current time is within the backup window. 2. If condition 1 is met, then the server checks for condition 2, to determine if a specified amount of time has elapsed since the last probe-based backup: • If condition 2 is met, then the server starts the probe-based backup. • If condition 2 is not met, then the server checks for condition 3, to determine if one or all of the probes are successful: – If the probe success criteria is set to Any, and any one of the probes is successful, then the server starts the probe-based backup. – If the probe success criteria is set to All, and all of the probes are successful, then the server starts the probe-based backup. Product features 23 Introduction Types of probes There are two different types of probes: ◆ An NMO probe. The NMO probe is implemented through the NMO program nsrnmoprobe. The nsrnmoprobe program returns a successful result (signifying that the condition being checked has been met) when it detects either of the following: • The number of Oracle redo logs generated since the previous probe-based backup exceeds a number known as the change threshold. • A new database incarnation (reset log) has occurred since the previous probe-based backup. ◆ User-defined probes. A user-defined probe checks if any other user-defined condition (other than the number of generated Oracle redo logs) has been met since the previous probe-based backup. (This option requires more advanced configuration.) To implement a user-defined probe, you must create a new script or program that checks for the condition, as described in “Configuring a probe-based backup” on page 97. You must configure the required parameters and NetWorker resources to specify the probe interval, backup window, and any other settings for a probe-based backup. “Configuring a probe-based backup” on page 97 provides details on how to configure a probe-based backup. Proxy backups and restores Proxy backups and restores provide continuous snapshot-based protection and availability of Oracle data on specific types of primary storage. A proxy operation involves both the NMO software and a specific PowerSnap Module. The EMC Information Protection Software Compatibility Guide on the EMC Powerlink® website provides a list of supported PowerSnap Modules. Proxy backups create point-in-time copies or snapshots of Oracle data, store the snapshots on primary storage devices supported by the PowerSnap Modules (for Symmetrix®, CLARiiON®, and so on), and optionally back up the data to secondary storage (such as tape) from the point-in-time copies. Proxy restores are used to restore the Oracle data that is backed up during the proxy backups. Chapter 7, “Proxy Backups and Restores,” provides more information on proxy backup and restore operations. 24 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction VMware support NMO 4.5 provided support for regular backups and restores of an Oracle database installed on a VMware Virtual Machine (VM) on an ESX server. NMO 5.0 extends this support with the support for the following advanced features of a VMware ESX server: ◆ VMotion — The VMotion feature enables migration of virtual machines from one ESX server to another while the servers are on. The migration is seamless to the applications running on the virtual machines, and a user does not experience any disconnection. If a migration occurs during an NMO backup or restore, the backup or restore is not interrupted. VMware documentation provides details on the VM requirements for VMotion. Distributed Resource Scheduler (DRS) — The DRS feature enables dynamic balancing and allocation of resources across multiple ESX servers. Depending on the DRS policies set by the user, the DRS can migrate or recommend that users migrate a virtual machine to a different ESX server by using VMotion. DRS can also start (at boot-up time) a virtual machine on a different ESX server. Since this feature uses VMotion, if a migration occurs during an NMO backup or restore, the backup or restore is not interrupted. ◆ The NetWorker Module for Oracle release notes provides details on the NetWorker requirements for the support of VMware features. Archived redo log backups Archived redo log backups enable recovery of the database to its predisaster state. Without archived redo log backups, the database can be recovered only to the time of the last consistent Oracle backup. In this case, transactions that occurred between the time of the last consistent backup and the time of the database corruption will be lost. Archived redo logs can be backed up by using the appropriate option of the RMAN backup command. Ensure that the NMO backups of archived redo logs are enabled. “Backing up all archived logs from each node” on page 147 provides a sample script to back up the archived redo log files in a RAC system. The appropriate Oracle backup and recovery documentation provides more information on setting up and running archived redo log backups. Control file autobackup RMAN performs a control file autobackup after each RMAN backup command if the control file autobackup has been enabled with the configure controlfile autobackup on command. Use this feature to restore the backup entries contained in the control file when the control file is lost and the Recovery Catalog is not available. Specify persistent settings for the control file autobackups with the configure controlfile autobackup command. For example, enable control file autobackup and specify the persistent setting for the format of the control file autobackup name with the following commands: configure controlfile autobackup on configure controlfile autobackup format for device type ’sbt_tape’ to ’/NMO_%f/’ Product features 25 Introduction If the control file autobackup is set to on and the RMAN backup is performed with NMO, the control file autobackup will also be performed with NMO. As a result, one or more channels of device type sbt_tape must be allocated for the restore. Note: Oracle also supports autobackup of the current server parameter file together with control file autobackup. Automatic channel allocation RMAN supports automatic channel allocation. This feature enables the configuration of persistent settings for automatic channels, for use in all RMAN sessions. ! IMPORTANT Manual and automatic channels are mutually exclusive and cannot be mixed in an RMAN session. The format of an automatic channel name of the device type for NMO backups and restores is ORA_SBT_n or ORA_SBT_TAPE_n, where n is the channel number. Do not use this name format for manual channel allocation for NMO. Otherwise, RMAN reports an error. With automatic channel allocation, specification of the send command before the backup or restore command causes the following error: RMAN-06422: no channels found for SEND command You must use the configure channel...parms... command to set the NSR* parameters for automatic channels for an NMO backup. Do not use the send command or option to set the NSR* parameters for automatic channels if you plan to use scheduled backups. Table 10 on page 201 lists all the NSR* parameters and their requirements. Example 1 Using the configure channel command with parms option for automatic channels Automatic channels are configured for NMO backups with the NetWorker server server1.emc.com by typing the following configure channel...parms... command: configure channel device type ’sbt_tape’ parms ’ENV=(NSR_SERVER=server1.emc.com)’ This command sets the default parameters for all the automatic channels. Example 2 Specifying parameter values per automatic channel Specific NSR* parameter values can be set for different channels (for example, a separate setting of parameter NSR_GROUP for each channel) by typing the configure channel n device type...parms... command, where n represents a channel number. An NMO debug file is specified for the second automatic channel by typing the following configure channel command: configure channel 2 device type ’sbt_tape’ parms ’ENV=(NSR_DEBUG_FILE=/db/logs/backup.log)’ Backup and restore optimization If backup optimization is enabled with the configure backup optimization on command, RMAN skips selected files during a backup, based on several criteria. The Oracle backup and recovery documentation provides more details on these criteria. 26 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Note: - To force a backup that would otherwise be skipped due to backup optimization, use the force option in the backup command. - When RMAN skips a backup due to backup optimization, it does not produce an error message. However, RMAN does issue a warning message similar to the following: skipping archive log file... ! IMPORTANT When using Oracle backup optimization with NMO backups and restores, run the crosscheck command regularly to synchronize the Recovery Catalog and NetWorker indexes. This ensures that backups expired by the NetWorker server are also marked as expired in the Recovery Catalog and RMAN does not skip a backup when a referenced backup has already expired in NetWorker. The restore optimization function prevents RMAN from restoring a file if the original file is already in the correct location and contains the expected information. Note: To force a restore that would otherwise be skipped due to restore optimization, use the force option in the restore command. Backup copies ! IMPORTANT If more than one RMAN channel is used for backup copies of an NMO backup, parameter values set with the send command or option are passed by RMAN to the first backup channel only. Due to this send command limitation, NMO does not support the use of RMAN backup copies commands during scheduled backups. NMO supports backup copies with manual backups only. Use the RMAN commands for backup copies only during manual backups when the parameters NSR_SERVER, NSR_DATA_VOLUME_POOL, NSR_DATA_VOLUME_POOL1, NSR_DATA_VOLUME_POOL2, and NSR_DATA_VOLUME_POOL3 are set with the parms option, not with the send command or option. The set duplex command is deprecated (no longer supported by Oracle, but still functional in some Oracle releases). The Oracle documentation provides more details. Despite the fact that RMAN provides different commands for duplexing backups, the rules for duplexing through NMO remain the same as with the set duplex command. Separate NetWorker pools must still be defined for each copy. “The set duplex command” on page 215 provides more information on the set duplex command and setting up NetWorker pools for each copy. Product features 27 Introduction Manual backups can be duplexed (up to four copies) by using one of the following commands: ◆ The configure...backup copies for device type sbt_tape to... command specifies persistent settings for duplexing backups through NMO. For example, specify persistent settings for duplex copies of datafiles and archived redo logs (respectively) in NMO backups with the following types of configure commands: configure datafile backup copies for device type ’sbt_tape’ to 2 configure archivelog backup copies for device type ’sbt_tape’ to 2 ◆ The backup command with the copies option applies to objects within the backup command. The backup...copies setting takes precedence over the persistent settings in the configure...backup copies command. The set backup copies command applies to all backup objects in the same run job. ◆ In the following examples, the parms option is used to configure the channel and set the required parameters. These sample scripts must be invoked manually with RMAN, for example, by using the following command: rman cmdfile script_name Example 3 Using the set backup copies command in the RMAN script The following RMAN script uses the set backup copies command to generate the backup copies. The parameters are set with the parms option, as required. The RMAN script must be invoked for a manual backup, not a scheduled backup: run { set backup copies 4; allocate channel ch1 parms ’ENV=(NSR_SERVER=server_name, NSR_DATA_VOLUME_POOL=nmo1, NSR_DATA_VOLUME_POOL1=nmo2, NSR_DATA_VOLUME_POOL2=nmo3, NSR_DATA_VOLUME_POOL3=nmo4)’; backup format '%d_%U' tag tag_name (tablespace 'SYSTEM' ); release channel ch1; } Example 4 Using automatic channels for backup copies The following configure commands are used to configure RMAN automatic channels. (The configure commands could also be included in the RMAN script.) The configure...backup copies command generates the backup copies. The parameters are set with the parms option, as required. The RMAN script must be invoked for a manual backup, not a scheduled backup: configure default device type to ’sbt_tape’; configure datafile backup copies for device type ’sbt_tape’ to 4; configure channel device type ’sbt_tape’ parms ’ENV=(NSR_SERVER=server_name, NSR_DATA_VOLUME_POOL=nmo1, NSR_DATA_VOLUME_POOL1=nmo2, NSR_DATA_VOLUME_POOL2=nmo3, NSR_DATA_VOLUME_POOL3=nmo4)’; 28 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction The RMAN script invoked for the manual backup is as follows: connect target sys/oracle@test; run { backup format '%d_%U' tag tag_name (tablespace 'SYSTEM'); } Backup of backup sets RMAN supports the backup of backup sets. If Oracle data has been backed up with device type disk, NMO can be used to back up these backup sets from disk to NetWorker volumes. For example, to back up all backup sets from disk to NetWorker volumes in a tape device, use the following command: backup device type sbt backupset all The backup set on disk can also be deleted with the delete input option in the backup device type sbt backupset... command. For example, to back up the backup sets that were created on disk more than a week ago and then remove the backup sets from disk, use the following command: backup device type sbt backupset completed before sysdate-7 delete input Cluster and RAC backups and restores The NMO software supports backups and restores of cluster and Real Application Cluster (RAC) systems for high availability and parallelism. A cluster system typically includes multiple nodes connected by a shared SCSI bus to which common storage is attached. Cluster services such as disk services can be defined and assigned their own IP addresses and names (virtual hosts). The services and their associated storage can migrate for failover between the physical nodes in the cluster. After a cluster service is configured as a NetWorker client, NMO can be used with NetWorker server software to back up and restore an Oracle database associated with the service, independent of the actual node that provides the service. A RAC system enables multiple Oracle instances across multiples nodes to access the same Oracle database at the same time. Oracle RAC is based on a cluster software infrastructure that provides concurrent access to the same storage and the same set of datafiles from all nodes in the cluster. All the database files reside on cluster-aware shared disks. After RAC and the associated cluster system are properly configured, NMO enables Oracle backups on either a single node or several nodes of the RAC system. A parallel Oracle backup uses Oracle instances running in parallel on multiple nodes of the cluster. NMO software supports restores of the Oracle data to any physical node in the cluster, regardless of which physical node originally performed the backup. Chapter 6, “Cluster and RAC Systems,” provides more information on cluster and RAC systems and how to configure the systems for Oracle backup and restore operations that use the NMO software. Product features 29 Introduction Configuration wizards NMO 5.0 software supports new backup and recovery configuration wizards that are integrated with the NetWorker Management Console (NMC). The configuration wizards used in NMO release 4.5 or earlier are replaced by the NMC-based wizards in NMO release 5.0. Configuration wizard plug-in components are installed with the NMO software on the NMO client host. NMC loads the NMO wizard plug-in at run time. You can run the NMO wizards from the NetWorker Console Administration window, which you can start on any supported host by using a web browser session and specifying the Console server URL. The NetWorker Module for Oracle release notes provides details on the NetWorker requirements for the support of the NMC-based configuration wizards. Main features of the wizards The configuration wizards can be used to configure the following for an NMO client: ◆ Scheduled Oracle backups (either typical or customized). “Configuring a backup with the NMC wizard” on page 72 provides details on using the backup configuration wizard. ◆ ◆ RMAN scripts for Oracle data restores to the original host. RMAN scripts for Oracle database duplication to either a local or remote host. “Recovery configuration wizard” on page 118 provides details on the recovery configuration wizard. The configuration wizards support NetWorker servers and clients in a stand-alone or cluster environment. The new wizards provide improved security and ease of management for backup and recovery configurations, compared to the wizards from NMO release 4.5 or earlier. Features of the backup configuration wizard The backup configuration wizard can perform the following: ◆ ◆ Configure a new NetWorker Client resource for an NMO backup. Configure a new or use an existing NetWorker Group resource for the backup Client resource. Configure new or use existing browse and retention policies for the backup Client resource. Optionally save a copy of the configuration settings from the Client resource to a nsrnmo script or RMAN script. Modify a backup configuration that was created with the NMC-based NMO configuration wizard. Modify a backup configuration that was created either with the wizard from NMO release 4.5 or earlier, or with the legacy method, but only after the configuration has been migrated according to “Migration of configurations for the wizard” on page 32. ◆ ◆ ◆ ◆ 30 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Note: NMO 5.0 still supports the legacy method of backup configuration whereby you manually create a nsrnmo script and RMAN script, set any required parameters in the NWORA resource file, and configure the NetWorker resources with NMC (without the wizard). “Configuring a backup with the NMC legacy method” on page 75 describes the legacy configuration method. “Configuring a backup with the NMC wizard” on page 72 provides information on using the wizard to create or modify a backup configuration. Features of the recovery configuration wizard “Features of the recovery configuration wizard” on page 119 provides information on the features of the recovery configuration wizard. Backup configuration storage with the wizard The backup configuration wizard stores the configuration information in a new hidden attribute named Backup Config in the NetWorker Client resource. Do not modify the new attribute manually. If you use the wizard to create a backup configuration, you must use the wizard to modify the configuration. In a backup configuration created with the wizard, the Client resource stores the parameters and RMAN commands (except for sensitive data, such as passwords) that would have been stored in the nsrnmo and RMAN scripts and NWORA resource file in NMO release 4.5 or earlier. Note: The backup configuration wizard stores sensitive data securely by using NetWorker lockbox services. The wizard does not automatically generate a nsrnmo script and RMAN script, but provides an option to save configuration settings to a nsrnmo script or RMAN script on disk. These scripts are meant for reference use only. When you run a backup that was configured through the wizard, the backup does not access any nsrnmo or RMAN script file that the wizard saved to disk. Instead, the backup accesses the configuration information that the wizard stored in the Client resource. The wizards do not store any database connection passwords in any RMAN scripts that are saved to disk. The backup configuration wizard also sets the following values in the Client resource: ◆ Backup Command attribute is set to: nsrnmostart -C [-c virtual_client] ◆ Save Set attribute is set to: RMAN:/_level[/] where: • database_Net_service_name is the the name of the Oracle database to be backed up. • level is the Oracle backup level (full, incr_differential, or incr_cumulative). • name_of_first_tablespace_or_datafile is the name of the first tablespace or datafile in the backup list. This name is included in Save Set attribute only if a partial database (subset of the entire database) is selected for backup. Product features 31 Introduction Features not supported with the wizards The configuration wizards cannot perform the following: ◆ ◆ Configure backups or restores in a RAC environment. Configure proxy backups or restores that require a PowerSnap Module. Proxy backups and restores must be configured without the wizard, as described in Chapter 7, “Proxy Backups and Restores.” ◆ Configure two different database backups in the same Client resource. A separate Client resource must be created for each database to be backed up on the same client host. ◆ Modify a backup configuration that was created either with the wizard from NMO 4.5 or earlier, or with the legacy method, unless the configuration has been migrated according to “Migration of configurations for the wizard” on page 32. Migration of configurations for the wizard The backup configuration wizard stores the scheduled backup configuration in the Client resource by using a configuration storage framework that is incompatible with the configurations created either through the wizard from NMO release 4.5 or earlier, or through a legacy method (without a wizard). The backup configuration wizard can modify only the following types of backup configurations: ◆ ◆ Configurations created with the new wizard. Configurations migrated to the configuration storage framework that is supported by the new wizard. If you have a backup configuration that was created with the wizard from NMO release 4.5 or earlier, or with a legacy configuration method, you must migrate the configuration before you can use the new wizard to modify it. The recommended migration method is to use the nsrnmoadmin command, as described in “Migrating a legacy configuration with the nsrnmoadmin command” on page 69. Note: Migration of a proxy backup configuration is not supported. “Requirements for using the nsrnmoadmin command for migration” on page 70 describes the requirements and limitations of migration with the nsrnmoadmin command. Migration converts legacy configuration files and resources (the nsrnmo script, RMAN script, NWORA resource file, and Client resource) to the configuration storage framework used by the new wizard. Migration with the nsrnmoadmin command does not create a new Client resource; the migration modifies an existing Client resource, such that you can then use the wizard to modify it. The migration process stores the following in a hidden attribute in the Client resource: ◆ Environment variable settings extracted from the nsrnmo script. (Any scripting commands in the nsrnmo script are ignored.) RMAN commands and options extracted from the RMAN script. NSR_BUNDLING, NSR_INCR_EXPIRATION, and NSR_ORACLE_NLS_LANG settings extracted from the NWORA resource file. ◆ ◆ 32 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction The migration process also sets the following values in the Client resource: ◆ Backup Command attribute is set to: nsrnmostart -C [-c virtual_client] ◆ Save Set attribute is set to: RMAN:database_Net_service_name Internationalization (I18N) and localization (L10N) The following sections describe internationalization (I18N) and localization (L10N) features that NMO release 5.0 supports in a non-English locale. I18N features NMO I18N is the capability of the NMO software to operate in a non-English environment or locale without itself generating non-ASCII data. After you set up NMO I18N as described in “Configuring I18N support” on page 67, NMO can process and display non-ASCII data that is passed to it by the operating system, NetWorker software, and Oracle software. The non-ASCII data can include text messages, dates, times, numbers, and so on. The EMC Information Protection Software Compatibility Guide on the Powerlink website provides details on the different languages supported and the operating system, Oracle Server, and NetWorker software requirements for NMO I18N. NMO I18N is supported for the following: ◆ ◆ Regular (nonproxy) backups and restores Proxy backups and restores with a supported PowerSnap Module release, as described in the NetWorker Module for Oracle release notes As a separate NMO feature, NMO localization (L10N) is the capability of NMO to itself generate non-ASCII data and print the data to the user interface. “L10N features” on page 35 provides more information on NMO L10N support. The term internalization is used differently in the NetWorker documentation (as opposed to this NMO documentation). NetWorker server and client documents refer to internationalization as the capability of the NetWorker software to both process non-ASCII data as input and generate non-ASCII data as output in a non-English locale. The extent of the NMO I18N support is dependent on the following: ◆ ◆ ◆ I18N support that is provided by the operating system on the NMO client host. I18N support that is provided by the NetWorker client and server software. National Language Support (NLS) or globalization support that is provided by the Oracle software. For example, if NetWorker software does not support non-ASCII data in a specific NetWorker resource attribute (such as the group name in the Group resource), NMO cannot support non-ASCII data in that resource attribute. The EMC Information Protection Software Compatibility Guide and the NetWorker documentation include more information on the I18N support provided by NetWorker. Product features 33 Introduction When NMO I18N support is set up as described in “Configuring I18N support” on page 67, NMO supports non-ASCII data in the following: ◆ ◆ ◆ ◆ Pathnames of nsrnmo scripts Pathnames of preprocessing and postprocessing scripts Pathnames of RMAN scripts Strings passed as command line options to the nsrnmo(.bat), nsrnmoadmin(.exe), nsrnmoinfo(.exe), and nsroraclecat(.exe) commands Tablespace names and datafile paths The format string of the RMAN backup command (unless the nsrnmoadmin -M or nsrnmoadmin -P command is used for migration of a legacy backup configuration on Windows) The tag string of the RMAN backup command Usernames in the connection strings to the target database and recovery catalog Note: Oracle does not recommend the use of non-ASCII text in the Oracle database usernames. Due to Oracle limitations, ASCII text must be used for the password of the target database. ◆ ◆ ◆ ◆ ◆ Values of the following parameters: • NSR_DEBUG_FILE • NSR_ORACLECAT_LOG_FILE • NSR_RMAN_ARGUMENTS • NSR_SB_DEBUG_FILE Note: Support of non-ASCII values for ORACLE_SID and TNS_ADMIN is dependent on the Oracle software. Support of non-ASCII values for LD_LIBRARY_PATH, LIBPATH, and SHLIB_PATH is dependent on the operating system. ◆ Additional values input in the NMO wizard, including the following: • New or existing names of NetWorker Group resources • Time data based on the time zone of the user ◆ Information displayed on the following screens of the NMO wizard: • Review and Edit the RMAN Script screen • Review and Accept the Client Configuration screen ◆ Content of output files created by the NMO wizard, such as nsrnmo scripts (for example, nsrnmo.bat or nsrnmo.sh file) and RMAN scripts Due to Oracle limitations, ASCII text must be input in the wizard for the following: ◆ ◆ ORACLE_HOME path Net service name of the Oracle target database, recovery catalog, or duplicate database The deduplication backup process, nsravtar, on the NMO client generates messages in English only. 34 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction When NMO I18N support is set up, NMO generates debug messages in English only. NMO generates error messages in the nmo.messages.raw file in a language-independent binary form, readable by the nsr_render_log program only. The nmo.messages.raw file replaces the nmo.messages file used in previous NMO releases. (The log file does not contain Oracle Server or RMAN errors.) The NetWorker administration guide provides information on how to use the nsr_render_log program to read any language-independent binary file, such as nmo.messages.raw. The PowerSnap Module documentation provides details on the PowerSnap options that support non-ASCII values. “Configuring I18N support” on page 67 describes how to set up NMO I18N support. L10N features NMO L10N is the capability of the NMO software to generate non-ASCII character and numeric data based on the locale of the user, and output the data to the user interface. This capability requires the installation of the appropriate NMO language packs in non-English locales. The non-ASCII data generated by NMO is printed to the command line or to specific log files or wizard screens. ◆ When NMO I18N is set up, NMO can process and display non-ASCII data that is passed to it by the operating system, NetWorker software, and Oracle software. When NMO L10N is set up by also installing the required NMO language packs, NMO can also generate non-ASCII data, localized according to the user locale. The non-ASCII data can include text messages, dates, times, and numeric values displayed in the locale-dependent format. ◆ The EMC Information Protection Software Compatibility Guide on the Powerlink website provides details on the different languages supported and the operating system, Oracle Server, and NetWorker software requirements for NMO L10N. NMO L10N is supported for the following: ◆ ◆ Regular backups and restores Proxy backups and restores with a supported PowerSnap Module release, as described in the NetWorker Module for Oracle release notes The extent of the NMO L10N support is limited by the following: ◆ ◆ ◆ L10N support that is provided by the operating system on the NMO client host. L10N support that is provided by the NetWorker client and server software. National Language Support (NLS) or globalization support that is provided by the Oracle software. When NMO L10N support is set up as described in “Configure L10N support” on page 69, NMO generates messages in localized form and displays localized text in the wizard, except for the following: ◆ Comments (lines starting with the symbol #) in the nwora.res file and RMAN scripts All debug messages, including the messages in the configuration wizard debug log files and in the log files specified by NSR_DEBUG_FILE and NSR_SB_DEBUG_FILE Output to the Oracle trace file ◆ ◆ “Configure L10N support” on page 69 describes how to set up NMO L10N support. Product features 35 Introduction Oracle Data Guard support NMO software supports Oracle Data Guard, an Oracle data availability and protection solution that involves the primary database and one or more standby databases over an IP network. As transactions occur in the primary database and redo data is written to the local redo logs, Data Guard automatically transfers this redo data to the standby sites and applies it to the standby databases, synchronizing them with the primary database. RMAN backups of datafiles, archived redo logs, and possibly other files can be offloaded to a physical standby database, and the backups used to recover the primary database or a standby database. RMAN and Data Guard documentation provides information on how to configure and back up a physical standby database, and use the backups to recover the primary or standby database. To configure NMO backups and restores in a Data Guard environment: 1. Follow the instructions in Oracle documentation on how to set up the required RMAN configurations, for example, to use a Recovery Catalog and the DB_UNIQUE_NAME parameter. 2. Install and configure the NMO and NetWorker client software on the primary database host, and on each physical standby database host involved in the backups and restores. 3. Configure a Client resource on the NetWorker server for the primary database host and each physical standby database host involved in the backups and restores. In the Client resource of the primary database host, specify the hostname of the physical standby host in the Remote Access attribute if you set NSR_CLIENT to the primary database hostname in the following step. 4. Create an RMAN script for the primary database and the standby database, setting the same NSR_CLIENT parameter value in both. The NSR_CLIENT value used for a backup should be the same as the NSR_CLIENT value used for the restore of that backup. Setting NSR_CLIENT to the primary hostname might be preferable. Parallelism Parallelism is a feature that enables NMO backup or restore streams of Oracle data from several clients, or many Oracle data streams from one client, at the same time. Different types of configuration settings enable different types of parallelism during NMO operations: ◆ The Parallelism attribute in the NetWorker Server resource specifies the maximum number of backup save streams that the NetWorker software allows to arrive in parallel at the server. The Parallelism attribute (a hidden attribute) in the NetWorker Client resource specifies the maximum number of data streams that the Oracle Server sends in parallel to the NetWorker server or storage node during an NMO backup. ◆ 36 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction ◆ For proxy operations, the PowerSnap parameter settings specify the maximum number of parallel save streams on the proxy client host. Note: The degree of proxy backup or restore parallelism is not controlled by the allocation of multiple channels in the RMAN script. Oracle uses only one of the allocated channels for the proxy backup or restore, unless specific backup options are used. ◆ Configurations on a RAC system enable parallel Oracle backups and restores with the NMO software on multiple nodes of a cluster. Chapter 6, “Cluster and RAC Systems,” provides more details. Policy uniformity If policy uniformity is enabled, NMO automatically enforces the uniformity of the browse and retention policies between all the dependent save sets in a scheduled backup cycle (whether or not save set bundling is enabled). When save set bundling is also enabled, all the save sets in a bundle receive the same browse and retention policies. After NMO performs an incremental scheduled backup, if the browse and retention policies of the save sets in the backup are longer than the policies of preceding dependent save sets in the same backup cycle, the NMO program nsrnmostart changes the policies of all save sets in the cycle to match the longest policy of the new incremental save sets. NMO modifies the policies recorded in the NetWorker media database. As a result, backups cannot expire and become recyclable before other dependent backups from the same backup cycle. The NMO software does not enforce policy uniformity for a manual backup, except when a subsequent scheduled backup is dependent on the manual backup, and then the policies of the manual backup are modified accordingly. Policy uniformity does not depend on whether save sets are stored on separate volumes. For example, if parts of a save set bundle are split onto separate volumes, all the save sets in the bundle still receive the same browse and retention policies. “Configure policy uniformity” on page 92 provides information on how to configure policy uniformity for NMO backups. Restartable backups RMAN can back up files that have not been backed up since a specified time. For example, to continue the backup of a database that was canceled 2 days ago, use the following command: backup device type sbt database not backed up since time ’sysdate-2’ RMAN compares the given time in this command with the completion time of the most recent backup of a datafile to determine if the datafile requires backup. The appropriate Oracle backup and recovery documentation provides more information. The following sections provide more information on how to cancel NMO backups: ◆ ◆ “Cancel a manual backup” on page 107 “Cancel a scheduled backup” on page 111 Product features 37 Introduction Retention policies RMAN provides an Oracle retention policy for backups. An Oracle retention policy is based on the recovery window or redundancy; it is not based on a defined time period, such as a year. Oracle considers a backup obsolete when it is no longer required according to the Oracle retention policy setting. Oracle checks the retention policy of a backup when the report obsolete... or delete obsolete... command is run. NMO supports the Oracle retention policy with some restrictions, since the NetWorker server has its own browse and retention policies to specify how long data is available for recovery. NetWorker browse and retention policies are based on a user-defined time period. Since the Oracle retention policy is independent from that of the NetWorker server, and there is no mechanism to synchronize these policies, the NetWorker and Oracle policies could conflict. Example 5 Expiring a backup A NetWorker server might expire an NMO backup that is not yet obsolete in RMAN, depending on the NetWorker browse and retention policies. Use of NMO cannot guarantee that the NetWorker server will not expire a backup volume until all the RMAN backups on that volume have been removed from the RMAN catalog. To avoid conflicts, perform either of the following: ◆ Disable the Oracle retention policy (and then use only the NetWorker server policy) with the following command: configure retention policy to none If the Recovery Catalog is used, exempt a backup from the retention policy with one of the following commands: change backupset...keep until/forever... backup...keep until/forever... ◆ (If you want to use the Oracle retention policy) Set the NetWorker browse and retention policies to be long enough that backups are kept on the backup volumes until the Oracle retention policy makes them obsolete. Set the NetWorker policies in the NetWorker Client resource for scheduled backups or through the NSR_SAVESET_BROWSE and NSR_SAVESET_RETENTION parameters. “Configure a Client resource with NMC” on page 87 provides more information on how to set NetWorker policies for NMO backups. ! IMPORTANT Run the crosscheck command on the NMO backups before running report obsolete or delete obsolete backups of the device type sbt_tape. This ensures that backups expired by the NetWorker server are flagged as expired in the RMAN catalog. As a result, RMAN can correctly identify which backups are not needed according to the Oracle retention policy. For example: 1. Run the following command to synchronize the RMAN Catalog and NetWorker indexes: crosscheck backup; 2. Run the following command to delete all obsolete backups defined by the current Oracle retention policy: delete obsolete; 38 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Save set bundling If NMO save set bundling is configured, NMO automatically creates a save set bundle for each scheduled backup cycle of an Oracle database object, by grouping all the dependent save sets from the same backup cycle into the save set bundle. A “backup cycle” includes a full backup of the database object and all subsequent incremental backups that are dependent on the full backup. Note: NMO does not support save set bundling for proxy backups. NMO performs save set bundling for regular Oracle backups only. During staging operations with NetWorker server release 7.4 and later, if the staging criteria determine that a particular NMO save set should be staged (migrated) and the save set is part of a save set bundle, the NetWorker server stages the entire save set bundle. If the nsrstage command is used to manually stage one or more save sets from a save set bundle, all the save sets in the bundle are staged. Note: After a staging operation during which all the save sets in a bundle are staged, the resulting available space on the staging device might exceed the lower-water mark specified in the staging policy. The NetWorker administration guide provides details on how to work with staging policies and perform automatic and manual staging operations through the NetWorker server. “NMO scheduled backups and save set bundling” on page 39 describes NMO save set bundling during regular scheduled backups, and how to configure save set bundling. If policy uniformity is configured, NMO automatically enforces the uniformity of browse and retention policies for all the dependent save sets of the same scheduled backup cycle or same save set bundle, which ensures that incremental backups do not persist after the backups they depend on have expired. “Other Oracle features” on page 44 provides more information on how policy uniformity relates to save set bundling. Save set bundling and policy uniformity can be enabled and disabled independently. NMO scheduled backups and save set bundling Use the information in the following sections to plan a save set bundling strategy and enable save set bundling for NMO scheduled backups. Both are performed to prepare for staging operations with NetWorker server 7.4 and later. “Configure save set bundling” on page 91 provides information on how to configure save set bundling for NMO scheduled backups. RMAN backup levels and dependencies An RMAN backup can be either full or incremental: ◆ A full (or stand-alone full) backup includes every used block of the database objects listed in the RMAN backup script (unused blocks might be skipped). This type of backup is created when you do not specify a backup level with the RMAN backup command. A full backup cannot be the parent of a subsequent incremental backup. (Incremental backups cannot be dependent on a stand-alone full backup.) Product features 39 Introduction ◆ An incremental backup is either level 0 or level 1. Incremental backups are created when you specify either incremental level=0 or incremental level=1 with the RMAN backup command. Incremental backups are dependent on preceding incremental backups in the same scheduled backup cycle: • A level 0 incremental is physically identical to a full backup, but is recorded as incremental in the RMAN repository. (A level 0 backup may also be referred to as "full" in other sections of this guide.) • A level 1 incremental can be either of the following: – A differential backup, which contains only the data blocks changed since the most recent incremental backup, whether level 0 or 1. The differential backup is dependent on the preceding level 0 or 1 backup. Incremental backups are differential by default. – A cumulative backup, which contains only the data blocks changed since the most recent level 0 incremental backup. The cumulative backup is dependent on the preceding level 0 backup. RMAN backup sets and NMO save sets NMO save set bundling is performed at the backup set level. An NMO backup (either full or incremental) generates one or more NetWorker save sets. The backup is also composed of one or more RMAN backup sets, with each backup set containing one or more backup pieces. A backup piece contains data blocks from one or more Oracle database files. Each NMO save set corresponds to one backup piece. Note: Backup set and backup piece are Oracle terms. Save set is a NetWorker term. ◆ A control file, parameter file (or spfile), archived log, or datafile cannot span more than one backup set. A control file or parameter file backup cannot span more than one backup piece. An archived log or datafile backup can span more than one backup piece in a backup set. ◆ ◆ It is possible to determine which backup set contains a specific datafile (by querying the v$ views in the Oracle database), but not which backup pieces within the backup set contain the datafile. An Oracle backup set contains either of the following: ◆ The backup of a control file, parameter file, or archived log, which is always performed as a full backup. Note: The backup of a control file, parameter file, or archived log is always placed in its own save set bundle. ◆ Full or incremental backups of one or more Oracle datafiles. A backup set can include both full and incremental backups. For example, a backup set might contain incremental backups of datafiles 1 and 2 and a full backup of datafile 3. Creating NMO save set bundles If save set bundling is enabled, all dependent save sets from the same backup cycle are included in the same save set bundle. Save sets are dependent when two or more save sets are required to restore a database object. (All the NMO save sets from a backup set are placed into the same save set bundle.) 40 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction At the end of a full or level 0 scheduled backup, the NMO software creates a new save set bundle for the backup set from the backup. If subsequent incremental backups are performed that are dependent on the level 0 backup, NMO adds their save sets to the save set bundle from the level 0 backup. A separate save set bundle is created for each scheduled backup cycle of a particular Oracle database object, where a backup cycle consists of a full or level 0 backup of the object and all the subsequent incremental backups that are dependent on the level 0 backup. A save set bundle contains one of the following: ◆ The save sets from a stand-alone full backup, with no other dependent save sets. For example, the save sets from the backup of a control file, parameter file, or archived log (always performed as a full backup) are placed in their own save set bundle. ◆ The save sets from a level 0 backup of an Oracle object and all subsequent incremental backups in the same backup cycle of the object. When an incremental backup occurs and NMO cannot find a preceding dependent backup in any existing bundles, NMO creates a new save set bundle for the incremental backup. Save sets from a manual backup are placed into a save set bundle only if a subsequent scheduled backup is dependent on them. The manual backup save sets are placed in the save set bundle at the same time as the dependent save sets from the scheduled backup. For save set bundling purposes, you can simultaneously run multiple backup cycles that back up different objects from the same database, as long as different files are backed up by the different cycles. For example, one cycle can back up datafiles 1 and 2, while another cycle backs up datafiles 3, 4, and 5 from the same database. The cycles can also be of different lengths. For example, one cycle can last a week, while another concurrent cycle lasts several weeks. Note: The backup copies feature and save set bundling of backup copies are not supported with NMO scheduled backups. Backup copies created during a manual backup are independent of each other, and each copy goes to a different NetWorker volume. If an error occurs during save set bundling, the bundling operation fails but the scheduled backup can finish successfully. Information about the bundling failure is printed to the savegrp output and to the debug file specified by NSR_DEBUG_FILE. How the nsrnmostart program performs save set bundling The NMO program nsrnmostart automatically places save sets into a save set bundle at the end of a scheduled backup, before the nwora.res file is backed up. “Configure save set bundling” on page 91 provides information on the nwora.res file. To perform save set bundling, the nsrnmostart program connects to the Oracle database by attempting to use the login and password from the RMAN script. If a login and password are not available from the script, the program uses the ORACLE_SID value from the nsrnmo script to search the nwora.res file for the NSR_ORACLE_CONNECT_FILE parameter, and uses the connection strings from the specified connection file. “Configure save set bundling” on page 91 provides more details on the requirements of save set bundling. Product features 41 Introduction After connecting to the Oracle database, the nsrnmostart program obtains all the required information about the backups from the Oracle control file (by querying the v$backup_set, v$backup_piece, and v$backup_datafile tables). The control file can store only a limited number of backup entries. When the maximum number of entries is exceeded, old entries in the control file are overwritten by new ones. Save set bundling is successful only if information in the control file about backed-up save sets has not been overwritten. The Oracle documentation provides information about proper maintenance of the control file and how much backup information the control file can store. The nsrnmostart program creates a save set bundle for each full or incremental level 0 backup. The program adds the save sets from subsequent incremental backups to the bundles of the full or level 0 backups they are dependent on. The name that the nsrnmostart program assigns to a save set bundle is a number corresponding to the save time of the oldest save set in the bundle. NMO provides the NetWorker server with the list of save sets contained in each save set bundle. After a scheduled backup, the NetWorker server stores the save set bundle name and the list of save sets it contains in the media database. You can view the bundle information by using the mminfo command, as described in “Save set bundling information in the media database” on page 43. Example 6 Save set bundling for a one-week scheduled backup cycle of a tablespace A one-week scheduled backup cycle of a tablespace includes a level 0 backup of the tablespace on Sunday and a level 1 backup every other day of the week. The save set bundle for the cycle is created during the Sunday backup, and save sets from each level 1 backup are added into the same bundle. The complete bundle contains the save sets from the seven daily backups of the tablespace. A new bundle is created for the next backup cycle during the following week. NetWorker staging restrictions When planning the strategy for NMO save set bundling, consider the following NetWorker staging restrictions: ◆ NetWorker cannot simultaneously stage all the save sets from a save set bundle if some of the save sets were backed up to separate volumes. NetWorker simultaneously stages save sets only if they are located on the same staging volume. Example 8 on page 43 provides more information. To ensure the proper staging of all the save sets from a save set bundle, do not split the backup between different staging volumes. If required, split the backup into different backup cycles, with each cycle going to a separate volume. ◆ NetWorker staging policies must not cause the save sets of an NMO backup cycle to be staged before the cycle is complete. For example, if a one-week NMO cycle starts on Sunday, the staging policy must not cause the partially complete save set bundle to be staged before the final backup of the cycle occurs on Saturday. To prevent a staging operation from splitting an NMO backup cycle, adjust the NetWorker staging policy accordingly. For example, adjust the policy so that older save sets are staged before new ones, or adjust the high-water and low-water marks. The NetWorker administration guide provides details on how to work with staging policies and perform automatic and manual staging operations through the NetWorker server. 42 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Save set bundling information in the media database The NMO software stores information about each save set bundle in the NetWorker media database. “NetWorker software” on page 47 provides more information about the media database. Query the media database by using the NetWorker command, mminfo, with the appropriate options: ◆ The mminfo -r command can display the name of the bundle associated with a save set. For example, the following command displays a list of all save sets and their bundles: mminfo -a -r "ssid,ssbundle" ◆ The mminfo -q command can display all the save sets in a specific bundle. For example, the following command displays all the save sets in the bundle named 12983479182: mminfo -a -q "ssbundle=12983479182" The NetWorker command reference guide and the UNIX man pages provide more information on the mminfo command and its available options. Examples of save set bundles and staging The following examples illustrate different aspects of save set bundling, and how splitting the save set bundles across volumes can affect staging operations. Example 7 Save set bundle join Two save set bundles are created by separate level 0 backups of files A and B. Then a new backup set is created by a level 1 backup of both files A and B. Since the new backup set is dependent on both of the preceding level 0 backups, NMO combines all three backups into the same save set bundle. If the original file A backup has the oldest backup time, NMO places the new backup set (from the level 1 backup) into the save set bundle of the (level 0) file A backup. NMO then moves the original (level 0) file B backup into the save set bundle with the other two backups. This method of combining existing bundles into a new save set bundle is known as a “save set bundle join.” Example 8 Splitting a save set bundle across volumes In both of the following cases, a save set bundle is split across multiple volumes. The parts of the save set bundle on different volumes must be staged separately by the NetWorker server: ◆ A backup uses multiple channels so the backup set spans multiple volumes. All the save sets belong to the same backup set and save set bundle, but parts of the bundle are stored on different volumes. During staging, only the save sets on the same volume can be staged together. A level 0 backup of file A is performed to volume A. An incremental backup of file A is then performed to volume B. Although both backups are recorded as belonging to the same save set bundle, the save set bundle is split across volumes. During staging, only the save sets on the same volume can be staged together. ◆ Product features 43 Introduction Example 9 Using save set consolidation to re-unite a save set bundle A level 0 backup of file A is performed to volume A. A level 1 backup of file A is then performed to volume B. Save set consolidation is used to merge the save sets from these two backups onto the same volume. Bundle names are preserved when save sets are moved from volume to volume by save set consolidation. The consolidated backup is staged as a single save set bundle. Other Oracle features This section describes supported features of the Oracle Server software. The NMO software supports the Oracle releases on specific platforms, as outlined in the EMC Information Protection Software Compatibility Guide on the Powerlink website. The NetWorker Module for Oracle release notes describes known NMO limitations related to specific Oracle releases. Examples of the Oracle RMAN features that NMO supports are as follows: ◆ ◆ Fast incremental backups that use change tracking files. Proxy backups and restores of archived redo logs. Note: Oracle does not support proxy backups of datafiles or archived redo logs that reside on Oracle Automated Storage. Oracle Automated Storage is also known by the term Oracle Automated Storage Management (ASM). ◆ ◆ ◆ ◆ Channel backup failover and backup piece restore failover. Management of backup duration and throttling. Backups and restores of data residing on Oracle Automated Storage. Flash recovery area and flashback database. The Oracle Recovery Manager documentation provides a complete list of the RMAN features. When using Oracle RMAN features with NMO, consider the following: ◆ A flash recovery area stores and manages files related to the recovery of a particular database. To back up RMAN disk backups, control file autobackups, and archived redo logs from the flash recovery area to NetWorker volumes: a. Allocate or configure one or more channels with the sbt_tape device type. b. Back up the files with one of the following RMAN commands: backup recovery area backup recovery files Note: Whether or not a flash recovery area is enabled, the backup recovery files command can be used to perform the backup. 44 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction For example, the following sequence of RMAN commands can be used to configure an automatic channel for NMO and back up the files from the flash recovery area: configure default device type to ’sbt_tape’; configure channel device type ’sbt_tape’ send ’NSR_ENV=(NSR_SERVER=server1)’; backup recovery files; ◆ If multiple channels are used for an RMAN backup command and one of the channels fails, Oracle fails over to another channel to continue the backup job. For example, if two channels are configured with different NetWorker volume pools and one of the channels fails over to the other channel during a backup, the entire backup goes to the volumes in the pool of that remaining channel. ◆ Before using the backup command with the duration...minimize load option, consider: • The minimize load option might impact the tape streaming since the transfer rate of data sent by RMAN might be slow with this option, depending on the duration value. Note: This is not a concern if you use the NetWorker backup to disk feature. • The minimize load option might cause an NMO scheduled backup to be timed out if RMAN does not send data to the NetWorker Module within the time frame specified in the Inactivity Timeout field of the corresponding NetWorker Group resource. ◆ Starting with release 10.1, RMAN does not print database connection strings (user/password@Netservicename) to the session output. As a result, the parameter NSR_RMAN_OUTPUT is not required (to suppress the connection strings in the log files) for an RMAN scheduled backup. Oracle11g specific features NMO 5.0 supports the following major Oracle11g features: ◆ ◆ ◆ ◆ Data Recovery Advisor Improved integration with Data Guard Archival backup through the RMAN backup...keep command Improved archived redo log management through the configure archivelog deletion policy command Recovery catalog enhancements, such as virtual private catalogs and the import and merging of recovery catalogs Multisection or intrafile backup and validation, with the backup of a single large datafile over multiple channels Improved block media recovery, with the blockrecover command being replaced by the recover...block command Configurable backup compression through the configure compression algorithm to command Block change tracking support in Data Guard ◆ ◆ ◆ ◆ ◆ Product features 45 Introduction ◆ ◆ Backup of read-only transportable tablespaces Oracle Enterprise Manager enhancements, with new interfaces for the Data Recovery Advisor Oracle Globalization Support enhancements ◆ To enable NMO support of two of the Oracle11g features, Data Recovery Advisor and archival backup, you must perform the additional configuration procedures described in “Data Recovery Advisor” on page 46 and “Archival backup feature” on page 46. The appropriate Oracle documentation provides more information on the Oracle11g features. Data Recovery Advisor The Oracle Data Recovery Advisor is a new tool in Oracle11g. Integrated with RMAN and Oracle Enterprise Manager (OEM), the tool enables a DBA to diagnose and repair database failures. Before you can use the Data Recovery Advisor to invoke an RMAN restore script that involves NMO to repair a database failure, automatic channels must be configured to specify at least the mandatory parameters NSR_SERVER and NSR_CLIENT. Note: The NSR_SERVER and NSR_CLIENT parameters are the minimum parameters required to perform a restore. Other NMO parameters may also be specified for the automatic channel configuration. To enable the use of Data Recovery Advisor with Oracle11g and NMO: ◆ If automatic channels have not been configured for NMO backups, use the following commands to ensure the basic automatic channel configuration: configure channel device type ’sbt_tape’ parms ’ENV=(NSR_SERVER=NetWorker_server_name, NSR_CLIENT=NMO_client_name)’; configure channel device type 'sbt_tape' parallelism number_of_restore_channels; ◆ If automatic channels are already configured for NMO backups, no additional configuration steps are required. Archival backup feature With Oracle11g, the RMAN backup...keep forever command enables the creation of an archival backup that is exempt from Oracle backup retention policies (but not automatically exempt from NetWorker retention policies). The archival backup is all-inclusive because every file required to restore a database is backed up to a single disk or tape location. To enable the use of the RMAN backup...keep forever command with NMO: 1. Configure an Archive type Pool resource through the NetWorker server. 2. Specify that the backup data must go to the Archive pool by performing one of the following: • Set the pool selection criteria accordingly on the NetWorker server. • Set the NSR_DATA_VOLUME_POOL parameter in the RMAN backup script. 46 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction 3. Set the parameter value NSR_SAVESET_RETENTION=forever through the send command in the RMAN backup script. Note: Ensure that the NSR_RETENTION_DISABLED option is not set in the RMAN backup script used with NMO. The NetWorker administration guide provides more information on how to configure resources and specify pool selection criteria through the NetWorker server. Software used in the NMO environment The following sections describe the different software components involved in the NMO environment. NetWorker software The NetWorker software comprises a high-capacity, easy-to-use data storage management solution that protects and helps manage data across an entire network. The NetWorker software simplifies the storage management process and reduces the administrative burden by automating and centralizing data storage operations. The NetWorker software enables a user to: ◆ ◆ Perform automated backups during nonpeak hours Administer, configure, monitor, and control NetWorker functions from any computer on a network Centralize and automate data management operations Increase backup performance by simultaneously sending more than one save stream to a single device Optimize performance by using parallel save streams to multiple backup devices or storage nodes ◆ ◆ ◆ NetWorker client/server technology uses the network remote procedure call (RPC) protocol to back up data. The NetWorker client software consists of client-side services and user interface programs. The NetWorker server software consists of several server-side services and programs that: ◆ ◆ ◆ Oversee backup and restore processes Maintain client configuration files Maintain an online client file index and online media database, which together comprise the online indexes on the NetWorker server During a backup, the NetWorker server makes an entry in the online client file index and records the location of the data in the online media database. These entries provide recovery information required for all backed-up data. Software used in the NMO environment 47 Introduction After a scheduled backup, the NetWorker server sends a record of the bootstrap file to the default printer. This is a printed record of the dates, locations, and save set ID numbers for the server’s online indexes that are required for restoring data. Keep the bootstrap printout on file as a quick reference in the event of a disaster, such as a disk crash or server failure: ◆ The NetWorker installation guide provides information on how to install NetWorker software. The NetWorker administration guide provides information on how to configure and use NetWorker software. ◆ NMO software NetWorker Module for Oracle (NMO) software is an add-on module for the NetWorker server that enables you to perform the following tasks: ◆ ◆ ◆ ◆ Manual Oracle backups Scheduled Oracle backups Restores of Oracle backup data Automated media management NMO software provides the following features: ◆ Capability to integrate database and file system backups, to relieve the burden of backup from the database administrator while allowing the administrator to retain control of the restore process. Automatic database storage management through automated scheduling, autochanger support, electronic tape labeling, and tracking. Support for backup to a centralized backup server. High performance through support for multiple, concurrent high-speed devices such as digital linear tape (DLT) drives. ◆ ◆ ◆ Together with the NetWorker server, NMO augments the backup and recovery system provided by the Oracle Server and provides a storage management solution that addresses the need for cross-platform support of enterprise applications. Proxy backups and restores of Oracle database files residing on specific types of primary storage devices are supported. These proxy operations are performed by NMO, with the NetWorker server and the appropriate NetWorker PowerSnap Module software. The NetWorker Module for Oracle installation guide provides information on how to install the NMO software. NetWorker PowerSnap Module software The NetWorker PowerSnap Module software works with the NetWorker server and NMO software to perform RMAN proxy backups and restores of Oracle data that resides on specific types of primary storage. Each type of primary storage requires a different type of PowerSnap Module. A proxy backup performed with the PowerSnap Module involves taking a snapshot of the Oracle data. The snapshot resides on the primary storage to ensure high availability of the database and eliminate downtime latency on the Oracle Server host. 48 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction During a proxy backup, the Oracle data can optionally be copied from the snapshot to a NetWorker storage device. The data is copied to the secondary storage by either the Oracle Server host or a proxy client host that is separate from the Oracle Server host. The following sources provide information on how to configure and run proxy backups and restores with the NMO and PowerSnap Module software: ◆ ◆ Chapter 7, “Proxy Backups and Restores” NetWorker PowerSnap Module documentation The EMC Information Protection Software Compatibility Guide on the Powerlink website provides a complete list of supported PowerSnap Modules. Oracle backup and recovery system This section describes the system used for regular Oracle backup and recovery. The NMO and NetWorker server and client software function with the standard Oracle backup and recovery system to produce an efficient Oracle data storage management system. The implementation of an Oracle backup and recovery strategy requires a knowledge of how the NetWorker software works together with the Oracle components. The regular Oracle backup and recovery system consists of the following: ◆ ◆ ◆ ◆ Oracle Server Oracle Recovery Manager (RMAN) Recovery Catalog (optional) Backup Management Tools for Oracle Enterprise Manager (optional) The NetWorker software consists of the following components: ◆ ◆ ◆ NetWorker server NetWorker client NetWorker Module for Oracle Figure 1 on page 50 illustrates the architecture of the regular Oracle backup and recovery system, and shows the functional relationship between the NetWorker and Oracle software components. The NetWorker Module for Oracle media management library (MML) is integrated with the Oracle Server during the NMO installation on the Oracle Server host. The NetWorker Management Console program (used to configure the NetWorker resources) and the Oracle Enterprise Manager (OEM) Backup Manager can be optionally located on a separate platform, referred to as the GUI console. Software used in the NMO environment 49 Introduction GUI console Oracle Server system Oracle database files RMAN NetWorker server OEM Backup Manager Recovery Catalog Oracle Server NetWorker Module for Oracle MML NetWorker client Storage medium NetWorker Management Console NetWorker server GEN-000170 Figure 1 Regular Oracle backup and recovery system Oracle Recovery Manager During the Oracle backup and restore operations, NMO acts as an intermediary between the NetWorker server and Oracle Recovery Manager (RMAN). RMAN is the main Oracle utility for backing up, restoring, and recovering Oracle datafiles, control files, and archived redo log files. It stores information about its operations in the control file of the backed-up database (target database) and, optionally, in the Recovery Catalog on the Oracle Server host. RMAN provides the following features: ◆ ◆ ◆ ◆ ◆ ◆ Online and offline Oracle database backups High performance through parallel backups and restores An intelligent interface to Oracle databases Well-defined backup strategies Checks for corrupt blocks during backups and restores Block-level incremental backups and restores The Oracle Recovery Manager documentation provides more information on RMAN. 50 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Oracle Recovery Catalog The Recovery Catalog is a collection of Oracle database tables that contain structural information about Oracle database backups and restores. The collection includes information about the following types of objects: ◆ ◆ ◆ ◆ ◆ ◆ Backup sets and backup pieces Image copies Proxy copies Archived redo logs Target database schema Stored scripts (user-created sequences of RMAN commands) The Recovery Catalog is maintained by the RMAN utility. This utility uses the catalog information or the database control file to determine how to perform requested backup and restore operations. Store the Recovery Catalog in the dedicated Recovery Catalog database. The Oracle Recovery Manager documentation provides more information on the Recovery Catalog, including the implications of not using it for backups and restores. NMO components Table 1 on page 51 lists the components that are installed on the NMO client host during the NMO software installation. Unless specified otherwise, the files are located in the same directory as the NetWorker client software. Table 1 NMO components (page 1 of 2) Description Plug-in jar files for the NMO backup and recovery configuration wizards. Name on UNIX fdiff.jar nwora.jar nwora_res.jar libcommonssl.7.5.build#.so libnwora.xx nsrnmo Name on Windows fdiff.jar nwora.jar nwora_res.jar In a subdirectory under /usr/lib/nsr/nmo or /opt/networker/lib/nmo on UNIX only. An NMO library that is required for communication with NetWorker. In /usr/lib on UNIX only. The main NMO library (known as Media Management Library in Oracle documentation) that is loaded by the Oracle backup or restore process. nsrnmo.bat The nsrnmo script that contains parameter settings for a particular scheduled backup. The script is only used for a scheduled backup that has been configured through NMC (the legacy configuration method without the wizard). In /etc on UNIX only. A sample template for the nsrnmo script. You should copy and customize this template, and save the original file in /etc. nsrnmoadmin.exe nsrnmodrpostcmd.exe nsrnmoinfo.exe nsrnmoprobe.exe The program that is used either to create resource settings in the NWORA resource file, or to migrate legacy backup configurations to the new format supported by the configuration wizard. A sample postcommand script that can be customized to back up specific files at the end of a scheduled backup, in preparation for disaster recovery. The program that determines the NetWorker volumes required to restore specified Oracle backup pieces from NMO backups. The program that probes for the number of generated Oracle logs as a condition that triggers probe-based backups. nsrnmo.sh nsrnmoadmin nsrnmodrpostcmd nsrnmoinfo nsrnmoprobe NMO components 51 Introduction Table 1 NMO components (page 2 of 2) Description The program that invokes a scheduled backup on the Oracle Server, launching RMAN by passing arguments to the Oracle utility. The program optionally runs precommand and postcommand scripts. Name on UNIX nsrnmostart Name on Windows nsrnmostart.exe nsroraclecat nsroraclecat.exe Not available on Linux Itanium, Solaris AMD64/EM64T, or Windows Itanium (platforms that do not support proxy backups). The program that is used to remove RMAN catalog entries during automatic catalog synchronization for proxy backups. The program that performs operations on behalf of the NMO configuration wizard on the local or remote NMO host. On Windows only. The orasbt.dll file is the main NMO library (known as Media Management Library in Oracle documentation) that is loaded by the Oracle backup or restore thread, and it uses nsrsbtcn.exe to perform any corresponding NetWorker operations. nsrorara nsrorara.exe nsrsbtcn.exe orasbt.dll NMO backup and restore processes This section describes the processes involved in regular backups and restores. To provide storage management services for Oracle Server data, NMO implements the media management interface, also known as the Oracle System Backup to Tape (SBT). This interface comprises a media management library (MML) that is integrated with the Oracle Server during the NMO installation on the Oracle Server host. Oracle loads the NMO MML at run time, and the Oracle Server backup sessions call the NMO MML software routines to back up and restore Oracle data to and from the media controlled by the NetWorker server. A regular Oracle backup can be performed in either of two ways: ◆ By issuing the appropriate commands through the RMAN command line interface. By using the Oracle Enterprise Manager Backup Management Tools, which include an optional graphical user interface to the RMAN utility. ◆ RMAN establishes connections with the target database. Each RMAN channel starts an Oracle Server backup session that performs the backup. During the backup, the following occurs: 1. The Oracle Server backup sessions read the datafile, control file, or archived redo log being backed up, and then write it to the NetWorker server through the MML. 2. The NetWorker server stores the Oracle data to the appropriate backup storage device. At the end of the Oracle backup, the NetWorker server updates the online client and media indexes with information about the backup media used and the Oracle data it contains. 52 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction Regular scheduled backup processes Note: “Deduplication backup processes” on page 55 provides information specifically for a deduplication backup. A scheduled NMO backup is a backup of Oracle data initiated by the NetWorker server. A regular scheduled backup includes the following interactions: 1. At the scheduled backup start time, the main NetWorker service, nsrd, starts the configured group’s backup by invoking the savegrp program. 2. The savegrp program requests that the NetWorker client-side service, nsrexecd, run the savefs program (mainly used for file system backups; it has no usage for Oracle backups). 3. The savefs program sends back information to the savegrp program. 4. The savegrp program contacts the nsrexecd service to start the backup. 5. For each client in the backup group and each of the client’s save sets, the following sequence of events occurs: a. The nsrexecd service starts a specific process, depending on how the backup was configured: – If the backup was configured through the legacy method (without the wizard), nsexecd starts the nsrnmo script, which then sets the required parameters and invokes the NMO program, nsrnmostart. – If the backup was configured through the new configuration wizard, nsexecd starts the nsrnmostart program directly. b. The nsrnmostart program starts the RMAN utility to run the required RMAN backup script. c. From this point on, the scheduled Oracle backup sessions follow the same steps as described in “Regular manual backup processes” on page 54. Note: At the end of a scheduled Oracle backup, the savegrp program also automatically backs up the NetWorker server bootstrap and the Oracle client file indexes. The bootstrap and client indexes are not automatically backed up at the end of a manual NMO backup. Figure 2 on page 54 shows how the Oracle Server, NetWorker server, and NMO processes interact during a regular scheduled NMO backup that was configured through the legacy method (without the wizard). NMO backup and restore processes 53 Introduction In a scheduled backup configured through the wizard, the nsrnmo process is removed from the picture, and the nsrexecd and nsrnmostart processes interact directly with each other. Oracle Server (NetWorker client) Backup pieces NetWorker server Storage medium Client file index Media database Oracle process (channel) NetWorker Module for Oracle MML rman tracking information nsrindexd nsrmmdbd NetWorker Module elements data nsrmmd interprocess communication savefs nsrnmostart nsrnmo nsrexecd GEN-001110 savegrp nsrd Figure 2 Regular scheduled NMO backup Regular manual backup processes Note: “Deduplication backup processes” on page 55 provides information specifically for a deduplication backup. A manual NMO backup is a user-initiated backup through an Oracle backup utility, RMAN or Oracle Enterprise Manager. NMO considers a backup scheduled through Oracle Enterprise Manager to be a manual backup. When the RMAN utility is invoked for a backup, Oracle Server backup sessions call the NMO media management library (MML) software routines to initiate the backup. A manual NMO backup includes the following interactions: 1. The Oracle Server backup session that loads the NMO MML (one such backup session for each allocated channel) contacts the nsrexecd service to obtain the NetWorker client information. 2. The Oracle Server backup sessions contact the main NetWorker service, nsrd, to obtain the required authorization and the identifier of the nsrmmd process that manages the requested backup device. 54 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction 3. The Oracle Server backup sessions send the backup data to the NetWorker media service, nsrmmd, to store on the appropriate backup volumes. 4. Tracking information is stored in the NetWorker online indexes: • The nsrmmd service records tracking information in the NetWorker media database by using the nsrmmdbd service. • The Oracle backup sessions send tracking information to the NetWorker client file index by using the nsrindexd service. Figure 3 on page 55 shows how the Oracle Server, NetWorker server, and NMO processes interact during a regular manual NMO backup. Oracle Server (NetWorker client) Backup pieces NetWorker server Storage medium Client file index Media database RMAN tracking information nsrindexd data nsrmmd NetWorker Module element nsrmmdbd Oracle process (channel) NetWorker Module for Oracle MML nsrexecd interprocess communication nsrd GEN-000171 Figure 3 Regular manual NMO backup Deduplication backup processes “Deduplication backups and restores” on page 21 describes the features of a deduplication NMO backup. For scheduled deduplication backups, the steps from “Regular scheduled backup processes” on page 53 still apply. A deduplication NMO backup includes the following interactions: 1. The Oracle Server backup session that loads the NMO MML (one such backup session for each allocated channel) contacts the nsrexecd service to obtain the NetWorker client information. 2. Each Oracle Server backup session runs one nsravtar process at any given time. NMO backup and restore processes 55 Introduction 3. The Oracle Server backup session contacts the main NetWorker service, nsrd, to obtain the required authorization and the identifier of the nsrmmd process that manages the requested backup device on the NetWorker server or storage node. 4. The Oracle Server backup session sends the backup data in the NetWorker save set format to the nsravtar process. 5. The nsravtar process applies deduplication logic to the backup data by using information in a local cache or by contacting the Avamar server, and sends the unique data blocks to the Avamar server (NetWorker deduplication node). 6. The nsravtar process sends a hash ID (one hash ID per save set) to the Oracle Server backup session. 7. The Oracle Server backup session sends the hash ID in save set format to the NetWorker media service, nsrmmd, to store on the NetWorker backup device. 8. Tracking information is stored in the NetWorker online indexes: • The nsrmmd service records tracking information in the NetWorker media database by using the nsrmmdbd service. The media database entry contains extended attributes that identify the backup as a deduplication backup, as described in “Deduplication backup information in NetWorker indexes” on page 115. • The Oracle backup session sends tracking information to the NetWorker client file index by using the nsrindexd service. Figure 4 on page 57 shows how the Avamar server, NetWorker, and NMO processes interact during a deduplication NMO backup. In the figure, the thickness of the data arrows indicates the amount of data passed between processes: ◆ All the data being backed up is passed between the Oracle Server backup session and nsravtar process. Hash IDs and new data blocks (never backed up before by the Avamar server) are passed between the nsravtar process and Avamar server. A single hash ID for the entire NMO save set is passed between the Oracle Server backup session and NetWorker storage node. ◆ ◆ 56 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction NetWorker server NetWorker storage node Hash ID NMO client NetWorker deduplication node (Avamar server) NetWorker client / utility node Oracle Server backup session with NMO MML acle Oracle data / hash ID GSAN Node 1 nsravtar Deduplicated data / hash ID GEN-001111 Node 2 Figure 4 Deduplication NMO backup Regular restore processes An NMO restore can be performed in either of two ways: ◆ By issuing the appropriate commands through the RMAN command line interface. Or ◆ By using the Oracle Enterprise Manager Backup Management Tools, which include an optional graphical user interface to the RMAN utility. The RMAN utility starts Oracle Server sessions on the target database. These Oracle Server sessions initiate the restore by calling NMO media management library (MML) software routines. Note: “Deduplication restore processes” on page 58 provides information specifically for a deduplication restore. A regular NMO restore includes the following interactions: 1. The NMO MML translates the object names requested by RMAN into a format that the NetWorker server understands, and forwards the names to the NetWorker service, nsrindexd. 2. The nsrindexd service verifies that the backup pieces exist in the client file index. 3. When the NetWorker server receives a restore request from the client, the main NetWorker service, nsrd, contacts the media service, nsrmmd. NMO backup and restore processes 57 Introduction 4. The nsrmmd service calls the media database service, nsrmmdbd, to determine which media contains the requested save set and issue a mount request. 5. The nsrmmd service reads the appropriate backup volumes and passes the data to the Oracle sessions through the NMO MML. 6. The Oracle Server sessions write the data to the disk. Figure 5 on page 58 shows how the Oracle Server, NetWorker server, and NMO processes interact during a regular NMO restore. Oracle Server (NetWorker client) Backup pieces NetWorker server Storage medium Client file index Media database RMAN tracking information Oracle process (channel) NetWorker Module for Oracle MML nsrindexd nsrmmdbd NetWorker Module element data nsrmmd nsrexecd interprocess communication nsrd GEN-000173 Figure 5 Regular NMO restore Once RMAN has restored the required files from the backup volumes, a database administrator can complete the standard Oracle database recovery. Deduplication restore processes A deduplication NMO restore includes the following interactions: 1. The NMO MML translates the object names requested by RMAN into a format that the NetWorker server understands, and forwards the names to the NetWorker server. 2. The NetWorker server verifies that the backup pieces exist in the NetWorker client file index and media database. 3. When the Oracle Server restore session determines from the media database information that the data exists in a deduplication backup, the Oracle session starts a nsravtar process on the NMO client. 4. When the NetWorker server receives a restore request from the client, the main NetWorker service, nsrd, contacts the media service, nsrmmd. 58 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Introduction 5. The nsrmmd service on the NetWorker server calls the media database service, nsrmmdbd, to determine which media contains the requested save set and issue a mount request. 6. The nsrmmd service reads the appropriate backup volumes and passes the data (hash ID) to the Oracle Server session. 7. The Oracle Server session passes the hash ID to the nsravtar process. 8. The nsravtar process retrieves the data corresponding to the hash ID from either the primary Avamar server or the replication Avamar server, and sends the data to the Oracle Server session. 9. The Oracle Server session writes the data to the disk. NMO backup and restore processes 59 Introduction 60 EMC NetWorker Module for Oracle Release 5.0 Administration Guide 2 Software Configuration This chapter includes the following major sections: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ Configuration roadmap................................................................................................ Verify the Oracle Server configuration....................................................................... Verify the NetWorker resources .................................................................................. Configuring I18N support ........................................................................................... Configure L10N support .............................................................................................. Migrating a legacy configuration with the nsrnmoadmin command ................... Configuring a backup with the NMC wizard........................................................... Configuring a backup with the NMC legacy method ............................................. Configuring a deduplication backup ......................................................................... Configuring a probe-based backup ............................................................................ 62 63 63 67 69 69 72 75 93 97 Software Configuration 61 Software Configuration Configuration roadmap The Oracle Server and NetWorker server must be properly configured before the NetWorker Module for Oracle (NMO) software can be used for backup and restore operations. Before configuring the Oracle Server and NetWorker server, ensure that the NMO software is installed on the Oracle Server host according to the instructions in the NetWorker Module for Oracle installation guide. To perform specific configuration procedures, you can use either of the following through NetWorker Management Console (NMC): ◆ ◆ Client backup configuration wizard for Oracle Legacy configuration method (without the wizard) that uses application-independent screens in NMC To configure a regular scheduled backup, follow the instructions in the following sections that apply to your particular environment: 1. Verify the Oracle Server configuration according to “Verify the Oracle Server configuration” on page 63. 2. Verify the NetWorker resources according to “Verify the NetWorker resources” on page 63. 3. If required, configure internationalization (I18N) support according to “Configuring I18N support” on page 67. 4. If required, configure localization (L10N) support according to “Configure L10N support” on page 69. 5. To use the new backup configuration wizard to modify a legacy configuration that was not created with that wizard, migrate the configuration first according to “Migrating a legacy configuration with the nsrnmoadmin command” on page 69. 6. Complete the backup configuration by using either the wizard or NMC: • “Configuring a backup with the NMC wizard” on page 72 • “Configuring a backup with the NMC legacy method” on page 75 (This section includes details on creation of nsrnmo and RMAN scripts and manual configuration of save set bundling and policy uniformity.) Refer to the following for additional information on configuring a deduplication backup or probe-based backup: ◆ ◆ “Configuring a deduplication backup” on page 93 “Configuring a probe-based backup” on page 97 Chapter 6, “Cluster and RAC Systems,” provides information on configuring any required cluster or Real Application Cluster (RAC) systems. 62 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration Verify the Oracle Server configuration The Oracle Server system must be properly installed and configured before the NetWorker server and NMO software is configured. To set up the Oracle Server system: 1. Install and configure the Oracle Server software components, including RMAN. The appropriate Oracle installation guide provides more information. 2. Set up and configure the target database and Oracle Recovery Catalog. The Oracle Recovery Manager documentation provides more information on the Recovery Catalog. 3. Set up and configure the Oracle networking software, Oracle Net. 4. Register the target database with the Recovery Catalog. The Oracle backup and recovery documentation provides more information. Note: Detailed information on these steps is available from Oracle user documentation and Oracle support services. Oracle support contact information is available at the Oracle website. Verify the NetWorker resources Verify that the required NetWorker resources are configured on the NetWorker server, according to the information in the following sections. NetWorker Server resource After the NetWorker server software is installed, the NetWorker configuration includes a preconfigured Server resource with attribute settings that influence the performance and security of backups. Table 2 on page 63 describes the main NetWorker Server resource attributes. Verify that the attribute settings in the Server resource are valid for the NMO backup environment. Modify the settings as required. Table 2 NetWorker Server resource attributes Attribute Name Parallelism Description Specifies the hostname of the NetWorker server. Specifies the maximum number of backup save streams that the NetWorker software allows to arrive concurrently at the server. The NetWorker server edition determines the maximum parallelism value. When multiple data streams are backed up simultaneously, the efficiency of the storage devices is increased. Specifies users with NetWorker Administrator privileges. The initial default setting of the attribute is root@hostname on UNIX and Administrators@hostname on Windows, where hostname is the NetWorker server hostname. “Specify the required NetWorker privileges” on page 64 provides more information. Specifies the key or pass phrase to use for AES encryption of Oracle data during an NMO backup. The pass phrase is required to restore the Oracle data from the backup. “NSR_AES_ENCRYPTION” on page 201 provides more information. Administrator Datazone pass phrase Verify the Oracle Server configuration 63 Software Configuration The NetWorker server online help and the NetWorker administration guide provide more information on how to configure a NetWorker Server resource and its attributes. Specify the required NetWorker privileges Certain NMO operations require specific NetWorker privileges. The NetWorker privileges are specified through the User Group resource. “NetWorker user group privileges” on page 64 provides more information. One NMO operation that requires special privileges is deletion. NMO attempts to remove an entry from the NetWorker index in the following cases: ◆ ◆ If the RMAN delete command is used. If a running Oracle backup is canceled according to the instructions in one of the following sections: • “Cancel a manual backup” on page 107 • “Cancel a scheduled backup” on page 111 Note: If the Oracle user is not granted the required NetWorker privileges in these cases, NMO fails to remove the backup save set entries from the NetWorker index. However, RMAN might remove the corresponding entries from the RMAN catalog, which would leave the NetWorker index and RMAN catalog unsynchronized. To resynchronize the index and catalog, issue the appropriate NetWorker media management command to manually remove the inconsistent save set entries from the NetWorker index. To enable NMO to remove an entry from the NetWorker index, ensure that the Oracle user has the required NetWorker privileges. Verify that the required user group privileges exist according to “NetWorker user group privileges” on page 64. NetWorker user group privileges The NetWorker server includes an access control feature. This feature allows NetWorker administrators to assign users to NetWorker user groups. Each user group has a specific set of privileges associated with it, as defined in the Privileges attribute of the User Group resource. The NetWorker server is installed with two preconfigured user groups: ◆ Administrators — Members of this group have privileges to perform all NetWorker operations. The root user on UNIX, and members of the Microsoft Windows Administrators group, are always members of this group and cannot be removed from the group. Users — By default, members of this group have privileges to back up and recover local data and monitor NetWorker operations. They cannot view or edit configurations. ◆ Note: The privileges associated with the Users group can be customized to fit the requirements of the NetWorker users in the group. The privileges associated with the Administrators group cannot be changed. By default, the NetWorker server assigns the following privileges to all users: ◆ ◆ ◆ Monitor NetWorker Recover Local Data Backup Local Data 64 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration The default user group configurations are sufficient for RMAN backup, restore, and crosscheck operations that use NMO. If the default user group configurations are changed, ensure that the required privileges are assigned for the operations. Verify that the required user group privileges exist for the NMO operations, as described in Table 3 on page 65. The NetWorker administration guide provides information on how to modify existing privileges. Note: Proxy backups and restores require the same privileges as regular Oracle backups and restores, plus the privileges required by the PowerSnap Module. The NetWorker PowerSnap Module documentation provides more information on the required privileges. Table 3 User group privileges required for NMO operations Operating system user that performs operation Required user group privileges Root user, or a member of the Microsoft Windows Administrators group, on the Oracle Server Oracle user on the Oracle Server Configure NetWorker Recover Local Data, Backup Local Data (These privileges are set by default) Recover Local Data, Backup Local Data (These privileges are set by default) Monitor NetWorker, Backup Local Data (These privileges are set by default) Recover Local Data (This privilege is set by default) Recover Local Data (This privilege is set by default) Operate NetWorker, and all its prerequisite privileges Recover Local Data (This privilege is set by default) Operate NetWorker, and all its prerequisite privileges Operation Migration of a legacy backup configuration with the nsrnmoadmin command Regular manual Oracle backup Regular scheduled Oracle backup Oracle user on the Oracle Server Root user, or a member of the Microsoft Windows Administrators group, on the Oracle Server Regular Oracle restore Oracle user on the Oracle Server RMAN crosscheck Oracle user on the Oracle Server RMAN backup deletion Restore of NWORA resource file backup to the Oracle Server Save set bundling Oracle user on the Oracle Server Root user, or a member of the Microsoft Windows Administrators group, on the Oracle Server Root user, or a member of the Microsoft Windows Administrators group, on the Oracle Server The Oracle user is defined as the following: ◆ On UNIX: • If Net service is used, it is the operating system user that starts the Net service. • If Net service is not used, it is the operating system user that runs RMAN. In the case of a scheduled backup, the operating system user is root on UNIX and system on Microsoft Windows. ◆ On Windows, the operating system user that runs the Oracle service (OracleServiceoracle_sid). ! IMPORTANT If the correct user group privileges are not assigned, an Oracle backup or restore fails with an error message that indicates the required user group privileges. The NetWorker administration guide provides more information on NetWorker user groups and setting user group privileges. Verify the NetWorker resources 65 Software Configuration NetWorker Schedule resource You can set the backup schedule to one of the existing schedules (provided by the NetWorker Schedule resources on the server) for the NMO client by using either backup configuration wizard or the legacy configuration method. A NetWorker Schedule resource specifies the attributes of the backup schedule. The NetWorker administration guide provides more information on the features of a Schedule resource. The NMO software does not honor the NetWorker backup levels (except skip) that are specified in the NetWorker Schedule resource. ! IMPORTANT For scheduled NMO backups, the NetWorker backup levels that appear in the Schedule resource do not determine the NMO backup levels. The level of the NMO backup must be specified as either full or incremental in the RMAN backup script. The backup level is determined by the level in the RMAN script only. You must configure a Schedule resource through the legacy method with NMC, as described in “Configure a Schedule resource with NMC” on page 87. NetWorker Device resources The NetWorker server uses a supported tape or disk storage device to write data during an Oracle backup and to read data during an Oracle restore. The NetWorker server configuration must include a Device resource for each storage device to be used for backups and restores. In addition, each storage device must contain a labeled and mounted volume. Configure the required NetWorker Device resources with the NMC program. The NetWorker administration guide provides more information on storage devices, the NMC program, and how to configure Device resources. The EMC NetWorker Hardware Compatibility Guide on the Powerlink website provides a complete list of the storage devices that the NetWorker server supports. The NetWorker administration guide also provides information on how to label and mount backup volumes in the storage devices, and how to configure any required storage nodes (with attached devices), autochangers, and silos. NetWorker volume pools NetWorker software directs backups to groups of media or backup volumes called pools. A pool is a specific collection of backup volumes that the NetWorker server uses to store, sort, and organize backup data. For example, backups of Oracle data such as tablespaces and archived redo logs can be directed to volumes in specific devices. Each NetWorker volume pool is defined by its Pool resource in the NetWorker server. The attribute settings in the Pool resource act as a filter that the server uses to determine the type of data to write to volumes in the pool. Each volume pool has a Pool Type attribute. Note: With NMO, the only valid pool types are backup and backup clone. 66 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration Each NetWorker volume belongs to either a preconfigured pool or a user-created pool. Each pool has a specific label template associated with it, providing an automated method to identify the media assigned to a pool. NetWorker software uses pools of volumes and label templates to track the data is on each volume. Note: If a customized volume pool is not specified for Oracle backup volumes, the NetWorker server routes data for an Oracle backup to the appropriate volume pool. Configure any required NetWorker Pool resources and corresponding Label Template resources with the NMC program. The NetWorker administration guide and NMC online help provide more information. Setting the NSR_DATA_VOLUME_POOL parameter To send data from a manual or scheduled backup to a specific pool, you can set the NSR_DATA_VOLUME_POOL parameter in the RMAN backup session. Chapter 3, “Backup Procedures,” provides more information on the two types of backups. Note: In the case of proxy backups, the parameter is used to specify the volume pool for live backups only (backups to secondary storage only). The parameter cannot specify the snapshot pool for instant backups. The only way to specify the snapshot pool is by configuring the NetWorker resources, as described in “Configuring the NetWorker Pool resources” on page 169. NSR_DATA_VOLUME_POOL is mandatory if backup copies are generated during a manual backup only. Separate NetWorker pools must be defined for each backup copy. “Backup copies” on page 27 provides more information on how to generate backup copies during a manual backup. Appendix A, “Parameters in an RMAN Session,” provides more information on the NSR_DATA_VOLUME_POOL parameters. Firewall support The NMO software provides firewall support. The ports that the NMO software uses for the firewall depend on the corresponding ports configured for the NetWorker server. To configure the firewall that the NMO software uses, follow the firewall configuration instructions in the NetWorker administration guide for the particular NetWorker server platform. Configuring I18N support “Internationalization (I18N) and localization (L10N)” on page 33 describes the features of NMO internationalization (I18N) support. To configure I18N support: 1. Ensure that you meet the “Requirements for I18N support” on page 68. 2. Follow the configuration steps in “Configure I18N support” on page 68. Configuring I18N support 67 Software Configuration Requirements for I18N support Ensure that all of the following I18N requirements are met: ◆ The NMO client host includes a supported internationalized version of the operating system, properly configured to operate in the non-English locale. The Oracle software provides the required National Language Support (NLS) or Globalization support, and the Oracle database is configured with the required non-ASCII character set. The Oracle Globalization Support documentation provides details. A supported NetWorker release 7.4 or later is installed: • Internationalized NetWorker server software is installed, either on the NMO client or on a remote host. • If the NetWorker server is located on a remote host, internationalized NetWorker client or storage node software is installed on the NMO client. The NetWorker installation guide provides details on installation of the NetWorker software. ◆ ◆ ◆ For I18N support during proxy operations, a supported release of the PowerSnap Module is installed and configured, as described in the NetWorker Module for Oracle release notes. The NetWorker documentation provides details on any other I18N requirements. Configure I18N support Note: Configuration of proxy backups or restores with the NMO wizard is not supported. Wizard references in the following steps do not apply to the configuration of proxy operations. The PowerSnap Module documentation provides details on the PowerSnap options that support non-ASCII values. To configure I18N support on the NMO client host: 1. On UNIX only, log in as the root user, then shut down the NetWorker services, set the environment variable LC_ALL to the appropriate locale, and restart the NetWorker services. For example, in a Japanese locale on UNIX, set LC_ALL as follows: # nsr_shutdown # export LC_ALL=JA_jp.eucJP # /etc/init.d/networker start 2. Set the environment variable NLS_LANG to the character set supported by the operating system and Oracle database, and then restart the Oracle Server. The Oracle Globalization Support documentation provides details on the NLS_LANG variable. For example, to ensure that Oracle properly returns Japanese text in a Japanese locale, set NLS_LANG as follows: export NLS_LANG=JAPANESE_JAPAN.JA16EUC % lsnrctl stop % lsnrctl start % sqlplus /nolog SQL*Plus: Release 10.1.0.2.0 - Production on Thu Apr 26 15:12:03 Copyright (c) 1982, 2004, Oracle. All rights reserved. SQL> connect sys/oracle as sysdba; 68 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration SQL> shutdown; SQL> startup; SQL> quit; 3. If you do not configure a scheduled backup with the configuration wizard, set the NLS_LANG parameter in the nsrnmo script to the same value as the environment variable NLS_LANG. For example, in a Japanese locale, set NLS_LANG in the nsrnmo script as follows: NLS_LANG=JAPANESE_JAPAN.JA16EUC Note: If you configure the scheduled backup with the configuration wizard, you can set NLS_LANG on a wizard screen. The wizard autopopulates the NLS_LANG field if NLS_LANG is set in the NWORA resource file. 4. To enable proxy catalog synchronization, set the NSR_ORACLE_NLS_LANG parameter to the same value as the environment variable NLS_LANG by using the nsrnmoadmin command. For example, in a Japanese locale, set the parameter by typing the following command: nsrnmoadmin -r add NSR_ORACLE_NLS_LANG JAPANESE_JAPAN.JA16EUC “Configuring the NWORA resource file with the nsrnmoadmin program” on page 188 provides details on the nsrnmoadmin command. The command sets the parameter value in the NWORA resource file, which is described in “The NWORA resource file” on page 183. Configure L10N support “L10N features” on page 35 describes the features of NMO localization (L10N) support. Note: L10N support for proxy operations requires PowerSnap Module 2.4 SP2 or later. To configure NMO L10N support, enable the locale by installing the appropriate NMO language pack for the user locale on the NMO client host. Each supported language has its own language pack. The NetWorker Module for Oracle installation guide provides details on how to install a supported NMO language pack on a UNIX or Windows system. Migrating a legacy configuration with the nsrnmoadmin command You can use the nsrnmoadmin command to migrate a scheduled backup configuration that was created with a legacy method (without the configuration wizard in NMO 5.0) to the configuration storage framework that is supported by the new NMO wizard. After the migration, you can use the new wizard to modify the backup configuration. As an alternative to using the nsrnmoadmin command for the migration, you can use the Specify the RMAN Script Template (Optional) screen of the NMO wizard to retrieve an existing configuration from an RMAN script. Configure L10N support 69 Software Configuration To migrate a legacy configuration with the nsrnmoadmin command: 1. Ensure that you meet the “Requirements for using the nsrnmoadmin command for migration” on page 70. 2. Use the proper nsrnmoadmin command and options, according to the “Migration command syntax and options” on page 71. Requirements for using the nsrnmoadmin command for migration Before using the nsrnmoadmin command to migrate a backup configuration, ensure that the appropriate requirements are met: ◆ “Windows 2008 and Windows Vista requirements for the nsrnmoadmin command” on page 189 are met on Windows 2008 or Windows Vista. The required NetWorker releases are installed, as described in the NetWorker Module for Oracle release notes. The nsrnmo script contains the mandatory ORACLE_HOME setting. The RMAN script contains a single valid value for each of the following: • Target database username • Password of the target database user • Net service (instance) name ◆ ◆ ◆ ◆ The RMAN script contains correct syntax for the following commands: • allocate channel • backup • connect • release channel • send ◆ The RMAN script does not contain any of the following commands: • @ • allocate channel for maintenance • configure • proxy Note: Migration of a proxy backup configuration is not supported. ◆ ◆ The RMAN script on Microsoft Windows does not include non-ASCII characters. You have all of the NetWorker privileges needed to query and update the Client resources on a NetWorker server, as described in Table 3 on page 65. The NetWorker documentation provides information on the required user group privileges. If you use the nsrnmoadmin command in interactive mode (without the -Y option), you can provide the names of all the users that will use the wizard to modify the configuration (after it has been migrated): • When you use nsrnmoadmin in interactive mode (without the -Y option), you are prompted by default for the names of all such users in ACL format (user@hostname). If you do not provide the usernames when prompted, you must add the usernames at a later time to the NetWorker Lockbock resource ◆ 70 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration for the client by using NMC to edit the resource. The NetWorker administration guide provides details on editing the Lockbox resource in the section on lockbox password management. • When you use nsrnmoadmin in noninteractive mode (with the -Y option), the migration does not prompt for any input. After the migration, you must add the usernames to the NetWorker Lockbox resource for all the users that will use the wizard to modify the configuration. ! IMPORTANT If you migrate the backup configuration of a cluster virtual client, you must do one of the following to enable scheduled backups of the client: - During the migration, when nsrnmoadmin prompts for names of wizard users to add to the Lockbox resource, specify the name system@physical_hostname (Windows) or root@physical_hostname (UNIX). - After the migration, use NMC to edit the Lockbox resource for the cluster virtual client, and add the name system@physical_hostname (Windows) or root@physical_hostname (UNIX) to the resource. Migration command syntax and options You must type the nsrnmoadmin command for migration on the operating system command line, as one of the following users: ◆ ◆ Root user on UNIX A member of the Microsoft Windows Administrators group The command user must meet the migration requirements listed in Table 3 on page 65. “Windows 2008 and Windows Vista requirements for the nsrnmoadmin command” on page 189 provides details for Windows 2008 and Windows Vista systems. The nsrnmoadmin command syntax and options are as follows: nsrnmoadmin -M -s server_name [-c client_name] [-g group_name] [-N save_set_name] [-Y] nsrnmoadmin -P -s server_name [-c client_name] [-g group_name] [-N save_set_name] The -M and -P options are mutually exclusive. Command options and settings in brackets ([ ]) are optional. Do not include the brackets when typing the command. Migrating a legacy configuration with the nsrnmoadmin command 71 Software Configuration Table 4 on page 72 describes the nsrnmoadmin command options. Table 4 Options of the nsrnmoadmin command for migration Option -M Description Specifies the migrate option. The nsrnmoadmin program performs the following: 1. Queries the NetWorker server resource database to locate all of the Client resources that match the values specified by the -c, -g, -N, and -s options. 2. Migrates each legacy configuration (the nsrnmo script, RMAN script, NWORA resource file, Client resource) to the configuration format that is supported by the new NMO wizard. Note: The nsrnmoadmin program can only migrate a configuration that physically resides on the host where the nsrnmoadmin command is typed. To migrate the Client resources for different physical hosts, you must run the nsrnmoadmin program on each physical host, or write a script to automate the process. -P Specifies the probe option. The nsrnmoadmin program performs a probe to query the NetWorker server resource database and locate all of the Client resources that match the values specified by the -c, -g, -N, and -s options, and prints the results to standard output. The program does not actually migrate any legacy configurations. Note: The nsrnmoadmin program can only probe configurations that physically reside on the host where the nsrnmoadmin command is typed. To probe the Client resources created for different physical hosts, you must run the nsrnmoadmin program on each physical host. -c client_name -g group_name -N save_set_name -s server_name -Y Optional. Specifies the hostname of the NetWorker client to be configured. Typically, this option specifies a virtual client in a cluster. The default value is the hostname of the local physical client. Optional. Specifies the name of the NetWorker group for the query operation. If this option is not specified, then a group name is not included in the criteria for the query of the server resource database. Optional. Specifies the value set in the Save Set attribute of the Client resource. If this option is not specified, then a save set name is not included in the criteria for the query of the server resource database. Mandatory. Specifies the hostname of the NetWorker server that backs up the client being configured. Optional. Specifies non-interactive mode, which causes the nsrnmoadmin program to proceed with a migration without prompting for confirmation. If this option is not specified, the nsrnmoadmin program displays all of the fields to be updated in the Client resource and requests confirmation to proceed with the migration. Configuring a backup with the NMC wizard To configure a backup with the wizard: 1. Review the information in “About the backup configuration wizard” on page 72. 2. Ensure that you meet the “Requirements for using the backup configuration wizard” on page 73. 3. Follow the configuration steps in “Configure a backup with the wizard” on page 73. About the backup configuration wizard NMO release 5.0 includes a new NMC-based backup configuration wizard (also known as Client Backup Configuration in NMC) that is integrated with a supported NMC release 7.5 or later. “Configuration wizards” on page 30 describes the main features of the backup configuration wizard. The wizard can configure the Client, Group, and Policy (browse or retention) resources for a scheduled backup. Other NetWorker resources 72 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration must be configured manually (without the wizard) through NMC, as described in “Configuring a backup with the NMC legacy method” on page 75. The wizard option for configuring a "typical" scheduled backup provides a more simplified workflow that generates predefined values (for the number of backup channels, backup name format, and so on). The wizard help provides details on the predefined settings used for a typical scheduled backup. To use the NMO wizard to modify an existing legacy configuration that was not created with the wizard, you must first migrate the configuration according to “Migrating a legacy configuration with the nsrnmoadmin command” on page 69. The following sources provide more information on the configuration wizard: ◆ ◆ ◆ ◆ NetWorker Module for Oracle installation guide NetWorker administration guide or release notes Descriptive inline text in the wizard Online help in the wizard Requirements for using the backup configuration wizard Before you use the backup configuration wizard, ensure that all of the following requirements are met: ◆ The NMC user that starts the wizard (the wizard user) has the Configure NetWorker privileges on the NetWorker server where the configuration is created. Communication between the NMC server, NetWorker server, and NMO client uses nsrauth authentication. The NetWorker documentation provides any requirements for nsrauth authentication. The required NetWorker releases are installed on the NMC server, NetWorker server, and NMO client hosts, as described in the NetWorker Module for Oracle release notes. ◆ ◆ Configure a backup with the wizard To create or modify a backup configuration with the wizard: 1. Start the NetWorker Management Console software. 2. Open the Administration window: a. In the Console window, click Enterprise. b. In the left pane, select a NetWorker server in the Enterprise list. c. In the right pane, select the application. d. From the Enterprise menu, click Launch Application. The Administration window is launched as a separate application. 3. In the Administration window, click Configuration. 4. In the Configuration window, click Clients. Configuring a backup with the NMC wizard 73 Software Configuration 5. Start the wizard by the appropriate method: • If you are creating a new backup configuration, use one of the following methods: – Select Configuration > Client Backup Configuration > New. – In the left pane under the client name, right-click Clients and select Client Backup Configuration > New. – In the main Clients list, right-click the NMO client and select Client Backup Configuration > New. • If you are modifying an existing backup configuration, right-click the NMO client in the right pane, and select Client Backup Configuration > Modify. 6. On each wizard screen that appears, specify the required options and values for the backup configuration. If you use the wizard to configure a deduplication backup, ensure that the Filesperset field is set to 1 on the Specify the RMAN Options (Part 1 of 2) screen. Each wizard screen includes an online help button that you can click to access descriptions of all the fields and options on the screen: • On all but the last screen, click Next to proceed. • On the last screen, Review and Accept the Client Configuration, click Create or Modify to create or modify the configuration, respectively, and click Finish to exit the wizard. If you choose to save configuration settings to an RMAN script on disk, you can edit the script later and also use the script for a manual NMO backup. The resources required for a manual backup must be configured with the legacy method (without the wizard). ! IMPORTANT When you use the wizard to configure a cluster virtual client, the wizard attempts to perform all of the additional settings required for the cluster environment, including the following: - Creating the required Client resources. - Adding the required ACL entries to the Lockbox resource, for the physical hosts provided in the Remote Access field on the NetWorker Client Properties screen of the wizard. - Setting the NSR_CLIENT parameter. - Adding the -c virtual_clientname option to the Backup Command attribute in the Client resource of the virtual client. In the Client resource of the virtual client, ensure that the Remote Access attribute is set with user@physical_hostname for each of the physical hosts of the cluster; otherwise, the backup might fail. 74 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration Configuring a backup with the NMC legacy method The following sections describe how to configure backups with the legacy method (without the configuration wizard). About backup configuration with the legacy method NMO release 5.0 still supports the legacy method of backup configuration, as used in previous NMO releases. To configure a scheduled backup, you can still manually create an RMAN script and nsrnmo script, set parameters in the NWORA resource file if needed, and configure the NetWorker resources with NMC. As an alternative, you can use the backup configuration wizard to configure a scheduled backup, as described in “Configuring a backup with the NMC wizard” on page 72. However, NetWorker resources other than the Client and Group resource must still be configured manually with NMC. For a manual backup, the NetWorker Client resource must be modified manually through the legacy method, as required. Create RMAN scripts for backups Create an appropriate RMAN script to perform the preferred type of manual or scheduled backup on the Oracle Server host. NSR* parameters in the script must be set with the methods described in “Setting the NSR* parameters” on page 200. The use of the send command is recommended where possible. “The send command” on page 211 provides more information. NSR* parameters cannot be set through other methods, for example, by using the setenv or set command on the operating system command line. Appendix A, “Parameters in an RMAN Session,” provides complete information on the NSR* parameters in the RMAN script or session. RMAN backup scripts can be stored as flat ASCII files. Alternatively, if a Recovery Catalog is used, backup scripts can be stored in the Recovery Catalog database. The appropriate Oracle backup and recovery documentation provides information on storing the backup scripts in the Recovery Catalog database. The following sections provide details on RMAN scripts for manual backups and scheduled backups. RMAN scripts for manual backups If automatic channel allocation and persistent settings are used, the backup command can be run as a stand-alone command. “Automatic channel allocation” on page 26 provides more information. Example 10 RMAN script for a manual backup The following RMAN script is for a manual backup of an entire Oracle database to the volume pool MondayFulls of the (remote) NetWorker server mars.emc.com: run { allocate channel t1 type ’SBT_TAPE’; allocate channel t2 type ’SBT_TAPE’; send ’NSR_ENV=(NSR_SERVER=mars.emc.com, NSR_DATA_VOLUME_POOL=MondayFulls)’; backup full filesperset 4 format ’FULL_%d_%U’ (database); Configuring a backup with the NMC legacy method 75 Software Configuration release channel t1; release channel t2; } To specify a Media Management (in this case, NMO) device, set the type option in the allocate channel command to SBT_TAPE. If a device is allocated by using the allocate channel t1 type disk command (with Oracle correctly configured and NMO uninstalled), backups can be directed to disk files through Oracle’s backup implementation. In the preceding RMAN backup script, the format string FULL_%d_%U specifies the name of each backup piece. This name can be anything, provided that each backup piece has a unique name on the NetWorker server. Substitution variables, such as %d and %U, can be used to guarantee unique names: ◆ ◆ %d specifies the name of the database. %U specifies a unique Oracle system-generated filename. A format string such as FULL or FULL_%d will not generate unique names. Similarly, the format string FULL_%U will not generate unique names for two databases that are being backed up to the same NetWorker server. ! IMPORTANT If a backup piece name is not unique, the Oracle backup fails. During a manual backup, the prefix RMAN: automatically precedes the backup piece name in the NetWorker media database. For example, if the backup piece name specified in the RMAN script is accounts_data_file, the manual backup records the save set name as RMAN:accounts_data_file in the media database. The mminfo command displays the save set name in this form. The following sources provide more information: ◆ The appropriate Oracle backup and recovery documentation provides information on how to write RMAN scripts. The Oracle Enterprise Manager documentation provides information on how to use the Oracle Enterprise Manager Backup Wizard to generate RMAN scripts. Appendix B, “RMAN Commands,” provides important information on RMAN commands. “Regular backup information in NetWorker indexes” on page 114 describes the information stored for a manual backup in the NetWorker indexes. ◆ ◆ ◆ Example 11 RMAN script for AES encryption during an Oracle backup The following RMAN script performs a nonproxy backup of the Oracle database to the NetWorker server mars.emc.com by using 256-bit AES encryption, as specified by the NSR_AES_ENCRYPTION parameter setting: run { allocate channel t1 type ’SBT_TAPE’; send ’NSR_ENV=(NSR_SERVER=mars.emc.com, NSR_AES_ENCRYPTION=TRUE)’; backup full filesperset 4 format ’FULL_%d_%U’ (database); release channel t1; } The AES encryption uses the key or pass phrase that is set in the Datazone pass phrase attribute of the NetWorker Server resource. “NSR_AES_ENCRYPTION” on page 201 provides more information. 76 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration ! IMPORTANT Keep a record of all pass phrases used for 256-bit AES encryption. Be careful when you change the pass phrase on the NetWorker server. If the pass phrase on the server is changed and you cannot remember the pass phrase used for an NMO backup, the encrypted data cannot be recovered. The NetWorker administration guide provides more information on pass phrases. Example 17 on page 122 shows a sample Oracle restore of an AES encrypted backup, with the NSR_ENCRYPTION_PHRASES parameter that specifies the original pass phrase that was used for the backup. RMAN scripts for scheduled backups ! IMPORTANT For scheduled backups (both regular and proxy backups), do not include send as part of the allocate channel command. The send command must be separate. For example, NMO does not support the following for scheduled backups: allocate channel t1 type ’SBT_TAPE’ send ’NSR_ENV=(NSR_SERVER=mars.emc.com)’; The following is the correct form of the commands: allocate channel t1 type ’SBT_TAPE’; send channel t1 ’NSR_ENV=(NSR_SERVER=mars.emc.com)’; With automatic channel allocation, specifying the send command before the backup or restore command causes the following error: RMAN-06422: no channels found for SEND command “Automatic channel allocation” on page 26 provides information on automatic channel allocation. Example 12 RMAN script for a scheduled backup The following RMAN script is for a scheduled backup of an entire Oracle database to the volume pool MondayFulls. The Recovery Catalog is used in this case: connect target target_user/target_passwd@target_Netservicename; connect rcvcat rcvcat_user/rcvcat_passwd@rcvcat_Netservicename; run { set command id to ’xxx’; allocate channel t1 type ’SBT_TAPE’; allocate channel t2 type ’SBT_TAPE’; send ’NSR_ENV=(NSR_DATA_VOLUME_POOL=MondayFulls)’; backup full filesperset 4 format ’FULL_%d_%U’ (database); release channel t1; release channel t2; } If automatic channel allocation and persistent settings are used, a scheduled RMAN backup script must still be created and contain the following commands: ◆ ◆ ◆ connect target connect rcvcat (if using a Recovery Catalog) backup Configuring a backup with the NMC legacy method 77 Software Configuration The command connect target target_user/target_passwd@target_Netservicename is mandatory in each RMAN script for a scheduled backup. This command establishes the proper connection to the target database. Specify the correct values in the connect target command: ◆ ◆ target_user is the user with SYSDBA privileges for the target database. target_passwd is the password of the target_user (for connecting as SYSDBA), specified in the target database’s orapwd file. target_Netservicename is the Net service name of the target database. This name is mandatory in the connect target command. ◆ A password file must be used for the target database. To use the password file, the orapwd utility might need to be used and the REMOTE_LOGIN_PASSWORDFILE parameter set to exclusive in the initoracle_sid.ora file. The appropriate Oracle documentation provides more information. Notes: ◆ Since each scheduled backup RMAN script requires a connect target command, each Oracle instance requires a separate scheduled backup RMAN script. In the connect target command, do not use the value internal for target_user or the value oracle for target_passwd. ◆ The command connect rcvcat rcvcat_user/rcvcat_passwd@rcvcat_Netservicename is mandatory if the Recovery Catalog is used for the scheduled Oracle backup. This command establishes the proper connection to the Recovery Catalog database. Specify the correct values in the connect rcvcat command: ◆ ◆ ◆ rcvcat_user is the owner of the Recovery Catalog database. rcvcat_passwd is the password of the rcvcat_user. rcvcat_Netservicename is the Net service name of the Recovery Catalog database. To enable the scheduled backup to be canceled, the scheduled Oracle backup script must include set command id to ‘xxx’ (where xxx can be any string of characters enclosed in single quotes). “Cancel a scheduled backup” on page 111 provides more information on how to cancel a scheduled backup. The remainder of the scheduled backup script in Example 12 on page 77, starting with the first allocate channel command, is similar to the manual backup script in Example 10 on page 75 except that the NSR_SERVER parameter setting is not included. ! IMPORTANT Do not set the parameters NSR_SERVER or NSR_GROUP in a scheduled RMAN backup script. NMO sets these two parameters to the values specified in the Client resource for the scheduled Oracle backup, and these values cannot be overridden. To have the scheduled backup automatically use a volume pool, the backup group can be specified in the Pool resource. The scheduled backup uses that pool unless the parameter NSR_DATA_VOLUME_POOL is set in the RMAN script. Then that parameter’s setting takes precedence over any pool associated with the scheduled backup group. If NSR_DATA_VOLUME_POOL is set in the RMAN script to a pool different from the one associated with the backup group, the scheduled backup uses the 78 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration NSR_DATA_VOLUME_POOL pool. It is the user’s responsibility to set that parameter correctly in the RMAN script for a scheduled backup. Each scheduled backup RMAN script must be stored as a text file. The database administrator should give minimal permissions to the scheduled backup RMAN script file. This way, unauthorized users cannot see the sensitive user IDs and passwords of the target and Recovery Catalog databases. If a single Oracle instance has multiple RMAN scripts associated with it (for example, to perform tablespace-level or file-level, full or incremental backups, and so on), the database administrator might choose to place the two common connect commands in a single file and invoke those two connect commands in all RMAN scripts by using the @ command. Test RMAN scripts for scheduled backups When you create an RMAN script, test the script before using it for scheduled backups. To test the RMAN script, type one of the following commands: rman cmdfile ’script_name’ send ’”NSR_ENV=(NSR_SERVER=NetWorker_server_name, NSR_GROUP=group_name)”’ rman nocatalog cmdfile ’script_name’ send ’”NSR_ENV=(NSR_SERVER=NetWorker_server_name, NSR_GROUP=group_name)”’ where: ◆ ◆ ◆ script_name is the RMAN script file pathname. NetWorker_server_name is the name of the server that starts the backup. group_name is the name of the scheduled backup group as specified in the Client resource. Customize the nsrnmo script Customize the nsrnmo script on the Oracle Server host by modifying the parameters in the script. The NMO installation on the Oracle Server host stores the following files: ◆ A sample nsrnmo script in the same directory as the NetWorker executables. The sample script filenames are: • nsrnmo on UNIX • nsrnmo.bat on Windows ◆ A template of the script in the /etc/nsrnmo.sh file on UNIX. Do not modify this file. Note: On Windows, save a copy of the original nsrnmo.bat file before modifying it. “Editing the nsrnmo.bat file on Windows 2008 or Windows Vista” on page 80 provides specific requirements for Windows 2008 and Windows Vista systems. Multiple versions of the nsrnmo script can be created (for example, one for each Oracle instance) on the same Oracle Server host. Each version of the script must have a unique name, starting with the letters nsr or save. On Windows, the name must also end in .bat or .cmd. Configuring a backup with the NMC legacy method 79 Software Configuration To create a new version of the nsrnmo script: 1. Copy the sample script file (nsrnmo on UNIX or nsrnmo.bat on Windows) to a file with a different name. 2. Customize the parameters in the new file. For example, you might create the new script file named nsrnmo_prodDB on UNIX or nsrnmo_prodDB.bat on Windows. All versions of the nsrnmo script must be located in the same directory as the NetWorker executables. Do not move the nsrnmo scripts to a different directory. Notes: ◆ A nsrnmo script from a previous NMO release works with NMO release 5.0. However, the nsrnmo script installed with NMO release 5.0 might include new parameter settings not found in the script from the previous release. To facilitate the correct reporting of scheduled backup save sets for a UNIX NMO client within the group details window of the NetWorker Management Console (NMC), specify the following shell within the nsrnmo script on UNIX: • /bin/bash, if it exists on the UNIX client • /bin/ksh, if /bin/bash does not exist on the UNIX client ◆ Editing the nsrnmo.bat file on Windows 2008 or Windows Vista Only a member of the Microsoft Windows Administrators group can edit the nsrnmo.bat file or any file located in the NetWorker_installation_dir\bin directory on Windows. On Windows 2008 or Windows Vista, you must follow these steps to edit the nsrnmo.bat file in the NetWorker_installation_dir\bin directory: 1. Click Start. 2. Right-click Notepad or any other text editor listed as a menu item. 3. Select Run as administrator. 4. Open the NetWorker_installation_dir\bin\nsrnmo.bat file in the text editor. 5. Edit and save the nsrnmo.bat file. The nsrnmo script on Solaris zones On a Solaris system with Solaris zones, a sparse root zone can have shared directories that are mounted from the global zone. Such directories are read-only on the sparse root zone. If NMO is installed on a sparse root zone and /usr is one of the shared directories, the nsrnmo script in /usr/sbin is read-only on the sparse root zone. In this case, the nsrnmo script must be edited on the global zone. If multiple sparse root zones are configured on a physical computer, all of the virtual sparse root zones see the nsrnmo script in /usr/sbin. In this case, each sparse root zone should use a unique script filename, such as nsrnmo1, nsrnmo2, and so on. The Backup Command attribute in the Client resource for each sparse root zone must contain the unique nsrnmo filename for that zone. “Configure a Client resource with NMC” on page 87 provides more information on the Client resource. Parameters in the nsrnmo script The sample nsrnmo script installed with NMO contains parameters that must be customized for a particular scheduled Oracle backup. The parameters in the sample nsrnmo script are all undefined by default. 80 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration The nsrnmo script contains only the parameters required on the particular system where the script is installed. The following parameters appear in the nsrnmo script on specific UNIX systems only: ◆ LD_LIBRARY_PATH appears in the script on: • HP-UX (64-bit Itanium) • Linux • Solaris ◆ ◆ LIBPATH appears in the script on AIX. SHLIB_PATH appears in the script on HP-UX (32-bit and 64-bit PA-RISC). Follow the instructions in the Oracle installation guide to determine which of the parameters (LD_LIBRARY_PATH, LIBPATH, SHLIB_PATH) to set on a particular operating system and to what value. The ORACLE_HOME parameter is mandatory for each scheduled backup, and must be set in the nsrnmo script. The other parameters in the nsrnmo script are optional, and can be left undefined in the script, if preferred. Note: For other parameters to be in effect during a scheduled backup, lines must be added in the nsrnmo script to define and export the parameters. The use of either the UNIX setenv command or Windows set command to set the parameters has no effect. The following sections describe the parameters that can be set in the nsrnmo script for scheduled backups. The comments in the nsrnmo script file provide details on the parameters: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ “ORACLE_HOME” on page 81 “LD_LIBRARY_PATH” on page 82 “LIBPATH” on page 82 “SHLIB_PATH” on page 82 “NSR_RMAN_ARGUMENTS” on page 82 “NSR_SB_DEBUG_FILE” on page 83 “ORACLE_SID” on page 83 “ORACLE_USER” on page 83 “PRECMD” on page 84 “POSTCMD” on page 85 “TNS_ADMIN” on page 86 ORACLE_HOME This parameter is mandatory for each scheduled backup. Set ORACLE_HOME in the nsrnmo script file to the home directory of the Oracle Server installation. The RMAN executable, rman, must be located in the subdirectory bin of $ORACLE_HOME. For example, if the Oracle Server installation is located in the directory /disk3/oracle/app/oracle/product/10.0, ORACLE_HOME must be set in the nsrnmo script as follows: ORACLE_HOME=/disk3/oracle/app/oracle/product/10.0 Configuring a backup with the NMC legacy method 81 Software Configuration LD_LIBRARY_PATH This parameter is optional for a scheduled backup. Set LD_LIBRARY_PATH in the nsrnmo script file to the pathname of the directory that contains the Oracle libraries, typically $ORACLE_HOME/lib or $ORACLE_HOME/lib64. For example, if the Oracle libraries are located in the directory /disk3/oracle/app/oracle/product/10.0/lib, set LD_LIBRARY_PATH in the nsrnmo script as follows: LD_LIBRARY_PATH=/disk3/oracle/app/oracle/product/10.0/lib Uncomment the line “export LD_LIBRARY_PATH” (by removing the # symbol at the start of the line) under the “export_environment variables()” function heading in the nsrnmo script: export_environment_variables() { export ORACLE_HOME export NSR_RMAN_ARGUMENTS : : export LD_LIBRARY_PATH } LIBPATH This parameter is optional for a scheduled backup. It appears in the nsrnmo script on AIX only. Set LIBPATH in the nsrnmo script file to the pathname of the directory that contains the Oracle libraries, typically $ORACLE_HOME/lib. To set LIBPATH in the nsrnmo script, follow the example shown in “LD_LIBRARY_PATH” on page 82. Replace LD_LIBRARY_PATH with LIBPATH. Uncomment the line “export LIBPATH” in the script. SHLIB_PATH This parameter is optional for a scheduled backup. It appears in the nsrnmo script on HP-UX only. Set SHLIB_PATH in the nsrnmo script file to the pathname of the directory that contains the Oracle libraries, typically $ORACLE_HOME/lib. To set SHLIB_PATH in the nsrnmo script, follow the example shown in “LD_LIBRARY_PATH” on page 82. Replace LD_LIBRARY_PATH with SHLIB_PATH. Uncomment the line “export SHLIB_PATH” in the script. NSR_RMAN_ARGUMENTS This parameter is optional for a scheduled backup. Set NSR_RMAN_ARGUMENTS to a double-quoted string that contains any valid combination of options for the RMAN executable, rman. The appropriate Oracle Recovery Manager documentation provides details on the valid options. For example, to append RMAN output to the message log file /nsr/applogs/msglog.log, set NSR_RMAN_ARGUMENTS in the nsrnmo script as follows: NSR_RMAN_ARGUMENTS="msglog ’/nsr/applogs/msglog.log’ append" To append RMAN output to the message log file /nsr/applogs/msglog.log if a Recovery Catalog is not used, set NSR_RMAN_ARGUMENTS in the nsrnmo script as follows: NSR_RMAN_ARGUMENTS="nocatalog msglog ’/nsr/applogs/msglog.log’ append" 82 EMC NetWorker Module for Oracle Release 5.0 Administration Guide Software Configuration NSR_SB_DEBUG_FILE This parameter is optional for a scheduled backup. It is used only for debugging purposes. Enable debugging by setting NSR_SB_DEBUG_FILE to the complete pathname of a file to receive detailed debug information for the scheduled backup. This file will exclude MML-specific debug information, which is directed to NSR_DEBUG_FILE (if set in the RMAN script). Note: If NSR_SB_DEBUG_FILE is undefined (by default), no debug information is generated. If a file with the specified pathname cannot be created, debug information is either directed to the default location or not generated. For example, to send detailed debug information for the scheduled backup to the /usr/logs/schedbkup.log file, set the parameter NSR_SB_DEBUG_FILE in the nsrnmo script as follows: NSR_SB_DEBUG_FILE=/usr/logs/schedbkup.log “NMO error messages” on page 222 provides more information on how the debug information is written if the parameter NSR_SB_DEBUG_FILE is set to an invalid pathname. ORACLE_SID This parameter is required for a scheduled backup in the following cases: ◆ The connect target and connect rcvcat commands for the scheduled backup are stored in a separate file, and the connect commands are invoked in the RMAN script by using the @ command. Save set bundling is enabled for the scheduled backup. A proxy backup is performed with catalog synchronization enabled. Chapter 7, “Proxy Backups and Restores,” provides more information on proxy backups and catalog synchronization. ◆ ◆ Set ORACLE_SID in the nsrnmo script file to the system identifier (SID) value of the Oracle database to be backed up. For example, if catalog synchronization is enabled for proxy backups and the SID of the Oracle database to be backed up is orcl10, ORACLE_SID must be set as follows: ORACLE_SID=orcl10 ORACLE_USER This parameter is optional for a scheduled backup configured through the legacy method (without the wizard) on UNIX only. Enable the scheduled backup for operating system authentication by setting ORACLE_USER to the username of the Oracle operating system user, which is set up to connect to the Oracle database through operating system authentication. Note: Using ORACLE_USER to perform an NMO backup through operating system authentication is not supported for the following: - A scheduled backup configured through the new configuration wizard. - A scheduled backup on Microsoft Windows. - A probe-based backup. - A scheduled proxy backup. Configuring a backup with the NMC legacy method 83 Software Configuration For example, to perform a scheduled NMO backup on UNIX through operating system authentication (the backup must be configured through the legacy method), set ORACLE_USER to the required Oracle operating system username: ORACLE_USER=Oracle_OS_username PRECMD This parameter is optional. Set PRECMD to the complete pathname of a file containing a preprocessing script to be executed before the RMAN backup script. Note: The pathname value of PRECMD must not contain any spaces. For example, instead of setting PRECMD to C:\Program Files\Legato\nsr\precmd.bat, set the parameter to C:\Progra~1\Legato\nsr\precmd.bat. If the pre-command script fails (returns a nonzero value), the scheduled Oracle backup does not proceed (that is, the RMAN script is not executed). ! IMPORTANT The script file must have permissions that allow execution by the root user, as the scheduled Oracle backup is always launched by root. The script should return a zero value when it succeeds and a nonzero value when it fails. The return of a nonzero value will cause the scheduled backup to fail. A sample preprocessing script for UNIX is shown as follows. This script is stored in the file whose complete pathname is specified in the parameter PRECMD in the nsrnmo script. For example, if the script is stored in the /usr/scripts/orashutdown file, set the parameter PRECMD as follows: PRECMD=/usr/scripts/orashutdown This sample script shuts down the Oracle database, presumably for an offline database backup. The su command is required in the script since the nsrnmo script runs as root user: #!/bin/ksh # Define Site Specifics Here TARGET_DATABASE=proddb ERRFILE=/tmp/precmd.log ORACLE_USER=proddb # # Scheduled backup launches as "root" run PRECMD as oracle user su - $ORACLE_USER -c "{ # Shutdown target database and start in maintenace mode export ORACLE_SID=$TARGET_DATABASE svrmgrl