Before patching, ensure backups are in place and execute below command as a reparation for SQL patching
hastop -local –force
• This
command should be executed only on active node and not on passive node
• You can
start patching active node and then passive node in parallel
• Once
patching is completed, you should execute hastart to bring back the VCS
cluster
• If in case
SQL patching has failed, it could be due to some issue with SQL and not VCS, we
should start troubleshoot based on errors and if we couldn't identify the root
cause
You will see the cluster will be showing faulted, but the services will be running fine on the background.
This will not affect the other instances running on the same nodes.
Perform the patching on both the nodes and they DB engine should be patched without any issues.
Hope this helps!! Please drop in comments if you have any issues.
No comments:
Post a Comment