Contents
Key takeawaysHow Protect is licensedPVU and ILMTCheck your positionPer terabyte against PVUThe Storage SuiteWhat we have seenAccount team linesContract termsWhat to do nextFAQIBM Spectrum Protect and its sister products are licensed by PVU, RVU, per terabyte capacity or the pooled Storage Suite rate. The metric you sign decides what an audit can count, and for large backup environments per terabyte usually costs less.
- Four metrics, one family. Spectrum products are licensed in PVU, RVU, per terabyte capacity or the pooled Storage Suite rate, and the metric on each entitlement decides what IBM counts.
- PVU depends on ILMT. Spectrum Protect on PVU without ILMT reporting carried full capacity exposure of 2 to 4 times the deployed footprint in our engagements.
- Capacity metrics win at scale. Buyers who converted PVU entitlements to per terabyte metrics at renewal cut storage software spend 20 to 35 percent and dropped the ILMT condition.
- Front end and back end differ. Protect Suite counts managed data in primary storage pools, Suite Front End counts the primary data you protect, and retention policy often decides which costs less.
- Size the Suite on measured data. About half of the Storage Suite bundles we reviewed were oversized, with 30 to 40 percent of licensed capacity never deployed.
- The rename changed names only. IBM Storage names replaced Spectrum, but the Passport Advantage part numbers and metrics carried over unchanged.
- Negotiate price last. Fix the metric and the pool size first, then ask for the discount with a credible competing product in the evaluation.
How is IBM Spectrum Protect licensed today?
IBM Spectrum Protect, now sold as IBM Storage Protect, is licensed in processor value units (PVU) on the servers that run it, or per terabyte of capacity through the Protect Suite offerings. Across the wider Spectrum family, IBM uses four metrics, and the one on your entitlement decides what an audit can count later.
The four are processor value units, resource value units (RVU), per terabyte capacity priced product by product, and the Storage Suite, which charges one pooled per terabyte rate across the family. The products overlap, but each metric sets what gets counted, what evidence the count needs and where exposure builds up.
| Metric | What it counts | Evidence the count relies on | Where exposure builds |
|---|---|---|---|
| Processor value units | Every activated core on the servers running the software, weighted by IBM's core factor | ILMT reports, if you claim sub capacity | When ILMT reporting lapses, sub capacity collapses to full capacity |
| Resource value units | Managed resources, priced on a tiered schedule | Your own count of managed resources against the tier table | Tier boundaries drift as the managed environment grows |
| Per terabyte capacity | The terabytes each product manages | Operations Center capacity estimates or IBM's measurement scripts | Follows real data growth, which makes it the usual migration target from PVU |
| Storage Suite per terabyte | One pooled capacity figure across the whole family | The same capacity measures, totaled across every product in the pool | Paying for pool capacity that is never deployed |
Which terabytes count, front end or back end?
Per terabyte licensing for Protect comes in two measures. Protect Suite counts back end capacity, which IBM defines as the terabytes of data stored in primary storage pools and repositories. Protect Suite Front End counts the size of the primary data you protect, and IBM does not require a license for replicated data.
For file systems, front end measures the active backup of the protected files. For databases and applications it measures the used size of the protected data, and transaction logs are left out. For smaller environments, IBM sells Suite Entry editions capped at a combined 100 TB.
- Front end usually suits long retention. Keeping more backup versions, or a replica at a second site, does not raise a front end count.
- Back end can suit short retention. Where few versions are kept, the managed data in primary pools can sit close to the source data.
- Retention changes shift the answer. A new rule that keeps backups for seven years instead of one raises a back end bill with no new data protected.
IBM began dropping the Spectrum prefix in 2023, and Spectrum Protect is known as IBM Storage Protect from version 8.1.19. The Passport Advantage part numbers and metrics underneath stayed as they were, so your entitlement records, audit positions and metric traps all carry forward under the new name.
A review of your storage licensing is still a review of Spectrum terms, whatever the current datasheet calls the product.
Does Spectrum Protect need ILMT on PVU licenses?
Yes. On PVU entitlements, Spectrum Protect counts every activated core on the servers that run it unless you qualify for sub capacity, and sub capacity needs ILMT deployed, scanning and reporting, as for every other IBM product sold in PVUs. Our ILMT and sub capacity guide sets out the full conditions.
IBM's terms give new sub capacity customers 90 days from their first eligible virtualized deployment to install ILMT. Reports must be generated at least once a quarter. Miss either condition and IBM can charge full capacity for every activated physical core on the host.
Why backup servers fall outside ILMT scope
PVU prices backup software by the compute it happens to run on. That worked when backup servers were few and static. Today Protect servers, proxies and data movers run as virtual machines on clustered hosts, and every host adds cores to the count.
The PVU count also reaches past the backup server itself. Every managed client node that IBM classes as a server needs PVU entitlements too.
The ILMT discipline also lands on servers the storage team rarely treats as licensed infrastructure. Storage engineers build backup hosts outside the application inventory, and the ILMT rollout plan often misses them. These are the servers most likely to be left out:
- New Protect servers. Virtual machines built after the last ILMT agent rollout.
- Data mover proxies. Machines added to back up virtual machines under Protect for Virtual Environments, another product IBM sells in PVUs.
- Cloned servers. Test and replica machines built from production images, carrying the software with them.
- Hosts moved between clusters. Cases where the ILMT connection to the virtualization manager was never updated.
A worked example of the full capacity gap
Say you run four Protect server virtual machines with 8 virtual cores each, spread over four hosts with 32 cores each. Most current two socket x86 servers carry 70 PVUs per core on IBM's PVU table.
| Position | Cores counted | PVUs at 70 per core |
|---|---|---|
| Sub capacity, ILMT reporting in place | 4 x 8 = 32 | 2,240 |
| Full capacity, no ILMT reports | 4 x 32 = 128 | 8,960 |
| Gap IBM can claim | 96 | 6,720, leaving the full capacity count at four times the licensed position |
That result sits at the top of what we found in practice. Unmonitored Spectrum Protect deployments carried full capacity exposure of 2 to 4 times their deployed footprint. The IBM audit penalty guide shows how that gap is priced once IBM puts it in a settlement.
IBM ELA Renewal Guide
The renewal sequence, contract terms and sizing method for IBM storage entitlements inside your wider agreement.
Get the white paper →How can you check your own Spectrum Protect license position?
Compare what you bought with what the Protect servers and ILMT say you run, before IBM makes the same comparison. Five sources cover most of it:
- Passport Advantage entitlements. Export the entitlement report and tag every storage part by metric, including lines bought under the Spectrum and Tivoli Storage Manager names.
- QUERY PVUESTIMATE. This Protect server command estimates PVUs for the nodes the server manages. Treat it as a planning figure, because it depends on clients reporting processor details and on each node's role being set correctly. It may also miss VMware or LPAR virtualization.
- Operations Center license estimation. It shows front end and back end capacity. IBM collects front end figures every 24 hours and back end figures every seven days, and labels both as planning estimates that are not legally binding.
- Front end measurement scripts. For clients Operations Center cannot see, IBM provides the dsmfecc scripts and a Central Reporting Tool that totals their output.
- ILMT reports. For PVU lines, confirm every Protect server, proxy and data mover host appears in the latest signed report.
When does per terabyte licensing beat PVU for Spectrum Protect?
In most environments we benchmark, per terabyte licensing costs less once you manage more than roughly 500 TB, and the gap widens as data grows. Buyers who moved PVU entitlements to per terabyte metrics at renewal cut storage software spend by 20 to 35 percent, and took those entitlements out of the ILMT condition at the same time.
A per terabyte metric counts what the storage software manages and grows with the data. PVU grows with the compute you add for restore speed, clustering and resilience, and those two curves separate as backup environments consolidate onto larger hosts.
How to price the conversion
- Total the PVUs you hold for Protect and its agents, and the annual support you pay on them.
- Measure front end and back end capacity for the same servers, monthly, for at least a quarter.
- Ask IBM for per terabyte quotes on both measures, with your three year growth priced in.
- Price the PVU renewal twice: at sub capacity, and at full capacity as the risk case if ILMT coverage slips.
- Ask how the support you have already paid on the PVU lines will be credited against the new purchase.
- Compare totals over the full term and sign the measure that wins on your own data.
Why we would leave PVU rather than repair ILMT on backup servers
When an audit readiness review finds unscanned backup servers, the usual advice is to extend the ILMT rollout and keep the PVU licenses. We think that treats the symptom. For storage software, the better course is usually to leave the metric, since per terabyte licensing counts managed data and carries no sub capacity condition.
In our engagements, the conversion saving came with that audit risk removed, which is why we put it on every storage renewal agenda. Keep ILMT on those servers for as long as any PVU lines remain, because exposure builds every quarter a scan is missing.
What per terabyte licensing still asks of you
Leaving PVU removes the ILMT dependency, but you still need a capacity count you can stand behind. Keep a monthly record of front end or back end capacity from Operations Center or the scripts, note which clients each figure covers, and file it with the entitlement.
When is the IBM Storage Suite worth buying?
The Suite is worth buying when the pool is sized to measured data. It charges one per terabyte rate across Protect, Scale, Virtualize and the rest of the family, priced on the capacity you manage rather than the number of products you run. You pay for the whole pool whether you deploy into it or not.
Sizing is where it fails. IBM tends to propose pools on projected consolidated capacity instead of measured deployment. Roughly half of the Suite bundles we reviewed were oversized, with 30 to 40 percent of the licensed capacity never deployed.
A worked sizing example
Say IBM proposes a flat 1,000 TB Suite pool for a three year term, built on a consolidation plan. You measure 600 TB under management today and expect 15 percent growth a year.
| Year | Managed TB, measured then projected | Flat pool TB | Unused TB |
|---|---|---|---|
| 1 | 600 | 1,000 | 400 (40 percent of the pool) |
| 2 | 690 | 1,000 | 310 (31 percent) |
| 3 | 794 | 1,000 | 206 (21 percent) |
A ramped entitlement of 600, 690 and 794 TB covers the same growth. The flat pool buys 916 terabyte years that sit idle over the term, which is the pattern behind the oversized bundles we see.
How to size a Suite pool
- Measure first. Use managed terabytes from Operations Center or your storage reports as the starting figure.
- Tie growth to named sources. Each year's figure should trace to a project, an application or a retention change.
- Compare with Protect Suite alone. If Protect accounts for most of your capacity, price Protect Suite on its own against the full Storage Suite.
- Ask for annual steps. Buy the pool as a ramp instead of paying for the year three figure on day one.
This is the same sizing discipline every pooled IBM commitment needs.
What have we seen in recent IBM storage negotiations?
Across roughly 20 to 25 IBM licensing engagements I advised between 2024 and 2026 that included Spectrum or IBM Storage entitlements, the license metric shaped the outcome more than the street price. The full capacity exposure and the conversion savings described above came up again and again.
Take 40 percent off a 1,000 TB pool when you use 600 TB, and you are still paying list price for every terabyte you use.
Price still mattered. Discounts of 30 to 50 percent off list were routine where a credible storage alternative sat on the table, because backup and storage software has real competitors and IBM prices against them when it has to.
The buyers who got both the conversion saving and the discount worked in the same order:
- Metric review first, deciding which lines stay on PVU and which move to per terabyte.
- Bundle sizing second, against measured terabytes.
- The discount conversation last, on a corrected base, inside the wider IBM agreement negotiation where storage trades against the rest of your IBM spend.
What will the IBM account team say, and how should you answer?
Expect some version of these four lines at a storage renewal. Each has a reply that keeps the decision on your data.
- "The rename moved you onto new IBM Storage terms." Ask for the specific part numbers and license information documents that changed. The part numbers and metrics carried over, so a claimed change needs a document behind it.
- "The Storage Suite gives you room to grow." Ask for the same pool priced as annual ramps against your measured terabytes, and compare the two totals.
- "Deploy ILMT now and the sub capacity issue goes away." ILMT stops future exposure but does not settle past quarters. Ask how IBM will treat the historical gap before you agree to anything.
- "Per terabyte will cost you more as your data grows." Ask for the per terabyte quote with your growth priced in, next to the PVU renewal at full capacity, both over the same term.
Which contract terms should you ask for on an IBM storage renewal?
Ask for terms that fix the measure, the price of growth and your right to shrink. These five matter most for storage software:
- Conversion credit. Support already paid on PVU lines credited against the per terabyte purchase, so you do not pay twice in the transition year.
- Measurement definition. Front end or back end named in the order, with the tool and the date the count is taken, so the measure cannot change at audit.
- Ramped Suite entitlements. Pool size set per year, each step with its own fixed rate.
- Price hold on added terabytes. The per terabyte rate for growth fixed for the term, as covered in our price hold clause guide.
- Reduction right. The option to cut unused Suite capacity at renewal without losing the rate, using the wording in our reduction rights guide.
What to do next
- This week. Check ILMT coverage on every PVU licensed storage server, because full capacity exposure keeps building until the scan reaches it.
- This month. Map every storage entitlement to its metric, old Spectrum and Tivoli Storage Manager part numbers included. The rename changed the product names, which makes older purchases harder to find in your records.
- Before renewal. Price the per terabyte conversion on your own front end and back end figures. It usually wins at scale and retires the ILMT dependency for those lines.
- Before any Suite quote. Size the pool against measured managed terabytes, never projected consolidation, and defend the growth curve line by line.
- At negotiation. Bring a storage alternative to the table and negotiate inside the wider agreement. Our IBM practice can run the review and the negotiation with you.
Frequently asked questions
How is IBM Spectrum Protect licensed?
Spectrum Protect, now IBM Storage Protect, is sold either in processor value units on the servers that run it or per terabyte through the Protect Suite offerings. Elsewhere in the family IBM also uses resource value units on tiered schedules, per terabyte pricing product by product, and the pooled Storage Suite rate. Check the metric printed on each entitlement line.
Does Spectrum Protect need ILMT?
Only for PVU entitlements where you claim sub capacity. ILMT must then cover every server running Protect components, with reports reviewed at least quarterly, or IBM can charge every activated core on the hosts. Per terabyte entitlements have no ILMT condition, although you still need a capacity measurement.
When does per terabyte licensing beat PVU for IBM storage?
Usually above roughly 500 TB of managed data, and the advantage grows with the data, because PVU follows compute while capacity follows what you protect. Price both over the full term, with your growth curve in the per terabyte quote and the PVU line at full capacity as the risk case.
Is the IBM Storage Suite a good deal?
It can be when the pool matches measured managed terabytes and grows in annual steps. It is poor value when sized to a consolidation plan, which is how about half the bundles we reviewed ended up oversized. Also check whether Protect Suite alone would cover most of your capacity at a lower rate.
What discounts are achievable on IBM storage software?
Discounts of 30 to 50 percent off list are common when IBM sees a credible competing backup or storage product in the evaluation. Ask for the discount after the metric and pool size are settled, so the percentage applies to the right base instead of to capacity you will never use.
Did the Spectrum to IBM Storage rename change licensing?
No. The names changed from 2023 onward, but the Passport Advantage part numbers, metrics and terms carried over. Keep the Spectrum and Tivoli Storage Manager names in your inventory next to the new ones, so purchases made under older names still match the deployments they cover.
Can Spectrum Protect Plus be covered by a Protect Suite Front End license?
Yes. IBM allows Protect Plus to be included in Protect Suite Front End and Suite Entry Front End entitlements, and publishes guidance on reconciling capacity when both products protect the same data. Ask IBM to confirm the reconciliation method in writing before you rely on it at renewal or audit.