For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Naveed_DG_16007's avatar
Naveed_DG_16007
Icon for Nimbostratus rankNimbostratus
Jun 06, 2014

Single SharePoint 2013 Farm for two geographical locations

I have posted a detailed question Here. One of the replies suggested F5 Gelocation feature.

 

I have a solution in place to ensure web requests from users in Location1 are routed to SharePoint Web front end server in Location1 and similarly for Location2. My question: is there any product which will ensure that when users upload a document from Location1 to a SharePoint site, it primarily should go to SQL server in location1 ? similarly when users upload a document from Location2 to a SharePoint site, it primarily should go to SQL server in location2!

 

Further, users in Location1 will always be interested in website1 (primary for Location1) and users in Location2 will always be interested in website2 (primary for Location2). Thanks in advance

 

application acceleration manager
availability
BIG-IP DNS
design
storage

1 Reply

  • Jason_40733's avatar
    Jason_40733
    Icon for Cirrocumulus rankCirrocumulus
    Jun 06, 2014

    Global Traffic Manager is the F5 answer to this problem. It works very well and integrates seamlessly with Local Traffic Manager F5 products.

     

    Same solution that was recommended for your other setup.

     

    https://f5.com/products/modules/global-traffic-manager

     

    We use it for our global corporate and customer needs. Great for directing geographic regions to their closest server and also provide secondary direction should a primary site go down.

     

    Jason