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

Monitor Windows Service on DR Servers

I am looking for a way to monitor services on a server that is a DR server for a PROD server.

ServerA is PROD

ServerB is DR

ServerB has Windows Services that need to be monitored however if ServerA's Services (different names) are UP I need to ignore ServerB's DOWN Windows Services.

I think I have alerting correctly configured but cannot work out how to have the status of the node shown as UP or IGNORED or UNREACHABLE.

Any help would be appreciated.

Cheers

Find more posts tagged with

Accepted answers

All comments

dgsmith80

I would think the best bet is to set up two Groups one for ServerA and one for ServerB and add all the components you are monitoring into each group, then set up a dependency between the groups. I've never tested this, but in theory, should work! Let me know how you get on.

lstreet

The dependancy's only seem to work where if ServerA's Services are DOWN ServerB's Services will be considered UNREACHABLE and no alerts will be sent.

I kind of need it the reverse of that

dgsmith80

You could set a custom property flag for ServerB monitoring, so that if the Node, Application or Component are flagged as DR then the alert will be ignored. The only catch is you will need a trigger to remove that flag in the event ServerA is down and the DR is active. You could use an alert action to change the custom property values, but that gets a little bit more fussy.

mohitonline

There is no such sure shot answer for this question. however there are work around's

and how you want to get it worked out for you based on your environment.

ServerA is PROD

ServerB is DR

You can enable monitoring on both the ServerA is PROD and ServerB is DR

however ServerB is DR and services will show down all the time. but you suppress the alerts by using solarwinds new feature (Mute Alert)

and when DR happens, that means services will be up on DR server and gets down on Prod server.

Now you can un-mute the alert on ServerB DR so that alerts can be triggered.

and at the same time you can suppress the alerts by (Mute Alert) on ServerA PROD since services will be down on PROD.

lstreet

The solution I've come up with is:

Monitor Service on ServerA (PROD)

No Monitoring of Service on ServerB (DR)

Alert on Down Service on ServerA

Alert Action:
Powershell script that runs to test ServerB's Services and whether they are Started or Stopped.

If Stopped, send replica SolarWinds Email to designated people.

If Started, do nothing.

I haven't setup a Reset Action yet, but it will just be a replica SolarWinds email for RESET

Cheers,

Laurie