In What order we should restart the SolarWinds server

Hi team,

I need guidance on the best practices for restarting the SolarWinds servers in our environment. We have a standalone DB server for SolarWinds, one Main Polling Engine, and one Additional Polling Engine.

What process should I follow before restarting the servers? Which server should I start first and then next? Is there a specific time gap I should maintain before restarting the other servers?

Find more posts tagged with

nta - network traffic analizer

support

Certified Professionals

solarwinds

solarwinds network performance monitor

Accepted answers

vinay.by

If you need a more detailed version of what I mentioned, then this is what I have been following for years as best practice and I have never got into trouble so far:

1. Stop High Availability service on all - where ever you have it, be it Main Poller or Additional Poller

2. Shutdown services on all additional pollers

3. Shutdown services on all standby pollers (if any - be it for Main or Additional)

4. Shutdown services on Additional Web Servers (if any)

5. Shutdown services on Main Poller

6. Reboot your DB Server - once it is back online - make sure you can access it and your DB seems fine

7. Now Reboot your Primary Poller (Main Poller) - make sure all services are up and give 5 mins so that it settles down

8. Reboot your Additional Pollers - give 5 mins for each additional poller so that the services are up and it settles down

9. Reboot your Standby Pollers - give 2 to 3 mins for each standby poller so that the services are up and it settles down

10. Start High Availability services on all - make sure HA is working fine for all

11. Finally, Reboot your Additional Web Server (if any, give 5 mins for each AWS Server for it to settle down)

Hope this helps.

All comments

vinay.by

Find the crono below:

1. Additional Poller (Stop SolarWinds services - don't reboot VM/Server), after all services are stopped go to Step 2

2. Main Poller (Stop SolarWinds services - don't reboot the VM/Server), after all services are stopped go to Step 3

3. Reboot your DB Server - Check if your DB Server has restarted successfully - wait for 2 mins - if you can connect to SolarWinds DB via studio do it - we ideally dont reboot the DB Server frequently - but yes you can based on your requirement.

4. Reboot your Main Poller (check if all SolarWinds Servers are back to normal) - check if all services are back to normal - wait for an additional 5 mins then proceed to Step 5

5. Reboot your Additional Poller (check if all SolarWinds Servers are back to normal) - check if all services are back to normal

Refer to the below url as well - its the same thing that I have mentioned above, but then this is SolarWinds KB

https://support.solarwinds.com/SuccessCenter/s/article/Orion-server-reboot-Best-practices?language=en_US

__PRESENT__PRESENT

vinay.by

If you need a more detailed version of what I mentioned, then this is what I have been following for years as best practice and I have never got into trouble so far:

1. Stop High Availability service on all - where ever you have it, be it Main Poller or Additional Poller

2. Shutdown services on all additional pollers

3. Shutdown services on all standby pollers (if any - be it for Main or Additional)

4. Shutdown services on Additional Web Servers (if any)

5. Shutdown services on Main Poller

6. Reboot your DB Server - once it is back online - make sure you can access it and your DB seems fine

7. Now Reboot your Primary Poller (Main Poller) - make sure all services are up and give 5 mins so that it settles down

8. Reboot your Additional Pollers - give 5 mins for each additional poller so that the services are up and it settles down

9. Reboot your Standby Pollers - give 2 to 3 mins for each standby poller so that the services are up and it settles down

10. Start High Availability services on all - make sure HA is working fine for all

11. Finally, Reboot your Additional Web Server (if any, give 5 mins for each AWS Server for it to settle down)

Hope this helps.

ImNishat

Thanks for your detailed information.

As of now, we are not using HA.