Comments on: Exchange 2010 DAG local and Site DR/Failover and Fail back/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/Microsoft Exchange & OWA Resources, Information - Optimize, Support, Manage | How-To | Guides | Reference | AdminSun, 01 Sep 2019 10:59:01 +0000hourly1http://wordpress.com/By: Amjad/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-22568Sun, 01 Sep 2019 10:59:01 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-22568Hi Krishna,
Excellent Article ….
Is it must to create new AD site for DR ? Can’t we add DR Site Servers ( Exchange & AD ) into Primary AD Default Site. ?

Please advise..

]]>By: Amjad/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-22567Sun, 01 Sep 2019 09:09:56 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-22567In reply to Baumchi.

Hi Krishna,

Can you please answer to Baumchi’s question because I also have similar doubt about odd & even in DR site.

Thank You

]]>By: Lincky/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-10317Sat, 02 Jan 2016 07:44:06 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-10317here I think you might be typo, the correct one should be

10.0.1.10 -NIC2 NIC1 – 172.168.1.10

Original Info

10.0.2.10 -NIC2 NIC1 – 172.168.1.10

Router

10.0.2.10 -NIC2 NIC1 – 172.168.2.10

]]>By: Triple5iks/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-9693Tue, 25 Aug 2015 01:46:47 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-9693Thankyou,detailed and so informative..

Simple question, could we perform drc switchover test without interupt on operational dc ?
An example if we only broke the link connection.
When the connection established and the replication occur, the stop-dag would applied and make the dc downtime.. Am i correct with this?

]]>By: vinod/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-8574Wed, 04 Mar 2015 14:40:14 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-8574Really good article , thanks evrybody

]]>By: Guru/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-8401Mon, 09 Feb 2015 06:09:09 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-8401Dear Krishna…

Do you have any post Similar article for “Exchange 2013 DAG local and Site DR/Failover and Fail back”

Thanks
Guru

]]>By: S.Nithyanandham/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-4811Sat, 12 Jul 2014 20:14:07 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-4811In reply to Krishna – MVP.

Hi ,

Thanks a lot for your response .I would like to clarify few more queries on my side .

Apart from last query ,Lets me explain you what is happening on my side , we had done the DR site failover as good as well and also all the databases get mounted in the DR site mailbox server .Even though by having such kind of a good DR site failover ,we cannot able to communicate to the exchange server in DR site by using the outlook clients in the production site .

when outlook clients in the production site tries to communicate to the exchange server in DR site it is not getting connected over mapi protocol (I.e over port no 135) ,instead of that it is getting connected to exchange server in Dr site over rcp over http protocol (i.e over port no 443).

We have good and stable wan link established between the production and the DR site .As per my knowledge i knew that the outlook client get exhaust while trying to connecting to exchange server in DR site over port no 135 (MAPI protocol). Because of that outlook is getting connected to exchange in DR site over port no 443 ( rpc over http) .

I don’t know which of my devices ( i.e router or firewall ) in the production site or DR site is blocking the outlook clients in the production site to get connected to exchange server in the DR site over port no 135 via mapi protocol .Please tell me how to find that and resolve this issue.

Steps handled on my side :

1. When i try to telnet to exchange server in DR site over port no 135 on outlook machine in the PR site and I found that it is working fine.

2. In addition to this ,when i try to configure and connect the outlook client machine on the same subnet where the DR site exchange server is residing , i can able to connect to the DR site exchange server without any issues with the help of that outlook client .

Please help me out on this issue

Thanks
S.Nithyanandham

]]>By: shishir/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-1823Tue, 03 Dec 2013 15:51:00 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-1823Hi Bro,
I have 2 exchange 2010 Sp3 (MBX/CAS/HT) servers in a DAG installed on windows 2008 R2. I have configured FSW on non exchange server on the same site which is windows 2012 server.The cluster is online and failover/failback happens properly. When we perform test-replicationhealth for any of the members of this DAG from the other exchange servers in the same organisation, I get the result as file share quorum failed with error “couldn’t access the file share witness share”.

Where as exchange trusted subsystem group already has admin rights on the server where we have configured FSW.

Please provide your input and suggestion to over come this issue.

Thanks
Shishir Kulkarni

]]>By: ytsionis/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-1818Mon, 18 Nov 2013 19:47:40 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-1818you showed very good analytical skills keep going to share knowledge thk u

]]>By: Tufail/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-1817Mon, 11 Nov 2013 11:57:14 +0000/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/#comment-1817“Excellent Document” keep going cheers!

]]>