Storage Manager - What we are working on...

We are currently working on STM version 5.7 and beyond (in parallel).  Some of the items we hope to deliver:

  • Storage Manager Server and Agent health and status overview
  • Product stability improvements
  • Preservation of Agent and Server settings on upgrade
  • Improved graphs
  • User-defined LUN Grouping
  • EMC PowerPath Support
  • Better "Storage Group" Dashboards


Disclaimer:  Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are based on the product teams intentions, but those plans can change at any time.

Dan

Anonymous
Parents
  • For me, the best thing SW could add is support for other MySQL DB engines - TokuDB or InnoDB. STM is used to monitor SANs in an enterprise environment, but the product itself has no redundancy (failover) and uses the MyISAM DB engine which is not ACID compliant. Not sure how big the average DB is for most users, but mine is over 300GB and growing. Any upgrades to STM takes 12-24 hours due to the required myisamchk. Myisamchk is single threaded. Even allocating maximum memory to all the myisamchk buffers (36GB out of 64GB), the process still takes 12-14 hours. Not sure when it became acceptable to have 12-24 hours of down time.  Don't get me wrong.  I love the product - when it's working, and always appreciate the new features - Just need a DB engine to match STM's capabilities.

Comment
  • For me, the best thing SW could add is support for other MySQL DB engines - TokuDB or InnoDB. STM is used to monitor SANs in an enterprise environment, but the product itself has no redundancy (failover) and uses the MyISAM DB engine which is not ACID compliant. Not sure how big the average DB is for most users, but mine is over 300GB and growing. Any upgrades to STM takes 12-24 hours due to the required myisamchk. Myisamchk is single threaded. Even allocating maximum memory to all the myisamchk buffers (36GB out of 64GB), the process still takes 12-14 hours. Not sure when it became acceptable to have 12-24 hours of down time.  Don't get me wrong.  I love the product - when it's working, and always appreciate the new features - Just need a DB engine to match STM's capabilities.

Children
No Data