Recovery for Db2: priced on the estate it protects, not the recoveries it runs.

BMC Recovery Management for Db2 is the recovery and resilience solution within the BMC AMI Data for Db2 family, with BMC AMI Recover for Db2 as its core component. It automates the backup and recovery of Db2 objects across data sharing and non data sharing environments, the tooling a shop relies on to bring Db2 data back fast and correctly after a failure. It is insurance against the worst day, which is exactly why it is rarely cut, and why its licensing deserves the same scrutiny as any deeply embedded product: a vendor can renew resilience tooling aggressively because no one wants to be the one who dropped it.

Recovery Management for Db2 is licensed on capacity. BMC uses MSU, the IBM measure of processor capacity, as the unit of measurement, so the entitlement is built on the MSU rating of the machines or LPARs where the product is authorized, carried under a multi year agreement rather than a charge per recovery. The Recovery Management premium feature is enabled through a specific license, so the exact components and features in scope matter. BMC also offers zConsumption Licensing (zCL), a consumption based model that prices against prior year measured MSU utilization with a year end true up.

Directional, pattern level. Confirm your own metric, components, and authorized capacity against the contract schedules before modeling a renewal.

The dominant driver is the MSU capacity of the Db2 environment the product is authorized to protect. Because the price tracks that footprint rather than recovery activity, a large or recently upgraded Db2 estate can carry a higher entitlement than the recovery workload alone would justify. The second driver is feature scope: Recovery Management premium features and the surrounding AMI components are enabled by specific licenses, so paying for capability you do not use is a real and common cost. The third is the BMC agreement structure and any uplift or escalator terms that raise cost over the term regardless of how the Db2 estate changes.

Recovery tooling exposure sits in the Db2 footprint and the feature set. Common traps we see at pattern level:

The entitlement is built on Db2 capacity and feature scope, so the levers work both. The five that pay:

Db2 recovery is a category with credible alternatives: IBM Db2 Utilities and Broadcom (CA) Db2 tooling cover overlapping recovery and backup ground, and a shop can evaluate a switch. But recovery tooling is the last thing most organizations want to disrupt, because the cost of getting recovery wrong dwarfs any licensing saving, and recovery procedures are deeply rehearsed into operational runbooks. That makes a switching threat real but heavy, and it should only be raised when genuinely prepared and tested. For most estates the more reliable wins are aligning the authorized capacity to the protected Db2 footprint, trimming unused feature scope, and choosing the licensing model deliberately.