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
Destination Parameters panel
Guided Recovery uses many values from the source database as default values for the destination database. You can modify these values if not appropriate for the destination database.
Note:
The Windows information you enter on this screen is case-sensitive. Be sure to enter the Windows information appropriately.
The Destination Parameters screen contains the following tabs:
Database Attributes. This pane appears when you first enter the Database Attributes screen. Each attribute name has identical source and destination attributes. You can change the destination attribute of the instance name, database name, and database home. Note that the instance name is case-sensitive while the database name is not case-sensitive.
If you use a temporary tablespace or data files, and you plan to write the data files back to the same location, do not modify the path. If you must modify the path, make sure that it is identical to the source path including case (upper, lower, mixed). Otherwise, the clone fails with an error that indicates the temporary file already exists. This limitation does not affect UNIX and Linux systems.
Control File Paths. This pane displays the source path and the destination path for each control file. You can change a control file destination path by clicking in the associated text window and entering the new path. You can also click Browse to navigate to the desired path. When you change a path, a highlight bar appears around the text window as a visual indicator that this path has changed.
Data File Paths. This pane lets you change the destination path for one or more data files. Enter the path in the text window provided, then select the data files on which to apply it, and press the Apply option.
Redo Log Paths. This pane displays the source path and the destination path for all redo logs. You can type in a new destination path or click Browse to navigate to the desired path. When you change a path, a highlight bar appears around the text window as a visual indicator that this path has changed.
Restore Options. This pane displays restore options. The option that is displayed on this pane is Number of parallel streams for restore and recover.
When you are done making changes on this screen, click . All the information from the previous screen is saved in preparation for the cloning operation. All the changes that are made in this screen are temporary and are active only for the cloning session.