NetBackup™ for Oracle Administrator's Guide
- Introduction
- Installing NetBackup for Oracle
- Planning the installation of NetBackup for Oracle
- Verifying the operating system and platform compatibility
- License for NetBackup for Oracle
- NetBackup server and client requirements for NetBackup for Oracle
- Requirements for using NetBackup for Oracle in a NetBackup cluster
- About linking Oracle RMAN with NetBackup for UNIX
- Configuring RBAC for the Oracle administrator
- Managing Oracle discovery and databases
- About Oracle discovery
- Managing Oracle databases
- View and edit Oracle database details
- Associate an RMAN catalog with a database
- Remove an RMAN catalog from a database
- Activate or deactivate a database
- Remove a database or pluggable database
- Manually add a database
- Manually add an Oracle instance
- Edit Oracle instance details
- Copy a RAC instance
- Remove an Oracle instance
- Load balance Oracle RAC instances
- Managing RMAN catalogs
- Manage a Data Guard
- Managing Oracle credentials
- About Oracle credentials
- Oracle credential types in the NetBackup Credential management
- Add a credential for an Oracle database or RMAN catalog
- View the credential name that is applied to an asset
- Edit or delete a named credential
- Register credentials for an Oracle database or RMAN catalog
- Manually validate database credentials
- Configure an Oracle Wallet with RAC within NetBackup
- Configuring Oracle policies
- Preparing for NetBackup for Oracle configuration
- About Oracle Intelligent Policies (OIP)
- Create 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
- Create a Data Guard policy
- Create bpstart_notify and bpend_notify scripts for an Oracle Intelligent Policy (OIP)
- Logging the RMAN input and output on a client
- About script-based Oracle policies
- Adding a new script-based Oracle policy
- About policy attributes
- Schedule properties for Oracle script-based policies
- Script-based policy - Storage and Retention
- Add clients to a policy
- About adding backup selections to an Oracle policy
- About configuring the run-time environment
- About creating 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 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 the 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
- Troubleshooting
- About troubleshooting NetBackup for Oracle
- About NetBackup for Oracle troubleshooting steps
- NetBackup debug logs and reports
- Enabling the debug logs manually (Windows) (NetBackup for Oracle)
- Enabling the debug logs manually (UNIX) (NetBackup for Oracle)
- 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 time-out 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 bporaimp parameters
Use the NetBackup parameters NB_ORA_SERV and NB_ORA_CLIENT to specify the NetBackup runtime configuration. Otherwise, the order of precedence for the runtime configuration variable settings is used.
Some parameters are valid only when writing to a storage unit. Other parameters are valid only when writing to a directory. In the following table, the right-most column contains either "Storage Unit" or "Directory" to indicate whether the parameter in that row is applicable for either writing to a storage unit or to a directory. Parameters that are recognized when writing to a directory are ignored when writing to a storage unit.
Table: bporaimp parameters and default values describes the bporaimp (bporaimp64 on some platforms) parameters and default values.
Table: bporaimp parameters and default values
Parameter | Required? | Default | Description | Target location |
|---|---|---|---|---|
N | no default | Optionally specifies a start date for the archive to be imported. Used with ARCHIVE_DATE_TO to specify a range. If not used, the most recent archive is imported. If the range used results in more than one archive, the most recent from the range is used. The date format is mm/dd/yyyy [hh:mm:ss]. | Storage Unit | |
ARCHIVE_DATE_TO | no default | Optionally specifies an end date for the archive to be imported. Used with ARCHIVE_DATE_FROM to specify a range. If not used, the most recent archive is imported. If the range used results in more than one archive, the most recent from the range is used. The date format is mm/dd/yyyy [hh:mm:ss]. | Storage Unit | |
BFILE_DIRECTORY | no default | Specifies a directory for the output of any BFILE columns being imported. Oracle's CREATE DIRECTORY command can be used to create the DIRECTORY in Oracle, and the name should match the name used in the export file. | Directory | |
COMMIT | N | Specifies whether bporaimp should commit after each array insert. The size of the array is determined by ROW_BUFFER. By default, bporaimp commits only after loading each table, and performs a rollback when an error occurs, before continuing with the next object. | Directory | |
DIRECTORY | no default | Optionally specifies a directory for the input of the bporaimp utility. | Directory | |
FROMUSER | no default | Optionally specifies a comma-separated list of users to import from an archive containing multiple users' tables. If not specified, all of the tables are imported. | Directory | |
HELP | N | Displays a help message with descriptions of bporaimp parameters. | Directory | |
IGNORE_ROWS | N | Specifies whether or not rows should be inserted into a table that is not empty. The default is that the table already exists and that it is empty. If it is not empty, IGNORE_ROWS = N causes an error to be reported, and the table is skipped with no rows inserted. IGNORE_ROWS = Y causes rows to be inserted with errors reported in the log file. If IGNORE_ROWS = Y and an error such as a primary key constraint violation occurs, no data is inserted if COMMIT = N. However, if COMMIT = Y, the array of rows (size determined by ROW_BUFFER) is not inserted, but bporaimp continues to process additional row arrays in the order in which they were exported. To cause all rows that do not violate a primary key constraint to be inserted, set COMMIT = Y, ROW_BUFFER = 1, and IGNORE_ROWS = Y. | Directory | |
KEYWORD | no default | Optionally specifies a keyword phrase for NetBackup to use when searching for archives from which to restore files. | Storage Unit | |
LIST | N | LIST = Y queries the NetBackup catalog and lists the archives available. Does not import the data if LIST = Y. | Storage Unit | |
LOG | no default | Optionally specifies a file name to receive informational and error messages. If this parameter is specified, messages are logged in the log file and not displayed to the terminal display. | Directory | |
NAME | no default | The name of the primary XML schema file. This parameter is required if LIST = N. | 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 | |
RESTORE_SCHEMA_ONLY | N | Used with RESTORE_TO_DIRECTORY to restore the XML schema files only to a directory. | Storage Unit | |
RESTORE_TO_DIRECTORY | no default | Optionally specifies a directory for the output of the bporaimp utility. If used, the XML data is not parsed and inserted into Oracle. | Storage Unit | |
ROW_BUFFER | 1000 | Specifies the size, in rows, of the buffer used to insert rows. Tables with LONG or LOB columns are inserted one row at a time. The maximum value allowed is 32767. | Directory | |
TABLES | no default | Optionally specifies a list of table, view, and partition names to import. If not used, all objects in the archive are imported. The objects must already exist, and the USERID must have INSERT privilege on the objects. The object names cannot be qualified with owner names, and the FROMUSER parameter is used to specify a particular owner. If a partition name is specified, it indicates the exported partition only and the rows are inserted according to the partitioning scheme of the target table. If the export contains partitions, and the import does not specify them, all are inserted. | Directory | |
TOUSER | no default | Optionally specifies a comma-separated list of users to import to that can be used with the FROMUSER parameter to change the table owners. The TOUSER Oracle accounts must already exist, and the USERID must have INSERT privilege on the tables that must also exist. | Directory | |
USERID | no default | Specifies the username/password (and optional connect string) of the user initiating the import. If a connect string is not provided, the ORACLE_SID environment variable is used. | Directory |