Amazon Elastic Block Store (EBS) from AWS is designed for application workloads that benefit from fine tuning for performance, cost and capacity. Typical use cases include Big Data analytics engines (like the Hadoop/HDFS ecosystem and Amazon EMR clusters), relational and NoSQL databases (like Microsoft SQL Server and MySQL or Cassandra and MongoDB), stream and log processing applications (like Kafka and Splunk), and data warehousing applications (like Vertica and Teradata).
N/A
HPE 3PAR StoreServ
Score 7.4 out of 10
N/A
HPE 3PAR StoreServ is a flash storage option, from Hewlett-Packard Enterprise.
It provides the optimized storage performance and cost for your workload and these options really work with SSD-backed storage and it improves the database performance. Keeping backups of your EC2 resources, including EBS volumes is a little bit tricky and its takes some more time and increase through put is also a tiring job to do.
HPE 3PAR StoreServ is a great storage device for both file and block-level storage needs. You can use it in place of SAN devices required by database servers. It provides an amazing compaction ratio and, hence, reduces overall storage footprint and cost. This is, however, slightly costly if your environment doesn't really see high transactions most of the time.
We are using HP 3PAR storeServ 8200 for both our file level and block level storage.
I really love the amazing compaction ratio provided by HP 3PAR. Some of our disks have compaction ratio above 25:1, which is super amazing. You can definitely look for around 75% reduction of storage footprints.
It has a great user friendly web console "SSMC"(StoreServ Management Console). This is an additional bonus and can be used by even non-storage people like DBA and Network to take a look at storage performance.
The system requires a physical or virtual system to manage upgrades and patches and for call home features. Most other systems have this integrated into the array. Just another piece of infrastructure to manage.
There are some system jobs that come pre-scheduled in the initial setup, but there is at least 1 job that should be added to this by default. When you delete storage, you also need to run a job to compact the CPG (a group where the luns all reside) to reclaim the previously used storage as free. This should be done by default at least monthly in the background.
There are 2 different GUI front ends that can still be used. The older version (3 PAR management console) is being phased out (has been for 3 years).
We are very satisfied with 3PAR performance and especially the IOPS (Input Output Per Second) is pretty amazing. It is easy to configure and doesn't require much knowledge of storage for Tier 1 support team.
Amazon EBS is a great tool and fairly easy to use as long as you are familiar with the Amazon Web Service ecosystem. It allows a great way for you to move storage around easily and allows you to quickly provision storage as needed based on the business requirement. For us, it's easy to move between our EC2 images that had been linked with EBS storage between these Amazon accounts.
The support for Amazon Elastic Block Store is great as long as you can articulate your needs. Like most tools, there may be some back and forth before you find a support person that is knowledgable in the tool and can provide you with necessary insights.
With their phone home technology, we usually have a replacement part on its way by the time we wake up in the morning, or if the event occurs overnight. We have had great support when we had questions or events that required a call.
So far I have only used Amazon Elastic Block Store (EBS) and Azure but comparatively [I] prefer AWS elastic Block store as its having more advantages than Azure and I found it quite satisfactory and it helped a lot for information storage. We are not looking for any other hosting provider at this time.
We still use NetApp storage enclosures at each plant for our routine file shares (CIFS) but I would love to swap them out for the HPE 3PARs as we use for our ERP app data. The 3PARS are simply faster and much better at near-instant replication. But even more importantly we can get the reporting that we need from the 3PAR within a few minutes, even custom reports. 3PARs are much easier to manage than NetApps in general and I think that the only place that they compete is in compaction.
When your application needs high IOPS storage, this is a great solution that will keep your business functioning.
Without Amazon Elastic Block Store you could try spreading your data across several standard drives, but that introduces complexity and still has IOPS limits.
