SQL dependent servers and rebooting

[gnussbaum]

Hi,

I was wondering if someone runs a batch job where Server1, Server2, Server3, etc. connect to a SQL DB and you install updates and shutdown. Then on ServerDB, you install updates and reboot. Once the DB server is up, the other servers mentioned start up again.

Is this possible to do in batchpatch?

[doug]

Yes, it’s possible to do this in BatchPatch. However, you still need to identify the way that you would turn on a computer that is powered down. If a physical computer is powered down then you could use Wake On LAN (WoL) to turn it on, or if it were a virtual machine then you could do it with a script. Once you have determined how you would turn on your powered-down computers, then you can integrate it all into BatchPatch as an ‘Advanced multi-row queue sequence.’ We have tutorials/examples at the following links:

---

‘Advanced multi-row queue sequence’ tutorials

Advanced multi-row queue sequence – Video tutorial

Advanced multi-row queue sequence – Written tutorial

Advanced multi-row queue sequence – Real world virtual machine update and reboot sequence example

---

‘Basic multi-row queue sequence’ tutorial

I think in your case you are probably going to want to use the ‘Advanced multi-row queue sequence’ rather than the ‘Basic multi-row queue sequence’ but since the tutorial here integrates some Hyper-V PowerShell commands, it might give you some additional ideas for how things can be done:

Basic multi-row queue sequence – Real world virtual machine update and reboot sequence example

---

Wake On LAN tutorial

If you are planning to use Wake On LAN but have never actually used it before, this tutorial might help:

Wake On LAN with BatchPatch

---

-Doug

[booster]

Hi gnussbaum

In this APP/DB scenario my scenario include a script where all APP services are first stopped and disabled, then the SQL services if needed (or only this one if no issue with the apps). Then all servers are patched together (same multiple steps jobs for all). I’ve so a better control in case of trouble and the patching itself does no more need any dependencies.

chose the best scenario following your needs :).

[Author]

Posts