Database DAG Failover

We have a 2 node DAG cluster. The database are evenly split between the two servers. The other day all databases moved to one of the DAGs. Normally when this happens I expect to see a server reboot or some sort of failure. But there
was none. I could not find anything in the event logs to advise as to what happens.
Does anyone know where else I should be looking and if there is any way to alert when databases move from one node to the other?
Thanks
Paul
Paul Glickenhaus

Hi,
If you are checking the event viewer in the following location you can find the associated event entries corresponding to DAG
Event Viewer>Applications and Services logs>Microsoft>Exchange>High Availability>
Regards from ExchangeOnline.in|Windows Administrator Area | Skype:[email protected]

Similar Messages

Exchange server 2010 DAG failover

Hi team ,
We have configured exchange server 2010 in DAG environment .
We have added 3 mailbox server in DAG . but my active mailbox copy failed the database are failover to another passive copy server & status is mounted . after failover emails service are not working.
Note : We have also configured NLB on CAS server .All exchange servers placed in single AD site
Please suggest

Hi
So are all your exchange servers the same? settings?
have you tried to fail the DB back to its original server? all services started on the other server?

Outlook looses connectivity after DAG Failover

Hi team,
Im running a lab environment with 2xCAS (WNLB) and 2xMBX (DAG) servers. Since it's a lab environment I've set the DC as my FSW. All Virtual Directories are pointing to 'mail.contoso.com' pointing to the two CASs which is WNLB'ed.
To test the DAG Failover I set up a Database(MDB01) on MBX Server 1 which is active, made a passive replica on MBX Server 2. I shut down Server 01, which holds the active databases mounted. meanwhile two clients were running and both were connected. Once
the server got shutdown, both clients(Outlook 2013) went to 'Trying to connect to server' status.
Meanwhile checking the powershell on the Mbx Server 02, i noticed that the database was mounted. Went back to clients and open'ed up OWA, working as normal. However, the outlook client is still stuck in the 'Trying to connect to server' status. And
i opened up the 'Connection Status' and tried to 'Reconnect' but still no luck. I had to close and open up outlook to get back into the 'Connected' mode.
Any idea why this might be happening?
*Since unlike Exchange 2010's CAS Array architecture is no more there I didn't made any changes to any RPCClientAccess.... attribute. Both mail.contoso.com and autodiscover.contoso.com are pointed to the VIP of the CAS WNLB.
Cheers!

Hello,
After you configure a single namespace, you need to restart outlook to connect the newly configured namespace.
Before DAG Failover, I recommend you use netstat -ano | findstr ":80" command to check your outlook connect to CAS server.
In order to check the issue, please do DAG failover again, and then use netstat -ano | findstr ":80" command to check your outlook connect to CAS server.
Additional article for your reference. (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.)
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support
Hi Cara,
Yes, here's the result from the query.
[IMG]http://i57.tinypic.com/im01na.png[/IMG]
But whenever i restart the client it gets connected in no time. I'm confused in why after a manual DAG failover this happens.
Manual failover - I shut the active copy, the passive copy was also down for around 15 mins, booted up the passive server, it said Databases as Disconnected and Active Manager error in getting them mounted up and had a 99234343231 of CQL. So
to mark the server active did a 'net start clussvc /forcequorum'. This got the databases mounted up. But clients, they doesn't get connected automatically :(
UPDATE - The client got connected after like
15 mins. :s

Oracle Database down /failover clause ?

hi
I am collecting the information regarding oracle database down / failover clouses , so all of you requested kindly send me your experience regarding Oracle database down/failover reason/clause.
thanks in advance
regards

Hi,
Are you looking for notes or scenarious.
If you are looking for some notes follow the below link:
http://pavandba.wordpress.com/category/dataguard/
Thanks,
Rafi.

Database link failover on RAC

Dear Friends.
Could you please provide me the information about implementation of Database links failover in RAC. (Oracle 10g RAC on linux)
I have created db links across the two RAC environments. Each RAC setup contains 2 nodes.
I have created DB link across the two RAC environemtns.
i.e I have created DB link between 1st node of Source RAC system to 1st node of Target RAC system.
If 1st node of Target RAC system is down, I need to setup in such way that the link should failover to node 2 of Target system.
I have tried all possible options of TAF. But I did not succeed. Is there anybody is implemented this type setup...?
How to setup tnsnames.ora on source DB to get this type of failover.
Thanks in Advance.
Best Regards
Kanumuri Raju

Oracle was kind enough to provide some configuration details in their docco. You may want to review this link:
http://download-east.oracle.com/docs/cd/B19306_01/network.102/b14212/advcfg.htm#sthref1275
The configuration needs to be performed in the TNSNAMES.ORA associated with the database initiating the link. If you want bi-directional TAF, you would need to update the TNSNAMES.ORA for 'both' databases.
I suggest you don't get your hopes up too high about the capability of TAF across DBLinks. I'm pretty sure you will not be able to get SELECT-based TAF. And I'm not absolutely sure which session rules will be used to determine the failover time.

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 - 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

3 Node DAG - Failover??

I have a Dag setup,
Main Site:
MB1 (2010 SP1)
MB2 (2010 SP1)
3 node CAS array
DR Site:
MB_DR (2010 SP3) - Running as CAS
I am working through installing SP3, DR site has been completed, all the CAS servers have been completed. I set MB2 to maintenance mode using .\startdagmaintenance.ps1 - confirmed all mailboxes were off the server.
I started installing Windows patches and rebooted several times, then one round of patches took out the network interfaces, this meant the server lost access to the SAN and the cluster service failed. This caused the mailboxes all to initiate a failover
to the DR server!
Now couple of questions:
1) Since the DAG member was in maintenance mode should the fact the cluster service failed cause the DAG to initiate a failover? I have to patch MB1 and know the network is going to do the same thing so want to stop this happening again.
2) The DAG is in DAC mode, I didn't think that it should auto failover to the DR site?
Thanks
Richard

Hello Rhoderick
Thanks, I have been reading through your posts. Below is the output of running the Packets Received discarded script
Processing server: OLD 2003 to be decommisioned
InstanceName
CookedValue
hp nc371i multifunction gigabit server adapter _2
0
ms tcp loopback interface
0
Uptime In Days: 673
Install Date 20/12/2007 12:24:29
Processing server: CAS01 (this holds the file share Witness) - Virtual
vmxnet3 ethernet adapter _2
0
vmxnet3 ethernet adapter
143757
Uptime In Days: 6
Install Date 18/11/2011 12:07:20
Processing server: CAS02 - Virtual
vmxnet3 ethernet adapter _2
0
vmxnet3 ethernet adapter
0
Uptime In Days: 5
Install Date 18/11/2011 15:00:01
Processing server: CAS03 (Physical)
hp nc373i multifunction gigabit server adapter _38
0
hp nc373i multifunction gigabit server adapter _39
0
Uptime In Days: 3
Install Date 10/01/2012 13:44:22
Processing server: MB_DR (Physical)
xsigo vnic dag_hb_254 [psdrd01]
0
hp nc373i multifunction gigabit server adapter _42
0
hp nc373i multifunction gigabit server adapter _43
0
xsigo vnic drmapiv253 [psdrd01]
0
xsigo vnic driscsi237 [psdrd01]
0
Uptime In Days: 20
Install Date 12/01/2012 11:10:13
Processing server: MB1 (Physical)
hp nc373i multifunction gigabit server adapter _42
0
hp nc373i multifunction gigabit server adapter _43
3171
xsigo vnic iscsi_b1 [psd02]
0
xsigo vnic hbv251_a [psd01]
0
xsigo vnic iscsi_a1 [psd01]
0
xsigo vnic hbv251_b [psd02]
0
Uptime In Days: 25
Install Date 28/11/2011 15:27:52
Processing server: MB2 (Physical)
hp nc373i multifunction gigabit server adapter _43
0
xsigo vnic hbv251_a [psd01]
0
xsigo vnic iscsi_a1 [psd01]
0
xsigo vnic iscsi_b1 [psd02]
0
xsigo vnic hbv251_b [psd02]
0
Uptime In Days: 2
Install Date 29/11/2011 09:46:09
The Results of the Check Event 1135 is
MB_DR :- 50
MB1:- 103
MB2:- 102
There has been an issue for a while (I have only worked here 2 months, but logs show going back a year and increasing frequency where the mailboxes are failing over to the other node, normally 8 databases are split 4 on each MB1/MB2 and the Mailboxes usually
move to MB2. I have increased the timeout values of the cluster and we haven't seen the Databases move in over a week (except when patching MB2).
It looks like there are lots of errors for CAS01's Production vNIC - could this be an issue seeing as it is the FSW?
Thanks for your help, if I can get this cracked it could help me pass my probation period :)

Need DAG Failover/ switchover monitoring email alerts

hello
I want to setup email alerts on exchnage 2010 DAG.
Like when a switchover happened
DAG mailbox failure
Can i set these with windows or i have take any third party utility

Hi,
Sometimes we need to know when a database failover to another server automatically, even though there are no problems for end users. To monitor database failover in DAG, you can check the following article.
Monitor Databases in DAGs
http://letsexchange.blogspot.com/2011/08/monitor-databases-in-dags.html
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.
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Mailbox move during DAG failover is stuck

I have a DAG setup on exchagne 2010. I had several mailbox moves going, some in progress and some queued. The destination mailbox database failed over to a different server. Now the inprogress and queued moves are stuck and I cant
suspend them. Any suggestions would be great.
Thank you

I have a DAG setup on exchagne 2010. I had several mailbox moves going, some in progress and some queued. The destination mailbox database failed over to a different server. Now the inprogress and queued moves are stuck and I cant
suspend them. Any suggestions would be great.
Thank you
At some point they should resume.
What does get-moverequeststatistics show for the status?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

How to re-build the Production database after failover

We have performed a failover in our environment by the below method . It was worst we are not able to bring up the production the only choice left over is failover.
We have enabled the flash back and created a checkpoint then failover.
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
9221
SQL> alter system set db_recovery_file_dest_size=14G;
System altered.
SQL> alter system set db_recovery_file_dest='/u01/oradata/flashback';
System altered.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database flashback on;
Database altered.
SQL> create restore point before_open_standby guarantee flashback database;
Restore point created.
SQL> alter database activate standby database;
Database altered.
SQL> select database_role from v$database;
DATABASE_ROLE
PRIMARY
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
9221 (This is the log sequence same after the failover also)
after the we have nearly some 30 log sequence are generated but it started from the no 1.
Now we need to rebuild the Production DB and to sync with the standby.. please help us with the steps and suggest some documents.

Hi,
Please take a look at this http://shivanandarao.wordpress.com/2012/08/28/dataguard-failover/
SHANOJ
Handle:     SHANOJ
Status Level:     Newbie (5)
Registered:     Feb 15, 2006
Total Posts:     154
Total Questions:     *25 (21 unresolved)*
Name     SHANOJ
Location     Chennai - India
Occupation     DBA
Biography     OCP 10G, LPI, ITIL V3
If you feel your questions have been answered, then please consider closing your threads as answered by providing appropriate points rather than leaving it open. Follow the forums etiquette.

What event should I use to remotely monitor a 2010 DAG failover occurence

I have a 2 Exchange 2010 servers installed on Server 2008 r2. Both have all roles, one is used as the primary server and the second is a passive back up. My question is about how to monitor when a database fails over to my passive server. It seems like there
should be an event logged, probably on the server that is taking the active copy since in theory the other one is non responsive for one reason or another. I've dug through the logs and I've found some events that seem to occur around that time, but nothing
that definitely says that a failover has occurred. Can anybody point me towards a reliable method of monitoring this?
Thank you in advance, Joel

A number of event logs can fire when there is a failover, but the most commons ones are:
Alternatively, test in the lab and grab the events as you bounce servers.
Log Name: Application
Source: MSExchangeIS
Date:
Event ID: 9796
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
Database "<Database" has been subject to a lossy failover. The database may be patched if the Information Store detects it is necessary.
and
Log Name: Application
Source: MSExchangeRepl
Date:
Event ID: 2099
Task Category: Service
Level: Information
Keywords: Classic
User: N/A
Computer:
Description:
The Microsoft Exchange Replication Service requested that Hub Transport server ...
and
Event ID: 2153
Source: MSExchangeRepl
The log copier was unable to communicate with server ''. The copy of database ' is in a disconnected state. The communication error was: An error occurred while communicating with server ''. Error: Unable to read data from the transport connection: An established
connection was aborted by the software in your host machine. The copier will automatically retry after a short delay.
Event ID: 4082
Source: MSExchangeRepl
The replication network manager encountered an error while monitoring events. Error: Microsoft.Exchange.Cluster.Replay.AmClusterApiException: An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API
'"OpenCluster() failed with 0x6d9. Error: There are no more endpoints available from the
Twitter!:

Database Mirroring failover

Hi,
I have configured mirroring, server A and server B, suppose if server A down, what are the action we need to tak bring up principal server.
Thanks in advance
Shashikala

Thank you. If we configured as safety with automatic failover. In this case mirror server will come online automaticaly if pricipl server down? or do we need to follow above steps to come nline.
Thanks
Shashikala
If witness is configured and principal is down and witness is able to form quorum with mirror automatic failover will happen. If quorum is not being formed anyhow for some reason no automatic failover will happen and then mnual failover will be required.
See various scenarios mentioned in below link (Database Mirroring Availability Scenarios)
Database mirroring in SQL server
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Outlook not connect to mailbox after DAG failover

Hi,
I have very annoying problem with Exchange Server 2013
on my production servers.
Below is my setup
DC – Windows Server 2012
CASHUB1 – Windows Sever 2012 (Exchange 2013 Standard)
CASHUB2 – Windows Sever 2012 (Exchange 2013 Standard + Witness Server)
MBX1 – Windows Sever 2012 (Exchange 2013 Standard)
MBX2 – Windows Sever 2012 (Exchange 2013 Standard)
So what's happening? After I move user's mailbox database from MBX1 to MBX2, Outlook (2007 with latest update and 2010 with latest update)
is being redirected to the server that holds the mailbox, and it’s ok. But, the problem arises when I turn off MBX1 and leave only MBX2 running - users are not able to connect to the MBX2. The moment the operating system on MBX1 is started, users connect to
MBX2 smoothly and everything works fine.
My DAG is working fine because when I turn off MBX1, MBX2 detects that change, and in a few seconds the database becomes active on MBX2.
So, DAG works perfectly, but since the MBX1 is turned off no Outlook client can connect to MBX2.
Also, if my Mailbox database is mounted on MBX2 and if
turn of MBX2 in a few seconds the database becomes active on MBX1 and Outlook client get connected on MBX1.
Thanks

Hi,
As far as I know, in Exchange 2013, Outlook clients don’t rely on the value stamped in the “RPCClientAccessServer”.
According to the error, we can try to Disable IPv6 & Change Hosts file:
http://www.julianben.com/2013/04/22/the-rpc_s_server_unavailable-error-0x6ba-was-thrown-by-the-rpc-runtime-process/
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.
Thanks,
Angela Shi
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!

Database DAG Failover

Similar Messages

Maybe you are looking for