HPE Community
Server Management - Systems Insight Manager
1753325 Members
5024 Online
108792 Solutions
New Discussion

Who Me Too'd this topic

Tom Keck
Occasional Advisor

‎04-30-2013 07:37 AM - edited ‎04-30-2013 08:06 AM

‎04-30-2013 07:37 AM - edited ‎04-30-2013 08:06 AM

Insight Control upgrade concerns

Experts,

During an attempt to upgrade our Insight v6 installation to V7 by an HP Support employee, our entire Insight database was corrupted.  Multiple attempts to recover from our SQL backups were unsuccessful due to DB table changes between V6 & V7.  Several complete server rebuilds & data restores back to V6 and re-upgrade attempts repeatedly corrupted the database. Finally we stayed on V7, rediscovered all systems and spent weeks recreating the many customized Insight collections and reports we had developed over many years.  Months later, after repeated complaints and escalations to HP, the answer we got was that the problem cause was that there was more than 50K events in our DB and that's why the update failed.  Does that sound reasonable to all of you?  If that's the case, the installation procedure badly needs to include checks for this before it proceeds!  Also, I've found that the provided event cleanup tasks only work when run manually but don't work when run by schedule if there are too many events.  Our CMS is an HP BL460 G7 server with 48GB of mem with the DB on a separate 3 node 96GB G7 SQL 2008 Enterprise cluster so this 50K event limit has got to be just poor programming inside Insight.   Has anyone else had this terrible misfortune?  What is HP doing to warn and prevent this for other customers?

"Never attribute to malice what can be adequately explained by ignorance or stupidity." - Isaac Asimov
1 person had this problem.
Reply
Who Me Too'd this topic
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.