Avamar: How to configure a specific network interface to be used for Avamar backup data

To ensure that incoming traffic addressed to the Avamar software uses a specified network card, create a file in C:\program files\avs\var called avagent.cmd. 

Add this line:

--netbind=1.2.3.4

Where 1.2.3.4 is the IP of the network to be used for backups.

Restart the backup agent service to pick this up. This should force avagent to use 1.2.3.4 and to register using this interface.*

The network topology determines and direct outbound traffic. If a specific route is added, with the appropriate (low) weight/metric, it determines the preferred outbound path.

On Windows, the "route add -p <avamar-server> MASK <netmask> <gateway-ip> <metric>" command can be used.

The " -p" option makes the route persistent.

Here is the complete syntax:

route ADD [destination IP address or subnet] MASK [subnet mask] [gateway IP address] [metric] IF [interface]

Example: route add -p 192.x.x.xx MASK 255.xxx.xxx.xxx 192.x.x.x METRIC 150 IF 14

The IF is a number 1, 2, 3, 4, so forth and it is the number of the Network Interface Card (NIC). It allows you to pick the NIC where the traffic is heading.  

To find the NIC interface list, run the command;
route print

Pick a value for METRIC that is LOWER than the values for the other routes with the same or similar IP address destination (route prefix) on the client. This can be determined from the "route print" output.

For more information about adding routes to Windows see the following links:

• http://www.tech-recipes.com/rx/478/nt2000xp-add-a-temporary-route-to-the-windows-routing-table/
• http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true
• http://technet.microsoft.com/en-us/library/cc757323%28WS.10%29.aspx