Need to restart backend UIM database (Best Practice for restart order for UIM)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We need to restart or patch the backend UIM database or database server. In doing so, what is the best practice?

Environment

DX UIM 20.4.x/ 23.4.x

 

Resolution

After rebooting/restarting the database, it is best practice to also do the following:

1. restart UIM Primary hub robot, then wait for it to come up
2. restart CABI robot, wait for it to come up
3. restart OC robot

-------------------------------------------------------

Best Practice to reboot UIM servers:
All servers should be restarted one at a time and you should wait for them to come back online before moving to restart the next server.

There are many dependencies that will not be found if servers are all rebooted at the same time and come up out of order.

Order of restarts:

1) Database Server
2) Primary Hub
3) HA
4) Cabi
5) OC (Operator Console main node)
6) Other OC server (Operator Console other nodes)
7) SNMPCollector
8) Other secondary hubs 1 at a time. 
9) Robots as needed. robots can be restarted in bulk as long as hub has been restarted and is available.

---------------------------------------------------