Rocket Servergraph Licensing: Renewal Levers.

Rocket Servergraph is a backup and recovery monitoring product. It pulls status, capacity, and performance data from a heterogeneous backup estate, including IBM Storage Protect, formerly Tivoli Storage Manager, and presents it in a single view so operations teams can catch failed jobs, forecast capacity, and prove recovery readiness. It reached Rocket Software (formerly through its own acquisitions and the broader portfolio Rocket has assembled) and sits alongside the modernization and connectivity tools the company sells into the mainframe estate. The commercial point for a buyer is that Servergraph is not a core z/OS engine: its license follows what it manages, and that distinction shapes both the cost and the levers.

Servergraph is commonly licensed on managed scope rather than z/OS MSU. The unit of measure is typically the number of backup servers or instances under management, and in some agreements the volume of protected data. Rocket has been moving portfolio toward term and subscription structures, so a current order may show an annual subscription with a managed count attached rather than a perpetual license plus maintenance. Confirm the exact metric on your order, because a per server basis and a per terabyte basis move in different directions as an estate consolidates.

Directional summary. Confirm the exact product entitlement, unit of measure, and managed count on your own Rocket order.

Three drivers set the number on a Servergraph line. The managed count, because the charge follows the number of backup servers or instances under watch, so an entitlement sized to a larger past estate keeps billing for monitors that no longer exist. The commercial model, because a shift from perpetual plus maintenance to subscription changes the cash profile and removes the option to drop maintenance and keep running. And bundling, because Rocket increasingly sells monitoring inside wider portfolio agreements where the individual line cannot be benchmarked. Servergraph rewards an estate that has been reconciled to current reality and punishes one where the count drifted up and never came back down.

The traps on a managed scope product differ from the MSU traps that dominate the rest of the estate. Count drift is the main one: instances added during a project remain entitled long after the project ends, and the renewal quietly bills the high water mark. Scope creep is the second, where Servergraph is pointed at backup environments the order never priced. The third is bundle opacity, where the line is folded into a larger Rocket agreement so the managed count is never tested against deployment. An independent reconciliation of entitled count against what is actually monitored is the defense, the same discipline we bring to Rocket contract review.

Right sizing comes first. Reconcile the licensed managed count against what is genuinely monitored today, because estates shrink as backup infrastructure consolidates and the entitlement almost never shrinks with them. Then unbundle the line so it can be benchmarked on its own managed scope rather than absorbed into a wider Rocket portfolio deal. Cap uplift across the term, and where the monitoring function can be met another way, a costed alternative adds leverage even when the plan is to renew. Because Servergraph sits outside the MSU bill, the optimization is cleaner than on a capacity tool: the count is countable, and a count that has drifted is the fastest money on the table. This is the heart of our Rocket renewal work.

Publisher hub: Rocket Software mainframe licensing. Related product: Rocket Terminal Emulation (BlueZone). Related concept: MSU explained. Put it to work: Rocket renewal advisory.