Not much information is available if this is an appliance or something as an installable component for Linux/Windows – this latter one would be similar to the arbiter of Simplivity. No surprise if solution need a wuorum/witness which must – capitals – reside at third location. In current readyness VMware, MSSQL+Windows are supported, but they have sketched plans to support Oracle as soon as possible. Already procured and running Nimble systems will get the feature too. This is a huge plus, I go nuts if I see grey checkboxes that are not clickable only if you pay. Replication will be supported over IP only and as usual it comes without buying additional licenses. It requires the same type of model on both sites, but my question would be what if the target site has a more beefy model – is that an issue or not. There are still some unclear areas around sync replication. Async was always possible, so to some extent resilient data centers could be created in the past based on that. Some customers required to rule out even this factor and in order to do that sync capability was a must. It might be fair to state that the storage will not crash or die in any event, but it is still one device – so as Synergy – and components in it can be dupliated but all of those are in some rack units, concentrated to the same squaremetres. There are many cases where the storage systems itself can do such high availability, but other datacenter components, like cooling, power lines can’t. Important to mention this does not mean that Nimble systems cannot deliver 99,99999% availability – Infosight again there to proove it.
Some weeks ago it was offically – and finally – announced the arrival of syncronous replication in NimbleOS. You cannot twist and turn it, no need to understand the trio of CPG-Virtual Volume-chunklet.įor anyone who wants storage, fast storage without the complexities attached. Application that will run there? VMware? There you go. So if someone is keen to set RAID6+2 for a CPG and set AO up, Nimble is not for them.
NIMBLE VOLUME COLLECTION FULL
Simply summarized, if anyone needs full in depth configurable parametres. Nimble cannot and will not deliver the same what a 3PAR does. There are many clients using Peer Persistence and VMware Metro Cluster. Me: If you need syncronous replication you might want to keep using 3PAR.Īs opposed the Nimble pricing is pretty much in the ballpark of a similar 3PAR system, but it’s features list a bit shorter and clients who could afford such a storage could not take it seriously as a one-to-one replacement option of their 3PAR – or other vendor – storage systems. Me: Sure it is, asyncronous replication is supported.Ĭlient: But our two 3PAR storage can do sync. Rephrasing it, not issue but lack of feature. Is was all good up to this point, but had one quite important issue. (HPE can be self confident since majority of their installed base do report to Infosight, they can get exact real life measurements about the achieveable dedup/compression ratio. This latter can have a huge impact on useable storage since it does that really well but more importantly inline. This is something which is the top most feature of this product and the largest advantage of the platform, next to the well known deduplication and compression capabilities. Nimble was always on par with 3PAR in the midrange storage category, it was safe to say it can perform under sub milisecond latency, can squeeze 300k IOPS for sure. Sync replication and Peer Persistence setup – HPE Nimble
0 kommentar(er)
