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
About performing a redirected restore with RMAN
Perform the following procedure on the destination client host if you want to restore any RMAN backups that another client owns.
The user on client A cannot initiate a redirected restore to client B. Only the user on client B, which is the client receiving the backup image, can initiate the redirected restore. Any user who belongs to the database group that performed the backup can restore it, unless the BKUP_IMAGE_PERM variable is set to USER.
If the RMAN catalog database has been lost, restore the catalog database first before continuing with the redirected restore.
To perform a redirected restore
- Enable a network connection to the RMAN catalog database that the source client used.
- Do one of the following:
On Windows, use the rman parms option to set the NB_ORA_CLIENT environment variable to the source client.
On UNIX, set the NB_ORA_CLIENT environment variable to the source client.
- On UNIX, check the bp.conf files on the source client. Make sure that the CLIENT_NAME variable either is not set or is set to the host name of the source client.
- Make the init.ora file of the source client available to the destination client.
Copy the file to the destination client or modify the file on the destination client. Change all location-specific parameters.
- Create a folder or set the permissions for a directory to restore the data files:
On Windows, create and start an Oracle service for the previously set ORACLE_SID. Create the folder to which you want to restore the data files.
On UNIX, grant write permission to the directory to which you want to restore the data files.
- Set up a password file for the destination client database.
- Start the database in the nomount state.
- Start RMAN, connecting to the catalog. On Windows, also connect to the target database.
- On UNIX, set dbid to be the DBID of the source client database. Connect to the target database without using a user ID and password.
- Run an RMAN restore script. On UNIX, you can alternatively type the RMAN commands for the restore.