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
Manually adding an Oracle database instance to the repository
New instances the instance discovery system finds on the clients are automatically added to the repository. However, you may need to add an instance manually. For example, you do not want to wait for the discovery service to discover the new instance.
If necessary, contact the Oracle database administrator for the correct set of credentials. The DBA can also manually add the instance if the DBA is not willing or allowed to share the credentials with the backup administrator. The DBA can manually add the instance using the nboraadm command on the client. The Oracle database user is required to have a certain level of credentials. The Oracle database user must have
SYSDBA privileges (based on version of Oracle).
To manually add an Oracle database instance to the repository
- In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Applications > Oracle.
- Click All Instances. All instances in the repository are listed in the right pane.
- Right-click All Instances and select New instance to display the following:
- Fill in the Instance Name, Host, and ORACLE_HOME parameters. Click Help to display descriptions of these parameters. For example:
- (Conditional) Use the Override Default TNS_ADMIN Path if you need to override the default network administration directory on the client system. Enter the fully qualified path for the network administration directory on this host. Click Help to display a description of the parameter. Example of the parameter:
- Click Provide Credentials.
- In the Register Instance dialog box, click Use Instance Credentials.
- Enter the instance credentials using one of the three options:
OS authentication only
Oracle authentication only
Oracle and OS authentication
- (Optional) You can also click Use Oracle RMAN Recovery Catalog to enter credentials for the RMAN recovery catalog.
- Click Ok.
The system tries to validate the credentials, report its findings, and return you to the Change Instance dialog box. Validation can fail for multiple reasons and a pop-up displays the error message. Click to save the credentials as entered. If you want to enter the credentials again, you can click and re-enter the credentials. If you save the credentials that caused the error, the instance is saved in the repository. You can edit the instance at a later time to correct the validation issue.