Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Oracle Administrator's Guide
  3. Performing backups and restores of Oracle
  4. About NetBackup for Oracle restores
  5. Redirecting a restore to a different client
  6. Example - Performing a redirected restore of Oracle
NetBackup™ for Oracle Administrator's Guide

Example - Performing a redirected restore of Oracle

For example, assume the following:

  • Source client is camel

  • Destination client is giraffe

  • Master server is lion

  • ORACLE_SID is test

  • The user is connected to the Oracle database using a local connection, not SQL*Net

  • UNIX user is ora on both camel and giraffe

To perform a redirected restore (example)

  1. Create the following file on server lion:

    Windows: install_path\NetBackup\db\altnames\giraffe

    UNIX: /usr/openv/netbackup/db/altnames/giraffe

    Edit giraffe to contain the name camel:

  2. Do one of the following:
    • Windows: Use the BAR GUI to set lion as the master server.

    • UNIX: Log onto giraffe as ora. Set SERVER=lion in $ORACLE_HOME/bp.conf. This server must be the first server that is listed in the bp.conf file.

  3. Modify the network tnsnames.ora file to enable the RMAN catalog connection.
  4. Create inittest.ora.file.
  5. Windows: Using Oracle administration, create and start ORACLESERVICETEST.
  6. Set the environment variable ORACLE_SID to test. On UNIX, also set NB_ORA_CLIENT to camel.
  7. Make sure that the destination database directory exists and has appropriate access permissions.

    The data files are restored to the directory path with the same name they had when they were backed up.

  8. Start the database in a nomount state.

    On UNIX, the following is the output:

    SQL> startup nomount pfile=$ORACLE_HOME/dbs/inittest.ora
    %rman catalog rman/rman@rcat
    RMAN> set dbid=<dbid of source database on camel
    RMAN> connect target/
    RMAN> run {
    RMAN>        ALLOCATE CHANNEL CH00 TYPE 'SBT_TAPE';
    RMAN>        SEND 'NB_ORA_SERV=lion, NB_ORA_CLIENT=camel';
    RMAN>        restore controlfile;
    RMAN>     } 
    
    SQL> alter database mount;
    %orapwd file=$ORACLE_HOME/dbs/orapwtest password=<oracle>
    %rman catalog rman/rman@RCVCAT
    
    RMAN>set dbid=<Saved dbID of Source Target>
    RMAN>connect target/
    RMAN>run {
    RMAN>        ALLOCATE CHANNEL CH00 TYPE 'SBT_TAPE';
    RMAN>        ALLOCATE CHANNEL CH01 TYPE 'SBT_TAPE';
    RMAN>        SEND 'NB_ORA_SERV=lion, NB_ORA_CLIENT=camel';
    RMAN>        restore database;
    RMAN>        restore archivelog all;
    RMAN>     }
    
    SQL>recover database until cancel using backup controlfile;

    Now apply the archived logs. Type cancel when you decide to stop recovery.

Feedback

Was this page helpful?
Previous

About performing a redirected restore with RMAN

Next

Using NetBackup for Oracle in a Microsoft Windows cluster environment

Feedback

Was this page helpful?