Veritas NetBackup™ for Oracle Administrator's Guide
- Introduction
- Providing feedback on Beta documentation
- 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 virtual names and NetBackup for Oracle
Users of a RAC can typically access the database by a virtual network host name. This access is dependent on the configuration of a RAC and any cluster software on which it is running.
The virtual network host name may be associated with an IP address in the following ways:
With an IP address for a host in the cluster
A virtual IP address for an Oracle database instance running on a host in the cluster
A failover virtual IP address that may move between the hosts in the cluster
Backup operations may use the various virtual network host names, or the network host name of the hosts in the cluster.
To differentiate between the various network names, the following terms and definitions are used:
Host name | The network host name that is associated with a specific host in the cluster. |
VIP name | The network host name that is associated with a virtual IP address specific to an instance in the cluster. |
Failover name | The network host name that is associated with an IP address that is active on a running node. This network host name is the network host name that can perform a backup at this time. |
Warning:
Do not use a single client name if the backup is load balanced across more than one node. In a load-balanced configuration, the node that hosts the IP address to which the client name resolves, generates successful backups. However, the jobs originating from the other nodes fail with status code 54.
Oracle 11g R2 Grid Infrastructure (CRS) includes the Single Client Access Name (SCAN) feature. A single SCAN can resolve to multiple IP addresses each assigned to a different physical node in the cluster.
A SCAN can be used in a NetBackup policy that receives the Application Backup request. However, this abstraction of the client name causes backup and restore jobs to fail with status code 54. Also, the client side fails with status code 6 (backup) or status code 5 (restore).
Accordingly, ensure that the client that appears in the NetBackup Oracle policy is not a SCAN. Also, ensure that any NB_ORA_CLIENT or CLIENT_NAME that the node provides in the backup request is not a SCAN. These names must reliably resolve on both the master server and the media server to an IP address. This IP address allows the server processes to connect to the node from which the backup request originated.