Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange 2013 2 node DAG, why are 65 ReplicationDagNetwork showing up in the ECP?

Posted on 2014-11-06
1
Medium Priority
?
714 Views
Last Modified: 2014-11-07
We have Exchange 2010 in place, trying to install Exchange 2013 in a 2 node DAG.   Running Exchange 2013 on Server 2012 R2 as a Hyper-V guest on a 2008 R2 Hyper-V host.

In my ECP under database availability groups for my DAG on my new Exchange 2013 nodes it show 65 ReplicationDagNetworks.  I actually only have one replication network and have verified in powershell that replication is using the correct network.

Also the command get-databaseavailabilitygroupnetwork fails with a "could not load file or assembly" error.

Not sure if that is related.
0
Comment
Question by:jasonbrandt3
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
jasonbrandt3 earned 0 total points
ID: 40428449
All but the ReplicationDagNetwork01 have empty IP settings.

Cumulative update 6 for Exchange 2013 SP1 is installed.

I have (2) iscsi connections to mount volumes for the database and log directories.  Those connections attach to a single SAN network and I disabled replication . (I have "ManualDagNetworkConfiguration" set to "True".

I cannot delete these extra ReplicationDagNetworks in ECP, nor can I disable replication over the MAPI network via ECP

Since I ran the command:
 Set-DatabaseAvailabilityGroupNetwork -Identity DAG2\DAGNetwork02 -ReplicationEnabled:$false -IgnoreNetwork:$true

I am now able to see info when I do a get--databaseavailabilitygroupnetwork as it looks like it opened a new powershell session with more permissions.

The remove command seems to have quite a delay when I try to remove the networks.  Even after specifying a domain controller that is NOT read-only.
Remove-DatabaseAvailabilityGroupNetwork -Identity DAG1\DAGNetwork04 -domaincontroller mydc.mydomain.lcl

I'll try removing all the invalid ones and waiting a few minutes, this problem may be resolved.
0

Featured Post

How Blockchain Is Impacting Every Industry

Blockchain expert Alex Tapscott talks to Acronis VP Frank Jablonski about this revolutionary technology and how it's making inroads into other industries and facets of everyday life.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

660 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question