Domanda

MSFT has been selling "zero down-time patching" in 2016 for a while now, but I'm having trouble finding details at this point on the subject.

I have heard that this requires HA in your farm. This indicates to me that "zero downtime" just means that users will be pushed to an available server while the patching-in-progress server is unavailable. That's something you can do right now in 2013 with HA.

Has anyone performed this in 2016 to see the results of the proposed zero downtime?

È stato utile?

Soluzione

It requires that all services be highly available (FE, Distributed Cache , Search, MMS, and so on). Patches may require a restart of any one particular server, hence the HA requirement. The goal is that there are no schema updates, which is what takes a farm down across the board during Config Wizard. That's what 'zero downtime' means.

EDIT 4/12/06: The first SharePoint Server 2016 patch has been released. Yes, it requires downtime on individual farm members. See SharePoint Server 2016 Zero Downtime – The Real World for additional details, but they're basically the same as what I mentioned here.

Altri suggerimenti

Yes this has been done and shown start to finish and this was achievable in previous versions of SharePoint. HA is the key to success here as its needed. The difference between previous versions and SharePoint Server 2016 is that we are no able to write back to Databases while upgrade is being performend. Link below gives more details and a demonstration

https://technet.microsoft.com/en-us/library/mt767550(v=office.16).aspx

Autorizzato sotto: CC-BY-SA insieme a attribuzione
Non affiliato a sharepoint.stackexchange
scroll top