You need to "trick" Avamar to think its using the replication interfaces instead of the backup interfaces. I did a while back at a customer site and I seem to remember it was fairly easy after giving it some thought.
For the Avamar side I followed the Avamar dedicated replication interfaces procedure.
After this I created interfaces on both DD(Source + Destination) systems on the replication network. Static routes and host mappings was necessary.
On Avamar the only thing I did was to create entries in the hosts file that destination DD system hostname would not resolve to DNS IP but replication IP.
in DD can't you change "Connection Host" parameter and specify interface on target DD that you want to replicate to. If traffic is still leaving source DD using incorrect interface, you might have to set a static route.
broeste1
1 Rookie
•
153 Posts
1399
0
Posted December 12th, 2016 00:00
Hi,
You need to "trick" Avamar to think its using the replication interfaces instead of the backup interfaces. I did a while back at a customer site and I seem to remember it was fairly easy after giving it some thought.
For the Avamar side I followed the Avamar dedicated replication interfaces procedure.
After this I created interfaces on both DD(Source + Destination) systems on the replication network. Static routes and host mappings was necessary.
On Avamar the only thing I did was to create entries in the hosts file that destination DD system hostname would not resolve to DNS IP but replication IP.