NetBackup™ for Oracle Administrator's Guide
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- Verifying the operating system and platform compatibility
- NetBackup server and client requirements for NetBackup for Oracle
- Requirements for using NetBackup for Oracle in a NetBackup cluster
- License for NetBackup for Oracle
- About accurate licensing for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Configuring RBAC for the Oracle administrator
- Managing Oracle instances and databases
- Managing Oracle credentials
- Configuring Oracle policies
- Preparing for NetBackup for Oracle configuration
- 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 primary server behavior
- Instances and databases tab
- Backup Selections tab
- Oracle tab
- Logging the RMAN input and output on a client
- About script-based Oracle policies
- Configuring the logon account for the NetBackup Client Service for NetBackup for Oracle
- Testing configuration settings for NetBackup for Oracle
- Managing Oracle RAC
- 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 Windows Server Failover Cluster (WSFC)
- Oracle cloning
- NetBackup Copilot for Oracle
- About Oracle Copilot
- Configuring an OIP using a share on the NetBackup appliance (Oracle Copilot)
- Creating an instant recovery point from an Oracle Copilot image (NetBackup Appliance share)
- Deleting an instant recovery point for Oracle Copilot instant recovery
- Configuring an OIP using universal shares (Oracle Copilot)
- Managing an instant access mount from an Oracle Copilot universal share image
- Cleaning up the Oracle Copilot share after point in time restore of database
- Single-step restore to ASM storage from an Oracle Copilot recovery point or instant access mount
- About restoring from a data file copy to ASM storage using RMAN
- Oracle Copilot with instant access
- Prerequisites when you configure an instant access Oracle database
- Things to consider before you configure an instant access mount point
- Backing up an Oracle database using Oracle Copilot policy with a universal share
- Configure an instant access mount
- View the livemount details of an instant access mount
- Configuring Auto Image Replication for Oracle instant access backups
- Delete an instant access mount
- NetBackup for Oracle terms
- Frequently asked questions
- 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
- NetBackup Dedupe Direct for Oracle
- About NetBackup Dedupe Direct for Oracle plug-in
- Verifying the operating system and platform compatibility
- Before you install NetBackup Dedupe Direct for Oracle plug-in
- Installing NetBackup Dedupe Direct for Oracle plug-in on the Oracle database server
- Using NetBackup Dedupe Direct for Oracle plug-in
- Configuring the NetBackup Dedupe Direct for Oracle plug-in
- NetBackup Dedupe Direct for Oracle rman.cfg file parameters
- Configuring External Certificate Authority (ECA)
- ECA msdp_app.cfg file parameters
- Configuring Oracle RAC
- Disabling Oracle stream handler
- Performing the RMAN backup directly to MSDP server
- Performing the RMAN restore directly from the MSDP storage server
- Creating an SLP to import the Oracle backups to NetBackup on Flex WORM
- Uninstalling the NetBackup Dedupe Direct for Oracle plug-in
- Other Oracle configuration
- 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 NetBackup for Oracle with Snapshot Client
- Error: Unable to re-create online log
- Minimizing timeout failures on large database restores
- Minimizing the loading and unloading of tapes for database backups
- Enabling the debug logs manually for NetBackup Dedupe Direct for Oracle plug-in
- Appendix A. Deduplication best practices
- Optimizing and deduplicating stream-based and proxy copy Oracle backups
- Oracle stream handler
- Configuring a stream-based Oracle backup
- Example RMAN script for a stream-based backup
- Editing the RMAN script and configuring NetBackup for Oracle for a proxy copy backup
- Example RMAN script for a proxy copy backup
- Appendix B. Snapshot Client support of SFRAC
- Appendix C. 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 D. 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 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 E. Register authorized locations
About bporaexp parameters
This topic describes the available bporaexp (bporaexp64 on some platforms) parameters.
Note the following:
Use the NetBackup parameters NB_ORA_SERV, NB_ORA_CLIENT, NB_ORA_POLICY, and NB_ORA_SCHED to specify the NetBackup runtime configuration. Otherwise, the order of precedence for the runtime configuration variable settings is used.
Some parameters are valid only when you write to a storage unit. Other parameters are valid only when you write to a directory. In the following table, the Target Location column contains either Storage Unit or Directory to indicate whether the parameter in that row applies to writing to a storage unit or to a directory. Parameters that are recognized when you write to a directory are ignored when you write to a storage unit.
Table: bporaexp parameters and default values shows the available bporaexp parameters with their default values.
Table: bporaexp parameters and default values
Parameter | Required? | Default | Description | Target location |
|---|---|---|---|---|
CONSISTENT | N | Specifies if bporaexp uses the SET TRANSACTION READ ONLY statement to ensure that the data from all tables is consistent to a single point in time and does not change during the execution of the bporaexp command. If the default of CONSISTENT=N is used, each table is exported as an independent transaction. | Directory | |
N | no default | Optionally specifies a directory for the output of the bporaexp utility. | Directory | |
HELP | N | Displays a help message with descriptions of bporaexp parameters. Does not export data if HELP=Y. | Directory | |
N | no default | Optionally specifies a keyword phrase that NetBackup associates with the image being created by the archive operation. Values for KEYWORD must be in double quotes. | Storage Unit | |
LOG | no default | Optionally specifies a file name to receive informational and error messages. If so, messages are logged on the log file and not displayed to the terminal display. | Directory | |
NAME | no default | The name of the primary XML schema file. | Directory | |
NB_ORA_SERV | default primary server | Optionally specifies the name of the NetBackup primary server. | Storage Unit | |
NB_ORA_CLIENT | default client | Optionally specifies the name of the NetBackup for Oracle client. | Storage Unit | |
NB_ORA_POLICY | default Oracle policy | Optionally specifies the name of the NetBackup for Oracle policy. | Storage Unit | |
NB_ORA_SCHED | default backup policy schedule | Optionally specifies the name of the backup policy schedule to use. | Storage Unit | |
OWNER | no default | Lists the Oracle schema owners to export. For each owner, the tables, partitions, and views that are owned by that Oracle account are exported by default. The PARTITIONS and VIEWS parameters can be used to exclude partitions and views. | Directory | |
PARTITIONS | Y | Optionally specifies whether or not table partitions are included. Only valid when used with the OWNER parameter. | Directory | |
QUERY | no default | Selects a subset of rows from a set of tables. The value of the query parameter is a string that contains a WHERE clause for a SQL select statement that is applied to all tables and table partitions listed in the TABLES parameter. For example, if TABLES = emp, bonus and QUERY = "where job = 'SALESMAN' and sal < 1600", two SQL statements are run:
Each query that runs refers to a single table at a time in the FROM clause, so it is illegal to have a join in the WHERE clause. | Directory | |
ROW_BUFFER | 1000 | Specifies the size, in rows, of the buffer used to fetch rows. Tables with LONG columns are fetched one row at a time. The maximum value allowed is 32767. | Directory | |
TABLES | no default | Lists the table names, view names, and partition names to export. The USERID must have SELECT privilege on the tables and views. The syntax used is:schema.table: partition name or schema.view name | Directory | |
USERID | no default | Specifies the username/password (and optional connect string) of the user initiating the export. If a connect string is not provided, the ORACLE_SID environment variable is used. | Directory | |
VIEWS | Y | Optionally specifies whether or not views are included. Only valid when used with the OWNER parameter. | Directory |
More Information