≡ Menu

EVA Management Utilities, Techniques, Tips and Tricks

Welcome to huge hallways

I’ve got a few minutes over the lunch break to post some comments about this U-Conn session that I’m in now, entitled “EVA Management Utilities, Techniques, Tips and Tricks(PDF)” by Gary McCready.

Here’s a summary of the Nuggets O’ Knowledge so far received:

  • When using Command View in a DR setup, the active CV box should be on the offsite location, because sometimes there are problems transitioning control to the DR site.
  • Don’t be surprised… the Command View service has to be restarted from time to time.  Just a sad statement of fact.  Maybe someday HP will fix Command View, or Microsoft will fix Windows.  Or both.
  • Four is the practical limit to the maximum number of EVAs that can be managed by a Command View server (contrary to the maximum of sixteen that is in the product specifications).
  • There are generally only two reasons to create more than a single disk group on an EVA
    • you have different sized disks, and don’t want to be hit by a capacity penalty by mixing them in a single disk group
    • you have a users that require having their data on separate spindles (a weak reason, but it exists anyway).
  • For Redundant Storage Sets (RSS) the sweet spot is eight drives.  Try to build disk groups in multiples of eight.
  • After replacing a failed disk, the status of the disk will go to rebuild and then leveling.  Leveling can take days or even a week or more depending on the size of the virtual disks, the array, traffic, usage, etc. etc. etc.
  • If there is *any* disk failure on an EVA, *all* Raid-0 virtual disks will fail and all data there will be gone.
  • SSSU will be my new best friend.  Storage System Scripting Utility enables the storage administrator to execute scripts to configure, manipulate and check status of storage.  Anything that can be done with HP Command View can be done with SSSU.  But the converse is not true — with SSSU the storage administrator has a tool that can execute easily repeatable, scriptable commands and capture their output.  Extremely useful in federally regulated companies (think pharmaceuticals, banking, etc.)
  • HP is working to enable SSH for SSSU.
  • HP Replication Solution Manager… good perhaps for small environments.  Good for simple tasks, and cannot manage more than four simultaneous “jobs.”  Not well supported by HP.  Read: Use SSSU and Command View instead.

That’s it so far… Jealous?  Anybody out there an SSSU, Command View or RSM expert that can chime in?

There will be more information after the second half of the session… in progress…

Spread the love

Comments on this entry are closed.

  • Matt June 21, 2010, 5:46 pm

    Only four EVA’s managed by Command View? I wonder what the limiting factor is, other than poor programming. How hard can it be to send a few SCSI commands and store some data in a database? Sheesh.

    SSSU sounds like it would be a nice tool. Hello, Nagios. 🙂

    • mike June 23, 2010, 12:14 am

      To be honest, this assumed that the EVAs are active and have replication running. Four is the maximum number you can reliably manage. After that, the load on the controllers and log files starts to have more of an impact on Command View reliability.

Next post:

Previous post: