I have two Sites , Site A in IN region and Site B in US region; both the sites have different internet connectivity and configured outlook anywhere.
OWA URL:- http://mailIN.abc.com
OWA URL:- http://mailUS.abc.com
So my query is if in Site A internet will goes down in that case users belongs to Site A won't be able to access OWA/outlook anywhere and rest of the things as there will be no in coming connection and will route the outgoing email while changing the send connector to US.
But is there any why i can redirect(incoming connection/ emails) the things from US site for the time being so that in case of internet connectivity failure in one of the site user did not face any issue they can connection through different site.
For OWA, I think you can remove the External URL of OWA virtual directory in site A, so the site A user can be proxied when they access http://mailUS.abc.com.
Outlook anywhere should work through site B until your exchange server is above SP2 RU3
Thanks James-Ex for your reply, Actually i am looking for redundancy. I will explain you bit more, we have two site and both are exposed to internet, both have different internet connectivity so my query is if internet in one of the site becomes unavailable so my exchange connectivity should not be affected on that affected site.
Like if user try to open https://mailIN.abc.com or Outlook anywhere from outside but it won;t be available due to the internet link is down so in THAT CASE what should we can do from EXCHANGE Perspective that things should be routed to other site or user can connect from US site and then they routed to IN location, if any thing can be done in this case...?
For this case , it's mean your both site have internet facing right? So it's mean your client will connect on their own site. and if one day internet of their site unavailable so what should you do right??
If i'm correct for your question.
For example if site A (https://mailA.domain.com) internet was gone so user cannot connect to the server surely.
in this case , if you're using Exchange 2013. This version can answer for question.
In exchange 2013 you don't have to use separate dns name for each site any more.
CAS server in site B can directly proxy to site A's mailbox server. don't like 2010 version.
it's mean you can only have 1 name with 2 public ID address for each site.
for more details read this article.
(scroll down to "site resilience")
HI, do you mean that in one of the affected site where the internet won;t be available i need to remove the "external URL" from exchange side ?? if yes then do i need to update any virtual directory settings ? how the external clients will connect or get into their mailbox ? i am using exchange 2010.
For example if site A (https://mailA.domain.com) internet was gone will they automatically routed to https://mailB.domain.com if yes then about about outlook anywhere will that work too ?? and once will get the internet connectivity back then we need to revert the setting back as it was their earlier and then again do we need to update any settings .. ??
Install SP2 & enable CrossSiteRedirection. If your OWA at Site A is down then it will redirect the connectoin to OWA at Site B.
Below is the command.
Set-OWAVirtualDirectory -Identity "Contoso\owa (Default Web site)" -CrossSiteRedirectType Silent
Cross-Site Silent Redirection only performs silent redirection for requests that are destined to <acronym title="Client Access Server">CAS</acronym> located in another Active Directory site (within the same Exchange organization) that have an OWA ExternalURL.
Regards, Sunny Kewalramani.