Our physical Solarwinds database server is having SQL (and other non-Solarwinds patches) applied this weekend.
We have stopped our two VM Solarwinds application servers (one server has NPM, NCM and NTA on it and the other only manages the Solarwinds NetFlow database using NetFlow Configuration Manager) before but never stopped the SQL server. There will be at least two reboots of the Solarwinds database server during these patches,
What I was going to do was stop the main VM (with NPM, NCM and NTA installed on it) using the "Shutdown Everything" on the Solarwinds Service Manager app just before the maintenance and upon receiving the "All Clear" after the end of patching/return to online status by the SQL server, click on the "Start Everything" button and test access to the Web Console and go through the various sections. Good so far? If not - what would you do differently/add/remove/modify?
But is that enough? (The Netflow database is kept separately on the second VM server.) If it isn't enough, what more should be done?
Am I missing some caveats, gotchas and other miscreant occurences? If so, which?
I was thinking that it might be prudent to schedule a backup of the database server tomorrow with services stopped as described above - any feelings? The maintenance backups done by the SQL team before these patches are apparently normally done with Solarwinds services running and I am wondering if those backups be guaranteed good?
