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
Redirecting a restore of an XML export archive to a new client using bporaimp
On UNIX and Linux, any user who belongs to the database group that performed the archive can restore XML export archive. The BKUP_IMAGE_PERM variable must be set to GROUP or ANY, not USER.
If you use a non-root service user account, specific access must be allowed for that user when you add files to the /usr/openv/netbackup/db/altnames
directory. The service user account must have full access to these files through the ownership or group and the permissions. For example, if the service user is svcname
and its group is srvgrp
, the file can have permissions of 400
. If the file owner is for a different user and group, the file permissions must allow access to the service user. For example, 777
. Equivalent permission settings must be used in a Windows environment.
Perform the following procedure on the new client host if you want to restore XML export archives that are owned by another client.
To redirect a restore of an XML export archive to a new client using bporaimp
- Set the environment variables for bporaimp (bporaimp64 on some platforms) on the new client, including ORACLE_HOME and ORACLE_SID.
- In the bporaimp parameter file, include the following lines:
nb_ora_serv = Netbackup_server nb_ora_client = original_client_where_XML_export_occurred.
- Specify any other bporaimp parameters.
- Run bporaimp.