Nearly two years ago, I presented a session called High Availability Design Considerations at TechEd North America 2010. During my session I described the changes we were making around how MAPI con...
Updated Jul 01, 2019
Version 2.0
Blog Post
Great read, thanks Ross. If a database *over to the secondary datacenter, is there a major benefit in having the AllowCrossSiteRPCClientAccess set to $False. For example, if the active database fails and the best copy selection process determines that the passive copy in the secondary datacenter is the best choice to active, all my end-users would be interrupted with a prompt informing them to close and re-open Outlook. Once the failed database is back online, if I want to change the active database back to the primary datacenter the users would again be interrupted by a prompt. I could also see this happening during server patching. So I have 2 questions please,
1. Could I change the AllowCrossSiteRPCClientAccess value to $False after a datacenter failure occurs, will the client automatically redirect to the standby CAS array without manipulating DNS records?
2. From a WAN prospective, if a database *over to the secondary datacenter, is there any savings in having the CAS servers traverse the WAN and communicate the mailbox server or is it negligible in having the client traverse the WAN and communicate to the CAS servers in the secondary datacenter?
Thanks so much