Orion in disaster recovery

Bump

bump

what does Bump mean ?

It's a way of knocking a post "up" a little (bumping it) so it will not get lost or pushed down in the queues amongst all the other chatter in hopes people will provide more (or any) information.

Having said that:

We don't have Orion in a DR state.  The best we have come up with is to put it into our DR site and run it from there.  All other options (using the Solar winds DR/HA software, putting things on VM's (to restore them in another location) or in clusters and failing stuff around, or adding multiple Orion systems and using a Ops Console) is currently too much to consider for us right now for Orion, but it will probably eventually be changed.

Our plan (today) is a simple one: If we have to do a DR scenario with only Orion, restore the database from backups and reinstall the software on whatever server we have (yeah there's more than this, like license keys transferred,having the proper software versions for the DB version backed up, etc.) but the gist of it is that the Orion monitoring system isn't considered a critical business app (for us) so it can take some downtime as we have several other monitoring apps to fall back on.  In a way, our DR plan is also having more than one monitoring system.

So you have no fail over to bring up Orion up in a critical failure?

Not something that's available at the flip of a switch. If it just totally tanked, or the datacenter it's in was suddenly filled with water, etc. we would wait until we were given the OK and a server(s) to restore to and we would reinstall the using database from the last backup and manually rebuild the app. Since Orion is not our single monitoring solution if its suddenly "gone" then the other systems could provide whatever status is needed until it could be brought back up, and probably cleaned up/reconfigured for any IP address changes of all the monitored systems.  In a way, we have a DR plan ("rebuild" plan, "have multiple monitoring systems with some overlap instead of a single point of failure" plan), just not an automated/High Availability one for Orion I thought you were inquiring about.

If Orion were our *only* monitoring app we would probably have a installation that would be built to stay highly available in a DR situation. Odds are we would go with any solution Solar Winds officially supports (Multiple Orion systems at different sites + Ops Console or installing the HA software...or both   I'm not sure if they actually support/recommend using VM migration or clusters for DR/HA for all components).

I have been doing Further research into this issue and it looks like the FOE services is the answer to Orion in a DR environment