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. Oracle policy configuration
  4. About script-based Oracle policies
  5. About configuring the run-time environment
  6. About the Oracle RMAN environment
NetBackup™ for Oracle Administrator's Guide

About the Oracle RMAN environment

The Oracle RMAN program inherits the environment of the program or shell from which it was started. The environment may come from a number of places:

  • The global environment or profile for the host

  • The profile of the user

  • The NetBackup master server

  • A non-NetBackup scheduler

  • A backup script

  • An interactive terminal session

Additionally, once RMAN is started it connects to the database instance and starts the Oracle database server processes that perform the backup. If the connection is by local logon and password (without a TNS alias), the Oracle database server process is a child of the RMAN program. The Oracle database server process inherits the environment from RMAN. Because the NetBackup for Oracle agent is a shared library loaded into the Oracle database server process it too inherits that environment.

However, if RMAN connects to the database instance by SQL*Net (logon and password@TNSalias) the Oracle database server process is a child of the SQL*Net listener service. This SQL*Net listener service was started previously and independently of RMAN. As a result, the NetBackup for Oracle agent does not inherit the environment from RMAN. Instead, the agent inherits the environment from which the listener service was started

To avoid unexpected results, it is recommended to configure RMAN to always use the send command to pass the desired variables and values to NetBackup explicitly. Alternatively the RMAN ENV parameter can be used to make the variables and values available to NetBackup.

Example 1. Use the send command to specify the policy and server to use for a database backup. As this example shows, specify the variables in the string in the RMAN script after all channels have been allocated and before the backup command.

run {
    allocate channel t1 type 'SBT_TAPE';
    allocate channel t2 type 'SBT_TAPE';
    send 'NB_ORA_POLICY=your_policy,NB_ORA_SERV=your_server';
    backup (database format 'bk_%U_%t');
    release channel t1;
    release channel t2;
 }

Example 2. Use the parms operand to specify the policy and server to use for a database backup. The parms operand is set with each allocate channel command in the shell script.

run {
    allocate channel t1 DEVICE TYPE 'SBT_TAPE'
    	PARMS "SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so,
    	ENV=(NB_ORA_POLICY=your_policy,NB_ORA_SERV=your_server)";
    allocate channel t2 DEVICE TYPE 'SBT_TAPE'
    	PARMS "SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so,
    	ENV=(NB_ORA_POLICY=your_policy,NB_ORA_SERV=your_server)";
    backup (database format 'bk_%s_%p_%t');
    release channel t1;
    release channel t2;
 }

Feedback

Was this page helpful?
Previous

About configuring the run-time environment

Next

About the environment variables set by NetBackup for Oracle

Feedback

Was this page helpful?