NetBackup™ for Oracle Administrator's Guide
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Configuring RBAC for the Oracle administrator
- Managing Oracle instances and databases
- Managing Oracle credentials
- Configuring Oracle policies
- Preparing for NetBackup for Oracle configuration
- About Oracle Intelligent Policies (OIP)
- About script-based Oracle policies
- Managing Oracle RAC
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- Managing expired backup images
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Windows Server Failover Cluster (WSFC)
- Oracle cloning
- NetBackup Copilot for Oracle
- Configuring an OIP using universal shares (Oracle Copilot)
- Oracle Copilot with instant access
- Prerequisites when you configure an instant access Oracle database
- 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 configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- NetBackup Dedupe Direct for Oracle
- Using NetBackup Dedupe Direct for Oracle plug-in
- Other Oracle configuration
- Troubleshooting
- Troubleshooting RMAN backup or restore errors
- Appendix A. Deduplication best practices
- Appendix B. Snapshot Client support of SFRAC
- Appendix C. 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 D. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Appendix E. Register authorized locations
About catalog names with RAC and Data Guard aware intelligent policies
Oracle Data Guard and RAC aware intelligent policies catalog the backup images under a special client name within the NetBackup catalog. Data Guard enabled policies use the format databaseName_databaseID
as the client name. RAC aware policies use the format databaseUniqueName_databaseID
. If a RAC database is in a Data Guard enabled policy, the catalog name uses the Data Guard catalog name.
A RAC database configuration within NetBackup consists of a RAC database entry along with the associated instances. Each instance has a single client (host) name that can access the backup images that NetBackup stores. RAC databases and the associated instances can be viewed and managed using the NetBackup web UI. They can also be viewed and managed with the nboraadm command using the options -list_rac_instances, -add_rac_instance, -modify_rac_instance, and -delete_rac_instance.
See the NetBackup Commands Reference Guide for details of the nboraadm command.
A Data Guard configuration in NetBackup consists of a Data Guard object with attributes of database name and database ID. The list of Data Guard configurations that are stored in the NetBackup relational database can be viewed using the nboraadm command with the -list_data_guard option.
RAC databases and single instances databases can be associated with a single Data Guard configuration. For Data Guard enabled policies, the Data Guard configuration in NetBackup is added or updated automatically at policy run time. Only RAC databases and single instance databases are added to a Data Guard configuration after a back up has occurred. Any client that is part of a RAC database configuration or single instance databases has access to the associated Data Guard backup images. User name and user IDs along with group name and group IDs should match across hosts in the Data Guard configuration to have access to the backed-up files.
To see the list of RAC databases or single instance databases that are associated with a Data Guard configuration use the nboraadm command with the -list_data_guard_rac_databases or the -list_data_guard_instances option.
If a database has not been backed up with NetBackup and needs future access to the database backups that NetBackup stores, it must be added to the Data Guard configuration. You can use the nboraadm command using the -add_rac_to_data_guard
or -add_instance_to_data_guard option to add the database to the configuration.
To remove access to the backup images, use the nboraadm command with the -remove_rac_from_data_guard or -remove_instance_from_data_guard option.
See the NetBackup Commands Reference Guide for details of the nboraadm command.
If restoring from an alternate NetBackup server domain (AIR domain target), for access to images that relate to Data Guard or RAC, the primary server must have certain conditions set. That server must have the same Oracle instance repository configuration duplicated into it to allow access from alternate nodes in the RAC cluster. Or, the server must have an alternate standby database in the Data Guard.
Additional host names can be added as aliases to an instance within NetBackup. This process is useful if a client is part of a RAC cluster or Data Guard configuration and has multiple network interfaces used to connect to NetBackup servers. Aliases can be listed, added, or deleted when the nboraadm command is used and the -list_instance_alias, -add_instance_alias, and -delete_instances_alias options.