David, Good to see that kind of paranoia!
I am glad that we am not the weird one who is doing all these things every month. -----Original Message----- From: david klein [mailto:[email protected]] Sent: Monday, February 21, 2011 8:27 AM To: spectrum Cc: spectrum Subject: Re: [spectrum] FW: SpectroServer and Widows Updates It is strongly recommended that you develop a maintenance methodology in which you have a person explicitly bring down cleanly the applications, explicitly initiate the patch/update set installation, give the shutdown/restart command, and validate the application when it comes up. Applying this rigor and process will allow more controlled behavior of your application and environment, and fewer surprises. Also, are you vetting Microsoft patches in your Dev/Test environment before allowing them to touch your *PROD* application server? If not, how are you certain they won't break your PROD application? Lastly, are your main and FT SpectroServer getting the patch/reboot at the same time? If you are, then you are kind of negating a major value of an FT application architecture. A sample MM might be: - Get change approval from the CAB - Run through patch testing during the day in D/T - Validate, Validate, Validate - Notify all your users - At the start of the maintenance window, send out a follow-up email reminding - Run the patch in the FT server - Reboot the FT server - Validate the FT server - Make sure your Spectrum is working in the FT server - Notify your users that you will be going into FT stand-in mode, and that they may need to restart OneClick so that it takes over on the FT side - Force failover from the Main server to the FT server - Run the patch in the main server - Reboot the main server - Validate the Spectrum in the main server - Either run backwards (stay in the FT server, and wait for the next maintenance/failure to flip back to the main server) or notify your users and flip back now during your maintenance window. On Tue, Feb 15, 2011 at 11:53 AM, Gaines, Reba R <[email protected]> wrote: > Has anybody experienced the following: > > > > We have Windows updates install periodically but automatically on the > Spectrum server. Upon system reboot, the SpectroServer is taking longer > than processd allows so it forces a shutdown as a last resort. When the > server comes backup, the processd is started but the SpectroServer isn't. > Thus, every Tuesday just after 3AM my phone rings, "Spectrum is DOWN". > > > > Any thoughts? > > > > Reba R Gaines, MBA/TM > > Unicenter/Solarwinds Systems Manager > > Ciber Defense Technology Systems > > 200 Westpark Drive, Suite 330 > > Peachtree City, GA 30269 > > > > (770) 268-7448 Direct Dial > > (678) 449-9080 Mobile > > > > --To unsubscribe from spectrum, send email to [email protected] with the > body: unsubscribe spectrum [email protected] -- david t. klein Cisco Certified Network Associate (CSCO11281885) Linux Professional Institute Certification (LPI000165615) Redhat Certified Engineer (805009745938860) Quis custodiet ipsos custodes? --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] ---------------------------------------- This message is intended exclusively for the individual(s) or entity to which it is addressed. It may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
