Cannot perform security update on SharePoint server where DB in Basic Always ON Availability Group

When performing security updates on SharePoint with a database in a basic Always On availability group, you may encounter errors if the secondary replica of the database is not synchronized or if the secondary replica is not available. Here are some suggestions you can try:

Verify the health of the Always On availability group: Check if the Always On availability group is healthy, and if the secondary replica is synchronized with the primary replica. If there are any issues with synchronization or availability, resolve them before proceeding with the security patch.

Failover the availability group: Failover the availability group to make the secondary replica the primary replica, and apply the security patch on the new primary replica. Once the patch is successfully applied, fail back to the original primary replica.

Use PowerShell to remove and add databases to the availability group: Instead of manually removing each database from the availability group, you can use PowerShell to remove and add the databases to the availability group. This can help simplify the process and save time.

Use a rolling upgrade approach: Upgrade one database at a time, by removing it from the availability group, performing the security patch, and adding it back to the availability group. This approach can be time-consuming, but it allows you to perform the security updates without impacting the availability of other databases in the availability group.

It is important to note that before attempting any of these suggestions, it is recommended to have a backup of the databases and to test the upgrade process in a test environment.

Hi @Vahid Ghafarpour ,

Thank u for the suggestions. Please find my response to your suggestions.

• Verify the health of the Always On availability group: Check if the Always On availability group is healthy, and if the secondary replica is synchronized with the primary replica. If there are any issues with synchronization or availability, resolve them before proceeding with the security patch.

 My Response: All are perfectly fine, status are synchronized and healthy for both servers.

• Failover the availability group: Failover the availability group to make the secondary replica the primary replica, and apply the security patch on the new primary replica. Once the patch is successfully applied, fail back to the original primary replica.

My Response: This model does not work since despite I make the secondary as primary, the databases are in basic availability group and synchronized. Regardless, I make the primary as secondary and vice-versa, this error will show up. In my experience the only way to patch is to remove the secondary replica and the patching will be successful, however I do not want to patch this way. That is why I am seeking for suggestion.

• Use a rolling upgrade approach: Upgrade one database at a time, by removing it from the availability group, performing the security patch, and adding it back to the availability group. This approach can be time-consuming, but it allows you to perform the security updates without impacting the availability of other databases in the availability group.

My Response: for rolling upgrade, eventually we must remove the databases from the availability group. If this is the purpose, than I can patch like I performed earlier, which is removing the databases from the availability group, perform the patch and add the databases in the availability group.

In conclusion, can u suggest any other method to patch SharePoint server while replicas are synchronized through Basic Always ON Availability Group. My purpose is not served. Plz see the errors and my architecture diagram.

Hi,

I hope you're doing well.

I'm currently dealing with an issue and found the solution in this article: https://rainesy.blog/updating-a-sharepoint-2013-farm-with-sql-always-on-availability-groups/

I hope this helps.