Exchange 2010 dag with only 2 servers

I have my exchange 2010 running on win server 2012 R2 and I have installed another exchange 2010 server with the same FQDN and I want to configure DAG with only these 2 servers. Can I implement DAG with only 2 servers?Can the mailbox,client access and hub
transport roles still work with only 2 servers? If Mailbox and Hub transport could work it will be fine for me as CAS switchover can always be done manually.My main concern is securing data. Any article on how to implement that would be highly appreciated.
Thanks

Hi,
Yes, we can create a DAG with 2Servers and Each server can have upto 100 database depends upon Standard or Enterprise.
Here is a great link that explains about DAG
Exchange 2010 DAG Installation
Mark as Answer/Helpful Post if it helps
Regards.
Naren Neelam, Messaging Consultant, ITBigBang (P) Ltd Www.ITBigBang.Com | Hire Us for Messaging Consulting

Similar Messages

Exchange 2010 - DAG with 2 servers - 1 server failed - limping along

We are using Exchange Server 2010 Enterprise. 2 servers in a DAG environment. We have a 3rd, non Exchange Server, acting as the witness server. Both Exchange Servers are running Mailbox, Client Access and Hub Transport roles.
We do not have any public folders to worry about.
We have a hard drive failure on one server, EXCH01. The information store is currently shut down on EXCH01, but the server itself is online. The second exchange server, EXCH02, is up and all in our organization are able to send/receive email.
However, if we shut EXCH01 off, no one in the organization can send/receive email. That hard drive is not going to hold out much longer, it is going to shut down and we will be down hard at that point. What do we need to look at in our DAG failover?
2nd, we will need to rebuild EXCH01 and restore a backup from EXCH02. Unsure of the proper steps/order to do this in. (No public
Any direction you can provide is very much appreciated.

2 options:
One: Simulate a Datacenter failover an force quorum on the remaining server in the event the first one fails:
http://technet.microsoft.com/en-us/library/dd351049(v=exchg.141).aspx
Two:Build a new Exchange Server lickity-split and add it the DAG now. With no mailbox databases on it , just as a voting member. Doing that, you will have 3 nodes in the DAG and you can down the failing server and not lose quorum and the databases will remain
mounted as 2 of 3 nodes will be up. ( Or better yet, remove the failing server from the DAG after adding a new server and then you have 2 nodes that are viable)
Not sure why you need to restore a backup of EXCH02 however?
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Proper way to install windows update on Exchange 2010 DAG with one mailbox server in Head Office and 1 mailbox server in DR site both are members of 1 DAG

Hi Guyz,
I have this setup in my exchange environment.
1 DAG with 2 members
- One member is located in Head Office and the other member is located in DR site. All of the mailbox databases are located only in HO (Plan to add additional second member in HO soon). Now what is the proper way to install windows patches on the
member in HO? I don't want to move the databases to DR site as much as possible.
Appreciate your feedback and Many thanks in advance guyz..
More power to all!
Regards,

Hi,
To update the DAG members with new patches, the update process should be managed to prevent all of the DAG members from being offline at the same time.
To do this, I recommend you move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.
For detailed steps, here is an article for your reference.
How to Install Updates on Exchange Server 2010 Database Availability Groups
http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-database-availability-groups/
Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2010 server with 2 DAG servers - DAG1 and DAG2 - backup with 2 DPM servers one for each DAG server

Hello,
Please advice, i have an Exchange 2010 server with 2 DAG servers - DAG1 and DAG2 - backup with 2 DPM servers, one for DAG1 and one for DAG2 is it possible ?

Hi,
I confirmed with Exchange support team that DAGs could be backed up separately.
Meanwhile backup database is important if you need to recover both Exchange server settings and database. See:
Recover a database availability group member server
http://technet.microsoft.com/en-us/library/dd638206.aspx
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange 2010 DAG and NIC Teaming | Team broke and now cluster doesn't see the box

Hello everyone,
Question for the group. We are running an Exchange 2010 DAG cluster with four boxes with active/passive DB's on each of the four boxes. We run HP boxes for Exchange and the NIC's are teamed. Now mind you, I arrived at this company well after this environment
was set up so I have inherited everything here.
What has happened is one of the four boxes had an issue after an otherwise normal reboot. We could no longer ping it. Logged into the ILO and was able to log into the server, only to discover its team NIC was messed up and our only option was to rebuild
the team NIC. So I rebuilt the team and gave it the original IP/subnet/gateway it had. The server reboots and we can ping it.
However, when I look in the EMC at Database Management, all the passive copies that were on that DB are showing Failed. Ok, so I suspend the copy and attempt to reseed. No luck. I get the error "The NetworkManager has not yet been initialized"
and it references my machine which had the bad team NIC. Curious, I go look at my Failover Cluster Manager.
Looking at the fail over cluster manager, I notice a X on the cluster and I am showing my server which had the bad team NIC being listed as down. I attempted to start the cluster service for the machine, but it did not work.
Is there something I a missing? What are my exact steps to take to get my cluster configuration working correctly again and see my box? Do I need to remove the box from the DAG, evict it from the cluster, and rejoin it again? If so, can I do this without
affecting the other three machines so users don't notice any outage?
Thanks for any help you can give!

Hi Kyle,
I am Chetan Savade from Symantec Technical Support Team & sorry to know the problem you faced because of SEP.
Symantec recommends that the Exchange server's OS always be protected by the latest available release of SEP. The Exchange server's message flow and Information Store must be protected by a dedicated mail security product, such as Symantec
Mail Security for Microsoft Exchange.
For cluster environment I would recommend to follow this article:
Installing the Symantec Endpoint Protection client to a Windows cluster server
http://www.symantec.com/docs/TECH91154
Installation best practices for Endpoint Protection on Windows servers
http://www.symantec.com/docs/TECH91154
Best Regards,
Chetan

Exchange 2010 DAG netowrk replications issues - Causing database copies to be disconnected and resynchronizing.

My
environment is as follows.<o:p></o:p>
We have 3 exchange 2010 servers.<o:p></o:p>
EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
The dag is configured to to communicate to all three.<o:p></o:p>
The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
DREX1 is located in another network. It is in another building connected via vpn. The ip
for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
(These are not the actual address, but the concept is similar)<o:p></o:p>
The dag network configuration is as follows.<o:p></o:p>
DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
and 192.168.100.52<o:p></o:p>
DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
160.100.3.51 and 160.100.3.52<o:p></o:p>
Last Friday, 3/7/14 something happened.<o:p></o:p>
To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
full backups of our exchange databases when I reviewed the backup jobs, the
exchange database backups using dpm2010 failed all weekend long starting at
11:00pm that Friday.<o:p></o:p>
The issue that occurred was that the database copies went to a status of Disconnected and
Resynchronizing, and after about 30 seconds, the status would show
Resynchronizing.<o:p></o:p>
All attempts to resolve this with the research methods failed. Deleting the
logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
Creating a new database worked, creating a database copy worked, but seeding the copy
failed. All with the same pattern, a status of Disconnected and
Resynchronizing, and after about 30 seconds, and the status would show
Resynchronizing.<o:p></o:p>
The database was mounted on EX2, and seeding to EX1
DREX1 has no issues.<o:p></o:p>
All the DAG networks were in a good status, all Green and all up. I could ping from
EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
fix, but after rebooting EX2, it all resolved. It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
was all healthy.<o:p></o:p>
We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
issue occurred; a status of Disconnected and Resynchronizing, and after about
30 seconds, the status would show Resynchronizing.<o:p></o:p>
The database was mounted on EX2 and seeding to EX1 again. I did not notice the
issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
Late Monday morning, my boss and I were looking at more articles, but all the same results,
delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
I mentioned that it was strange because the networks were all up. What made us try the next
scenarios was just "luck" I guess. I made a statement about not remembering
which networks DAG replication took place over. Again, we have a LAN and
a BACKUP network. Bother were listed to use replication, so we decided to
disable replication over the BACKUP network in the EMC. Immediately, the
database copies switch to healthy and started seeding.<o:p></o:p>
Later that evening I enabled replication over the BACKUP network and it failed again with
a status of Disconnected and Resynchronizing, and after about 30 seconds, the
status would show Resynchronizing. I disabled the replication over the
BACKUP network and the database copy went back to healthy<o:p></o:p>
The last round of windows updates were pushed to these boxes the Friday before the
issues began, 2/28/14. I don't believe the updates to be the issue. <o:p></o:p>
Can anyone make any suggestions as to where to look? It worked with the BACKUP
network enabled to so long that is eluding me as to why the issues would start
all of a sudden. I am also confident that the switch configuration for the
BACKUP network has not been changed at all in at least 2-3 months. I am
still open to look at the config. Please help if you can.<o:p></o:p>
<o:p></o:p>
Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
the database copies so that I can be alerted when the status changes. We
use WhatsUpGold 16.2 to monitor the devices. <o:p></o:p>
Thanks for any future assistance.<o:p></o:p>
Ian
Ian

You don't have to enable the Replication on Backup Network.
You should collapse your DAG network.
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
Post the result of Below command:
Get-DatabaseAvailabilityGroupNetwork
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 DAG backup & Transaction logs

Hi,
What is Microsoft recommended best practise for Exchange DAG group backup in an environment where there are Active & multiple (2-3) passive copies of the databases?
Is it a good practice to backup transaction logs as frequently as possible in addition to daily full backup ? This I belive will allow to restore the DB to the latest possible state
using last good full backup & transaction logs (Like restoring SQL databases)
Thanks

Hi,
Windows Server Backup can't backup passive copy. If you want to backup both active and passive copies, you need to use DPM or other third party.
Here is a similar thread for your reference.
Exchange 2010 DAG Backup Best Practices
http://social.technet.microsoft.com/Forums/exchange/en-US/269c195f-f7d7-488c-bb2e-98b98c7e8325/exchange-2010-dag-backup-best-practices
Besides, here is a related blog below which may help you.
Backup issues and limitations with Exchange 2010 and DAG
http://blogs.technet.com/b/ehlro/archive/2010/02/13/backup-issues-and-limitations-with-exchange-2010-and-dag.aspx
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 MBX with a Exchange 2003 Frontend server. Coexist?

We currently have a exchange 2003 environment with 5 mailbox server and 1 front end server. We would like to introduce a 2010 Exchange MBX server. Is that possible? Do we just install the MBX role with CAS/HT?
Thnaks,

Hi
You need to have MBX,CAS and HUB all the three in Exchange 2010 else they wont be functioning without any one of them.
You can introduce Exchange 2010 server in Exchange 2003 server environment
Ensure you have at-least Exchange server 2003 SP2 else the it wont allow you to install Exchange 2010
You can only deploy Exchange 2010 in an Exchange 2003 organization that operates in native mode
Below article for your reference
http://technet.microsoft.com/en-us/library/aa998604(v=exchg.141).aspx
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Exchange 2010 - Outlook can only open 8 other users' calendars

I have a company that I moved to Exchange 2010 from Exchange 2003 recently. The old Exchange 2003 server has been removed from the organization. They have 30 mailboxes on a single server. Everything has been running smoothly but I have just discovered an issue.
In this office there is one person who coordinates meetings, decides who uses what conference room for a given meeting, etc. She has full access to all of the other users' mailboxes. With Exchange 2003 she could access all of the other users' calendars simultaneously and would view them in overlay mode in Outlook 2003 and/or Outlook 2007.
With Exchange 2010 she can only view the first 8 calendars she clicks on. If she tries to open a 9th calendar Outlook responds with the error message "The set pf folders could not be opened."
I don't believe it to be a rights issue as she can open any 8 calendars upon first running Outlook. To access any others she has to uncheck one or more of the calendars previously selected, exit Outlook, restart Outlook and select different users calendars.
This is only happening with Exchange 2010 - I've tested it on my Exchange 2007 server and another client's Exchange 2003 server and one can open as many other users calendars as there are.
Is this a known limitation of Exchange 2010 or a new bug? Any workarounds?

I'm betting that you have met the Exchange 2010 throttling policy......
Take a read through this post please, the section on throttling:
http://blogs.technet.com/b/rmilne/archive/2013/03/26/kicking-it-old-school-outlook-2003-partying-with-exchange-2010.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 Integration with Salesforce

Hello,
We are planning to integrate our Exchange 2010 environment with Salesforce. This is to sync the contacts and events for Salesforce users. They need us open the ports between Exchange 2010 servers and Salesforce servers. Is it fine if the ports are
opened between CAS array and salesforce servers ? or do we need to open the ports between all the exchange servers or salesforce servers? Please advise.
Thanks,

Hi,
Great information from both Derbyshire and Martin. Also find additional information for your reference:
Exchange Network Port Reference
http://technet.microsoft.com/en-us/library/bb331973(v=exchg.141).aspx
Thanks
Mavis Huang
TechNet Community Support

Exchange 2010 dag migration to exchange 2013 help

If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
A B -------------- C D
Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
A1 ----------- C1
B ------------- D
Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
A1 B1 ----------- C1 D1
Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
Anand_N

Hi,
When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
Migrating an Exchange 2010 DAG to Exchange 2013
http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 DAG's - 4 Mailbox Servers in 2 Datacenters with per site redundancy

I recently came into a company with an Exchange 2010 sp1 environment where there are two data centers in two different subnets (10.70.62.0 and 10.80.56.0)
Each datacenter has 2 mailbox servers (4 servers total) but their plan was to have only enough storage space to host 1/2 of the databases on each server. So instead of server 1, 2, and 3 being copies of each other, ServerA is a copy of ServerA and ServerB
is a copy of ServerB
Server     -    Databases
Site1mbA - Primary Database copy 1-10
Site1mbB - Primary Database copy 11-20
Site2mbA - Secondary Database copy 1-10
Site2mbB - Secondary Database copy 11-20
Normally if there were enough storage space I would keep a copy on each server and replicate within 1 DAG.
However since not all the databases are on each member server do I need to use 2 DAGS? 1st for Site1mbA & Site2mbA and 2nd for Site1mbB & Site2mbB
I feel I would need the 2 DAG's because with 1 DAG if Site1mbA server went offline the DAG couldn't switch to the Failover Cluster IP for Site2 because there are still active mailboxes in Site1 on Site1mbB.
Does that make any sense or am I over complicating it?
Thanks!

There is no rule that every server in a DAG must have a copy of every Database. You could do this with one DAG, but if the WAN goes down then the DAG will be active in only a single site not both.
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx#FourTwo
As illustrated in the previous example, using a single four-member DAG extended across two datacenters can provide high availability and site resilience for the mailbox services and data. However, if a WAN outage occurs, only the primary datacenter retains
service because it contains the majority of the voters. The datacenter with the minority of voters loses majority, and the DAG members in that datacenter lose quorum and go offline.
To deploy highly available Mailbox servers in a multiple datacenter environment, where each datacenter is actively serving a local user population, we recommend that you deploy multiple DAGs, where each DAG has a majority of voters in a different datacenter,
as illustrated in the following figure.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

I have AD and Exchange 2010 installed on different servers. can I control both with powershell from the AD server?

Hi all,
I have a lab env that include: 2 server 2012 with AD DS, 1 server 2012 with Exchange 2010, 1 server 2012 that I will install later Edge server.
I have a script that can build all my AD and Exchange infrastructure . This script was tested on single server that hosted both AD DS and Exchange.
My question is how to run the script let say from one of the AD DS servers and do his magic also on the Exchange server?
momu

Hi,
Take a look at this:
https://gallery.technet.microsoft.com/office/Create-a-new-implicit-5fdafe45
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

Exchange 2010 DAG Replication - too much data crossing the wire

I’m replicating 3 Exchange databases from our production active Exchange 2010 server across the WAN to another passive Exchange 2010 server at our DR site.
The Exchange server at the DR site does not have any active databases, i.e. no users are hitting that server.
We are running Update Rollup 8 for Exchange Server 2010 SP1 on both these servers.
The two sites are connected via a 10Mb/s MPLS connection and all the databases are in sync and the replication is working fine.
I have setup a network sniffer at the primary site and see a sizable amount of data crossing the wire from the production Exchange server to the DR Exchange server.
When I query the production Exchange server using the Tracking Log explorer and only choose the EventID ‘RECEIVED’ that should show me the amount of data that has been committed to the database.
If I choose a date range that is the same exact range that I have used to capture the raw data with my sniffer the amount of data the sniffer shows crossing the wire is 10 fold compared to what the Tracking Log Explorer shows.
If I actually count up the data in the LOG files it is about 20% more than what is crossing the wire but that seems to be because the DAG is compressing the data.
If in a one hour timeframe there is 500MB of data crossing the wire to the DR Exchange server the tracking log explorer will show only 50MB.
I would like to know why the data crossing the wire far exceeds the amount of data that is truly being sent/received from the primary exchange server.
Perhaps I’m simply not getting a true view of the amount of data being committed to the exchange server using the Tracking Log Explorer.
Maybe there is a better way to report how much data is being committed to the exchange databases.
Any assistance would be appreciated…

Two things.
1 - you must update Exchange to SP3 and a recent RU. Willard has already provided the links, which point back to my blog if you want to see the lifecycle map for Exchange 2010. SP1 has been out of support since January 2013. Time to move
on pllease
2 - Looking at the tracking log is not sufficient. I would not expect that to show everything.
I want to know what traffic you see as excessive. What ports are you seeing used here?
My money is on content indexing. CI will use additional traffic over and above log repl traffic. Expect CI traffic to be roughly the same again. You can test this by disabling CI on the database or stopping the services on the DR server.
To disable the CI for the database:
Set-MailboxDatabase DBName -indexEnabled $False
Or stop the Exchange search services on the DR box to leave production unaffected.
Again - you need to update Exchange. You would be better to do that now rather than when something breaks and Microsoft support cannot fully assist you since you are not uptodate.    I'll leave discussion of the security issues resolved
in recent Exchange RUs aside.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 DAG Failover does not works

Hi Experts,
I have a Exchange 2010 setup in a DAG environment. We have 2 MBX servers in the main site and 1 MBX server in the DR site , all part of one DAG. We have 2 HUB/CAS servers in the main site and 1 HUB/CAS server in the DR site.
Recently we had to do our BCP test for audit purpose. We had issues in doing failover to the DR site and below is the error faced.
Please advise urgently on the possible causes and resolution steps for it as we need to do this test again on the coming weekend.
"EvictDagClusterNode got exception Microsoft.Exchange.Cluster.Replay.AmClusterEvictWithoutCleanupException: An Active Manager operation failed. Error An error
occurred while attempting a cluster operation. Error: Evict node 'sme-ho-mbx01' returned without the node being fully cleaned up. Please run cluster.exe node <NodeName> /forcecleanup to complete clean up for this node.. ---> System.ComponentModel.Win32Exception:
The wait operation timed out"
So, basically one of the MBX server was not evicting from the Cluster due to which failover did not work.
Would appreciate some urgent thoughts for the possible resolution.
regards
abubakar
Md.Abubakar Noorani IT Systems Engineer Serco Ltd.

Hi,
Yes, you can run the Stop-DatabaseAvailabilityGroup without shutting down the Mailbox server. During the process of DAG failover to DR site, the Stop-DatabaseAvailabilityGroup cmdlet should be run against all servers in the primary datacenter. If the Mailbox
server is unavailable but Active Directory is operating in the primary datacenter, the Stop-DatabaseAvailabilityGroup command with the ConfigurationOnly parameter must be run against all servers in this state in the primary datacenter.
And please note that the Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of DagOnly.
Based on the error message, it seems that you should run the cluster node nodename /forcecleanup cmdlet against the specified node in the main site. Have you tried this to check the result?
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 dag with only 2 servers

Similar Messages

Maybe you are looking for