Per http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx#hwLocServers, support for stretch farm topologies SharePoint 2013 was unsupported. As a result of our continuous efforts to review and update our product performance and capacity boundaries, we are pleased to announce supportability for a
limited set of stretch farm topologies under the definition of distributed topologies. All of these topologies are based on a prerequisite of minimal (< 1ms) latency between components of the farm (see also https://technet.microsoft.com/en-us/library/cc748824(v=office.15).aspx#CfgStretchedFarm).
Topologies that do not meet this definition remain unsupported and are not under consideration for review at this time.
Frequently Asked Questions
|Q1||My customer wants to distribute their topology across one or more distinct geographic boundaries (i.e. between cities, states, provinces), is this supported?|
|Q2||My customer maintains a logical datacenter comprised of one or more physical buildings on a single site. Is this supported?|
|A2||Yes, providing there is a highly consistent intra-farm latency of <1ms, 99.9% of the time over a period of ten
minutes. (Intra-farm latency is commonly defined as the latency between the web front-end and database servers)
|Q3||My customer’s latency exceeds 1ms – what can I do to get them to a supported configuration?|
|A3||See http://technet.microsoft.com/en-us/library/cc263031.aspx for documentation detailing high availability and disaster recovery topologies possible with SharePoint Server 2013.|
Be aware that it will take a couple of weeks till the the SharePoint 2013 article will be updated as it will have to got through official review and approval process.
[Update March 2017] For SharePoint 2016 see these articles: