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

Hot-Standby Data Retention issue

Our primary SLX has data retention settings of 180 days, 180 days, 730 days (detail, hourly, daily). Over the weekend one of our additional pollers was down and our Hot-Standby server went active. It appears according to the log on the Hot-Standby that it ran db maintenance and had the default 7 days, 30 days....settings which cleared our database of a huge amount of data we planned on keeping. Even with the hotstandby actively polling, I can't access the system manager on the box. Support said this is normal behavior...I need to know how to make sure this doesnt happen again. I assume the data retention settings were in the db and that all db maintenance should be pulling from same location but I guess that is not the case. Is their a registry setting or config file on the hotstandby I need to edit?

Find more posts tagged with

Accepted answers

All comments

vhcato

Does anyone know the answer to this? If this is normal behavior, that's not good...

FormerMember

Yeah, I'd sure like clarification on this too. This is not good. Our settings are not default either. I've been under the assumption that the data retention settings were stored in the db and used by the HS server.

Brian, thanks for bringing this to light!

FormerMember

Data retention settings are stored in the registry, so you need to set them to be the same on the Hot Standby server.

vhcato

Denny,

We are about to make some significant upgrades to our Orion implementation, and as part of that, we are considering the purchase of a Hot Standby Engine. Unfortunately, I was unable to find any official documentation detailing its true capabilities. As a result, I spent several hours looking through each and every thread resulting from a search, which really shouldn't be necessary.

Is the Hot Standby Engine considered a strategic product going forward? If so, would it be too difficult to create a document to help customers understand exactly what to expect with regard to its capabilities, and also to point out little gotcha's like this registry setting that could (and apparently has) bitten people in the form of a significant loss in collected data? Having this documented would be quite valuable to customers who are considering purchasing this product, as well as to those who own it today. Some things that should be covered are issues like the one noted in this post, as well as spelling out exactly how and when the fail-over function takes place, what services are covered such as base polling and statistics collection, web, and additional module support (if any), and if it provides any services while in the "standby" state, such as the website.

FormerMember

Vic,

We plan to continue support for Hot Standby, and we also intend to expand its capabilties, although I have no firm timeline for the latter. I'll share your comments about the documentation with the rest of the team.