IBM XIV Room for Improvement

Mark Cecil
Systems Engineer V, Enterprise Storage Systems at a financial services firm with 10,001+ employees
Management accessibility. Both the GUI and the CLI require installation of a Java-based thick client, which is ridiculous, plus a drain on resources. Also, if you have a large complex version of XIV, the GUI must contact and load each one of the units before the GUI is available for use. This is frustrating. I would rather have a web GUI served directly from the unit, and a CLI accessible directly through SSH. For multi-system management, it might be useful to have a thick client, or a hub of some sort, but there is almost no reason to have a GUI that requires communication with all of your units at once just to make a volume or mapping. View full review »
SysAdm 7291
Sr. System Administrator at a tech services company with 11-50 employees
* Copies * The power supplies * Expansion * Some Snap operations, regarding consistency groups * The change form synchronous mirroring to asynchronous (and vice versa) without reconfiguration from scratch View full review »
Hitesh Thappa
Senior Storage Engineer with 10,001+ employees
There are a few. One that comes to my mind is the pool resize restriction in the case of drive failure. Until the drive is replaced, the pool_resizing is locked. This has been an issue a lot of times, especially when the contract says IBM will not replace disks until three drives fail. (Single drive replacement can be requested as well in severe cases). View full review »
Systems Engineer II at a tech services company with 10,001+ employees
This product was not a good fit for our organization as we have a ton of latency sensitive applications and XIV was not able to keep up with IO + latency demand. Adding an SSD tier to improve the latency demand as this product was sold as being a Tier 1.5 array, but it is far from that. View full review »

Sign Up with Email