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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Longhorn is performing well as storage for databases and in almost any solution that uses exclusive access to volumes (ReadWriteOnce in Kubernetes nomenclature). When write access is required from many clients (ReadWriteMany) Longhorn Block Storage covers its volumes with NFS (file-based) access. Longhorn Block Storage also is well fitted in every architecture where data security (snapshots, backups, multiple replicas) is more important than access speed (in terms on IOPS and MiB/s).
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
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).
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
ReadWriteMany Longhorn volumes are still using NFS (file-based) protocol in the core.
Using iSCSI as main protocol instead of FC ties Longhorn to Ethernet-based LAN which is in most architectures much slower that FC-based SAN.
Longhorn could implement S3 as alternative access protocol to its volumes.
Backups, and snapshots configuration could be configured at each volume-level by administrators (maybe from additional CRD object?), because currently is configured at storage-class level which is not granular enough.
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Longhorn is mature software defined storage solution that is still developed and receive new functionalities. From the beginning every Longhorn volume have multiple (at least two) replicas, can leverage manual or automatic snapshots and backup to external S3 volume. Longhorn provides nice and clear GUI for administrators, but also can be managed from CLI.
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
GlusterFS was first Persistent Storage solution used in our Kubernetes-based clusters. It is file-based what in some usages led us to many data corruptions. CEPH is object-based persistent storage which can be used as file-based Persistent Storage in Kubernetes. It is also is much more resource-hungry than other solutions including Longhorn. Dell PowerScale (or Isilon) is a hardware-software solution, that provides volumes that can be accessed by file-based NFS and CIFS protocols. Recently was added access to its volumes with object-based S3 protocol. Longhorn is in the middle. It is block-based, it is build on industry standards like iSCSI, performs very well on 10Gbit or faster LAN and commodity hardware (or in virtual machines)
