What is your primary use case for Nimble Storage?

We have type of a private cloud-hosted solution in our data center. Nimble allows incredibly, fast data access for our SAN to our hypervisors and cluster. Nimble is just so good at what they do as far as the adaptive and hybrid flash stuff. We have two arrays: We have an adaptive and hybrid. We have a lot of healthcare clients. We have some who are in surgery at five in the morning. We are running these pretty heavy, intensive databases and SQL servers on the Nimble (or which are pulling off the Nimble). Having that type of server pinned to a specific volume, then having that volume accessible and prioritized over the other data which is on there, that is super helpful. This is why we like Nimble and what they do.

Our primary use case if for our central data storage. This contains our files, financial services, and customer data.

We use it to extend the data center a little further. We have videos which are very large in size and which cannot be compressed. We ran out of space in the data center so we moved the media data center and expanded it. The videos are a business-critical application. We provide videos for students to access 24/7.

We have a primary data center, and then a secondary data center for our applications and our colo (colocation data center). Our financial and document management systems are on this platform.

Secondary storage and supplemental primary storage are our use cases. We use Nimble for business-critical applications such as accounting, our in-house EPS platforms.

The primary use case is to monitor my storage. We are in radiology. Although most of our radiologists just read x-rays, there are moments when it is STAT read, where they have to read things ASAP. This applies to the emergency room and emergency departments. Sometimes, things need to be read, and it is a matter of life or death. This can also apply to cancers, detections, etc. Therefore, we need to make sure the storage stays up, and it is working. Then, our radiologists can do their job.

Our primary use of this solution is to host business-critical applications in the cloud for customers.

It is our primary source platform. It underlines all of our Tier 1, Tier 2, and Tier 3 applications. We use hybrid, not flash.

Our primary use for this solution is SAN storage for virtual server workloads. We do not use cloud volumes.

The primary use case is production storage. We run ERP applications, as an example, of our business-critical applications.

We use it in small business setups with 10, 15, or 20 VMs per customer. Our entire system runs on Nimble Storage, e.g., Windows Active Directory, Windows Servers, and WEP.

In our company, it is the back-end storage for virtual machines and file storage. On our website, there are many different business-critical things running.

We use it for all of our storage, backups, and our user storage. Everything goes onto it. We have gone from multiple devices down to a single Nimble. It hosts all of our databases for all of our servers. It hosts the servers themselves and our GFS retention jobs. It hosts everything that is critical for our business. We went from hosting a lot of our external storage on ten different NASs. Now, we have all of our storage on a Nimble. Previously, we had three or four chassis just full of stuff. We consolidated our server space down to 25 percent of what it used to be, just from storage. It is because of the way Nimble handles that storage. It can compress it down, making it smaller for us.

The primary use case is storage virtualization. We use it for public facing customer workloads.

We use Nimble for both our primary storage and for VDI.

We use Nimble for our virtualized workloads. We have been using it close to three years. Therefore, it was even before the HPE acquisition of Nimble that we started using it. It has been performing well so far. Initially, we purchased Nimble for low-end or less critical workloads, and it has started to evolve. Now, it is right up there with our Tier-Two storage for CO3 and CO4 level workloads.

For my new company, we bought tens of them, almost 50. Our use case is to swap out the existing FCoE infrastructure from one of the other array providers and switch to Nimble because we were having performance issues. And the use case is more for our KSN databases. We chose Nimble because we need high performance, low latency, and a good price for SSD. We PoC'ed, and they won.

It's an adjunct storage repository and it compliments our 3PAR solution. We currently use it as a file store for backup, file, and compute storage workloads.

We use Nimble to virtualize all of our applications. For the hypervisor we use VMware. We use Nimble for the storage platform for the hypervisor. It's been performing amazingly.

Our Nimble unit serves our corporate storage infrastructure, all running VMware on top of it. It's primarily VDI file storage and the virtual environment itself. We have been using it for about three years and the performance has been excellent. We haven't had any outages.

Nimble is a secondary VMware environment in our organization, so it's not running mission-critical applications at this point or responsible for complex business needs.

It is storage for our VMware vSphere servers. It is also a destination for some Commvault backups and replications. We use it for a number of things. It has been three years, and the performance has been great. We have bought eight more since buying the first one.

The AF5000 array is the primary storage for our iManage DMS 10 document management systems. It allows the best performance for users using the system.

Nimble storage is our primary Production storage vendor. We use this with VMware on a daily basis including a new AFA5000 all flash array for our DMS system.