Veritas NetBackup™ for Oracle Administrator's Guide
- Introduction
- What's new about NetBackup for Oracle
- About NetBackup for Oracle
- NetBackup for Oracle features
- NetBackup for Oracle terminology
- NetBackup for Oracle operation using the Oracle Intelligent Policy
- Logging the RMAN input and output on a client
- NetBackup for Oracle operation using a script- or template-based policy
- About Oracle RMAN
- About the Oracle recovery catalog
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- Verifying the operating system and platform compatibility
- NetBackup server and client requirements
- Requirements for using NetBackup for Oracle in a NetBackup cluster
- About the license for NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Oracle policy configuration
- Preparing for NetBackup for Oracle configuration
- Instance management for an Oracle Intelligent Policy
- About the NetBackup Discovery Service
- Viewing the Oracle database instance repository
- Manually adding an Oracle database instance to the repository
- Registering an Oracle database instance
- About Oracle database instance groups
- Adding an instance to an instance group
- Automatic Registration of an instance group
- About instance actions
- About Oracle Intelligent Policies (OIP)
- Creating an Oracle Intelligent Policy (OIP)
- Oracle database upgrade effect on Oracle Intelligent Policies
- Configuring NetBackup for Oracle automatic backup schedules
- About NetBackup for Oracle schedule properties using Oracle Intelligent Policy
- Oracle Intelligent Policy - Storage and Retention
- About Oracle Intelligent Policy master server behavior
- Instances and Databases tab
- Backup Selections tab
- Oracle tab
- About using a NetBackup appliance share for Oracle backups (Copilot)
- Configuring an OIP using a share on the NetBackup appliance (Copilot)
- About script- or template-based Oracle policies
- Adding a new script- or template-based Oracle policy
- About policy attributes
- About backup schedules, templates, and scripts
- About schedule properties
- Script- or template-based policy - Storage and Retention
- Adding clients to a policy
- About adding backup selections to an Oracle policy
- About configuring the run-time environment
- About creating templates and shell scripts
- Starting the NetBackup Backup, Archive, and Restore interface
- RMAN templates and shell scripts
- Creating RMAN templates using the NetBackup for Oracle RMAN template generation wizard
- Creating an RMAN script from a template
- About creating RMAN scripts manually
- About storing templates
- About storing shell scripts
- Configuring the logon account for the NetBackup Client Service for NetBackup for Oracle
- Testing configuration settings for NetBackup for Oracle
- Performing backups and restores of Oracle
- Overview of using NetBackup for Oracle
- Maintaining the RMAN repository
- Querying the RMAN repository
- About NetBackup for Oracle backups
- Browsing backups using the bplist command
- Managing expired backup images
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Microsoft Windows cluster environment
- Creating an instant recovery point from an Oracle Copilot image
- Deleting an instant recovery point for Oracle Copilot instant recovery
- Cleaning up the Copilot share after point in time restore of database
- Single-step restore to ASM storage from a Copilot recovery point
- About restoring from a data file copy to ASM storage using RMAN
- Guided Recovery
- About OpsCenter Guided Recovery
- Setting up for Guided Recovery cloning
- Guided Recovery cloning pre-operation checks
- Performing a Guided Recovery cloning operation
- Select a Master Server dialog
- Select Source Database panel
- Select Control File Backup panel
- Destination host and login panel
- Destination Parameters panel
- Selection summary panel
- Pre-clone check panel
- Job Details panel
- Guided Recovery post-clone operations
- Troubleshooting Guided Recovery
- NetBackup for Oracle with Snapshot Client
- About NetBackup for Oracle with Snapshot Client
- How NetBackup for Oracle with Snapshot Client works
- About the NetBackup for Oracle backup and restore operations
- Database objects supported by advanced backup methods
- About NetBackup multistreaming
- RMAN multiple channels
- Restoring data files to a new location
- Redirecting a restore to a different client
- Symbolic links and raw data files (UNIX)
- Quick I/O data files (UNIX)
- RMAN incremental backups
- Proxy backup examples
- About configuring Snapshot Client with NetBackup for Oracle
- Restoring NetBackup for Oracle from a snapshot backup
- About configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- Troubleshooting
- About troubleshooting NetBackup for Oracle
- About NetBackup for Oracle troubleshooting steps
- NetBackup debug logs and reports
- Enabling the debug logs manually (Windows)
- Enabling the debug logs manually (UNIX)
- About the NetBackup for Oracle log files
- Setting the debug level on a Windows client
- Setting the debug level on a UNIX client
- About RMAN utility logs
- Troubleshooting RMAN backup or restore errors
- Troubleshooting the UNIX browser interface and wizards
- Troubleshooting NetBackup for Oracle with Snapshot Client
- Minimizing timeout failures on large database restores
- Minimizing the loading and unloading of tapes for database backups
- Delays in backup job transfer and completion
- Appendix A. Real Application Clusters
- Appendix B. Best practices for protecting Oracle RAC with NetBackup
- Oracle RAC with NetBackup best practices
- About using Templates and Oracle Intelligent Policy (OIP) with RAC
- About NetBackup for Oracle operations
- Example RAC configuration: Failover name exists and backup is not load balanced
- Example RAC configuration: Failover name exists and backup is load balanced
- Example RAC configuration: Failover name is not available and backup is not load balanced
- Example RAC configuration: Failover name is not available, and backup is load balanced, one policy with custom script
- Example RAC configuration: Failover name is not available and backup is load balanced, simple script with manual policy failover
- Image catalog configuration for RAC
- Configuring the appliance within a RAC environment
- Appendix C. Deduplication best practices
- Appendix D. Snapshot Client support of SFRAC
- Appendix E. Script-based block-level incremental (BLI) backups without RMAN on UNIX and Linux systems
- About script-based block-level incremental (BLI) backups without RMAN
- About BLI backup and restore operations
- Verifying installation requirements for BLI backups without RMAN
- Creating NetBackup policies for script-based BLI backup
- Number of policies required for BLI backup
- About BLI policy attributes
- About the BLI client list
- Backup selections list for BLI backups
- About schedules for BLI backup policies
- Example Oracle BLI backup policy
- Setting the maximum jobs per client global attribute
- About BLI backup methods
- Creating notify scripts for BLI backups
- Performing backups and restores
- About troubleshooting backup or restore errors
- Appendix F. XML Archiver
- NetBackup for Oracle XML export and XML import
- About the environment variables set by a user in the XML export parameter file
- About XML export templates and shell scripts
- Performing an XML export archive
- Browsing XML export archives using bporaimp parameters
- Browsing XML export archives using bplist
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Additional XML export and import logs
- Appendix G. Register authorized locations
About the bp.conf file on UNIX systems
A NetBackup for Oracle user can create a bp.conf file in the Oracle user's home directory on the NetBackup for Oracle client host. When a NetBackup for Oracle operation is started, the user's bp.conf file is searched before the master configuration file (/usr/openv/netbackup/bp.conf). Any option that is found at the user level overrides the same option's setting at the master level.
Table: Options for the user bp.conf file shows the options that you can set in the user's bp.conf file.
Table: Options for the user bp.conf file
Option | Purpose |
|---|---|
This option specifies the name of the policy to use for the backup. | |
This option specifies the name of the Application Backup type of schedule to use for the backup. | |
This option specifies the name of the Oracle client. This name is especially useful for a redirected restore operation. | |
Use this option to increase the number of seconds that the Oracle client initially waits for a response from the NetBackup server. The default is the greater of 900 or CLIENT_READ_TIMEOUT. | |
Set to NO to disable metadata collection. By default, metadata collection is enabled in NetBackup. Turning off metadata collection prevents NetBackup APIs and the NetBackup web UI from returning backup information about the database. Also, Guided Recovery operations do not function properly with metadata collection disabled. Review Table: Disabling the metadata option for more information about what happens when you disable metadata collection on either the user or the master | |
This option specifies the name of the NetBackup master server. There can only be one SERVER option in the user | |
This option causes NetBackup to include more information in its debug logs. |
The following table describes the effect on Oracle discovery and metadata collection when the ORACLE_METADATA setting changes in either the user or the master bp.conf file.
Table: Disabling the metadata option
User | Master | Result |
|---|---|---|
YES | YES | Oracle discovery is performed and metadata is collected. |
NO | YES | Oracle discovery is performed and metadata is not collected. |
YES | NO | Oracle discovery is not performed and metadata is collected. |
NO | NO | Oracle discovery is not performed and metadata is not collected. |
For more information, see the NetBackup System Administrator's Guide, Volume I.
The following shows example bp.conf entries for an Oracle user:
SERVER=jupiter CLIENT_READ_TIMEOUT=900 VERBOSE=1