I have the below set up for availability group :
Always on configured in SQL Server 2017:
- Primary is read write and secondary is read only.
- Both primary and secondary are configured with asynchronous commit and manual failover
The set up is only for DR purpose and for reporting. It's not configured using a cluster. We have not failed over nor want to fail over to secondary.
I need help in steps to follow if I have to apply patches on both primary and secondary.
Recently when applying patches, always on broke on and had to reconfigure. Kindly advise the best possible way to reboot the primary and secondary servers without failover .
Thank you for all the possible options and solutions . But the business requirement is not to do any failover .
The issue is recently after windows patch is applied and server is rebooted , always on primary replica is going to resolving status.
It’s databases are in status of not synchronizing / pending recovery.
Always we are ending up re- doing the AG configuration.
The steps we followed are - stop data movement from primary and secondary , stop sql services , after reboot , start sql services and resume data movement .
Is there anything which should be avoided or anything which needs to be done additionally in order to overcome primary AG breaking ? Failover is not a option for us ( not my scope to request that requirement to change as it’s management decisions ) kindly need help