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
Number of policies required for BLI backup
A database BLI backup requires at least one Standard type policy.
This policy usually includes the following:
One full backup schedule
One incremental backup schedule
One user-directed backup schedule for control files and archive logs
Only one backup stream is initiated for each backup policy during automatic backups. To enable multiple backup streams, define multiple policies for the same database. If you have more than one database SID, configure policies for each SID. If you intend to do simultaneous backups of more than one SID on the same file system, use Nodata Storage Checkpoints. Set the METHOD to NODATA_CKPT_HOT.
For example, to back up file systems F1, F2, F3, and F4 with two streams, you need to define two policies (P1 and P2) with F1 and F2 backed up in P1, and F3 and F4 backed up in P2. If you have one large file system that needs to be backed up with multiple streams, divide the files in the file system between different policies. After a file is added to a policy, it should stay in that policy. If you must rearrange the file list, do so only prior to a full backup.
If you have more than one policy defined for an Oracle database instance, NetBackup groups the database instance by the NetBackup keyword phrase. Identify one of the policies as the POLICY_IN_CONTROL in the NetBackup notify scripts. This policy performs database shutdowns and restarts. All policies with the same keyword phrase need to be configured to start simultaneously.
Warning:
Care must be taken when specifying the keyword phrase. A multistream backup is attempted if the backup process finds more than one policy with the following characteristics: Each policy has the BLI attribute set, each policy is active, each policy contains the same client, and each policy has an identical keyword phrase.
Typical failure status is: "74 - timeout waiting for bpstart_notify to complete."
You can check the file systems on the backup client to see if they are included in one of the NetBackup policies on the server. To see if you need to add any new file systems to the NetBackup policies, run the following commands from the server on a regular basis, perhaps as a cron(1) job:
# cd /usr/openv/netbackup/bin/goodies/ # ./check_coverage -coverage -client mars -mailid \nbadmin
The preceding command generates the following output and mails it to the specified mailid:
File System Backup Coverage Report (UNIX only) ----------------------------------------------- Key: * - Policy is not active UNCOVERED - Mount Point not covered by an active policy MULTIPLE - Mount Point covered by multiple active policies CLIENT: mars Mount Point Device Backed Up By Policy Notes ----------- ------ ------------------- ----- / /dev/vg00/lvol3 production_servers /home /dev/vg00/lvol5 production_servers /oradata1 /dev/dsk/c1t0d0 block_incr1 /oradata2 /dev/dsk/c1t0d0 block_incr1 /oradata3 /dev/nbuvg/nbuvol UNCOVERED /opt /dev/vg00/lvol6 production_servers /oracle /dev/vg00/oracle production_servers /stand /dev/vg00/lvol1 production_servers /usr /dev/vg00/lvol7 production_servers /var /dev/vg00/lvol8 production_servers
If there is an UNCOVERED file system that is used by Oracle, add it to one of the NetBackup policies so that all the necessary file systems are backed up at the same time.
Note:
After a file system is added to a policy, it is a good idea to keep the file system in that policy. If you change the policy, NetBackup performs a full backup the next time backups are run even if an incremental backup is requested.