Want the “real world” scoop on the new Distributed Cache Service in SharePoint 2013? In this article, SharePoint PFE Vladimir Medina from Mexico City shares some tips from the field to help you keep your SharePoint 2013 Farm healthy.
If you, like me, are playing with SharePoint 2013 or if you have plans to migrate/deploy SharePoint 2013, you may have already heard about Distributed Cache (a.k.a. Velocity or AppFabric). In this post, I’d like to make you aware of some tips from the field that may help you avoid some serious issues in your production Farm.
First things first, see the following articles to learn about planning and managing Distributed Cache on SharePoint 2013:
Plan for feeds and the Distributed Cache service in SharePoint Server 2013
Manage the Distributed Cache service in SharePoint Server 2013
As you know, real world scenarios are always different and more challenging than TechNet “ideal world” and some tips that we noted from Premier support cases are really valuable:
If you’d like to sleep well before and after your new SharePoint 2013 deployment/migration process, I encourage you to bookmark this article . I’m also really interested in your experience and comments, so please share your stories with us and help us learn and share more tips about SharePoint – all will be welcomed!
Original content from Vladimir Medina. Posted by MSPFE editor Pam Lahoud.
Thank you for this Blog!
Is is required to run Distributed Cache service on a 2-Tier farm (SQL server, SP server).
This is not clear:
Run the following cmdlet on all the servers except the one left running for availability:
If all servers have the service stopped then leave one without running this cmdlet, which will be your first server to restart.
Suppose you have two Distributed cache servers and you have a maintenance (reboot) to do. what would you do?