SharePoint 2019 on-premises restart and shutdown sequence during Windows OS patching

Imran Nawaz 46 Reputation points
2023-07-26T13:50:08.9+00:00

Hi Microsoft Team,

Kindly, we have 9 servers SharePoint 2019 on-premises farm.

2WFE, 1App, 1Search, 1office Online, 1Distribution Cache, 1 OneDrive and 2 SOL always one HA servers.

The OS patch team install the windows OS patching on SharePoint farm servers.

Question: Kindly I need to know what is the services stop start and restart and shutdown sequence. all OS patch not apply one go. most of time it require 2-3 time restart the servers. is this effect farm services what is the better approach, kindly need help. and which SharePoint farm server need to first stop services and shutdown and power up.

Regards,

Imran

Microsoft 365 and Office | SharePoint Server | For business
{count} votes

1 answer

Sort by: Most helpful
  1. Zehui Yao_MSFT 5,876 Reputation points
    2023-07-28T01:49:48.5466667+00:00

    Hi Imran Nawaz, it is a pleasure to be able to help you.

    Based on my knowledge, there is no specific order in which you need to shut down your farm (or bring it up).  All services will simply connect back up once the associated service is available.

    And based on my understanding of the issue, the only rule I would recommend is to start the DC first, then the machine(s) running SQL Server, then everything else. Shutdown is the reverse. Since Stopping the cache results in partial data loss. The Feed Cache depends on the Distributed Cache service.

    For more information, you can refer to the documentation: Manage the Distributed Cache service in SharePoint Server 


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.