Connection Server – Patching and Rebooting

This post was originally published on this site

Looking for suggestions on how people are applying patches…actually handling the reboot post patch with multiple connection servers. They can be temperamental if not rebooted in order.


We have heard differing methods for handling reboot:

  1. Shut them all down, reboot 1st, wait for it to come all the way up…reboot 2nd, rinse, repeat.
  2. Shut them all down, power them all up at the same time


Our patch schedule is 1 connection server is considered ‘DEV’ and gets patched(and rebooted) a week prior to the other two, considered ‘PROD’.


We recently ran into these servers having sync errors. We were scratching our heads trying to figure out ‘what changed’ and the subject of patching (the reboot) came up.


How are you handling the ‘care and feeding’ of these temperamental systems?


Thank you and drive fast, take chances.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.