Super SQL Server Clusters for SharePoint - Part 1

When I demonstrated AlwaysOn for SharePoint Disaster Recovery setups a while ago, the SQL cluster model I setup wasn’t strictly speaking highly-available. This is because there’s no failover for SQL Servers synchronising data between both SharePoint farms. A couple of people have pointed this out now and as this is technically a potential fault, I…

2

Running SharePoint Farms in Azure

Running SharePoint farms is an increasingly popular IT workload for the cloud/Azure for all sorts of reasons. There are though some important differences in running SharePoint on-premises to on-cloud, and this is mainly what this blog-post is about. But first, some Cloud Kool-Aid… Why Azure Absolutely Rocks for SharePoint Farms In short, Azure lets you…

1

Multi-subnet SQL Server Clusters + SharePoint 2013 + SPDatabase.MultiSubnetFailover

Small but significant update; earlier I described a problem where SharePoint can get its’ knickers in a twist when it comes to consuming a SQL Server endpoint that exists in multiple clusters. Well the problem is real enough; anyone with this configuration that has a failover will probably find SharePoint mysteriously unable to connect to…

1

Troubleshooting AppFabric Timeouts on SharePoint

SharePoint 2013 uses AppFabric to host a bunch of stuff in a cache-cluster. This is awesome mainly because each web-front-end server doesn’t have its’ own cache island that can’t be shared with the other web-front-ends and the likelihood of a cache-miss is much lower (especially if the load-balancer doesn’t do sticky-sessions), thus the caching becomes…

4

Building True Multi-Subnet Windows Server Failover Clusters

Something you may have heard of if you know clustering at all is the idea of “multi-subnet clusters”; a capability introduced in Windows Server 2012 (if memory serves) to Windows Failover Clustering. It’s conceptually the same thing as a normal cluster; it’s designed to withstand an instance failure but multi-subnet clusters allow us to withstand…

3

SharePoint 2013 + Distributed Cache (AppFabric) Troubleshooting

Two messages you may have seen if you’ve administered SharePoint 2013 in anyway way about caching are “This Distributed Cache host may cause cache reliability problems” and/or “cacheHostInfo is null” from PowerShell. This article is about how to fix those errors & caching reliability problems in general for SharePoint 2013. Update: see a simplified version…

49

SharePoint AD Failover Review

A key part of the SharePoint high-availability puzzle is a healthy and highly-available Active Directory; if AD dies then so does your SharePoint farm too, broadly speaking. However more specifically, that opening statement should really say “each and every SharePoint server needs AD failover” for the whole thing to work – if just one server…

0

Multi-subnet Clustered SQL + RegisterAllProvidersIP + SharePoint 2013

Those of us that have even the most passing knowledge of SharePoint will know that it needs a SQL Server instance to work at all. If SQL goes down it takes SharePoint with it which is why it’s quite common to have SQL clustered to make sure SQL stays alive at all costs. I’ve covered…

4

SharePoint 2013 and SQL Server AlwaysOn - High Availability SharePoint

What is AlwaysOn and why use it for SharePoint? Update: SQL 2014 + SharePoint 2013 (abridged) guide also available. Also if you want to use AlwaysOn for SharePoint Disaster Recovery, then you’ll want to have a look at this article – http://blogs.msdn.com/b/sambetts/archive/2015/04/24/setting-up-sharepoint-disaster-recovery-sites-with-sql-alwayson.aspx AlwaysOn is a great new feature to SQL Server 2012 that allows consuming clients…

45