2 Bronze

DDBoost w/ Avamar using Interface Groups

Jump to solution

Hi team.

I have seen some discussions using interface groups with DDBoost.

I would like to configure it correctly from the start.  I understand that I just add the interfaces to the Interface Group in my DDBoost IP Interfaces tab, configure the clients, and DDBoost will find the least used IP and use that IP instead.  (If I'm wrong, please correct me!)

I have also seen some people discuss adding a 3rd, LACP device or Failover devices to their Interface Group?  If we only intend to use 2 physical connections to this Data Domain using the DDBoost IFGroup, why do I need this 3rd IP and entry in my IFGroup?

For Example, I have configured...

sysadmin@Some_Datadomain# ifgroup show config all

Group-name     Status     Interface   Clients   Replication
------------   --------   ---------   -------   -----------
default        disabled           0         0             0
Site A         enabled            2         1             0
------------   --------   ---------   -------   -----------

Group-name     Status      Interfaces
------------   -------   ------------
Site A      enabled   1.2.3.4
Site A      enabled   1.2.3.5
------------   -------   ------------

Group-name     Status    DD Boost Clients
------------   -------   ----------------
Site A   enabled   *
------------   -------   ----------------
No replication mtrees with remote hosts in ifgroup
File replication is allowed on ifgroup.
Client may use any interface.


And my networking looks like this...

sysadmin@Some_DataDomain# net show settings

port    enabled   state     DHCP   IP address                   netmask          type   additional setting

                                                                /prefix length

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

ethMa   yes       running   no     1.2.3.3                      255.255.255.0    n/a

                                   IP_v6_Nonsense**   /64

eth1a   yes       running   no     1.2.3.4                      255.255.255.0    n/a

                                   IP_v6_Nonsense**   /64

eth1b   yes       running   no     1.2.3.5                      255.255.255.0    n/a

                                   IP_v6_Nonsense**   /64

eth1c   no        down      no     n/a                          n/a              n/a

eth1d   no        down      no     n/a                          n/a              n/a

eth3a   no        down      no     n/a                          n/a              n/a

eth3b   no        down      no     n/a                          n/a              n/a

eth3c   no        down      no     n/a                          n/a              n/a

eth3d   no        down      no     n/a                          n/a              n/a

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

** auto_generated IPv6 address


0 Kudos
1 Solution

Accepted Solutions
3 Argentum

Re: DDBoost w/ Avamar using Interface Groups

Jump to solution

LACP should only be used if your stuck on NFS/SMB usage.  The reason you might create a failover pair is the primary IP for BOOST needs to be up for initial connection. If you loss the primary, the initial connection will fail and so will boost.  Once the connection is made the IFgroup is cached and a port/nic/route failure will be handled.

So the best practice for boost is to have the primary NIC setup as a failover pair, and all other nic added to the ifgroup.

View solution in original post

0 Kudos
4 Replies
3 Argentum

Re: DDBoost w/ Avamar using Interface Groups

Jump to solution

LACP should only be used if your stuck on NFS/SMB usage.  The reason you might create a failover pair is the primary IP for BOOST needs to be up for initial connection. If you loss the primary, the initial connection will fail and so will boost.  Once the connection is made the IFgroup is cached and a port/nic/route failure will be handled.

So the best practice for boost is to have the primary NIC setup as a failover pair, and all other nic added to the ifgroup.

View solution in original post

0 Kudos
2 Bronze

Re: DDBoost w/ Avamar using Interface Groups

Jump to solution

Awesome response!

So, to make sure I comprehend properly, I would do the following. 

  1. Make eth1c and eth1d either a LACP or Failover virtual device, veth0.
  2. Point my applications to that veth0 IP. (Avamar, other DDBoost apps, ect)
  3. Create my IFGROUP with the 2, single port IP address.  eth1a and eth1b in my example above.
  4. Watch my apps connect to the DD using the veth0 address initially, but then use the IFGROUP IPs once the DDBoost kicks into gear to send the bulk of the data.

A follow up question to this, if DD replication is setup, would it use IFGroups at all, or would it only use the veth0 port I would set up?

0 Kudos
3 Argentum

Re: DDBoost w/ Avamar using Interface Groups

Jump to solution

Correct!!!

  Replication doesn't use the ifgroup, so a veth0 would be the best solution for redundancy too

7 Thorium

Re: DDBoost w/ Avamar using Interface Groups

Jump to solution

Managed file replication (DDBoost for RMAN, Avamar) does use ddboost for replication.

https://www.emc.com/collateral/software/white-papers/h7082-data-domain-replicator-wp.pdf

0 Kudos