Parent Site

WIN2012R2 DC1 - 10.1.1.2

Exchange 2013 MBX & CAS - 10.1.1.3

DATABASE : MBXDB1

DR SITE

WIN2012R2 DC2- 10.1.2.2

EXCHANGE 2013 MBX & CAS - 10.1.2.3 (MBXSRV2)

DB NAME MBXDB2

ECP, OWA Works fine with Parent Site, the DR site server sees parent server databases but parent server not synching or seeing DR Exchange server. 

While executing Get-mailboxdatabase -Status | select name, mounted from DR site exchange server in EPS.

Name Status 
---- ---------
MBXDB1 mounted
MBXDB2 mounted 

but when checking from Parent site.

Name
----

MBXDB1 mounted
MBXDB2

WARNING: Exchange can't connect to the Information Store service on server MBXSRV2.domain.local. Make sure that the
service is running and that there is network connectivity to the server. 

Checked the services, running on both servers. Any idea what could be the issue? 

Hi ,

1.Is that servers are in DAG ? If so please share me the output for the below mentioned command.

get-mailboxdatabasecopystatus * | ft -au

2.Then check all the core exchange services are up and running in all the exchange nodes.

test-servicehealth

[PS] C:\>get-mailboxdatabasecopystatus * | ft -au

Name                              Status      CopyQueueLength ReplayQueueLength LastInspectedLogTime ContentIndexS
                                                                                                          tate
----                                   ------      --------------- ----------------- -------------------- -------------
MBXDB1\HQEXCH01         Mounted     0               0                                      Healthy
MBXDB2\DREXCH01         ServiceDown 0               0                                      Unknown

[PS] C:\>test-servicehealth


Role                    : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeDelivery, MSExchangeIS,
                          MSExchangeMailboxAssistants, MSExchangeRepl, MSExchangeRPC, MSExchangeServiceHost,
                          MSExchangeSubmission, MSExchangeThrottling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeMailboxReplication, MSExchangeRPC,
                          MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Unified Messaging Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, MSExchangeUM, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost,
                          MSExchangeTransport, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

Hi ,

Based on the given info , what is understand is given below.

There are two nodes in DAG.On that DREXCH01 node is in down state because it shows service down on the output.

Based on my knowledge ,If we wanted to have the expected output and also up to date sync in DAG .we need to have both the nodes up and running in DAG.

Note : Please ensure the node DREXCH01  is active and surviving in cluster and also make sure cluster service is started on the node.

I checked all the nodes and services are running fine. 

Hi ,

Then what about the status of the node DREXCH01 in the fail-over cluster.

Because why i am asking it showing as service down.

Hi Ganesh,

Great checklist from S.Nithyanandham.

Please also try to re-mount the database on DR site, then re-start the Information Store service and sync the copy manually for testing.

Also check whether there is any related Error message.

 

Check to make sure Exchange Trusted Subsystems is part of the local administrators group. If it's not take a look at group policy you may have a policy set to remove users from the local administrators group.

• Marked as answer by Mavis_HuangMicrosoft contingent staff, Moderator Monday, December 08, 2014 6:16 AM

Check to make sure Exchange Trusted Subsystems is part of the local administrators group. If it's not take a look at group policy you may have a policy set to remove users from the local administrators group.

• Marked as answer by Mavis_HuangMicrosoft contingent staff, Moderator Monday, December 08, 2014 6:16 AM

Does Test-ReplicationHealth provide any useful failure messages?

No Test-ReplicationHealth doesn't shows up anything much. 

Ganesh,

Has this issue been resolved?? Can you please share the update it would be helpful for the forum..