Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. This update scenario uses two phases to install the update on farm servers. These phases are as follows:. During the update phase, the farm can continue to be in production with minimal downtime. However, during the build-to-build upgrade phase, the farm will be unavailable.
If users attempt to access content while the farm is upgrading, the result could be failed upgrades or excessive slowdowns in the upgrade process because of resource contention and locking. Such an attempt is unsupported and untested. You can use the illustration as a guide as you go through the steps in the following procedure, "To install the update". Remove half of the web servers WEB-1 and WEB-2 from rotation in the load balancer, or pause the load balancer to stop incoming requests to the servers.
On each web server that is out of the load-balancing rotation WEB-1 and WEB-2 , run the executable file to install the update. Verify that these web servers were updated successfully by reviewing the upgrade log files.
Remove the remaining web servers WEB-3 and WEB-4 from rotation in the load balancer, or pause the load balancer to stop incoming requests to the servers. On each web server that is out of the load-balancing rotation, run the executable file to install the update. Verify that both of the web servers were updated successfully by reviewing the upgrade log files.
To do this, perform the procedure Install a software update for SharePoint Server which appears later in this article, and then return to the next step in this procedure. If your farm has additional application servers that do not host Search components, run the update executable file to install the update on these servers. At this point in the process, the databases and other components such as settings, features, and site-level data must still be upgraded because the SharePoint Products Configuration Wizard was not run on any of the farm servers.
However, the farm should be capable of running in backward compatibility mode. The following illustration shows the steps that upgrade the farm servers to finish the patching process.
During this process, the sites that are being upgraded will not be available to users. Monitor the status of the upgrade on each server before you upgrade the next server in the sequence. We recommend that you create a backup of the farm before you begin to upgrade. The following procedure shows all the steps to upgrade the farm. You can upgrade all components within the same outage window, or you can take some smaller outage windows and upgrade separate parts of the farm at different times.
If you want to break up the upgrade stage, you can upgrade the following components in separate outage windows:. If the software update contains updates to services that must be applied, you can upgrade the service, and then resume operating the farm step 8 in the following procedure until it is possible to take a longer farm outage to complete the content and farm upgrade.
You can take a short farm outage to upgrade only a few content databases steps 3 and 4 in the following procedure each time and then resume farm operation step 8 in the following procedure.
You can repeat the process over successive outage windows until you upgrade all content and the farm servers are ready to be upgraded. You can also upgrade individual content databases in parallel for a very small number of content databases at the same time.
However, do not attempt to upgrade too many content databases in parallel because it will slow down the overall upgrade process and extend the outage time. We recommend that you do not upgrade more than two content databases on the same SQL Server volume at a time. Start the upgrade for each content database that will occur in parallel several minutes apart to prevent lock contention as the upgrade process starts.
In addition, limit the number of content databases that you upgrade on a single web server or application server. Each additional upgrade process will consume a relatively large amount of resources.
The typical number of content databases that you can upgrade per web server or application server is four databases. However, be sure not to exceed the number of databases that are being upgraded per SQL Server volume, no matter which web server or application server originates the upgrade. Remove the web servers WEB-1 to WEB-4 from rotation in the load balancer, or pause the load balancer to stop incoming requests to the servers.
The sites and services will not be available until upgrade is complete and the servers are returned to an active load-balancing state. Some updates might also require you to run additional PowerShell cmdlets to upgrade specific service applications. Notes for a software update might indicate that you have to upgrade a specific service so that it will continue to operate after patching. This applies to a service that cannot operate in backward compatibility mode, for example.
You can create a short offline period to upgrade the service without having to upgrade the complete farm.
The additional PowerShell cmdlets to upgrade specific service applications should be in the notes if this is required. Remember we had 67 before, so 67 is the number to beat. Now there 84 Important patches and a couple of optional updates thrown in for good measure. There they are, the patches inside of the February CUs.
They are checked, so if we had Windows Updates set to automatically install, they would be. So make sure you look around in here and understand what is going to be patched now.
SharePoint should continue to work just fine as your servers update themselves. This is the same group that contains the Office Clients like Word and Excel.
I hope that clears up some of the confusion over the recent change to SharePoint patching. If you have any questions or comments, leave them in the comment box below.
However, downtime is not completely eliminated. The sites and services will not be available while the database content is being upgraded. Be sure to note that downtime is minimized, not eliminated, so I still perform the farm updates during maintenance windows outside normal working hours. This pattern has served me well over the years. If you have any suggestions or tips that you follow to update a production SharePoint farm, please let me know in the comments below!
We enable companies to achieve desired business outcomes by helping them transform, innovate and succeed in the Microsoft Cloud. Contact Us.
0コメント