Hi Dynamox,

Yes, you state the ifgroup as a "replication ifgroup" and provide it with IP members and drop your Mtrees in there to use those members - example from my rather limited lab box... But hopefully it helps...

Group-name      Status          Interface   Clients   Replication

-----------    --------         ---------   -------    -----------

default          enabled            3         1             0

rep_testing      disabled           0         0             0

data             disabled           1         0             0

Rep_ifgroup      disabled           1         0             1

-----------      --------       ---------   ------- -----------

Group-name         Status        Interfaces

-----------      --------   -------------

default           enabled      172.18.XX.XYZ

default           enabled      172.18.XX.YYY

default           enabled      192.168.1.2

data              disabled     192.168.10.2

Rep_ifgroup       disabled     124.88.44.22

-----------      --------   -------------

Group-name Status    DD Boost Clients

---------- -------   ----------------

default enabled   *

---------- -------   ----------------

Group-name   Status     Replication Mtree                   Replication Remote Host

-----------  --------  ----------------------------------  -----------------------

Rep_ifgroup  disabled  /data/col1/DDBoost_rep_import_test      DD-dr

-----------  -------- ----------------------------------   -----------------------

File replication is allowed on ifgroup.

Client may use any interface.

Hello Jonathan,

Let's say this is my current network connectivity, might have to scroll to the right to see entire text in the code field below.

sysadmin@dd9300# net show hardware
Port    Speed     Duplex    Supp Speeds      Hardware Address    Physical   Link Status   State
-----   -------   -------   --------------   -----------------   --------   -----------   -------
ethMa   unknown   unknown   10/100/1000      00:60:16:73:71:86   Copper     unknown       down
eth1a   unknown   unknown   100/1000/10000   00:60:16:82:eb:0c   Copper     unknown       down
eth1b   unknown   unknown   100/1000/10000   00:60:16:82:eb:0d   Copper     unknown       down
eth1c   unknown   unknown   100/1000/10000   00:60:16:82:eb:0e   Copper     unknown       down
eth1d   unknown   unknown   100/1000/10000   00:60:16:82:eb:0f   Copper     unknown       down
eth3a   10Gb/s    full      10000            00:60:16:82:09:90   Fiber      yes           running <-- LACP Port-Channel
eth3b   10Gb/s    full      10000            00:60:16:82:09:91   Fiber      yes           running <-- Ifgroup used by Avatar and RMAN
eth3c   10Gb/s    full      10000            00:60:16:82:09:92   Fiber      yes           running <-- Ifgroup used by Avamar and RMAN
eth3d   unknown   unknown   10000            00:60:16:82:09:93   Fiber      unknown       down
eth4a   10Gb/s    full      10000            00:60:16:82:09:90   Fiber      yes           running <-- LACP Port-Channel
eth4b   10Gb/s    full      10000            00:60:16:82:09:9d   Fiber      yes           running <-- Ifgroup used by Avamar and RMAN
eth4c   10Gb/s    full      10000            00:60:16:82:09:9e   Fiber      yes           running <-- Ifgroup used by Avatar and RMAN
eth4d   unknown   unknown   10000            00:60:16:82:09:9f   Fiber      unknown       down
-----   -------   -------   --------------   -----------------   --------   -----------   -------

Typical configuration where eth3a and eth4a are my "entry" interfaces.  Avamar, DDBoost for RMAN  clients all point to the IP address assigned to this interface

Then we have eth3b,eth3c,eth4b and eth4c each assigned a VLAN interface and part of the default ifgroup.

Now we need to replicate Mtree used by Avamar as well as RMAN Mtree to another DD.  From what I understand, Avamar replication will need to be configured using Avamar interface so that it it replaces the Avamar metadata in addition to the actually data stored on DD.  So my goal was to connect eth3d and eth4d and use them explicitly for DD to DD replication.  Eth3d and Eth4d will be connected to a layer 2 network, so it's not routed.  I need to make sure that Avamar and RMAN do not try to use this ifgroup because they won't get too far since it's not routed.

When I create this new ifgroup, I can specify that it's dedicated for replication only, its members will not be advertised to Avamar/RMAN boost clients ?

Thank you