What to Ask About Licensing Before You Buy a Used NetApp Controller

2026-09-18T15:47:26-05:00

The hardware is the easy part. A FAS or AFF chassis either arrives tested or it doesn't, and that's a question any decent seller can answer. Licensing is where secondary-market storage purchases actually go wrong, and it usually goes wrong quietly — after the PO, when the system is on the floor and someone runs license show.

Licenses Are Attached to a Serial Number, Not to a Chassis

ONTAP feature licenses are node-locked. From Data ONTAP 8.2 onward, license keys are node-specific and will only install on the controller they were purchased for, and ONTAP checks installed keys against the controller serial numbers in the cluster once it boots. That's also why a controller or motherboard replacement requires new keys — the system serial number changes.

The practical consequence: "the system came with ONTAP installed" tells you nothing. Features can appear enabled while the entitlement behind them belongs to someone else. NetApp draws this distinction directly — a key being installed isn't proof the controller is entitled to the feature, and operating that way is a compliance problem to be corrected.

What Changed with Newer ONTAP

If you're buying anything running recent ONTAP, the format is different. Starting with ONTAP 9.10.1, licenses are delivered as a NetApp License File — one file enabling multiple features — and since May 2023 AFF and FAS systems ship with either the ONTAP One or ONTAP Base suite. The file format supports bundle licensing, so a bundle arrives as a single NLF rather than a stack of individual keys.

This matters when you're comparing listings. A system described as having "all the licenses" may be carrying legacy 28-character keys, an older bundle NLF, or ONTAP Base with far less enabled than the buyer assumed. Those are three different purchases.

Five Questions Worth Asking Any Seller

Which specific licenses come with the system? Not "fully licensed" — the actual package names.
What form are they in? Legacy keys or an NLF, and for which ONTAP version.
Are they tied to the serial numbers of the controllers I'm receiving? If the seller swapped a controller, the keys may not match what ships.
What happens to entitlement on transfer? Ask how ownership is recorded and what that means for your ability to buy support.
If I need a feature that isn't included, what does adding it cost? Better to price that before the PO than after.

Ownership Registration and Support

The reason ownership matters is support eligibility. A system whose ownership has been properly transferred can be brought under a NetApp support agreement; one that hasn't generally can't, which leaves third-party maintenance as the support path. Both are legitimate options and plenty of environments run happily on third-party support — but it's a decision, not a detail, and it should be made before purchase rather than discovered afterward.

Worth knowing that NetApp's own position is restrictive here: the company treats its software entitlements as belonging to the original purchaser. Any seller telling you licensing is a non-issue on used gear is skipping a real step.

How We List Them

We state what's included on each system: which bundle, which features, and whether the unit is offered with transferable ownership. If a system is hardware-only, we say so, because that's a legitimate purchase too — for a lab, a cold spare, or a chassis you'll license yourself.

We currently have licensed AFF and FAS controllers in stock, including AFF-A800, AFF-A250, AFF-A700A, FAS8300, FAS8200 and FAS2720, with shelves and drives to build any of them out. Send us the model you're after, or the workload you're sizing for, and we'll tell you exactly what comes with it.

The Truth About Drive Health and Real Lifespan: What Matters Most?

2024-11-22T08:36:37-06:00

The Truth About Drive Health and Real Lifespan: What Matters Most?

When it comes to predicting how long your SSD will last, there are two common metrics people rely on: Drive Health (often reported via SMART attributes) and Manufacturer Endurance Ratings (e.g., Total Bytes Written or TBW). While these can be helpful guidelines, they don’t always tell the whole story. The real-world lifespan of an SSD often far exceeds these indicators, making actual usage and workload trends the more reliable way to estimate remaining life.

Let’s dive into why real-life usage should be your primary focus and explore this with a real-world example.

What is Drive Health?

Drive Health, typically reported as a percentage, reflects how much of a drive's rated endurance has been used. For SSDs, this is based on metrics like:

Percentage Lifetime Used (SMART attribute).
Wear Leveling Count (how evenly data writes have been distributed across memory cells).
Remaining Spare Cells (unused cells that replace worn-out ones).

For instance, my Samsung 980 PRO 1TB SSD reports:

Percentage Lifetime Used: 10%
Total Data Written: 25.6TB (of a rated 600TBW)

This suggests I’ve used 10% of its rated life, which seems straightforward—but the reality is much more nuanced.

What Do Manufacturer Endurance Ratings Mean?

Manufacturers assign endurance ratings like TBW (Total Bytes Written) as a benchmark for how much data a drive can write before it might fail. For my Samsung 980 PRO:

Rated TBW: 600TB
Data Written So Far: ~25.6TB
Drive Health Reported: 90% remaining.

At this rate, I could easily expect to use this drive for over 15 more years, assuming my usage stays consistent. However, these ratings are conservative by design. Tests in real-world scenarios often show drives surviving 2-3 times their rated endurance.

How Extreme Would My Usage Need to Be to Exhaust the SSD by Year 5?

Let’s take this a step further. What if I wanted to exhaust my SSD within the manufacturer’s 5-year warranty period?

Current Status:

Power-on time so far: 1.73 years.
Remaining time to 5 years: 3.27 years.
Remaining endurance: 574.4TB of writes available (600TB total - 25.6TB written).

Required Daily Writes: To determine the daily writes needed to exhaust 574.4TB in the next 3.27 years:

Remaining time in days:
3.27 years × 365 days/year = 1,194 days.
Daily writes calculation:
Remaining TBW ÷ Remaining Days = 574.4TB ÷ 1,194 days ˜ 481GB/day.

This means I would need to write nearly 500GB/day—12x my current workload of ~40GB/day—to exhaust the drive within 5 years.

How This Correlates to Enterprise SSDs

For enterprise SSDs, the logic remains similar, though the workloads and endurance metrics differ significantly:

Higher TBW Ratings:
Enterprise SSDs are often rated for multiple petabytes written (PBW) due to their use in write-heavy applications like databases, virtualization, and AI training.

Example: A 1TB enterprise SSD rated for 10 Drive Writes Per Day (DWPD) would have a TBW of:

TBW = DWPD × Capacity × Warranty Period (in days)

TBW = 10 × 1TB × (365 days/year × 5 years)

TBW = 10 × 1TB × 1825 days

TBW = 18,250TB (or 18.25PB)

If this drive experiences 500GB/day of writes (similar to the previous calculation):

Time to Exhaust TBW = Total TBW ÷ Daily Writes

Time to Exhaust TBW = 18,250TB ÷ 0.5TB/day

Time to Exhaust TBW = 36,500 days (or ~100 years).

This shows that even under workloads of 500GB/day, an enterprise SSD could last an estimated 100 years—far beyond its rated warranty period of 5 years.

Enterprise Workloads:
Data centers regularly write several terabytes per day, depending on the workload. While enterprise SSDs are built for these intensive tasks, this example illustrates how robust their endurance ratings are when compared to actual usage.
Monitoring Real Lifespan:
Both personal and enterprise SSDs benefit from monitoring actual workloads rather than relying solely on health percentages. Enterprise environments often use tools to track total writes and SMART attributes like reallocated sectors and error rates to plan replacements.

Using Real Lifespan to Predict Drive Life

Instead of relying solely on Drive Health or Manufacturer Estimates, consider these real-life factors:

Write Patterns:

Track how much data you actually write to the SSD daily or monthly. For instance:

My consumer SSD has written 25.6TB in ~1.7 years, averaging ~40GB/day.
Using the same formula for enterprise SSDs:

An enterprise SSD rated for 18,250TB would last:

Time to Exhaust TBW = Total TBW ÷ Daily Writes

Time to Exhaust TBW = 18,250TB ÷ 2TB/day = ~9,125 days (~25 years).

This highlights that even heavy workloads allow for significant longevity.

Conclusion: Why Real Lifespan is More Important Than Drive Health

This example demonstrates why real-world usage should be the focus over static health percentages or conservative manufacturer estimates. My Samsung 980 PRO, with 90% health and a modest workload, is projected to last decades under current conditions. Even to exhaust it within its 5-year warranty period, I would need to push extreme workloads of 481GB/day—far beyond typical workloads for my use.

For enterprise SSDs, the same principle applies. Their rated endurance may be higher, but real-world workloads show similar trends: most drives outlast their warranties significantly. By focusing on actual usage patterns—such as total data written and workload types—you gain a clearer, more accurate picture of how much life your drive really has left. This approach not only prevents premature replacements but also maximizes the value of your storage investment.