Video Screencast Help

REQUIRED_INTERFACE on the same subnet?

Created: 16 Nov 2012 • Updated: 10 Dec 2012 | 5 comments
This issue has been solved. See solution.

I've got a verified network bottleneck on one of my Netbackup redhat linux clients. Production data volume is causing backup performance to suffer, and backup performance is critical to keep oracle archive redo logs from filling up available filesystem space.

There is a second physical NIC available.

We do not have a dedicated backup subnet, or this would be easy.

When using the REQUIRED_INTERFACE directive in bp.conf, do the network interfaces have to be on different subnets?

For example, "eth0" is, and we add "eth1" as Will "REQUIRED_INTERFACE=" work properly, and send the backup data out the interface?

Comments 5 CommentsJump to latest comment

Will Restore's picture

Worth a shot.

BTW, starting with NBU 7.1,


Will Restore -- where there is a Will there is a way

mph999's picture

wr beat me to it, required interface is the old way and should not be used, in preference of preferred network which has multiple  ways in which it can be used, plenty of technotes explaining the different ways.


Regards,  Martin
Setting Logs in NetBackup:
Nicolai's picture

I don't think PREFERRED_NETWORK it will help you. Since both NIC are on the same network the OS will use the first NIC it find in the routing table that matches the destination network.

I  would recommend creating a LACP network channel instead. Only thing to metntion - you need the network admin to create a LACP channel for you on the switch side.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

mph999's picture

Despite its name you can specify a particular ip address


Regards,  Martin
Setting Logs in NetBackup:
Wile E. Coyote's picture

Yes, the ideal solution is to trunk the two interfaces together, but that's going to cause a disruption and a lot more paperwork that nobody is willing to deal with.

Plumbing a new interface can literally be done any time.

We would plumb the new interface on the same subnet as the media server, but we don't know what, if anything, that will break as far as database and application connectivity. Unfortunately we do not have a dedicated backup network.