What is your primary use case for HPE 3PAR StoreServ?

It has dynamic allocation. I have 16 terabytes of storage allocated to various nodes as external storage. It has met our needs. We’re looking for something similar with enhanced scalability. We have about 96 servers and want to increase that to around 200. We need a centralized solution that can easily scale and integrate different types of storage.

We have 70 virtual machines, which include various services such as Active Directory, mail server, phone server, file server, security, firewall, and antivirus.

We are a telecom company. We are using the tool mainly for processing applications.

I primarily use the product for self-storage.

We are using the solution for capacity storage.

We use HPE 3PAR StoreServ for storage. We need stable storage solutions for the virtual machines in our organization.

The solution is mostly used for storage.

We are using HPE 3PAR StoreServ for our main enterprise application database. We have a split of hard drive usage in the solution, such as SATA drives.

StoreServ is one of several storage solutions we use, and we also have some SAP and high-availability application workloads. We use it for storage and also as a backup repository.

We host and store everything we have in HPE 3PAR StoreServ. We created the laws and connected them to our servers, and on those servers, we have VMware as a hypervisor. We make backups of all the data from the servers.

We use 3PAR for data storage in a factory setting. We currently have about 200 users working with it across multiple departments, including production and finance.

Our primary use case of this solution is to store all share market data. It's a depository system and we store the share market data and transactions in the central repository. This solution is deployed on-premises.

We use HPE 3PAR StoreServ for all the storage needs for the hospital I work at.

We use it for our financial system.

We use the solution for database backups.

We use it on a project basis and based on the customer's requirements. We use the HPE systems in data centers with servers and virtual environments. This is the most common use case.

We use this product as our primary storage. We are in the manufacturing industry and we use the HPE 3PAR StoreServ to store our company data and then we can retrieve it as required.

We use HPE 3PAR StoreServ for data storage. Hewlett Packard Enterprise (HPE) had something in the contract because if you can compress data very well, you don't need that much capacity in your systems. If it was not possible to compress to a certain degree, they put some extra capacity in the systems. We bought that borrowed capacity but they separated the one-piece storage boxes added to our environment to get along with that bigger growth in capacity. Despite that, it is a wonderful system with an excellent graphical user interface. Still, new functions are being rolled out.

We use the solution for multiple business applications, with SharePoint, our internal management system and Exchange 2016. We are customers of HPE 3PAR and I'm a system engineer.

This solution hosts our core banking system. Mostly everyone in the bank uses it — about 1,000 users.

I want to build a MetroCluester in VMware.

Generally, clients use the solution as primary storage or data storage for corporations. They also use it for data replication where they replicate to another site or even on the same site. They're typically replicating the data for a backup situation.

We use it for all kinds of needs, such as infrastructure needs, and application services. We are using the latest version of this solution.

It is used in data centers. We are using HPE 3PAR StoreServ 8400.

I use 3PAR as the standard storage. The main production is VMware, and it is connected to 3PAR across fabric switch. The fabric switch between them is MDS Switch and Notebook 8. We also have a Hyper-V environment, which is connected to the same storage. The main service is the exchange service. I have a public cloud and a private cloud. I use 3PAR as a private cloud.

The primary use case of this solution is for clusters, database work (Oracle and MySQL), and storage.

We use it only for storage.

We use the 3PAR to host our SQL Database and Oracle Database. We also use it for VMware and vCenter.

We use the StoreServ as our main storage device. We have one unit in the main site and the other in the DR site, with replication between them. We have a file server running, it hosts our database, and it acts as our Exchange server.

We primarily use the solution as on-prem with local SAP HANA application servers. We have five of them.

We are using it for Oracle Databases. We're are also using it for VMware and NetBackup. It's one of the storage solutions for NetBackup.

We use this product for our server storage. Our systems are primarily used for ERP.

I use this product in VMware Shared Storage. I work with VVoL, but I have a problem that is related to the update.

We have deployed HPE 3PAR systems on all database-related storage including MSSQL and Oracle. All of the SQL databases are running on VMware, and the database-related storage is mounted as RDM. The Oracle database is mounted directly to HPE 3PAR with remote-copy enabled.

We use this solution for mixed, unpredicted workloads.

We use it for the production and backup environments. We use it for a service that we deliver directly in our data center for our customers. It's a live environment, directly for the customers.

We use 3PAR as our primary storage array.

Our primary use for this solution is data storage.

We provide DoD services for military healthcare. The storage is used for healthcare delivery.

We use this solution internally for our test environments.

It is our primary storage for all of our data. Everything from personnel systems to file shares, print services, and databases are mission-critical applications that we run on 3PAR.

Primarily, we use it for SAP storage. At this moment, we are running an ERP system on it. SAP is our mission-critical app.

3PAR is our primary storage for everything aside from VDI, which is where we are using our Nimble. We use everything from point of sale to database. Those are the two big mission-critical applications. There is also virtualization for servers.

It is our main storage solution for our entire VMware environment. Everything run on the solution is core: MEDITECH, all the EMRs, and back-ends support services. We use a combination of flash and spinning disk. For some of our less critical functions, since we run everything on the 3PAR, there is no reason to spend the extra money on flash to run the stuff that is not super mission-critical.

It is storage for our SAP environment. SAP is the mission-critical application that we run on the solution.

It is our primary storage. The entire company runs off 3PAR. Right now, we are in a VMware environment. All of our virtual machines are stored on 3PAR, along with all of our EMR applications, practice management solutions, and email. All of our virtual machines are running off of 3PAR. Our file server is on there too.

The primary use case is DR. We use it in the automation industry.

We're currently running two 3PAR 7200 storage units in high availability. We have three workload tiers. We have Nearline, FAST class, and SSD. Our primary ERP system is an Oracle JD Edwards running on Microsoft SQL Server 2008 R2 that is all on SSD. Then, we have other workloads for our barcode. Our engineering solutions are running on FAST class, and then most of our traditional file and print, storage, and workloads are running on Nearline SATA. Also, have two 4200 LeftHand SANs in the environment. I put very low priority VMs on those two LeftHand SANs. They are minor application servers. They don't need a whole lot of performance. However, the LeftHand SANs are now seven years old. The 3PAR SANs are now five years old, and I have to replace everything in 2020, and I'm looking at HPE SimpliVity, Nimble, and potentially 3PAR as the storage architecture for that environment. Our JD Edwards, which is our ERP system, that is critical. Also, our barcode scanning, because we do a lot of barcode scanning out in the shipping and manufacturing warehouse. Our accounting system is part of the JD Edwards too. All of that is on the SSD. We're currently evaluating whether we upgrade to JD Edwards 9.2 or if we deploy Microsoft Finance and Operations. If we go with Microsoft Finance and Operations, that'll be totally in the cloud, and I'll be able to carve a third of my storage requirements out because it will no longer be necessary to run an on-premise ERP solution. My directive when I was hired in 2016 as a direct IT manager versus an outsourced IT manager, as I was when I started in 2014, is anything and everything I can take to the cloud goes to the cloud. If I do that, it reduces the need for all SSD on-premise, and that's actually what I'm trying to get to, because I'd rather utilize Microsoft Cloud, Azure, Office 365, and Dynamics 365. I want to utilize that cloud for my performance, whereas on-premise traditional file, print, and storage doesn't really need SSD.

We use 3PAR for everything. There is not much we don't use it for. Most of our storage is on 3PAR at this point. We run SAP, VDIs, and all of our server infrastructure on it for the most part as mission-critical applications.

We use it for mission-critical apps and database. It runs our core banking applications.

It is for the storage that we use. Our entire banking system is on it, which is mission-critical.

We use it for our file shares, our virtual hard drives, and for all of our Hyper-V clusters. It stores everything, like backups. We have virtualized almost all of our servers, except the ones that require high I/O, like maybe our SQL Servers. Everything else in the entire organization runs off of our 3PARs. We actually aren't all-flash, but we do have flash drives for our hottest data which is used most often. This definitely makes everything much more efficient.

The primary use case would be disaster recovery and uptime. The entire company and our fire pump division, for the most part, are run on this solution. Getting rid of spinning media is our primary objective.

We have two use cases: * We use it with our internal applications, so for internal use. * We are provider of national research computing infrastructure. Therefore, we are using it out there with all our systems. There are not many mission critical applications or processes that we run on 3PAR. The mission critical applications are usually the ones for internal university purposes, like ERP systems. Our research systems are not a mission critical since our researchers can run their computing again in a week.

We use three power arrays. The first array is for video storage and video surveillance. The second array is for production of our virtual machines. Pretty much everything is run on one of these three systems.

We use 3PAR as our centralized storage for database use, mostly. It's also data stores for our VMs. We have a few Oracle Databases running on 3PAR and we have our production VMs running on 3PAR, as well.

As a partner, we use it to run databases and for virtualization. Another use case is the cloud.

The primary use case is production data. The mission-critical app that we run on this solution is SQL.

This solution provides flash storage for our servers. Our environment contains Linux operating systems, VMware, and some web servers.

We use this solution for low latency, high-performance workloads.

Our primary cases for HPE 3PAR Flash Storage 7000 are: * Transport sector * Four nodes, 1000 virtual machines * Entire rack solution * Partially flash * 350TB (dense IO).