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 the NetBackup for Oracle Template Wizard or in the RMAN script. A few can be set in multiple places, most notably those that specify the master 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.
The template fields for Client name and Schedule name, if specified in the backup template.
The template fields for Server name and Backup policy name, if specified in the backup template and initiated from the client.
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 bpdbsboraor RMAN is started.
The environment variables that the login or shell inherits.
The environment variables that the master 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 master server selects the first policy of type Oracle for the client name.
The master server selects the first schedule of type Application Backup (stream-based) or Automatic Full Backup (proxy) from the policy.
Note:
The Server name and Backup policy name that is configured within a backup template are only used when initiated from the client.
If the backup is initiated from an automatic schedule on the master server the operation is different. The backup uses the name of the master server and policy that was used to initiate the template. This operation allows a template to be used with multiple policies, with different automatic schedules, and even different master servers.