Veritas NetBackup™ for Oracle Administrator's Guide
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Linking Oracle RMAN with NetBackup on UNIX platforms
- Oracle policy configuration
- Preparing for NetBackup for Oracle configuration
- Instance management for an Oracle Intelligent Policy
- About Oracle Intelligent Policies (OIP)
- About script- or template-based Oracle policies
- About adding backup selections to an Oracle policy
- About configuring the run-time environment
- About creating templates and shell scripts
- About creating RMAN scripts manually
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- About NetBackup for Oracle restores
- Redirecting a restore to a different client
- Using NetBackup for Oracle in a Microsoft Windows cluster environment
- Guided Recovery
- 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 configuring Snapshot Client with NetBackup for Oracle
- Restoring NetBackup for Oracle from a snapshot backup
- About NetBackup for Oracle restores of volumes and file systems using snapshot rollback
- About configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- Troubleshooting RMAN backup or restore errors
- Appendix A. Real Application Clusters
- Appendix B. Best practices for protecting Oracle RAC with NetBackup
- 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
- Verifying installation requirements for BLI backups without RMAN
- Creating NetBackup policies for script-based BLI backup
- 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 XML export templates and shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- About redirecting a restore of an XML export archive to a different client
- Troubleshooting XML export or XML import errors
- Appendix G. Register authorized locations
Troubleshooting each stage of the backup or restore
The following explains the sequence of events for an action initiated by RMAN and suggests solutions for the problems that can occur at each point in the sequence:
A backup or restore can be started in any of the following ways:
From an RMAN backup or restore initiated from the operating system prompt such as:
rman target user/pwd[@TNS_alias] \ rcvcat user/pwd[@TNS_alias]\ cmdfile RMAN_script_file_name
Where the RMAN_script_file_name is fully qualified.
Using a template that runs from the NetBackup client interface or from bpdbsbora.
Manually from the administrator interface on the master server.
Automatically by an automatic backup schedule.
If an error occurs now, check the RMAN log.
RMAN verifies its environment and then issues requests to the API.
On Windows, some information, such as the NetBackup version, API versions, and trace file name, is registered with RMAN. An error now is usually due to a problem with client and server communication. Check the messages in the bprd and the bpcd logs for clues.
On UNIX, some information, such as the NetBackup version, API versions, trace file name, and NetBackup signal handlers, is registered with RMAN. An error now is usually due to a problem with client and server communication. Check the messages in the bprdand the bpcd logs for clues. Also verify the bp.conf entries on the client.
RMAN issues a backup or restore request.
The API gathers necessary parameters and sends the backup or restore request to the NetBackup server. The API waits until both the server and client are ready to transfer data before it returns to the request.
The API then sends this information to the master server's bprd process.
To troubleshoot a problem in this part of the first sequence, examine the following file:
If the bprd process failed, check the logs for bprd and bpbrm.
A failure now is frequently due to bad NetBackup server or Oracle policy configuration parameters.
On Windows, try setting the SERVER and NB_ORA_POLICY values in the client environment.
On UNIX, try setting the SERVER and POLICY values in the bp.conf file on the client or by setting environment variables.
For example, the following C Shell setenv commands specify the Oracle policy, schedule, and server for NetBackup to use:
setenv NB_ORA_POLICY policyname setenv NB_ORA_SCHED application_backup_schedule_name setenv NB_ORA_SERV NetBackup_server
RMAN issues read or write requests to the API, which then transfers data to or from the NetBackup server.
A failure here is probably due to NetBackup media, network, or timeout errors.
RMAN tells the API to close the session.
The API waits for the server to complete its necessary actions (for example, it verifies the backup image) and then exits.
An error can originate from either NetBackup or RMAN, as follows:
RMAN aborts if it encounters an error while it reads a data file during the backup (for example, if Oracle blocks are out of sequence). It also aborts if NetBackup sends a bad backup image during the restore.