Content Index State Failed - Exchange 2010 2 Node Dag

Hello,
Last night I needed to restart one of my Exchange 2010 DAG nodes. I moved all Active Database copies of this node to the other node in the DAG. I then restarted the node with no Active Database copies. When the server came back up I moved
the Active Database copies back onto the node that they were initially on. The node that I restarted now shows the ContentIndexState of all Databases as "Failed". Test-replicationhealth gives the following results:
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server S01
Name                                          Status
CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
Length    Length                             State
DB01-MS01 (A-B)\S01                     Mounted         0         0
Failed
DB02-MS01 (C-D)\S01                     Healthy         0         0
1/26/2011 9:57:40 AM           Failed
DB03-MS01 (E-G)\S01                     Healthy         0         1
1/26/2011 10:02:38 AM         Failed
DB04-MS01 (H-J)\S01                     Mounted         0         0
Failed
DB06-MS01 (M-N)\S01                     Healthy         0         0
1/26/2011 10:02:25 AM         Failed
DB07-MS01 (0-P)\S01                     Healthy         0         0
1/26/2011 9:57:17 AM            Failed
DB08-MS01 (Q-R)\S01                     Mounted         0         0
Failed
DB09-MS01 (S-T)\S01                     Mounted         0         0
Failed
DB05-MS01 (K-L)\S01                     Mounted         0         0
Failed
DB10-MS01 (U-V)\S01                     Healthy         0         0
1/26/2011 10:01:59 AM          Failed
DB11-MS01 (W-Z)\S01                     Healthy         0         0
1/26/2011 9:57:50 AM           Failed
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server S02
Name                                          Status
CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
Length    Length                             State
DB01-MS01 (A-B)\S02                     Healthy         0         0
1/26/2011 10:00:36 AM Healthy
DB02-MS01 (C-D)\S02                     Mounted         0         0
Healthy
DB03-MS01 (E-G)\S02                     Mounted         0         0
Healthy
DB04-MS01 (H-J)\S02                     Healthy         0         0
1/26/2011 10:02:29 AM Healthy
DB06-MS01 (M-N)\S02                     Mounted         0         0
Healthy
DB07-MS01 (0-P)\S02                     Mounted         0         0
Healthy
DB08-MS01 (Q-R)\S02                     Healthy         0         0
1/26/2011 10:02:32 AM Healthy
DB10-MS01 (U-V)\S02                     Mounted         0         0
Healthy
DB11-MS01 (W-Z)\S02                     Mounted         0         0
Healthy
DB05-MS01 (K-L)\S02                     Healthy         0         0
1/26/2011 10:02:21 AM Healthy
DB09-MS01 (S-T)\S02                     Healthy         0         0
1/26/2011 10:01:33 AM Healthy
[PS] C:\Windows\system32>test-replicationhealth
Server          Check                      Result     Error
S01          ClusterService             Passed
S01          ReplayService              Passed
S01          ActiveManager             Passed
S01          TasksRpcListener         Passed
S01          TcpListener                  Passed
S01          DagMembersUp           Passed
S01          ClusterNetwork            Passed
S01          QuorumGroup               Passed
S01          FileShareQuorum            Passed
S01          DBCopySuspended            Passed
S01          DBCopyFailed               Passed
S01          DBInitializing             Passed
S01          DBDisconnected             Passed
S01          DBLogCopyKeepingUp         Passed
S01          DBLogReplayKeepingUp       Passed
I appreciate any help. Thank you.
R

[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus
Name                                          Status
CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
Length    Length                             State
DB01-MS01 (A-B)\01                                 Mounted
0         0                                  Healthy
DB02-MS01 (C-D)\S01                               Healthy         0
0           1/28/2011 11:05:45 AM Healthy
DB03-MS01 (E-G)\S01                               Mounted         0
0                                  Healthy
DB04-MS01 (H-J)\S01                                Healthy
0         0           1/28/2011 11:07:50 AM Healthy
DB06-MS01 (M-N)\S01                               Healthy         0
0           1/28/2011 11:02:12 AM Healthy
DB07-MS01 (0-P)\S01                                Mounted
0         0                                  Healthy
DB08-MS01 (Q-R)\S01                               Healthy         0
0           1/28/2011 11:09:08 AM Healthy
DB09-MS01 (S-T)\S01                                Mounted
0         0                                  Healthy
DB05-MS01 (K-L)\S01                                Mounted
0         0                                  Healthy
DB10-MS01 (U-V)\S01                               Healthy         0
0           1/28/2011 11:02:53 AM Healthy
DB11-MS01 (W-Z)\S01                              Mounted         0
0                                  Healthy
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus
Name                                          Status
CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
Length    Length                             State
DB01-MS01 (A-B)\S02                              Healthy         0
0           1/28/2011 11:08:27 AM Healthy
DB02-MS01 (C-D)\S02                    Mounted         0
0                                  Healthy
DB03-MS01 (E-G)\S02                              Healthy         0
0           1/28/2011 11:10:36 AM Healthy
DB04-MS01 (H-J)\S02                               Mounted         0
0                                  Healthy
DB06-MS01 (M-N)\S02                              Mounted         0
0                                  Healthy
DB07-MS01 (0-P)\S02                              Healthy         0
0           1/28/2011 10:58:23 AM Healthy
DB08-MS01 (Q-R)\S02                              Mounted         0
0                                  Healthy
DB10-MS01 (U-V)\S02                               Mounted         0
0                                  Healthy
DB11-MS01 (W-Z)\S02                              Healthy         0
0           1/28/2011 11:09:45 AM Healthy
DB05-MS01 (K-L)\S02                               Healthy         0
0           1/28/2011 11:09:42 AM Healthy
DB09-MS01 (S-T)\S02                              Healthy         0
0           1/28/2011 11:08:34 AM Healthy

Similar Messages

Content index state: Failed

Hi.
I have been restoring the entire Windows after a bigger problem in the past. However, there were data for Exchange server at a completely different disk which was not affected.
But now I can not load up OWA and when you look in the ECP so says the following under databases "Content index state: Failed"
I have tried to repair it but without any success.
The operation couldn't be performed because object '0747478411\MAIL-SERVER01' couldn't be found on 'server'.
+ CategoryInfo : NotSpecified: (:) [Update-MailboxDatabaseCopy], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : DD4CF704,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopy
+ PSComputerName : mail-server01
Update-MailboxDatabaseCopy "0747478411\MAIL-SERVER01" -CatalogOnly
All i have in owa now is
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.

Hi Jesper,
Thank you for your question.
By my understanding, we should not simply recover window system, we should performance a disaster recover for Exchange by the following link:
https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx
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

Exchange 2013: Content Index State Failed

I am running two, two node DAG's with Exchange 2013.
One DAG pair is running 5 databases with Server 2012 Standard and the second DAG pair is running Server 2008 R2 SP1 Standard with a single shared database.
No matter what I try, ALL 6 databases show "ContentIndexState: Failed" with "ContentIndexErrorMessage: An internal error occurred for the database or its index.".
I have tried rebuilding the indexes manually, automatically and manually copying the database files between servers. I also receive errors when trying to failover the databases because the content index state is failed.
In my test environment I have a very similar setup working fine with no issues.
Please let me know what I can try to get this resolved.
The error I receive when running the following set of commands is:
suspend-MailboxDatabaseCopy dag2db1\mbox1
update-MailboxDatabaseCopy dag2db1\mbox1 -deleteexistingfiles
[PS] C:\Windows\system32>update-mailboxdatabasecopy dag2db1\mbox1 -deleteexistingfiles
Confirm
Are you sure you want to perform this action?
Updating database copy DAG2DB1\MBOX1 on server MBOX1
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): a
WARNING: Seeding of content index catalog for database 'DAG2DB1' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Therevwas no endpoint listening
at net.tcp://localhost:17063/Management/SeedingAgent-0A2745DF-4522-42AB-9115-5DDE9EDEF1C612/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
[PS] C:\Windows\system32>

Hi Folks,
Here we go;
"On
August 14th, we announced the removal of the
MS13-061 Security Update for Exchange Server 2013 due to an issue where the patch changed settings for the search infrastructure, placing the content index for all databases into a failed state. As of today, we have released updated security updates
for both Exchange 2013 RTM CU1 and Exchange 2013 RTM CU2."
Details below;
http://blogs.technet.com/b/exchange/archive/2013/08/27/now-available-updated-release-of-ms13-061-security-update-for-exchange-server-2013.aspx
Yavuz Eren Demir
After installing this patch (Exchange2013-KB2874216-v2-x64-en.msp) seeding of the databases was impossible.
Error:
warning
Seeding of content index catalog for database 'Database02' failed. Please verify that the Microsoft Search (Exchange) and
the Host Controller service for Exchange services are running and try the operation again. Error: Could not connect to net.tcp://localhost:3863/Management/SeedingAgent-F293698C-B2D0-40CA-A2C3-FB37982E708712/Single. The connection attempt lasted for a time
span of 00:00:02.0592000. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:3863. .
Looking at the two services mentioned in this warning I've noticed the Microsoft Exchange Search Host Controller (HostControllerService)
was disabled
After Changing it to Automatic and enabling it, the problem was salved

Content Index State: Failed and Suspended Exchange Server 2013

On my passive Server "Content Index State" mailbox database is still Failed and Suspended for almost a week.
Actions Taken to Resolve the Issue:
- Update-mailboxdatabasecopy
-Delete the exisiting folder of database on passive server and run database copy on EAC
Still got FAILED AND SUSPENDED content index state.
Need some advice guys..
Thanks!

Hi,
Please check the following article and see if it can resolve your problem.
https://support.microsoft.com/kb/2807668
Please check the active database, make sure the content index is healthy. If possible, please rebuild content index of active database. And then reseed passive database copy to check result.
Best regards,
Belinda Ma
TechNet Community Support

Content Index State Failed - After every restart on 2010 mbx server

I noticed that everyone is saying just to run the catalog only command on any database that gets
Contnt index state failed after a restart. but what if you are faililng over 30database and 20 of them get corrupted? run this commadn 1 by 1? really?

Thanks
wawoodwa , this command solved my problem!!!
On other sites I found command:
"Update-MailboxDatabaseCopy –Identity ‘DB2’ –CatalogOnly" it was not working, I got the same error as OldSchoola.

Content Index State Crawling

We have an Exchange database that seems to always have a Content Index State that is crawling. Some end users have complained about slow searches and indexing issues (which is expected). We have
stopped the search services and renamed the catalog directory in an effort to rebuild the search catalog, but it just goes right back to crawling. The database is only about 300GB, so I don't think size is an issue.
Could it be there is some corruption on the database that is causing issues with the index catalog. We have removed the database from the DAG and tried it as a stand alone database, with the same
results.
Any ideas would be appreciated.

did you find anything in the event viewer (app/Sys logs).
You may consider restarting Search Indexer service and then check if that gets healthy or not.
If it still doesn't say healthy then you might have to consider Resetting Search Index for problematic Database or all database if all if it is a problem with all databases.
Refer to the link below to get info about how to reset Search index for a database.
Exchange
2010 Database copy on server has content index catalog files in the following state: Failed
Establishing Exchange Content Index
Rebuild Baselines – Part 1
How To Troubleshoot Issues With Exchange 2010 Search
Reply back with the outcome!
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Database passive content index state stays FailedAndSuspended even after reseeding

I have a mailbox database with two copies in a database availability group, the active copy is healthy and its content index state reports healthy as well, the passive copy is healthy but its content index state reports FailedAndSuspended.
I tried the: Update-MailboxDatabaseCopy <DBName>\<ServerName> -CatalogOnly more than one time, it completes (says 100KB written) but the state never changes.
I even tried to manually stop the service>delete CI>start the service, the CI folder was recreated (about 1 GB) but still the state is still FailedAndSuspended.
Please Help!

I found the following warning in the event log,
Event ID: 1009
The indexing of mailbox database Main-EX02-DB1 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.CatalogReseedException:
The component operation has failed.
   at Microsoft.Exchange.Search.Engine.SearchFeedingController.DetermineFeederStateAndStartFeeders()
   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()
   at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)
   at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)
I checked online, and found one website talking about the "ContentSubmitters" group, which I created in the Exchange Security Groups OU without any members but with stated permissions:
https://abdullrhmanfarram.wordpress.com/2013/06/16/event-id-1009-content-index-status-of-the-mailbox-databases-failed/

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Exchange 2010 SP3 DAG Flip Flop File Share Witness Issue

Hi All,
We are facing one strange issue with Exchange 2010 SP3.
Our environment is as below
a single DAG spanned accross 2 AD sites with 6 MBX server.
Each site have 3 MBx server.
File Share Witness is on Hub server in primary site.
Note: The DAG IP is from Primary DC VLAN and which cant be streched accross DC due to network restrictions/limitations.
It was working fine till date.
But, yesterday onwards we are facing issue.
All DB dismounted and DAG name disappear from EMC and while doing refresh its giving error as below
Exception type: Microsoft.Exchange.Data.DataValidationException
Exception message: Could not convert property WitnessServer to type UncFileSharePath. Error while converting string 'vesthub700.mydomain.com\DAG1.mydomain.com' to result type Microsoft.Exchange.Data.UncFileSharePath: "vesthub700.mydomain.com\DAG1.mydomain.com"
is not an acceptable path. You must use an absolute, local, long file path, that doesn't contain '~', or a UNC path. Parameter name: path
We are not able to execute any cmdlets related to databaseavailabilitygroup from EMS and its giving same error.
Failover Cluster DAG resource is Flip/Flip continuously.
Its only become stable after reboot of the hub server holding FSW and the 1st mailbox server.(Cluster Owner)
We are even not able to move cluster group to different server.
Performed ExBPA no such issues found which related to DAG.
Performed clsuter validation.
Only generic cluster events in Mailbox servers.
Observation:
Its only become stabe if we remove the msExchFileShareWitness Value for DAG1 using ADSIEdit.
And the problem recurs if we set it back again.
Any help or suggestion is appreciated.
Thanks,
soumen
Soumen Ghosh

Hi Belinda,
Thanks! I have checked the Mailbox Server Application Log and found few 2155 Event Id generated at the time of the issue occured.
Process Microsoft.Exchange.ServiceHost.exe () (PID=9312). Configuration object CN=DAG1,CN=Database Availability Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=com
read from DCTDK35.mydomain.com failed validation. DataValidationException will be thrown. Set event logging level for Validation category to Expert to get additional events about each failure.
One update is that the DAG is stable now after we set an alternate FSW last night.
Regarding the 2nd IP assignment for DAG for the 2nd subnet, we have gone through technet and other sites which refering to add the same from EMC or EMS.
Is it sufficinet to simply adding the 2nd IP to DAG from EMC or EMS? Or do we need to take any other special consideration.
Also, adding another IP it will create one more IP address resource to Failover Cluster, but I belive at a time both the IP wont be online. Do we need to keep it offline manually or its automatically taken care by Exchange.
Please suggest.
Also, regarding executing the CollectOverMetrics.ps1 we are following
http://www.msexchange.org/articles-tutorials/exchange-server-2010/monitoring-operations/monitor-dag-database-failover.html
but failed to execute. Can you suggest the correct parameter.
Thanks,
Soumen
Soumen Ghosh

"Resend" option is not working for specific user. "The Operation Failed" Exchange 2010 Outlook 2013

Hi Everybody. I have a weird one for you.
I have a user that gets an "operation failed" message whenever trying to use the "resend" option on any email (It's the one right under recall). I had tested up and down on her machine. Exchange 2010 Outlook 2013
Ran in safe mode, recreated her profile, disabled virus scanning, repaired office. (weird, the font just changed sizes on me)
After all of this I tested on other computers, other users seem to be able to "resend" just fine. However her account does not work on any computer I try, internal or external to the network.
It looks more like a profile issue.
She's a very active archivist, so she only has 486MB of space used by her mailbox.
It's well under quota.
It's been really puzzling me.
MCSE 2003, Exchange. MCTS Vista, 7. Administrator of awful, neglected website http://timssims.net

Hi Timssims,
Since there is only one user in the org has this issue, it seems an issue on the Outlook client side.
I suggest asking Outlook Forum for help so that we can get more professional suggestions.
For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
However I also have some suggestions for your reference:
1. If this issue occur on Cached Mode, I suggest turning to Online Mode for testing.
2. Please also paste the detailed error message if "operation failed" is not the
complete information.
3. If still not works after perform operations above (including suggestions from Outlook Forum), I suggest re-creating a new mailbox for the specific user just as Martin suggested.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Database redundansy health check failed ( Exchange 2010 sp3 )

Hello all ,
One of the mailbox server have been getting the following error in in application , sometimes
RealCopyQueu is 256 and sometimes 0 and healthy .
Kindly share how can resolve it please

Hi,
I suggest we refer to the following article to troubleshoot this issue. Run
Database Redundancy Check Script.
http://social.technet.microsoft.com/Forums/exchange/en-US/b1cfbc4b-b17d-4148-adce-1a565d0f5746/exchange-2010-event-id-4113-msexchangerepl-health-check-failed
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Moving Exchange 2010 Production DAG Setup and Servers to difrent Date Center with new IP Addresses

My Setup
Exchange 2010 SP3 2 Mailbox, 2 Hub/CAS, 2 TMG Servers in Production
Exchange 2010 SP3 2 Mailbox, 2 Hub/CAS, 2 TMG Servers in DR Site
Exchange 2010 DAG implemented with site level redundancy
Requirement
Need move Production Exchange setup along with DAG configuration to a new location.
IP Addresses for servers and DAG setup will change
No change in Server name and DNS names
During production server movement Mail services will be activated from DR Site
Need help in planning and executing the IP Address change/DAG Change
and Server movement.
Kumar K S

Hi,
I will have the following plans:
1. Active the DR site as the main site during the migration.
2. Moving the Server to the new site
3. Change the activate back to the Production Servers
https://social.technet.microsoft.com/Forums/exchange/en-US/fb9a27c3-81f8-4079-aeb8-42119b1e23bf/changing-ip-address-of-exchange-server
Thanks,
Simon Wu
TechNet Community Support

Exchange 2010 SP3 DAG Witness/Quorom Server Placement with 3 Datacenters

Hi we have 2 Exchange 2010 SP3 Server in the same Organization in a DAG
First one in Datacenter 1 in Germany
Second one in Datacenter 2 in Austria
There is a Third Datacenter available in Switzerland
Where should we place the Witness Server?
Our major concern is not a WAN Link will go down, most time a Datacenter will loose Power for some hours due
maintenance work or other things.
Is it a good idea to place the Witness Server in the third Datacenter!?
We found a Document which some missconception which talks about placing the witness always in
the primary Datacenter. But the Datacenter Switchover Document for Exchange 2013 says use a third Datacenter.
Is that also okay for Exchange 2010 or are they totally different?
Thank you in advance
Troga

Hi,
It is a new configuration option in Exchange 2013 that we use a third location for hosting the witness server.
Placing FSW in the third location will privide the ability automatically failover databases to the other datacenter in response to a datacenter-level failure event.
For more details, you can look at the "Witness server placement considerations" section in the following article.
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 /2013 DAG Design

Hi All,
I Have Gone through some Articles and Blogs where i read about the DAG Design and Member server placement in Site Resiliency Scenarios..
I just want to know what and how many DAG Designs we can propose to Customers.
As per my knowledge and study i came across -
(A) Active/Passive Model with Shared Namespace (Single DAG)
(B) Active/Passive model with different namespaces (Single DAG)
(C) Active/Active Model with Different Namespaces (2 DAGs).
I am Just Curious to know is there any other model DAG that can be proposed apart from above mentioned Designs in terms of both Namespace and Database Active copy Location.
Also can you also put some light and clarify whether we can have
Active/Active Model with Shared Namespace (Single DAG). I have read it is supported in exchange 2013, if so can we do the same in Exchange 2010 as well. If not what makes this design different in exchange 2010 v/s exchange 2013. How can we
achieve this design in exchange 2013?
I got a good article on above scenarios
here but I have some terms or paragraphs bit
confusing. Please help me to understand the bold lines in below paragraph.
Since we typically only have active users connecting to the primary datacenter (at least the majority of the users connect to this datacenter unless a site failover occurs),
the autodiscover record (autodiscover.exchangelabs.dk) in external DNS points to the load balancer in the primary datacenter. The internal “AutoDiscoverServiceInternalUri” on the CAS servers in the primary datacenter has been configured with a value of https://mail.exchangelabs.dk/autodiscover/autodiscover.xml,
and the same goes for the CAS servers in the failover datacenter. Now you could choose to point the AutoDiscoverInternalUri on CAS servers in the failover datacenter at “https://failover.exchangelabs.dk/autodiscover/autodiscover.xml” but
you can easily up on in a situation where SCP’s aren’t reachable during a site failover. Also, cross-site traffic caused by Autodiscover have a minor impact on the WAN link since autodiscover requests consists of small XML based text files.
Also in
Active/Passive model with different namespaces (Single DAG) or Active/Active Model with Different Namespaces (2 DAGs) model do we still repoint EWS,OA,EAS
etc. web service records in public DNS. If yes what should be their value (please refer
Complete Site failover Segment in Above URL)
it would be very helpful if you could provide any detailed Design diagram as mentioned in URL to understand the things better. or any Technet Articled with well
description
Thanks in advance
Regards
Aanand Singh
Regards, Aanand Singh

Hello,
The sentence " you
can easily up on in a situation where SCP’s aren’t reachable during a site failover. Also, cross-site traffic caused by Autodiscover have a minor impact on the WAN link since autodiscover requests consists of small XML based text files." I
understand that if site failover occurs,as long as the CAS servers are available in the primary datacenter, clients will continue to connect to the CAS servers in this datacenter. The CAS servers will not be used in the failover datacenter.
Consider WAN outage, we recommend you deploy Active/Active Model with Different Namespaces (2 DAGs).
Besides, I recommend you configure DNS to round-robin between the VIPs of the load balancers in each datacenter to realize single namespace.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx
http://blogs.technet.com/b/scottschnoll/archive/2012/11/01/storage-high-availability-and-site-resilience-in-exchange-server-2013-part-3.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Cara Chen
TechNet Community Support

Content Index State = 5?

Hi all,
I have a sort of strange issue. When i look at the database copies check the ContentIndexState column, i would have expected the status to be 'Healthy' or 'FailedAndSuspended' or even 'Crawling'. I have two copies where the status is simply just '5'. Anyone
have some idea what is happening here and how to correct it?
/Trev

Hi,
Agree with Andy. Please run the Update-MailboxDatabaseCopy cmdlet against this database copy to check result.
You can also rebuild content index to check result, the time of rebuding index is based on the database size.
Best regards,
Belinda Ma
TechNet Community Support

Content Index State Failed - Exchange 2010 2 Node Dag

Similar Messages

Maybe you are looking for