cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

How to ensure correct replication ports are used for data domain for optimised duplication

Hi All,

 

I am configuring optimised deduplication between two data domains, we have a dedicated Ip for replication from DD A to DD B. Can you please let me know what we need to on data domain end to configure MFR replication and how to ensure we are using replication IP for dedup from source to destination and not IF group IPs used for backups.

Tags (2)
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: How to ensure correct replication ports are used for data domain for optimised duplication

@Sachin507 

Best to consult DD documentation such as these:

https://www.emc.com/collateral/TechnicalDocument/docu61798.pdf

Using Dynamic Interface Groups for MFR
The Dynamic Interface Group (DIG) feature provides the ability to control the interfaces
used for DD Boost MFR to direct the replication connection over a specific network, and to
use multiple network interfaces with high bandwidth and reliability for failover
conditions. All Data Domain IP types are supported—IPv4 or IPv6, Alias IP/VLAN IP, and
LACP/failover aggregation.

and 
https://www.emc.com/collateral/TechnicalDocument/docu85192.pdf

View solution in original post

1 Reply
Highlighted
Accepted Solution!

Re: How to ensure correct replication ports are used for data domain for optimised duplication

@Sachin507 

Best to consult DD documentation such as these:

https://www.emc.com/collateral/TechnicalDocument/docu61798.pdf

Using Dynamic Interface Groups for MFR
The Dynamic Interface Group (DIG) feature provides the ability to control the interfaces
used for DD Boost MFR to direct the replication connection over a specific network, and to
use multiple network interfaces with high bandwidth and reliability for failover
conditions. All Data Domain IP types are supported—IPv4 or IPv6, Alias IP/VLAN IP, and
LACP/failover aggregation.

and 
https://www.emc.com/collateral/TechnicalDocument/docu85192.pdf

View solution in original post