What is your primary use case for Pure Storage FlashArray?

Pure Storage FlashArray is used for storage purposes.

I work for a Pure partner, so we are actually doing deployment of the arrays at the customer sites. That's one part. The second part is that we help customers to maintain the infrastructure. Not all of them, but many of them.

The main use case for this solution is block storage. I deal with the transportation logistics industry.

We used Pure Storage FlashArray for the first two or almost three years strictly for VMware block storage. We bought another FlashArray, a C-series, for our file share, and we migrated everything from Isilon to C-series. We have two FlashArrays, X-series and C-series. C-series is mainly for file share and we use shares basically, while X-series is strictly for block storage for our VMware.

I use Pure Storage FlashArray ( /products/pure-storage-flasharray-reviews ) for backend storage in our VMware environment.

I managed Pure Storage in my previous organization for various clients. We had clients from multiple domains, such as the financial domain, the automotive sector, and the banking industry. These customers had three different types of applications using Pure Storage. One of them was the Oracle Database with high throughput and low latency requirements. The second one had time-sensitive functions, where a two-millisecond delay was acceptable but a five-millisecond delay was not. It required indexing and low latency. The third type of use was hosting a virtual infrastructure, such as VMware VMs. These are the three areas where people used Pure Storage, specifically FlashArray storage, in their environment.

Initially, there were a few use cases we started with when looking at alternative storage platforms. Once upon a time, we were ran a different platform that was physically huge, power hungry, low on capacity and mediocre on performance. Use was complex and did not scale very well. It was also very cost prohibitive to maintain. We quickly outgrew it, especially when we started to adopt VMware vSphere virtualization. We knew we had to replace this beast with something that made more sense for us. We needed to reduce the footprint down to something a lot more reasonable. We wanted to contain costs, especially when it comes to hardware investments and maintenance renewals. We also needed more intelligence, visibility and flexibility in our data storage platform. We were introduced to Pure Storage through one of our long-term partners in the Chicagoland area who brought them in for a meet and greet. Their presentation was compelling. It was exciting to see what they were doing with technology, especially with the concept of data deduplication, so we decided to give it a go. The results were simply unbelievable. We deployed Pure into multiple datacenters effectively consolidating down entire row's of storage to a single rack. It ran circles around our legacy platform and what it did for VMWare was really something to see. Boot times were drastically reduce, latency went from 30-40ms down to sub millisecond...consistently. As we continued to use Pure and their products evolved to add in additional features/technologies, we were able to solve other issues we never knew we had. Our BC/DR playbooks were effectively rewritten to take advantage of array to array replication for disaster recovery. Snapshots cut our product upgrade times in half because we no longer needed to rely on taking full backups of our environment before deploying new code. Snaps were immediate and rolling back was almost just as fast. It was a true game changer. Pure had single handedly improved our business strategies and making us more agile in provisioning storage and overall, running our datacenters. Over the years, we have witnessed Pure continuing to deliver new feature sets and technical enhancements in it's Purity code base. Did I mention that all of these features and enhancements are part of cost of support? Yep...no nickle and diming people to death.

Virtualization with ESXi, Hyper-V, XenServer, KVM is the primary use case. VDI, containerization, AI, HPC are some other use cases seen in my day-to-day consulting with customers.

I use Pure Storage FlashArray to provide LUNs or volumes for end users who want to work on a database for zoning, enabling them to operate effectively with end-user arrays.

We use Pure Storage FlashArray for storage provisioning.

We use Pure Storage FlashArray as well as FlashBlade. In Pure Storage FlashArray, we have the SAN and NAS storage models. We focus on performance when it comes to enterprises. We need both types of storage, one is for better performance and the other one is for larger space requirements. We use both types of storage at the same time.

In terms of Pure Storage FlashArray, I am using the iSCSI protocol. We are building virtual machines on it. It is like a data store on the ESXi hypervisor. VMware virtual machines are built on it.

We use Pure Storage FlashArray as the primary storage of our organization.

We use Pure Storage FlashArray for storage allocation, DR, replication, and performance. We are migrating both servers and storage to Pure Storage.

Our VMware infrastructure uses a Pure Storage FlashArray as its primary SAN storage solution.

We have a contract with Pure Storage, and we use it for VMware and database server storage provisioning. We have multiple applications in the environment, and we are provisioning from Pure Storage.

I use FlashArray to manage storage and DR sites for my clients.

I'm a Pure Storage partner and I have implemented two use cases for my customers. In one case, my FlashArray works like storage, but my CPU is in my other servers. In my other case, it works only as a backup.

We have our own hosted environment that utilizes Pure. We also use it for customers. We use the solution both internally and externally. We use the tool for data storage and backups.

Our customers primarily use Pure Storage for virtualization, whether it is VMware or Hyper-V. They choose Pure Storage for its high-performance, low-latency, and reliable all-flash arrays, which are essential for efficiently running virtualized workloads, including critical applications, databases, and virtual machines.

We use it just for test purposes in our organization.

It's a very simple tool to use with extremely low latency and high performance.

We primarily use the solution for storing data for applications.

The tool provides storage to new servers and maintains provision storage volumes like creating new servers for Windows and Linux, which are the system administrations of the storage system.

This solution has been part of a POC. We've been evaluating the solution.

Our primary use case for this solution is focused on enterprise solutions, a support solution that needs either performance, reliability or cost. For example, most companies have databases, virtualized workloads, or VDI workloads. So with those kinds of environments like the Block Storage, it is perfect because it switches very well with the cost, performance, and reliability ratio. Additionally, it's easy to deploy to benefit the IT team in the management costs.

Pure Storage FlashArray is used for hosting applications, such as Vmware, HyperV, and virtualized applications.

I work for a company that offers outsourcing services for IT solutions. I work in system support and we are resellers of Pure Storage FlashArray.

We primarily use the solution for storage.

Pure Storage Flash Array is used for data storage.

I help our customers build FlashArray.

We use Pure Storage FlashArray because of the increased demand for high IOPs for some of our internal applications that were required to read and write in faster sway.

We are using Pure Storage FlashArray for all of our data. We use the deduplication feature and it is working well.

We are a solution provider and the Pure Storage FlashArray is one of the products that we implement for our customers. I have installed three of them in the past month. The primary use case for this product is high-performance storage.

We are in the health industry and use this product for block storage. We have VMware hosted on our Pure FlashArrays and we have a Citrix environment. We also have Oracle running as our SQL database. Our VMs run from Pure. We have also done a couple of PoCs with the Blade solution for using the file share system.

FlashArray is our main repository for all our VMware.

My primary use case is selling... :-)

Right now, I am responsible for an installed base of +200 systems here in the region which are used for a variety of workloads. 

From that point of view, I can actually say what a FlashArray is NOT designed for...
1.)  A very big part of the data is Unstructured Data, especially compressed and/or encrypted.
2.)  See number 1.
3.)  Large sequential write workload of compressed data - that´s just not good for flash components

Everything else is possible to place on the FA. The performance is always predictable because of the architecture so you can actually calculate the behavior for any type of workload pretty easily. No need to take in any type of caching, block sizes and read/write ratios. If you need some detailed information considering certain workloads, in particular, feel free to ask.

Regards
Terence

We use it for server virtualization and VDI. 

My primary use case of this solution is array management.

We use Pure Storage FlashArray for machine learning, storage, backups, and computing.

We are using the latest version.

We primarily use the solution for storage.

We use Pure Storage FlashArray in a couple of backup products. Our DDP offerings, data platform offerings, is where we use Veritas with Pure Storage FlashArray. Then, we use the Pure Azure Service model with the secure multi-tenancy features. Pure Storage FlashArray can be managed centrally. In individual file cases where most customers were looking for performance-based, minimum latency applications, we have deployed Pure Storage FlashArray.

We use this solution to assist with our on-premise database workloads; In conjunction with our Oracle database and SQL server database. Within our organization, there are roughly four people using this solution.

We use this solution for block storage.

We put the solution onto the VMware environment and all the Microsoft SQL servers. We do the synchronization between two data centers, so that is has a very low latency. We just have a few milliseconds of latency which is a ready performance, and near perfect.

We use flash storage for VDI architecture and database architecture.

We are basically using it for the department of space and online education purposes. We are using its latest version.

Our primary use case is to keep the disc for all the critical systems in the company.

We are a system integrator and this is one of the solutions that we provide for our clients. For our most recent customer, this solution is being used to host VMware workloads in an on-premises deployment.

We are a system integrator and this is one of the solutions that we provide for our clients. For our most recent customer, this solution is being used to host VMware workloads in an on-premises deployment.

Our primary use case of this solution is for Citrix. We use the on-premise deployment model.

We use the solution for the vendor support. It's a banking software system. It's an IBM system and it requires some Pure Storage for the backend and SSDs for performance. The vendor supports Pure Storage.

We primarily use this solution for our SQL server in an on-premises deployment. Having a dedicated array for our SQL server is very nice. We are running VMware on Pure, and the main driver for that is because it is all-flash. Also, we wanted a dedicated solution for our SQL environment. Running on Pure has given us the ability to scale out our SQL environments. We tripled our environment in the past three years since implementing this solution, and we have not had any issues with the storage keeping up with the workloads. We are making use of some of the VMware integrations that have been developed by Pure, but we are really waiting for the copy data management part.

We use this solution for general, primary storage in an on-premises deployment.

We use the FlashArray X20, M20, M10. We have regulations against cloud, so we're mostly on-Prem. However, we do use Office 365 for email and we have Azure for development on another team but I don't manage that team. Our primary use case of this solution is to house data stores on virtual machines.

We use the hybrid cloud deployment model of this solution and use both AWS and Microsoft Azure as our cloud providers. Our primary use case for this solution is for mixed workloads. We are running VMware on Pure. Pure gave us the storage because we're a partner so we're running on it.

Our primary use case of this solution is to manage our virtual environment and storage so our entire VMware environment runs on Pure.

We use the solution on-premises and each array has a different use case. We have VDI, SQL, and General and the program provide better integration between the management and visibility of the solution. Our organization takes advantage of the VMware integration developed by Parrot and this gives us a lower level administrative access to more admins that don't have a background in storage.

We use the private deployment model of this solution. In terms of our cloud provider, we use Azure, we are signing on with AWS, and we'll be using vCloud in the next quarter.

We use the on-premises deployment model of this solution. Our primary use case is for virtualization.

We use the private deployment model of this solution and VMware for our storage provider. Our primary use case of this solution revolves around our clients. We have different tiers of storage. We use the Pure Storage FlashArray for our tier-one storage, our higher-level storage to support not only multi-tenant clients but also our private cloud clients, and to provide them with an all-flash storage solution.

We use the on-premise deployment model of this solution for the bank. We use AWS as our cloud provider.

We use the private on-premise deployment model. Our primary use case of this solution is for virtual machines. We just use it as storage for our vCenter environment.

We primarily use the solution for internal storage for all virtual environments. We also use it for the SQL database, Oracle and private cloud. The storage is used to manage the internal private environment.

Our primary use case for Pure Storage is for disaster recovery. We use AWS for our cloud provider.

We primarily use the solution for desktop virtualization. I have IOPS and IOPS input/output. The reason that we have virtualization required for the media is because of high IOPS and we're able to maintain it with PR. The encryption is pretty high. We like the encryption right on the storage.

We use the solution for VM storage in a private cloud model. The main motivations we had to run VMware on Pure were the simplicity and cost. We're using the M70 R2.

Our primary use case for this solution is for tier 1 critical applications on-premises. Our organization takes advantage of the VMware integration developed by Pure by integrating with vRealize.

Our primary use for this solution is storage. We have a private cloud deployment.

We use virtual servers on there.

In our company, we implemented a Pure Storage FlashArray for our VM virtualized environment. We do have vCenter integrated with Pure Storage. We use that application to deploy virtual volumes on our Pure Storage solution. We are still in the beginning stages, so we only have four virtual systems running on it. However, in the coming months, we will be migrating the bulk of all of our VMs over to vCenter and Pure Storage.

It is for storage.

We have all-flash for our SQL environment.

We use it for our financial core storage. It has been a good product. It has a lot of good features on it.

Anytime that you need fast storage.

We attach it to a Cisco UCS for VMware.

We use it as our primary application driver for all of storage reasons in our data center for both our corporate and production environments. We just did all-flash, and all-flash is better than anything disk related.

It is storage for our database system.

As a customer, we use them as our Tier 1 storage arrays. It has been amazing. It's extremely fast, reliable, and resilient.

We use it as reliable storage.

It is our core storage.

It's the back-end storage for all our virtual environments.

The primary use case is for any server and database that has high I/O demands on disk.

The primary use case is to run SAP applications on top of the flash solutions. SAP is very important to our business. It's a key function. We are running ERP and CRM systems. Our systems run on-premise.

The primary use case is SAP. It work very well. SAP is very important to our business. We are running all ERP solutions. Our configurations are run on-premise.

Our primary use case is SAP.

The primary use case is big data. SAP is very important for our business. We are running our management system on SAP, so it's very critical. We are running SAP S/4HANA and other ERP modules. We run our config on-premise.

We have a lot of MEDITECH electronic health records systems running on it, as well as some other ancillary applications, but it's core hospital EHR, predominantly.

We use it for performance, the capacity of deduplication, and compression of the data.

There are two real use cases. * General purpose infrastructure for VMs. * Business technical applications, such as Oracle DB or MS SQL DB.

We have workloads that demand high IOPS, so a lot of speed, fast access, time, and overall high performance.

The primary use case is storage for payment platforms.

We use the space and optimize the makeup of the storage products.

The primary use case is for the data and storage that we utilize in our managed services. We also use it in the company. We localized it.

It's a high performance storage array. We want some deals regarding replication and stretch cluster.

The primary use case is block storage for retro machines running on VMware ESXi and Red Hat with Kernel-based Virtual Machines (KVMs).

We are a reseller of Pure Storage FlashArray. Our customers use it for virtualization, artificial intelligence, and machine learning.

We use it for VMware virtualization.

We are using Pure Storage as an all-flash product. It is a niche product, and only used for high performance data. With Dell EMC, they have all-flash arrays, but they also have other types of storage. Our client use the solution for DevOps and their high speed databases.

All of our production and development workloads run on Pure Storage.

The primary use of Pure Storage was for a data virtualization project using Belfrics. We needed the latency that would be required for the product. We are moving into a DevOps environment and CI/CD. Their departmentalization was an enabler because database is a service in the pipeline where the underlying risk factor has to be correct, especially the storage. This primarily applies to the driver and the infrastructure as a base, but the end game is to have a DevOps pipeline.

We use it for storage of critical data, and for storage of replicated backups.

We use Pure Storage on our databases. We have massive SQL databases, four-node clusters and we present a LUN directly to them. Then we have Fusion-io cards as a backup. We also use Pure in our data centers to replicate our databases for our DR center so that we can be secure.

Our primary use of Pure Storage was for a data virtualization project using Belfrics. We needed the latency that would be required for the project. The analytics that we gather is used for just one environment (which is big in the banking industry). Production wise, it's running Oracle. Performance wise, it's basically running enterprise applications.

Our primary use case of this solution is for the production storage, development, and DR storage.

Our primary use case of this solution is for Microsoft SQL.

Our primary use case of this solution is for the fast storage and database.

We use this solution for everything. We have a mixed storage use.

Our primary use case of this solution is for Rack Database Storage and Virtualized Server Storage.

Our primary use case of this solution is for storage. We use it to ensure better application performance and to improve the user experience of the application. The cross-storage appliance improves the overall application experience. We have been using this solution as an on-premise solution. It has been useful for our critical applications.

Our primary use case is a big bucket of storage for VMware. We run our virtual machines mostly to make sure that we have our SQL databases sitting on Pure Storage, because it's the fastest storage which we have available.

We're a service provider, so it's the primary storage for hosting our customers.

We use this solution for storage of critical data and for storage of replicated backups. We use Zerto replication software. We write all of those backups to Pure Storage and then we use those in our disaster recovery scenarios.

The primary use case is for on-premise storage. I have personally used this solution for 15 years, and now, four years with my current company.

All of our production, development, and workloads run on it.

The primary use case is virtual machines.

We run our production Oracle workload on it.

VMware is currently our main use case because it dedupes really well.

Our primary use case of this solution is to keep our production and DR data in this storage.

We've been using this solution for four years. We are on-prem with Pure and we are not using any of Pure's off-prem product. We do have experience with a variety of storage in AWS. For us, it's still two very different things, we like Pure Storage because our key business systems are still on-prem. It's been extremely reliable and gets the job done. Our primary use case is for Oracle databases, data warehouses, and mission critical apps.

It is the SAN backbone for our company. We have multiple SANs, all Pure at this point. It runs everything from tasks to business intelligence to enterprise applications.

We have bare-metal boxes now so we are thinking of going Cloud. We have to have a hybrid solution because we're closer to the financial industry and we have regulations that require us to have on-premise systems. In that case, we would go with Pure Storage.

We use this solution for our database, log store, and for the file system.

We use it for nearline storage.

Pure has become the main storage solution for our customers. It is mainly used for our customers' Oracle databases.

Since we're a database shop, we primarily do databases on Pure. Everything else follows from that.

We use it for VDI.

We're providing some ESXi solutions to our customers with high performance.

Our customers are using Pure Storage to replacing old storage infrastructure.

Our primary use case has been our production Oracle campus management database environment. We use Oracle PeopleSoft as our campus management solution and underneath that we have about six terabytes of Oracle Database. Our most demanding use-case for Pure Storage has been hosting these high performance, transactional databases, while also hosting all of our other critical application storage needs (MSSql data-warehouse, BI/Analytics, VMWare).

We use Pure Storage for most of our databases, as well as for other application binaries.

We sell a SaaS offering of the storage to our customers. We use the storage as our main storage and also as our backup storage.

We do a lot of Oracle implementations and getting Oracle workloads to run faster and better. For a lot of our customers, they are looking at Pure Storage for its underlying storage. It makes everything a lot easier for them in terms of increasing performance, lowering operational costs, and making their day-to-day lives easier.

Most of our customers who use Pure Storage have one of two scenarios: * They have production data with high performance requirements running out of Pure Storage, and they want an efficient way to make a copy of that data onto some other storage for backup and DR purposes. For this scenario, we have integration with Pure Storage that allows us to very efficiently leverage their APIs to capture that data without the need to do things like repeated full copies of that data, leverages their snapshot APIs and differential APIs which tell us what's different from one snap to another to another. * The customer has their data, maybe it is on Pure Storage or it's on some other array, then they want to use Actifio to get a copy onto a Pure Storage array. For example, an Oracle user might need to make a copy of a large Oracle Database. They would want us to spin that database up in one or more lower, testing, or QA environments. These environments sometimes have high performance requirements, which could be met by placing a copy on Pure Storage on them. Another example is a customer who has Oracle Exadata. Obviously, Oracle engineered systems have very high performance, and they don't want to have all of their test and dev copies in that Exadata platform, because of the cost of the platform. Therefore, Pure Storage, combined with Actifio, captures the data efficiently from the Exadata environment, then stores it on the Pure Storage disk. We then present that data to their test servers, which can be the Exadata Compute Servers or it can be any non-Exadata Linux-based Oracle servers. Then, they can have great performance because of the high speed delivery of data from Pure Storage using Actifio.

We use it for virtualization.

We use Pure Storage FlashArray as the storage for our virtual servers and our reporting databases.

The Pure Storage array houses our entire production environment. Production consists of VMware 5.5 on three HPE DL360 G7 hosts.