+1-888-365-2779
Try Now
More in this section

Forums / Deployment / How to deploy to hardware load balanced farm

How to deploy to hardware load balanced farm

2 posts, 0 answered
  1. Rich
    Rich avatar
    1 posts
    Registered:
    31 Jan 2013
    04 Feb 2013
    Link to this post

    Hello.  I searched through the last few years worth of topics and didn't find anything that addressed this issue.

    I have an existing enterprise server configuration that needs a cms set up.  I'm looking at SiteFinity with the load balancing addon to see if it will fit this need.  The documentation page for setting up load balancing seems to skip over which parts are necessary in a hardware load balanced environment.

    My requirements:
    1- No single point of failure - there cannot be a single server in the configuration that will bring the entire system offline if it goes offline.
    2- Each server in the farm must be stand alone and able to be excluded from the farm at any time without human intervention.  Our load balancer will automatically remove a server from the rotation if it detects any issues with it, so the CMS needs to continue working as intended if/when this happens.
    3- The servers in the farm may not be co-located and a network share between them may not be available.

    Can SiteFinity work in a multi-server configuration as outlined above?  We intend to use an existing Sql Server cluster for storage.  File system storage for anything stored in the CMS is a deal killer.


  2. Atanas Valchev
    Atanas Valchev avatar
    414 posts
    Registered:
    04 Jan 2016
    07 Feb 2013
    Link to this post
    Hi,

     Sitefinity is flexible when it comes to the load balancing, either hardware or software. There are only a couple of requirements that need to be met:

    • The configuration files and search index files on each server need to be identical, either through a shared store or a tool that keeps all the files in sync. To minimize the files modified on the server, the configurations can be stored in the database.

    • The other requirement is that the servers must be able to communicate between each other. This is required by the service that invalidates the cache dependencies and ensures that the latest content is displayed on the frontend, regardless of the node.

    Your questions:

    1- No single point of failure - there cannot be a single server in the configuration that will bring the entire system offline if it goes offline. - Each instance of Sitefinity is functioning on its own. If one of the servers stops functioning for some reason, the rest will continue to operate normally. Since all servers are pointing to one Database, it needs to be protected with a fail safe backup

    2- Each server in the farm must be stand alone and able to be excluded from the farm at any time without human intervention.  Our load balancer will automatically remove a server from the rotation if it detects any issues with it, so the CMS needs to continue working as intended if/when this happens. - As I mentioned above, if one of the frontend server is removed from the rotation, the rest will continue to function normally.

    3- The servers in the farm may not be co-located and a network share between them may not be available. - In this case, the files are on each separate server and should be kept in sync either by a third party tool or the configurations stored in the database.

    The default provider stores the binary data in the database unless configured otherwise.

    Greetings,
    Atanas Valchev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
2 posts, 0 answered