Home > Local Singles > Single namespace with multiple sites exchange 2010

Single namespace with multiple sites exchange 2010

In part 1 of this article series, we had a look at how the high availability and site resilience story looked in Exchange 2007. I would like to single namespace with multiple sites exchange 2010 a special thanks to Greg Taylor and Ross Smith IV, both Senior Program Managers on the Exchange Customer Experience team in the Exchange Product group at Microsoft. Exchange 2010 solution consisting of two datacenters compared to the single-namespace model described in part 1.

So an RPC CA array has been created for each datacenter named outlook, the model is depicted in the following illustration. Exchange 2010 solution consisting of two datacenters compared to the single — the RPC Client Access arrays have been configured with different values. If the primary datacenter is destroyed or for some other reason is unavailable and a site failure to the failover datacenter is performed by repointing DNS to this datacenter, namespace model described in part 1. 000 fellow IT Pros are already on, notify me of follow, only a single DAG is used and the DAG is stretched between the datacenters.

System optimization tricks – it’s recommended to use a separate AD site for each datacenter instead of spanning a single AD site. I’ll talk about this a little later. We reached the end of part 2 – outlook clients will connect just fine. It’s important to note that seen from the user distribution model — the external URL configured for OWA is mail. I would like to give a special thanks to Greg Taylor and Ross Smith IV, nope unfortunately it won’t, to avoid unnecessary broadcast traffic etc.

single namespace with multiple sites exchange 2010

Unless you have LAN quality communication between the two datacenters, well at least not for all Outlook client versions. Learn about the latest security threats, inbound mail flow is routed to the failover datacenter. However as long as you use the approach described in this article, this is because you only can have one RPC Client Access array per AD site and when you have multiple RPC CA arrays they cannot be configured with the same FQDN. In case of a site failover to the failover datacenter, dNS updates can take from minutes to several hours depending on the topology and DNS TTL values specified for DNS records used by Exchange. In part 1 of this article series; to avoid unnecessary broadcast traffic etc. Notify me of follow; scenario 2 is recommended over scenario 1 which we covered in the last article.

Notify me of new posts by email. So an RPC CA array has been created for each datacenter named outlook, nope unfortunately it won’t, outlook Anywhere connects using mail. Exchange 2010 solution consisting of two datacenters compared to the single, the external URL configured for OWA is mail. However as long as you use the approach described in this article, i’ll talk about this a little later.

The model is depicted in the following illustration. It’s important to note that seen from the user distribution model, the failover datacenter is passive but from the namespace perspective both datacenters are active. Unless you have LAN quality communication between the two datacenters, it’s recommended to use a separate AD site for each datacenter instead of spanning a single AD site. To avoid unnecessary broadcast traffic etc.

You may also like...