Its always depends upon your organization policies.. Replications jobs u can disable ,if any other jobs and its running then u have to contact job owners and ask is it ok to stop... upon confirmation u can stop or wait until the job completes...
Why we need to change synchornous commit to asynchornous commit and why we need to change readable to no After providing downtime we are proceeding with patches upgradation Any reason why need to change to asynchronous commit Any challenges while we doing patches upgradation like msp and msi files missing kindly do on this video
We switch to asynchronous commit mode during patching because the secondary replica will be unavailable. In this mode, the primary replica doesn't need acknowledgment from the secondary, ensuring that users won't experience any delays. Additionally, even though we schedule downtime, sometimes the application still points to the server, which can delay the patching process. To avoid this, we set the readable secondary to "No," which closes any existing connections to the secondary. This ensures that the patching proceeds smoothly, allowing us to complete the task on time.
This is one of the most important term how to patch in always on but I have Currently DAG in this how can we apply the patch can u Please make the video on this then I also do this then remove from DAG n do this video practical
I have already done on removal of DAG ruclips.net/video/xmjSgzxJaFc/видео.htmlsi=ZvBwJpD7y02nGv0S There are multiple scenarios on this, Lets assume both Both Availability groups replicas have same version, then patching is also same how we showed in this video, First we need to do on secondary availability group (secondary replica) after that we need to fail over this forwarder replica, and then fail over back to forwarder. now repeat the same in secondary of global primary.
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Super Harsha Bro, works great for my environment, Thanks for your efforts.
Glad it helped your environment!
Thank you, sir, for your quick response and for uploading a video.
It's my pleasure
Thanks for sharing this knowledge
My pleasure
Thanks for Sharing🤝
Thank you too👍
Thanks for sharing 🙏
Welcome 😊
Thanks for sharing this
My pleasure
Can you please explain patch on clustering as well??
Sure, I'll be able to work on it once I have some free time.
What about the always on jobs and normal backup jobs ,replication jobs..do we need to disable before doing or we can ignore the jobs ?
Its always depends upon your organization policies.. Replications jobs u can disable ,if any other jobs and its running then u have to contact job owners and ask is it ok to stop... upon confirmation u can stop or wait until the job completes...
Why we need to change synchornous commit to asynchornous commit and why we need to change readable to no
After providing downtime we are proceeding with patches upgradation
Any reason why need to change to asynchronous commit
Any challenges while we doing patches upgradation like msp and msi files missing kindly do on this video
We switch to asynchronous commit mode during patching because the secondary replica will be unavailable. In this mode, the primary replica doesn't need acknowledgment from the secondary, ensuring that users won't experience any delays.
Additionally, even though we schedule downtime, sometimes the application still points to the server, which can delay the patching process. To avoid this, we set the readable secondary to "No," which closes any existing connections to the secondary. This ensures that the patching proceeds smoothly, allowing us to complete the task on time.
This is one of the most important term how to patch in always on but I have Currently DAG in this how can we apply the patch can u Please make the video on this then I also do this then remove from DAG n do this video practical
I have already done on removal of DAG
ruclips.net/video/xmjSgzxJaFc/видео.htmlsi=ZvBwJpD7y02nGv0S
There are multiple scenarios on this, Lets assume both Both Availability groups replicas have same version, then patching is also same how we showed in this video, First we need to do on secondary availability group (secondary replica) after that we need to fail over this forwarder replica,
and then fail over back to forwarder. now repeat the same in secondary of global primary.