We are using a SQL Server 2005 cluster to host our SolarWinds db. Whenever we need to failover the instance the "SolarWinds NetFlow Service" stops and needs to be manually restarted.
All other SolarWinds services continue to run as expected. They log a few errors in the Event Log but they re-connect to the database.
Has anyone else seen this behaviour and found a workaround?
Alternatively, how can I increase the database timeout setting for the NetFlow service? The errors in the Event Log indicate that it is set to 20secs and it takes longer than that for our instance to failover.