I’m writing a doc to update our PM servers for Linux Monthly Patching schedules. We have the ability to have the servers staged to run in sequence of patching, and I was looking around to see if there is a best practice.
I want to ensure that I plan that the DB and DA and Console servers are staged properly. The DC's really don’t have a requirement of sequence, but I plan to do one 1 DC (per Data center) per stage.
What is the recommended order to bring the environment down and back up for regularly scheduled system patching at the OS level?
All supported Performance Management releases
It is recommended that we follow the same path an upgrade follows to ensure the servers are stopped, patched and started in the correct order.
This path helps minimize data loss on the Data Collector servers following this path.
Ensure successful database backups of the Data Repository and Performance Center MySql netqosportal and em databases are safely set aside before performing any patching. Without these we're at risk of unrecoverable failure should something go wrong with the server during patching.
The recommended order that follows the recommended upgrade path is as follows.