SharePoint Farm-3 tier of architecture-Web Front End Server-High Availability, Load Balancing and Scalability

SharePoint Farm, have 3 tier of architecture, Web front end Server, Application Server and Database Server.
High Availability in SharePoint is implemented at the 3 levels. In database tier, multiple database server have Always On Availability Group to have HA. In Application Server tier, SharePoint Farm, implement HA internally itself.
For Web Front End Server, following are some of the options.
Options possible:
1. Hardware based Load Balancer like F5 , Citrix Netscaler, KEMP
 Plus Points:
o Sticky session
o Strong support for High Availability
o Excellent support for Load Balancing
o Best support for Scalability
 Negative Points:
o Cost for Hardware

2. Software based load Balancer like nginx and haproxy
 Plus Points:
o Sticky session
o Strong support for High Availability
o Excellent support for Load Balancing
o Best support for Scalability
 Negative Points:
o Cost comparatively less the Hardware solution
3. Windows Feature – Network Load Balancer
 Plus Points:
o Sticky session
o Cost Free – Part of Windows server
 Negative Points:
o Limited support for High Availability
o Limited support for Load Balancing
o Does not have good Scalability
o Does not support Multiple subnet IP based network
4. DNS Based Geographic distribution
Either via DNS policy (Reference: https://docs.microsoft.com/en-us/windows-server/networking/dns/deploy/app-lb )
Or core DNS Round Robin implementation
Not a real solution for HA and Load Balancing.
 Plus Points:
o Cost Free – Part of DNS Server (Windows server)
 Negative Points:
o No support for High Availability
o Limited support for Load Balancing
o Limited Scalability

Best of luck for SharePoint Farm with High Availability, Load Balancing and Scalability.

Advertisements

CSR-JSLink for SharePoint / Office 365

Topic: CSR-JSLink for SharePoint / Office 365
Audience: Executive
SCOPE: Brief

Click here to see CSR/JSLink presentation

Record Management in SharePoint

Presentation

Topic: Record Management in SharePoint
Scope: basic
Level: Executive

Click here to download presentation

SharePoint Central administration-The object UserProfileADImportJob Name=

Problem:
In SharePoint Central administration, while starting timer job to start synchronization from AD to Sharepoint, following error is thorwn.
An update conflict has occurred, and you must re-try this action. The object UserProfileADImportJob Name=SharePoint Production 2016 User Profile Service Application_UserProfileADImportJob was updated by XXXDomain\xxxUser, in the OWSTIMER (1920) process, on machine XXXMachineName. View the tracing log for more information about the conflict.
Solution:
Clearing the SharePoint Configuration Cache as per guide here:
https://www.zubairalexander.com/blog/clearing-the-sharepoint-configuration-cache/

SharePoint 2016, new features

Topic: SharePoint 2016, new features
Audience: SharePoint Consultant
SCOPE: Basic

Click here to download presentation

SharePoint Branding Strategy

Topic: SharePoint Branding Strategy
Audience: SharePoint Consultant
SCOPE: Cross Referenced

Click here to download presentation

SharePoint Enterprise 2016-Project Server Integration

Project Server Integration In past versions of SharePoint Server, Project Server was an add-on that needed to be installed and patched separately from SharePoint. This often led to enterprises having a dedicated farm for Project Server, instead of hosting Project Server on the same farm as the enterprise SharePoint farm. In SharePoint Server 2016 , Project Server is fully baked inside. SharePoint 2016 binaries, patches, and language packs include all the fixes needed for Project Server. Project Server is now simply a Service Application you have to configure. However, the licensing for Project Server is still an add-on on the price of the SharePoint license.

So created a site collection based on Project server integration.
https://msdn.microsoft.com/en-us/library/ee662105(v=office.16).aspx