We patch all our Windows Servers that host a BL infrastructure component through BL since a long time now and had no issues so far.
As our DB is running on Solaris which isn't patched that often, we are in the lucky position that we can reboot the App-Servers one after another without taking the whole System down.
To achieve that, we take the AppServers out of the Authentication-Load-Balancer address and adjust the Job-Rules, so that they don't do any work.
In your scenario to minimize downtime you could probably reboot them all at once, as when DB or FS goes down, the AppServers are have to be shutdown anyway.
Thanks. Is it also possible to set any server/job property to isolate only the BL appservers alone, from rebooting at the end of job, while other servers targeted as part of the patch deployment will be rebooted on completion of patching?
1 of 1 people found this helpful
not within one job, as the Job can either Reboot or Not.
You would need to use a separate Job with different Reboot options to make sure certain servers don't reboot.