Why Nimble Storage?

Akins IT • October 9, 2018
Connect with us

A common question I get as a solution architect is “Why?” Why that firewall? Why that server? Why do it that way?" In this write up I’d like to dive a little bit into why I enjoy working with Nimble Storage and some of the benefits we see our clients taking advantage of.


Simple


Just about anything you could want to do with your storage appliance is easy with Nimble. With some storage appliances, performing basic setup or making configuration changes is very complicated and not user friendly. Hence, why some companies must bring in a storage expert. I am not trying to talk myself out of work here, but with some basic understanding of storage, most IT admins can setup and manage a Nimble infrastructure with ease.


If you need more performance for a workload, simply apply a pre-built or custom performance policy to the volume where the workload resides. If you want the best performance for some workloads but don’t have the budget for all flash, pin the specific workload to cache. It is all very simple and seamless. If business goals demand disaster recovery readiness, purchase a second array for the DR site, enable replication. Done.


I have seen the situation many times where a company’s storage has run out or is about to run out with relatively short notice. To remedy, they must spend $50,000 or more on storage but it’s not in the budget this year. Unfortunately, this is not uncommon. Nimble has a neat feature where the array will give you predictive analytics based on past data growth as to when your array will run out of space and make recommendation to add another array or shelf.

Flexibility


Say you came across the situation where the business decided to expand, larger projects are started, or you’ve simply had the same infrastructure for 3-5 years. Its time to increase your storage capacity. In some situations, this is a massive undertaking and a lot of planning, preparation, and ground work needs to be done. With Nimble, the purchase of an expansion shelf fixes your problem as fast as you can plug it in. I have done this for customers many times and they are always surprised at how easy it is. All you must do is point the array to recognize the shelf and expand the storage pool. Incredibly quick to do. Of course, make sure you have the rack space, I’ve seen that one go bad.


In other situations, you might have enough storage, but you need more performance, which is not a problem. You can perform a controller upgrade at any time and even during production. If required, you can even add an all flash shelf to a hybrid array and use the shelf for the caching of your performance intensive workloads. 

Support


Last but certainly not least is Nimble support… Wow! As a solution architect, I deal with a lot of different companies and their support staff. I can honestly say Nimble support is some of the best out there. When you call in, there is no “Let me make a case for you and someone will call you back next month.” There is no, “Sir, can you please unplug it and plug it back in?” You speak to an experienced engineer immediately who knows what they are talking about. Not only experienced with Nimble, but the surrounding infrastructure as well- i.e. VMware, Hyper-V, Server OS, Switching, etc. Often when I am explaining Nimble support to customers I have them call their support line and quiz the engineer. Never have I had a client bothered by the support experience. I dare you, too! Give them a call and quiz them.

In summary, Nimble Storage is a great fit for a variety of scenarios. Hopefully this write-up answers the “Why?” question for a lot of you!

View a Sample of our Cybersecurity Report
By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts