About configuring the run-time environment
When the Oracle Intelligent Policy is not used, there are many user configurable variables that can affect the operation of NetBackup for Oracle. Most can be set only in an RMAN script. A few can be set in multiple places, most notably those that specify the primary server, client name, policy, and schedule.
When these variables are configured in multiple places, the following order of precedence is used (the list is ranked highest to lowest):
RMAN SEND command variables, if specified in the backup script.
RMAN ENV parameter variables, if specified in the backup script.
Environment variables that are inherited from the Oracle listener process startup environment, if RMAN connects to the database using TNS SQL*Net.
Environment variables that are set in the backup script before RMAN is started.
The environment variables that the login or shell inherits.
The environment variables that the primary server initiation of an automatic schedule sets.
On UNIX, the Oracle user's configuration file;
$HOME/bp.conf.The NetBackup configuration:
Windows: The
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Configregistry keys.UNIX: The
/usr/openv/netbackup/bp.conffile.Both: The NetBackup GUI settings for server, client name, optional default policy, and optional default schedule.
The following defaults apply:
A server must be specified, there is no default.
The client name defaults to the host name.
The primary server selects the first policy of type Oracle for the client name.
The primary server selects the first schedule of type Application Backup (stream-based) or Automatic Full Backup (proxy) from the policy.