How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
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.
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 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'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.
The primary use case is DR. We use it in the automation industry.
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.
It is storage for our SAP environment. SAP is the mission-critical application that we run on the solution.
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.
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.
Primarily, we use it for SAP storage. At this moment, we are running an ERP system on it. SAP is our mission-critical app.
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.
This solution provides flash storage for our servers. Our environment contains Linux operating systems, VMware, and some web servers.
The primary use case is production data. The mission-critical app that we run on this solution is SQL.
As a partner, we use it to run databases and for virtualization. Another use case is the cloud.
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.
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 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.
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.
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.
We use this solution for low latency, high-performance workloads.
* Transport sector * Four nodes, 1000 virtual machines * Entire rack solution * Partially flash * 350TB (dense IO).
It's used for allocating disk to many servers.
For use with a major database for telecom customers who need to collect all of their customers' information.
It is our main point of storage for many applications. We use VMware so we have all the hosts connected to the 3PAR and that's the central point of storage for our whole organization. It's definitely critical, we can't live without it because that's where all the servers and data are hosted, on the 3PAR.
The our primary use cases for 3PAR are: * We have some secure applications which use it. * We have some built-in, embedded applications that we use on it. * We have some major critical applications which run on 3PAR. * We are using flash arrays 2850 and 8440. The company has been using 3PAR for approximately eight to 10 years. I joined in 2015, and since the day I joined, we had these 8440s flash arrays. Lately, this year only, we bought these new flash arrays, because we had some issues with the 8440s, especially with the drives. After we migrated the 8440s to the 2850s, we have not been seeing performance issues anymore. It seems as if all of the performance issues have disappeared, which is a big achievement.
It's the main storage system, both for the primary site as well as the DR site. We have complex business needs. Our business has multiple databases - both Oracle and SQL - an Exchange environment, Active Directory environment, websites, web servers, SharePoint. We have a variety of use cases - including development VMs for custom web apps - all being stored on 3PAR at the primary site. The DR site gets Veeam backups of the primary site, so we have the backup recovery on our other 3PAR.
Our use case for 3PAR is for all our block storage. Our biggest consumption for 3PAR is for our hypervisors, VMware and Hyper-V. We're almost 90 percent virtualized and 3PAR fits the need for hypervisor environments very well. We got our first 3PAR in 2008 or 2009 and we're up to 71 3PARs now.
It's for storage, provisioning to our R&D teams. The developers provision the storage and test their products. The storage is critical for our development.
We deploy 3PAR across all of our locations, Canada-wide. It provides primary storage. It covers complex business needs. All of our financial applications sit on it, all of our databases sit on it. We also use it for unstructured data storage, and we're about 95 percent virtualized so it runs all of our virtual workloads.
We use it as a primary storage device for user data and applications. It covers complex business needs in our organization. We have a lot of secure data on there. A lot of our financial applications run on our 3PAR. It has been excellent. We've got a 7440c at my office and then we have two 8000 series at the other sites. We're using Adaptable Optimization, we've got the different tiers of disks. We find that the performance is excellent, really excellent.
Normal file storage, SQL databases, Cache databases, and replications to our DR instance. The business needs it covers for us are not highly complex, only a little. Performance is good. We've had some issues with doing virtual volume updates using Snapshots. We've had some issues with the dedupe garbage collection process as well. Supposedly those have been addressed with the latest OS update that we've yet to apply.
Low latency storage for production trading systems. We have multiple trading platforms which are trading different products regionally. The complexity comes when we are applying those trading algorithms globally. It has to be efficient in executing those trades, getting the right prices for the customers with the right spreads for the customer. You have every global FX currency that is present plus equities and future options. If you put all these things together, it gets quite complex. We have been extremely happy with 3PAR so far.
Virtual machine data storage. It's serving one specific business need. It is performing as expected. It hasn't been fully exercised as we're still moving production onto it.
The primary use case for 3PAR would be security video recording, and the security video is used for multiple purposes. In the healthcare environment, it will be used for real-time locating, patient wandering, infant abduction, asset tracking, and staff duress. Taking it to the next level of healthcare, in pharmaceuticals one has to keep track of the production and movement of products and retain those records for a period of two years, as per federal regulations. So now, we need multiple levels of storage: immediate storage, short-term, and long-term, with the data being kept for up to two years. In these scenarios, 3PAR is an ideal solution, and we've had a lot of success because of its capabilities and the different types of storage. You can mix SSDs with running drives and slower drives for longer-term storage, minimizing your cost but maximizing your storage. And you can also evolve storage as needed. You can increase the amount of storage by adding in drives on the fly, as the need arises. 3PAR provides a very ideal solution for some of my customers.
VMware and SQL. In terms of performance, we had an issue with the earlier version, the 7400, an iSCSI issue. They replaced it with one from the 8000 series and it has been doing pretty well so far.
Our use case is primary storage.
It's primarily used as our primary SAN, storage area network. We store all sorts of data and VMs on that particular set of disks. It's for local data center usage. We have three data centers now, one in Atlanta, one in Dallas, one in Provo. We aren't doing any site to site replication. It's really just localized and we're trying to get to a point where we are actually doing site to site replication for DR and things of that nature. The performance is good. We enjoy it. We like it.
It is for our IT. It is our kitchen sink; we use it for everything.
We target 3PAR because of the availability aspects that it brings with a synchronous replication. I work with a lot of medical and larger business organizations which are looking for the ability to run stretch clustering between data centers. If they lose a full data center, they can use this to flap over live without application downtime. This is probably the biggest thing that comes into play from an availability aspect. Then, there is also inherently a lot of the performance which comes with it. E.g., if I have a lot of high demand applications, it is one of those where the system, the all-flash array, the 8450, and even the 9450 that recently came out, can keep the latency and response time down.
I am with a healthcare system. It is for our electronic medical record. It has been fantastic. No issues.
It is our primary storage. We use it with our VMware environment and all of our high performance applications are stored on it. I work for an equipment distributor, but we have various business lines: everything from earth moving to electric power generation. These are very different needs. Then, we have our accounting system which is on there, plus business intelligence. All these are different types of workloads. We purchase the 3PAR that has flash tier and we can migrate between the spinning disk and flash. It seems to work very well. It self-optimizes. I do not need to worry about it. It does its job. It is the self-driving car. You let it do its thing and it gets you where you need to go.
We are using 3PAR for production workloads, processing insurance policies and claims, file shares, and storage. It has been performing well so far. We have had a few hiccups on the configuration side, but we have been working with HPE on them. For the most part, the product has been pretty seamless.
It is for mission critical storage. We use it to keep high uptime. We have two 3PAR systems that we leverage. Its performance is good. We have a lot of applications that have high I/O, and 3PAR handles those with no problem.
We use it for virtualization, vCenter, and infrastructure. We have simple needs. We are a very small shop and are not a technology company, but we do have mobile apps and websites that we provide to our customers. I am new with the company. I have only been there about a year now, but I understand that they have had this system for at least three to five years. The performance has been fantastic. It has not had many issues whatsoever, and what issues they do have, the support picks up on it quickly. They send us tickets saying that they are doing work without us even having to engage them. So, that is very nice.
It runs all our tier one and two apps. Right now, we are replicating between two 3PARs and two different data centers. We use for our tier one and two apps, so they can do failover, synchronous replication. We have been running 3PAR for three years. It was running well until we tried to split our two 3PARs and put them into two different data centers. Then, we had a lot of problems.
We use it as a shared storage solution for a virtualized environment. It is not for complex business needs. It is really just for storage, and not even a very large amount of storage: between 20 to 40 terabytes. We have used it in three environments. We were not happy with the performance initially, because it turned out the system was initially designed for Fibre Channel, and we needed iSCSI. So, we used the iSCSI configuration option off of 3PAR. This was probably when 3PAR was purchased by HPE, but the performance were extraordinarily bad in terms of I/O capabilities. It took a long time to obtain HPE's help and resolve the issue. This was for iSCSI in the context of VMware for shared storage.
Our customers use it for primary SAN storage. They have multiple business needs for their enterprise-class business, e.g., for high-end data processing, oil, and natural gas. We also have media customers, who are trying to use it. The businesses are predominantly all verticals who use it. The performance is awesome. It is one of the best storage products comparatively to like size competitors. I am a big fan of 3PAR.
We use this for our highest tier level applications, our tier 0 through tier 2, so those are our mission critical and business essential type of applications. We want to make sure that we have the most critical things running on the best equipment that we have, and it is performing well right now. We have been working with 3PAR for almost three years now. We leased two arrays, struggling with it a bit. However, HPE did right by us and provided the resources (people, hardware, and additional storage) to do what we needed to do.
We use 3PAR as our main production environment. Therefore, we use it for everything from VMware to our NAS solutions. It is used for complex business needs, because we also store all of our databases on the 3PAR as well. We have a lot of systems at the airport where I work. So, we have a lot of Oracle databases, which run a lot of core functionality. This includes the financial systems. We have a large maintenance program, and we have to track all of our maintenance needs. This is all done through an Oracle database. All of these databases are on the 3PAR. We have about 500 users. All of their user data is stored on the 3PAR for groups and user data. Then, most of our environment is in VMware. Thus, we have a reasonable sized VMware environment of about 700 servers, and that all runs off of the 3PAR.
We are using it for the storage for our on-premise servers, which are both Oracle workloads, as well as having many VMs. We have a lot of complex business needs around legacy things. Our organization has been using 3PAR for about a decade. The performance has been good.
Our primary use for 3PAR is virtualization, SQL Server data, and backup logs. We also use it for our Citrix VDI environment. We have been using 3PAR for two years. It has been performing as expected. We are actually getting ready to invest a big chunk of money to expand our 3PAR.
It hosts our virtualization platform. It works really well.
We use 3PAR as the primary storage in our environment for all our Tier 1 applications. We have been using it since 2015. It has performed well. You guys have gotten a lot better with the 8000 and 20000 series.
It is our primary storage array for our virtual environment. We implemented it in the beginning of 2016. It has done well for us.
3PAR completes the HPE solution for my clients. It gives them an environment that is straight HPE from a storage perspective, from a networking perspective with Aruba, from a compute perspective with Synergy. It completes the whole show with 3PAR on the storage side. The performance of 3PAR is beautiful.
We use about 40 percent of our workload in 3PAR. We have 3PAR 7400, V-Class series. We use dynamic tiering, so we have a mixed workload, SSD Fibre Channel and Nearline storage. In terms of performance, it has been a little bit up and down, but overall there isn't much to complain about. It's because we have the Nearline storage, so that doesn't perform well. That is the reason we have SSD and Fibre Channel tiering. We use Adaptive Optimization and that helps us to improve certain applications using those high-performance tiers.
It's our primary storage for our VMware environment. Performance has been excellent. We don't have multiple business needs. It's just focused on our virtual storage.
We using it for our core compute (storage). We have had it for about two years and had zero problems with it.
3PAR is our main storage solution that we use for anything and everything, mainly Oracle right now. But we also have different db8s as well flute.com on our 3PAR. We have a number of different things on it. It's outstanding, it works like a champ. We have been using it for about 15 years. We have a T400 sitting in the data center right that I'm trying to get up off of. We've been using 3PAR for quite a while.
We run a High Performance Computing grid for Nuance and run GPFS on top of 3PAR. We are using SAS-based 3PAR for data and the 8450s, all SSD, for the metadata. It has been performing great. We have had SSD based 3PARs since 2013 and we have only lost about four drives so far.
We use it as our main data storage for everything from SQL Server, storage, databases, to all our virtual machines - servers and desktops - to file storage for everything: for the city's mapping. We use it for just about everything we do. The performance is amazing. It's been probably one of the best products we've bought in years.
It serves as our centralized storage for three tiers of storage, and we have half a petabyte. It performs very, very well.
Our primary use case is data retention. We also use it for test environments and deploy systems for customers as well. The performance from it has been excellent, from what we have seen so far.
Our primary use case for 3PAR is our EMR application. We're in healthcare. We also use it for virtualization. The performance is excellent.
We use 3PAR as a shared platform for services, applications, and databases.
Which is better and why?
Let the community know what you think. Share your opinions now!