Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Some tips about high availibility

1 - Never uninstall HA on your active server. You can break it and never recover it correctly.

- If you do you cannot (from what I have tried and what solrwinds has talked me through) recover from this. You can't even reinstall NPM on the active server.

Though if someone else has done this then please tell me how this is resolved.

Find more posts tagged with

Accepted answers

All comments

shaun_9999

Just a quick update. From moving the services over to my less broken server I am able to install solarwinds again (currently running the config and install) if this works then This should be a sticky for anyone else who's stupid and doesn't take a snapshot.

aLTeReGo

shaun_9999, are you saying you stood up a secondary server, failed over to it making it the 'active' member in the pool, then uninstalled Orion from that server? I'm just trying to understand the steps involved that landed you in a vicarious position.

shaun_9999

Having a play, I discovered the following and it's respective action:

- Repairing all of solarwinds. This produces no positive results. I still had a corrupted solarwinds and was having issues connecting to the web front end.

- Removing solarwinds, the database and then the VIP and reinstalling. NB - I could have done this a little wrong, but the order I did it was remove the VIP, uninstall all of solarwinds and then remove the database. After installing solarwinds again I still had the same issues.

So, from my experience

How weird. This did not get sent. Anyways here is yesterdays stuff I wrote down.

shaun_9999

So this is the config I had:

I had two servers: one was active, one was passive. Both were in a HA cluster and it failed over and worked fine.

Now, after building this environment and making sure it worked and then presenting this to my manager, he said 'it's good, but we don't need it yet'. This is fine. I still needed the environment as I need to test quite a bit before I got live.

So I thought (without snapshot) I'll uninstall everything on my active server (I have no idea why) before I did this, I removed the DHCP reservation from the out DHCP server. Disabled the HA. Ensured that the HA was disabled and then proceeded to uninstall everything.

At this point I did think: I think I have just broken everything. I uninstalled everything from the most important to the least. After I tried to log back into my environment and couldn't, I then knew I had broken everything.

Jan_Pelousek

OK... Here are few minor uncertain things, which are maximally important :-)

You wrote you uninstalled your Active server while the HA was disabled - when HA pool is disabled, HA pool is not established or HA is globally disabled, it's the same situation as if you won't have HA at all.

Now depends on which server you uninstalled - was this the Original main server or the backup server? Here's quite temporary obstacle, where by default just the original main server is holding the license store.

If you destroy it, you won't get any license leases until you promote another server to the license server and activate the product licenses there. This article may clarify you some relationships - Migrate SolarWinds products to a new server with a new IP and hostname - SolarWinds Worldwide, LLC. Help and Support

Classic installers have implemented checks for the pools enabled state and are forcing you to disable the pool before installation. This is not truth for uninstallation process, which is driven by the product msi installers, where those checks can't be incorporated, so you need to keep in mind you need to disable the pool/HA before you plan to do some server maintenance to avoid unintended failovers

So in your case. Let's say we have servers A - Original Main server, B - Standby Main server.

What's supposed to be safe:

- Uninstall the standby servers while the pool is enabled or disabled. If they're active and pool is enabled, uninstallation here will invoke the failover back to main as the uninstaller stops the services.

- Destroy the Additional polling engines in HA pool - the second pool member will take the resonsibilities and the original license.

What is not supposed to be safe (currently):

Decomission the original main server regardless if this is active or standby. You'll destroy the license store

I hope it helps you to understand better.