Exchange 2013 DAG - Failover Cluster Warnings

I have two new Exchange servers (PROD1 and DR1) that I recently updated to CU8 in preparation for going into production. After reboots, I noticed that I had a warning on the "Server Manager" window.
PROD1 lists itself, DR1, and DAG1 as servers though it marks DAG1 as not accessible.
DR1 lists only itself and PROD1. It does not list DAG1.
PROD1 is generating a ton of failover cluster errors (1205, 1254, 1069, 1044) while DR1 is clean.
In the Failover Cluster Manager of each server, the object of DAG1 is listed as "Offline". It has two IPs - one for each of the Exchange servers' subnets (this is where I think I screwed up). The IP for PROD1's subnet is 10.2.8.131
and is "Failed" and the IP of DR1 is 10.4.8.131 and is "Offline". The IP of PROD1 is 10.2.8.132 and DR1 is 10.4.8.132.
Attempts to bring the cluster object online fail "due to the failure of one or more provider resources".
The instructions I followed to set up the DAG did not mention the need for multiple NICs. I now think this is incorrect and would be willing to use separate subnets and NICs for the DAG if necessary. (I could use 10.2.12.X and 10.4.12.X instead.)
I am currently still able to fail the database copy between DR1 and PROD1 without any problems.

Hi Jkm,
As you said :PROD1 is generating a ton of failover cluster errors (1205, 1254, 1069, 1044) while DR1 is clean.
I suggest you post failover cluster errors to
[email protected] for our troubleshooting.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Similar Messages

Configuration Exchange 2013 DAG on two Server Data center 2012 with Hyper -V roles

Dears,
I try to planning and installation two hosts ( Data center 2012 servers) then install Hyper-V role on both this server, then create VM on each Data center server to be install Exchange 2013 on them.
After that I want to configure DAG between Exchanges servers, so what are the prerequisite to do that ?
Note: I use external IBM storage that will be located all VMs and DAG
Many thanks

Hi Moon,
In addition to Gulab's suggestion, I would like to clarify the following things:
1. Yes, we can use Standard or Datacenter version of the Windows Server 2012 operating system to configure Exchange 2013 DAG.
2. Each member of the DAG should be running the same operating system.
3. The DAG with an even number of members should have a witness server. A witness server is a server outside a DAG that's used to achieve and maintain quorum when the DAG has an even number of members.
What's more, here are some helpful articles for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx#HR
High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2013 DAG with VMWare Clustering

Hi team,
I'm looking at a scenario where there are 3 Hosts with a SAN for storage and is
Clustered for failover with so many other server/applications. The requirement is to have a High Available environment with Exchange 2013. Now I want to know the possibility of having 2xCAS (WNLB) and 2xMailbox Servers with DAG.
1) Want to know if this is a supported scenario, where DAG is implemented in a VMWare cluster.
2) The DAG on cluster is to ensure that even if no host failure occurs i have VM level failover. and if Host Level failover occurs I have cluster based failover.
Any guidance is much appreciated.
Thank you.
Cheers!

Hello,
It is not supported configuration that combining VMware HA solution with the Exchange application-aware high availability solution.
Here are some articles for your reference.
http://blogs.technet.com/b/keithmayer/archive/2012/08/28/best-practices-for-virtualizing-microsoft-exchange-2010-msexchange-itpro-hyperv-vmware.aspx#.Uxfd2P7xuM8
http://exchangeserverpro.com/microsoft-vs-vmware-on-exchange-virtualization-and-ha-best-practices/ (
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.)
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

DAG Failover Cluster Service Errors

Hi all,
I have six Exchange 2013 SP1 mailbox servers installed on Server 2008 R2 configured in two seperate DAG's (3 and 3).
I'm using a single NIC on all the servers for replication and server connectivity.
I pre-staged the DAG computer object in AD (and assigned permissions), and configured DNS entries for both (confirmed and resolvable). I also configured the DAG network subnet and DAG IP address via EAC.
At the moment I have active DB's on each server and then a passive copy on each other server, and all instances are healthy.
However, when I look in the WFC on each server, there are a ton of errors in the cluster event logs. All of the nodes show up as green, along with the cluster network, but the cluster shows "The cluster network name is not online".
Cluster resource 'Cluster Name' in clustered service or application 'Cluster Group' failed.
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'contoso.com' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
The cluster identity 'DAG$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.
I've removed and re-added DNS records, and double checked the permissions on the CNO object. What else can I do?

Hi,
Its not a good idea to add a static DNS-Record for the DAG - Remove it and on the member holding the PAM, run ipconfig /registerdns.
Martina Miskovic
It also turns out that the CNO objects were never re-enabled by Exchange during the DAG creation process. Once I followed your steps above, and manually enabled the object in AD, the DNS entries auto-populated and everything came online.
Thanks for the help!

Test-ReplicationHealth Database Redundandacy and Database Avaliability *FAILED* Exchange 2013 DAG setup

Trying to setup DAG between 2 exchange 2013 servers - one of them being in the remote location with physical point to point line. We have no firewall rules between 2 locations
EX01 ( on site)
EX02 (remote)
ETH01 10.11.1.2/24 - MAPI                       ETH01 10.11.13.15/24
ETH02 10.0.0.1/30 - REPLICATIOn            ETH02 10.0.0.2/30 - REPLICATION
Witness server is in 3rd remote location
These are the test results I get from Test-ReplicationHealth and Cluster Network Validation
I also run a Nmap command to make sure udp port 3343 is open on both sides
alex serdyukov

Hi,
The error message said that current Redundancy Count was 1 but expected Redundancy Count was 2. Therefore, Database 'IT2013' does not have enough copies configured to meet the validation criteria.
Please replicate that database to another server at least. We can refer to Hinte's suggestion to
add another copy for the database 'IT2013' in the DAG then check whether the issue persists.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

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 2013 DAG / client access

Hello
I'm in the planning of a new Exchange 2013 infrastructure. The infrastructure will be located in a datacenter and should host about 1000 mailboxes. I have read many whitepapers and tutorials, but some things are still unclear to me.
- Microsoft suggests multi-role servers for this amount of users because client access is no more than a reverse proxy in EX2013. Is this correct? I've read that one users with 200 mails/day needs 8.5 MCycles with only DB and 10.63 MCycles with DB and CAS
on the same server. So I plan to start with 2 multi-role servers in a DAG. What's your oppinion on this?
- Client connections: I assume the clients connect to the cluster IP of the DAG. How do they get directed to the server on which their database is online? Does each server need to have the cluster IP and a public IP to which the clients connect?
- SMTP: As I understand the documentation, mails are sent from the server which the user is active on. (Which makes sense for high availability.) What is best practice regarding the protocol logs? Do the support employees need to search in the files on 2
servers?
Thank you very much for your input!

Hi
I would use the firewall for load balancing unless there is a technical reason why this is not possible. NLB is not recommended as it is not service aware - you cannot configure a probe to test OWA is working for example - so if you already have something
better that would be my choice.
In the choice between IIS ARR and NLB or CAS and NLB I would go for IIS ARR as this reduces you license costs, but neither of these is better than the appliance/firewall option.
I've never used NLB for load balancing other than on TMGs so I cannot say what the performance is like behind a firewall, in theory your assumption would be correct.
The load balancer doesn't make this decision it just spreads the load between the active servers, the CAS role connects the use session to the correct mailbox server:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Steve

Exchange 2013 DAG with single site and 2 multi-role servers with error "MapiExceptionIllegalCrossServerConnection"

Hi,
I've got a lab with a domain controller and an Hyper-v with on it two multi-role exchange 2013 CU7 servers on W2K12 R2 OS, configured in DAG semplified (but the problem is the same also if I use the classical DAG configuration), a witness server, and a L7
load balancer for the exchange servers.
When I made the test to disable the OWA application pool where I've got the active mailbox database of the user, the balancer in correct manner redirect the session to the other exchange multi-role server, but the client in his OWA session is no more
able to send new mail with the error "Error your request can't be completed rigt now. Please try again later."
The only strange log that I see on the server in the MAPI client access directory where there is the following error message:
2015-01-21T08:00:45.132Z,956,1,/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt,,Microsoft.Exchange.RpcClientAccess.Monitoring.dll,15.0.0.0,Cached,,,,MapiHttp,Client=Microsoft.Exchange.RpcClientAccess.Monitoring,R:4ab7b6c8-54ee-4be3-aa9d-f8c856c4c47c:2,C:MAPIAAAAAOC4+7OCoZOjkqeKuoumlKSEtYO5ibyGs4bc/879z/vD9sX1zP28AwAAAAAAAA==|S:0-mGmHRQ==,OwnerLogon,0x6BB
(rpc::Exception),00:00:00.0310000,"Logon: Owner, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt in database last mounted on Exch2.lab.net",RpcEndPoint: [ServerTooBusyException]
Client is being backed off -> [ClientBackoffException] Mailbox was moved to a different mailbox server. A client needs to retry. -> [IllegalCrossServerConnectionException] Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt.
-> [MapiExceptionIllegalCrossServerConnection] Monitoring mailbox [] with application ID [Client=MSExchangeRPC] is not allowed to make cross-server calls from [Exch1.lab.net] to [Exch2.lab.net] [diag::AAAOAAAA/wAAAAAAAAAAAgAAAAA=],,,[email protected],
The CAS try to access the mailbox on the other server, but without success.
Someone have idea how to solve?
Thanks

Hi Hinte, sorry for the answer delay.
I've run the command you suggest to check the HealthMailbox status, but seems that all are fine:
[PS] C:\Windows\system32>get-Mailbox -Monitoring | ft name, servername
Name ServerName
HealthMailbox7021deb6ae104dadbf52feedfa7fa68b exch1
HealthMailboxb83c9040b32e4d1197f7f54f6709bb7f exch1
HealthMailboxb1c32037890b43fbb2af2efe7c36ba00 exch1
HealthMailbox8d174269b494458daf9ade5099e22845 exch1
HealthMailboxaa7d10f02d2d4cc588243b291ead3e3a exch1
HealthMailboxeb32c30a019f42968a7cbc49a6ac3e65 exch1
HealthMailboxc6ff1d36ba154c5db5411b44718edcbd exch1
HealthMailbox75dc7caa7e8c4a3b812a01b607536d48 exch1
HealthMailbox16c86e512f454e7890b80c180ce19c00 exch1
HealthMailboxc6e447f7dba24d9b913f1dfcabe9f927 exch1
HealthMailbox40fa5a3f2abc4accae6286cd98abc90a exch1
HealthMailbox2712b9544bad4e7b8b671be2cda8cfde exch2
HealthMailboxe2559124da20499386bf8103dcb21e9b exch2
HealthMailbox3264c6078dad45d4a78c56a3afe81df1 exch1
HealthMailboxacacc51eb8bc4717b295ddf0adccf77e exch2
HealthMailbox64c4dd8cddac4c4e8bb7314010e797b1 exch1
HealthMailbox4a92bfa14fdd47fbb27c19513f6d2beb exch2
HealthMailbox465d2a69de93430e84b4d699a88cb0c3 exch1
HealthMailbox97b578e57cd44204820fffa416b25633 exch2
HealthMailboxb411059771db4647bb775c665ec29440 exch1
HealthMailboxf981dde6f4134f839bf41eb0000434e4 exch2
HealthMailboxc33801c7c3b1474f8aa6065249bb4fca exch1
HealthMailbox2282128ed8d14937998212edd15adf20 exch2
HealthMailboxe3d12b756cf545239b38be4607904ae1 exch2
[PS] C:\Windows\system32>
Regarding the test sugested to diable instead the OWA App Pool only the OWA virtual directory, I've not found on IIS the possibility to stop the access to this virtual directory.
Also on exchnage Administration page there is no the possibility to switch off this virtual directory only (or I don't found where is this setting).
Regards

How do you delete specific message from users in Exchange 2013 DAG database?

Our network has been inundated with spam from INTUIT.COM with the SUBJECT: PAYMENT OVERDUE and contains a link to download a form from a Dropbox. Obviously, very suspicious and clearly spam. We're using Postini as our Edge Transport/ Spam filter but messages
are still getting in. I've enable anti-spam on all my mailbox servers, set the SCL values but that hasn't worked.
I understand that Exchange Edge Transport role has the more aggressive spam fighting features but Microsoft also recommends an online spam filter.
Needless to say, we've taken steps to quarantine those messages based on subject and sender in Postini but now would like to delete those messages from the users in went to. My users are two different DAG mailbox databases. I found this article http://www.techieshelp.com/delete-mail-from-multiple-mailboxes/ but
the command didn't work. I'm thinking its because I have DAG and a couple of databases. I even tried "get-mailbox -database "databasename" | search-mailbox -searchquery subject: "Payment Overdue"" and that didn't work.
I'm running Exchange 2013 SP1 DAG across two sites comprised of four 2013 SP1 mailbox servers.

Check this out
http://technet.microsoft.com/en-us/library/ff459253%28v=exchg.150%29.aspx and specifically look at the section titled "Search messages and log the search results"
Or you can use this
http://technet.microsoft.com/en-us/library/aa996371%28v=exchg.150%29.aspx with the WHATIF parameter
Alternatively if you are open the 3rd party solutions check out Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp
which would allow you to see the search results and then delete OR if desired you can set the On FIND action to Export to PST and then Delete so that you can preserve and then remove messages on the fly as the search system finds
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Verifying correct setup for Exchange 2013 DAG

This should be a relatively simple question. I've just set up the DAG on my new Exchange 2013 deployment, it spans two servers, MB1 and MB2. Both are dual-horned, on both a replicator subnet and the LAN. I notice that the 2013 DAG is automatically
setup by default, so I want to make sure it's been setup optimally. I'm going by this article:
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
My main concern is it looks like I should be seeing two DAG networks set up, as per this:
Enumerated DAG network settings for a multi-subnet DAG
Name
Subnets
Interfaces
MAPI access enabled
Replication enabled
MapiDagNetwork
192.168.0.0/24
192.168.1.0/24
EX1 (192.168.0.15)
EX2 (192.168.1.15)
True
True
ReplicationDagNetwork01
10.0.0.0/24
10.0.1.0/24
EX1 (10.0.0.15)
EX2 (10.0.1.15)
False
True
But I'm only seeing a MapiDagNetwork in my list of DAG Networks. Did it fail to install the ReplicationDagNetwork? If so, what's the best way to go about fixing it? Seems preferable to keep the automatic setup.
----------- Ron E Biggs Network Administrator Entertainment Studios

Hi,
I am just writing to check on the status of the problem.
Is there any update on this issue?
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

What new in Exchange 2013 DAG

Hi Team,
What's the difference between Ex2010 & Ex2013 on DAG enviroment.

Hi,
The articles provided above are very helpful, one thing I like is that we can now use a third location for hosting the witness server. This is not recommended or not possible in previous versions of Exchange.
If you deploy the DAG's witness server in the third location, then the DAG can automatically failover databases to the other datacenter in response to a datacenter-level failure event. In Exchange 2010, we have to failover to another datacenter manually.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 DAG configuration help

Please help on E2013 DAG as step by step.
Microsoft direct FSMO query

Hi,
The following articles may help you.
http://blogs.technet.com/b/winde76/archive/2011/03/23/step-by-step-create-a-database-availability-group-dag.aspx
https://gallery.technet.microsoft.com/office/Install-Exchange-server-b5cce9e4
Best regards,
Belinda Ma
TechNet Community Support

How do you assign a user or group FULL access to all Exchange 2013 DAG mailbox databases?

How do you assign a group or user FULL mailbox access rights to ALL mailboxes in the Organization or DAG mailbox databases?
Commands I've tried with no avail:
get-mailboxdatabase -server “exch01″ | add-adpermission -user “domain admins” -AccessRights GenericAll
get-mailboxdatabase -identity "DAG database" | add-adpermission -user "user" -accessrights FullAccess
Please let me know if you can help! Thanks.

Get-Mailbox | Add-MailboxPermission -Identity UserMailbox -User "Domain\Group" -AccessRights FullAccess - worked for me! Thanks again!

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2013/2010 coexistence DAG functionality?

Hi, so this is a bit of a silly question. But I need to make sure I understood the situation correctly.
I currently have an Exchange 2010 DAG with 2 servers and I am mid way through (In the Exchange Server Deployment Assistant) introducing my first Exchange 2013 server.
The plan is to make the new 2013 server the active DAG member one of the old 2010 servers the passive member for a short term until that 2010 server is rebuilt to 2013, but that's not going to work is it? Once I migrate a 2010 user to a 2013 database, that
user only exists in 2013, right?
Theres no way of adding a 2013 database into a 2010 DAG, so that if the 2013 server is down, the 2010 server will become active?
Thanks

No, there is not. You will build a new Exchange 2013 DAG and move mailboxes from Exchange 2010 to Exchange 2013 mailbox databases.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 DAG - Failover Cluster Warnings

Similar Messages

Maybe you are looking for