This post is more than 5 years old
89 Posts
0
2344
Exchange DAG cluster network choice during install
I was wondering if anyone had run into this. I'm using the "Cluster Configuration Wizard" to setup a DAG client. When it gets to the "DAG Client Settings" step, where you, among other settings, add the DAG IP you will be using. It also lists all the networks on the Exchange server. Is there a network that specifically needs to be used?
I get a red "x" beside one of our private internal replication networks, but am trying to choose a different network that is public to use with the Avamar DAG IP I chose, but and it won't let me proceed, it gives me a message box, that errors need to be corrected before proceeding. Do I have to use the network marked with the red "x", Avamar seems to think so I suppose since it won't let me proceed. Does the Avamar IP used have to be on a network that has Exchange DAG Replication enabled? The one I was trying to use does not, but can communicate with Avamar, the other three networks have DAG replication enabled but are not accessible by Avamar? Any help would be appreciated as this one is getting confusing and frustrating. Thanks as always.
Clarkson14
89 Posts
0
April 28th, 2017 07:00
Thanks for the reply. For some reason, it wouldn't let me choose another network other than the one that had the red "X" next to it, if I chose our backup network that was listed, the one I wanted to use, as what sounds like you have, it wouldn't proceed.
I ended up just using an IP from the internal replication network and that seemed to take care of things, not the way I wanted but got it working. We're migrating to O365 and our DAG is only down to one DB so it wasn't really a big deal at the end of the day, but I still would have preferred to use the backup interface.
Matthew1970
7 Posts
0
April 27th, 2017 12:00
Exchange 2013
The Avamar DAG IP is part of the Exchange Cluster but it does not need to be on the same VLAN as the Exchange Replication. In fact, in our case we have a Backup VLAN. We added a vNIC to all of our Exchange Servers on that VLAN and then leveraged an IP on there for the Avamar DAG piece. Not sure if that answers your question.
Cluster Client Settings:
DAG group name = Avamar cluster client for EXCH-DAG
Backup cluster client name = Avamar-DAG
Bring Avamar DAG client online and register with Avamar server True
Backup cluster client IP = xxx.xx.xx.xxx
Network mask = xxx.xxx.xxx.xxx
Backup DAG networks:
DAG network name = Cluster Network 1
Selected backup DAG network = Cluster Network 1