WebSphere DR and cold standby licensing.
A disaster recovery copy of WebSphere is not automatically free. Whether it needs a license depends on how cold the standby truly is, and idle is not the same as unlicensed. Auditors test that distinction closely.
Most organizations run a second copy of WebSphere for resilience, and most assume the recovery copy carries no license cost because it is not serving traffic. That assumption is right for one specific configuration and wrong for the others. IBM distinguishes between cold, warm, and hot standby, and only the coldest end of that spectrum attracts no charge. The audit risk is that a standby labeled cold internally has quietly become warm in practice.
The governing idea is processor activity, not business intent. A standby qualifies for relief when it is genuinely dormant: the software installed but not started, the machine off or idle, no synchronization or processing happening. The moment the standby is doing work, running the software, replicating data, or sitting ready to take over instantly, it is consuming capacity, and capacity is what PVU counts. The label your runbook uses does not change what the processor is doing.
The three standby states
- Cold standby. The software is installed but not running, and the system is off or idle until a failover is invoked. This is the state that generally carries no separate license charge.
- Warm standby. The software is running and data is synchronizing, ready to take over quickly. The processor is active, so the copy generally requires licensing.
- Hot standby. A fully active copy able to serve immediately, often load sharing. This is licensed like production.
Where the audit finding comes from
The common trap is drift. A copy set up as cold standby gets a replication job added so recovery is faster, or the software is left running so failover is smoother. Each change is sensible operationally and each one moves the copy toward warm. ILMT, watching processor activity, records the standby as active, and IBM reads an active install as a licensable one. The organization believed it had a free recovery site and discovers an unlicensed environment in scope.
How we defend it
We establish the true state of each recovery copy from the evidence rather than the label. Where a standby is genuinely cold, we document the dormancy and the failover procedure to support the no charge position. Where it has drifted warm, we reconcile it against entitlements, apply sub-capacity correctly to the recovery hosts, and where appropriate fold the recovery footprint into the broader settlement rather than letting it stand as a separate, full-capacity surprise. The goal is a recovery posture that is both resilient and defensible.
IBM licenses standby by what the processor is doing, not by what the runbook calls it. Keep cold standby genuinely dormant and document it, because the moment a recovery copy runs the software or replicates data continuously, ILMT records it as active and IBM treats it as licensable.
Recovery copies in the audit scope?
Our Audit Defense engagement establishes the true state of each standby, documents genuine cold standby, and reconciles any active copy before it becomes a full-capacity finding.
See Audit Defense →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.