A backup job for an Oracle RAC instance fails when specifying a Network Interface
Article ID: 100015917
Updated On:
Description
Error Message
Final error: 0xe0000f02 - The Backup Exec server could not connect to the remote computer. The remote computer may not exist on the selected subnet. Try an alternative network interface, or allow Backup Exec to choose any available network interface.Resolution
WORKAROUND:
Step 1: Hosts file
Add a 'variable' host name to the hosts file on every Oracle Server with an IP address of the specific / required Network Interface.
In this example, I use "mynetwork1" as the variable host name.
Example:
192.168.1.101 node1
192.168.2.101 mynetwork1
Step 2: Registry or ralus.cfg
Add the 'variable' host name into the Windows registry or ralus.cfg on every Oracle server.
a) Windows registry
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Go to the following registry key
HKLM\Software\Veritas\Backup Exec For Windows\Backup Exec\Engine\Agents\XBSA\Oracle RMAN Agent\SID\
IMPORTANT: The variable host name needs to be listed before the already existing node name
Example:
Value before update: node1
Value after update: mynetwork1 node1
b) ralus.cfg
Open the ralus.cfg file and look for the following line and add the variable host name before the existing node1 value.
Example:
HKLM\Software\Veritsa\Backup Exec For Windows\Backup Exec\Engine\Agents\XBSA\Oracle RMAN Agent\SID\
Step 3: Remote Agent
Restart Remote Agent and wait for a while until the updated information is advertised.
Step 4: Ensure that a backup and restore job works.
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. While this issue may be resolved in a future major revision of the software at a later time, it is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Issue/Introduction
Additional Information
