Oracle RAC - hosts file on the Backup Exec server

category: solutionz · date: 2016-12-31 · updated: 2026-10-02 · author: LALA

Oracle RAC Solution · Config document · referenced from Backup Exec server and RAC backup

noteThese two lines give the public names of the nodes addresses of the backup network. They are right on the Backup Exec server only and contradict DNS on purpose.

The lines added to the local resolver file of the Windows server that runs Backup Exec. They make the plain node names resolve to the backup-network addresses there. The notes give the reason as a condition: if the production network of the nodes (public, VIP and SCAN addresses) is in effect a back-end network for the application servers and so not directly reachable, the backup server has to be given addresses it can reach.

Item	Value
Path on the host	`C:\Windows\System32\drivers\etc\hosts`
Deployed on	`mng-backupsrv01`, the Backup Exec server (Windows)
Edited with	`notepad`
Shown here	the two lines of the notes; the rest of the file is not in them
Backup Exec version at the time	Backup Exec 15 (14.2 FP5)

The file

ini

10.30.30.11 oradb01.example.net oradb01
10.30.30.12 oradb02.example.net oradb02

The same names in DNS

Name	In DNS on `dns1`	In this file
`oradb01.example.net`	`10.30.10.11`, public	`10.30.30.11`, backup
`oradb02.example.net`	`10.30.10.12`, public	`10.30.30.12`, backup
`oradb01-bck.example.net`	`10.30.30.11`	not listed
`oradb02-bck.example.net`	`10.30.30.12`	not listed

The names with -bck and the virtual node rac-clsopdb-1234567890 (the number stands in for the real database identifier and is made up) need no line here: the zone holds them with backup-network addresses already, see example.net zone. The notes name this file as the other possible place for the virtual node's records and then use DNS for them.

The override is what lets the entries ORADB01.example.net and ORADB02.example.net of the Oracle server list in the Backup Exec server settings work at all from this server.

Checked against Backup Exec 25.1

As built	Today
Node names and the virtual node made resolvable by hand, here and in DNS	The guide says that Backup Exec uses the fully qualified domain name to connect to the node; it gives no instruction to create `hosts` or DNS entries for a RAC

The file is therefore as much a local decision today as it was then.