IBM i High Availability Options: PowerHA, Db2 Mirror, Logical Replication, and Hosted HA
What are the high availability options for IBM i?
Four families. PowerHA SystemMirror for i clusters systems around an independent auxiliary storage pool (IASP) and switches or replicates it with geographic mirroring, Metro Mirror, Global Mirror, or LUN-level switching. Db2 Mirror for i runs two nodes active-active with synchronous replication over a RoCE link at campus distances. Logical replication products (Precisely Assure MIMIX and iTERA, Maxava HA, Rocket iCluster, Fortra Robot HA, and others) replay journaled changes to a live target at any distance. And managed providers will run any of these for you. The right choice depends on your recovery targets, distance requirements, IASP readiness, and staffing, plus a role swap testing discipline you will actually keep.
Practical decision support
Set recovery targets before you shortlist HA products
Use this guide to match written RPO and RTO targets, distance requirements, IASP readiness, and staffing reality to one of the four HA families before any vendor conversation.
- Get RPO and RTO from the business in writing first; the technology choice falls out of the targets, not the reverse.
- Score IASP readiness honestly: PowerHA's value is gated on moving applications into an IASP.
- Treat any option as unproven until a full role swap has succeeded and is scheduled to recur.
At a glance
Key takeaways
Four families, different physics
PowerHA switches or replicates an IASP, Db2 Mirror runs active-active at campus distance, logical replication replays journal entries anywhere, and managed providers operate any of the three for you.
PowerHA's toll booth is the IASP
Application data must move into an independent auxiliary storage pool before PowerHA can protect it. Since 7.5 it ships as a single edition, and Fortra develops it on IBM's behalf.
Db2 Mirror is not distance DR
Active-active synchronous replication over RoCE is a campus-distance continuous availability play (roughly 10 km on RoCE v2). Adopters pair it with a separate DR layer.
Untested HA is just DR
Fortra's own guidance says it is not HA until a full role swap has succeeded, and IT Jungle reported in 2025 that many shops go months or years without testing one.
HA Is Not DR, and Most Shops Need a Position on Both
High availability and disaster recovery answer different questions. HA keeps the business running through component failures and planned maintenance, usually with a fast, rehearsed role swap to a live secondary. DR is what happens after you lose the site: recovering somewhere else, with recovery point and time objectives measured in minutes to hours. This guide covers the HA technology choice; our IBM Power disaster recovery guide covers the DR strategy side.
The gap between owning HA and having it is real. Fortra's guidance is that a system that has never completed a full role swap successfully is only set up for DR, not HA, and an August 2025 IT Jungle article reported that many IBM i shops with HA or DR in place had not tested a full role swap in months or years.
The Four Architectural Families
Every credible IBM i HA design belongs to one of four families. First, PowerHA SystemMirror for i, IBM's cluster product, which switches or replicates an independent auxiliary storage pool between nodes. Second, Db2 Mirror for i: two nodes active-active with synchronous replication at campus distance. Third, logical replication, the oldest and most widely deployed family, which replays journaled changes object by object to a live target. Fourth, hosted and managed HA, where a provider operates one of the first three on your behalf. The families also combine: IBM's stated typical pattern pairs LUN-level switching for local HA with Metro Mirror or Global Mirror to a second site, and Precisely publishes a reference for running Assure MIMIX alongside Db2 Mirror.
PowerHA SystemMirror for i: Clustering Around the IASP
PowerHA SystemMirror for i (licensed program 5770-HAS) is IBM's cluster-based HA and DR offering, and it starts with an architectural commitment: application data must live in an independent auxiliary storage pool. The IASP is the unit PowerHA switches or replicates, so a shop that still keeps everything in SYSBAS faces a one-time project of moving libraries and IFS directories into the pool. That work is the toll booth for everything else PowerHA does. Since release 7.5, IBM has sold PowerHA as a single edition, retiring the old Express, Standard, and Enterprise split, and Fortra develops the product on IBM's behalf under a collaboration that began in 2017, when Fortra was still HelpSystems.
Replication comes in two flavors. Geographic mirroring is host-based: IBM i itself mirrors the IASP at the page level over IP, which makes it storage-agnostic (internal disk, external storage, or a mix) and available in synchronous or asynchronous modes. Per Fortra's PowerHA FAQ, synchronous delivers a recovery point of zero at distances up to roughly 300 km, while asynchronous has no distance limit and a recovery point of a few seconds on an unplanned failure; treat the distance figure as guidance and verify against your latency budget. With IBM external storage (DS8000 and FlashSystem lines), PowerHA instead drives Metro Mirror, Global Mirror, FlashCopy, and LUN-level switching, which reassigns the LUNs holding an IASP to another IBM i instance.
Licensing is per processor core with software maintenance, and since IBM's October 2024 announcement, subscription terms from 90 days to five years are available; verify current pricing with IBM or your Business Partner. PowerHA 7.6, which arrived with IBM i 7.6 in April 2025, added Power Virtual Server integrations (IASP LUN-level switching and FlashCopy inside PowerVS, plus Global Replication Service support) along with health dashboards and real-time RPO reporting for geographic mirroring. Expect switchover time in minutes rather than seconds, driven mostly by IASP vary-on and application restart; vary-on scales with the environment, so measure yours.
Db2 Mirror for i: Active-Active at Campus Distance
Db2 Mirror for i (5770-DBM), announced with IBM i 7.4 in 2019, is different in kind: it is active-active. Both nodes accept work, and every eligible database write commits on both before completing, over an RDMA over Converged Ethernet (RoCE) link. IBM positions it as "near-continuous availability": the loss of one node can be close to invisible to users on the other.
The constraints are distance and scope. RoCE v1 kept the nodes in the same data center or campus (about 200 meters for most adapters); RoCE v2 is routable and supports up to about 10 km, with synchronous latency the practical ceiling. On scope, Db2 Mirror replicates the database plus many SYSBAS object types (user profiles, authorities, programs, data areas, data queues), but IFS objects are not block-replicated: they must live in an IFS IASP managed by a cluster resource group, made accessible on both nodes through the Mutable File System. On cost, IT Jungle reported a list price of $20,000 per core at launch, along with an external SAN requirement; both are 2019 figures, so verify current terms with IBM. Under the October 2024 subscription structure, the Db2 Mirror base is no-charge, with paid Continuous Availability and Migrate While Active options; IT Jungle reported Migrate While Active at $700 per core for a 90-day subscription.
Because of the distance ceiling, Db2 Mirror pairs with a DR layer rather than replacing one. At launch, IT Jungle asked IBM and the logical replication vendors whether it would kill the third-party HA market; the consensus was no, because Db2 Mirror covers fewer object types than logical replication and is a campus play, not a distance DR play. Precisely's MIMIX-plus-Db2-Mirror solution sheet exists for exactly that pairing.
Logical Replication: The Incumbent Approach
Logical replication is the incumbent. Products in this family read journal entries, usually through IBM i remote journaling, send them to a target system, and apply them object by object. Because the mechanism is transaction-level rather than block-level, it works across any distance, mixed OS releases, and any combination of storage, including cloud targets such as IBM Power Virtual Server, Skytap on Azure, and provider-hosted LPARs. IT Jungle wrote in 2017 that the vast majority of IBM i HA deployments used logical replication rather than clustering.
Two practical properties define the tradeoff. The target is a live, usable system: vendors note the replica can run tape backups, queries, and reports without touching production, something a block-replicated IASP copy cannot do the same way. In exchange, you own the administrative overhead: choosing which objects replicate, watching apply lag, and running audits and sync checks so you can trust the target when it matters.
Who Owns Which IBM i HA Product in 2026
This market has consolidated hard, and product names have outlived several owners. Ownership affects support, roadmap, and pricing leverage, so verify it at contract time. The table reflects what we could confirm as of this writing.
| Option | Products | Lineage | Status as of this writing |
|---|---|---|---|
| Precisely | Assure MIMIX, Assure iTERA, Assure QuickEDD | Vision Solutions (MIMIX, iTera) merged with Syncsort in 2017; Syncsort became Precisely in 2020; QuickEDD came from Trader's | Assure MIMIX version 10 released; Precisely owned by a private equity consortium led by Clearlake Capital and TA Associates |
| Maxava | Maxava HA | Privately held New Zealand company founded in 2000; *noMAX products rebranded Maxava HA in 2010 | Independent; cloud replication targets include PowerVS, Skytap on Azure, Google Cloud, and AWS; offers simulated role swap testing |
| Rocket Software | Rocket iCluster, plus HA Assist for switched-disk and geomirroring deployments | Ex-DataMirror: IBM acquired DataMirror in 2007, then sold iCluster to Rocket in a deal closed in January 2012 | iCluster 9.4.0 shipped December 2025 with IBM i 7.6 support and web UI improvements |
| Fortra | Robot HA (also develops PowerHA for IBM) | Bug Busters RSF-HA, acquired by HelpSystems in 2016; HelpSystems became Fortra in November 2022 | Positioned as an affordable, fast-setup option using remote journaling of selected libraries and objects |
| Shield Advanced Solutions | HA4i | Independent Canadian developer | HA4i 7.4 shipped in 2024; requires IBM i 7.3 or later |
One quirk when comparing quotes: per IT Jungle, iSam Blue's iSB-HA is an OEM of the same RSF-HA codebase behind Robot HA, so two apparently competing products can share an engine.
Hosted and Managed HA: Buying the Outcome
If nobody on staff wants to own replication administration, the market will sell you the outcome instead. Connectria offers managed replication, primarily using MIMIX, from customer systems into LPARs in its data centers, with implementation and 24x7 monitoring handled by its staff (it describes itself as the largest IBM Power MSP in North America; a vendor claim). Maxava's Fully Managed Disaster Recovery program, launched in 2023, packages planning, implementation, monitoring, virtual and real role swap testing, and 24x7 crisis support through MSP partners such as Service Express and Meridian IT.
The cloud platforms have moved the same direction. Skytap on Azure announced a turnkey Assure MIMIX integration in October 2023 for cloud-based IBM i workloads, and Fortra documents Robot HA replication into Skytap as well. On IBM's side, PowerHA 7.6 brought IASP LUN-level switching, FlashCopy, and Global Replication Service support inside IBM Power Virtual Server. For how these services are typically packaged, see our overview of managed IBM Power cloud providers. Managed HA costs more per month, but it converts an internal discipline problem, the swap drills nobody schedules, into a contractual obligation.
Directional Comparison of the Options
Directional characterizations only: recovery times depend on your environment, and pricing changes. Verify specifics with IBM or the vendor.
| Option | RPO and RTO (directional) | Distance and storage | Admin burden and cost | Best fit |
|---|---|---|---|---|
| PowerHA geographic mirroring | Sync: zero data loss; async: seconds. Switchover in minutes, driven by IASP vary-on | Sync to roughly 300 km per Fortra; async unlimited; any storage | Low day-to-day admin after the IASP migration; per-core license or subscription | IASP-ready shops wanting IBM-supported clustering without external SAN |
| PowerHA with external storage replication | Metro Mirror: zero data loss; Global Mirror: seconds. Switchover in minutes | Requires IBM DS8000 or FlashSystem-class storage; LUN switching is local, mirroring spans sites | Needs storage skills; license plus storage replication features | Shops standardized on IBM external storage; IBM's typical pattern is LUN switching locally plus Metro or Global Mirror for DR |
| Db2 Mirror for i | Zero data loss; node loss can be near-invisible to the surviving node | Same data center or campus; up to about 10 km on RoCE v2 | Highest complexity; historically the highest cost (verify current pricing with IBM) | Continuous availability requirements that justify it, always paired with a distance DR layer |
| Logical replication | Seconds of apply lag typical; role swap in minutes when rehearsed | Any distance, any storage, mixed OS levels, cloud targets | Ongoing object selection, audits, and sync checks; wide price range across vendors | The general-purpose choice; live target usable for backups and queries |
| Managed HA service | Depends on the underlying technology; defined in the contract | Target typically in the provider's or a hyperscaler's cloud | Provider carries administration and swap drills; recurring service fee | Teams without the appetite or headcount to run replication themselves |
Role Swaps: Testing Is the Product
Whatever you buy, the swap is the product. A replication environment proves nothing until the secondary has actually carried production and handed it back. Fortra's guidance bears repeating: "it's not HA if you've never completed a full role swap successfully. Until you do a role swap, your system is only set up for disaster recovery." The failure mode IT Jungle described in August 2025 is common: HA installed years ago, swaps deferred, runbooks stale, and the people who wrote them gone.
The discipline that works: simulated role swaps for low-risk rehearsal where the product supports them, genuine scheduled swaps so the secondary carries real production periodically, the runbook updated after every exercise, and audits or sync checks running between swaps so drift gets caught early. If a vendor demo dwells on replication speed and never shows the swap tooling, ask why. An HA product whose swaps are never exercised delivers DR at best, at HA prices.
How to Choose: Work Backward from the Targets
Start from written recovery targets, then let the constraints filter the field. If the business genuinely needs near-zero outage through node failures, and will fund it, that points to Db2 Mirror, paired with logical replication or Global Mirror for distance DR. If you need zero data loss with a rehearsed, minutes-long switchover and your applications can move into an IASP, PowerHA fits. If you need to span long distances, mix OS levels, replicate into a cloud, or use the secondary for backups and reporting, logical replication is the default answer. If the honest constraint is staffing, buy managed HA and put the swap cadence in the contract.
Combining layers is normal: local continuous availability plus remote logical replication is a documented, vendor-supported architecture. What should not happen is choosing a product before the RPO and RTO conversation with the business, or signing with a vendor whose ownership and release currency you have not checked. If you want an independent read on your targets, IASP readiness, and shortlist, our free assessment is built for exactly this decision.
Risks and Common Mistakes
Use caution
Treating installed HA as working HA
Replication that has never survived a full role swap is untested DR, not HA. Trade press reporting in 2025 found shops going months or years without a swap test. Schedule swaps before you celebrate the install.
Use caution
Expecting Db2 Mirror to cover distance DR
Db2 Mirror is a campus-distance continuous availability product (roughly 10 km on RoCE v2). Site-loss protection requires a second layer: logical replication, Global Mirror, or asynchronous geographic mirroring.
Use caution
Planning around stale pricing figures
The widely quoted $20,000 per core Db2 Mirror figure is IT Jungle's 2019 launch reporting, and subscription options have changed the structure since. Verify current PowerHA and Db2 Mirror pricing with IBM or your Business Partner before building a business case.
Frequently Asked Questions
What is the difference between high availability and disaster recovery on IBM i?
High availability keeps the workload running through component failures and planned maintenance, usually with an automated or fast role swap to a live secondary system. Disaster recovery is recovering somewhere else after losing the site, with recovery point and time objectives measured in minutes to hours. Fortra's guidance is blunt: if you have never completed a full role swap, you have DR, not HA. Most shops need both layers, and the testing cadence matters more than the brochure.
What is PowerHA SystemMirror for i and how does it work?
PowerHA SystemMirror for i (5770-HAS) is IBM's clustering product. Applications and data move into an independent auxiliary storage pool (IASP), and PowerHA either mirrors that IASP at the page level over IP (geographic mirroring, synchronous or asynchronous), switches the LUNs holding it between systems, or drives Metro Mirror, Global Mirror, and FlashCopy on IBM external storage. Synchronous modes give a recovery point of zero; a switchover requires varying the IASP on at the target, so recovery time is typically minutes. It is licensed per core, sold as a single edition since 7.5, available on subscription terms since late 2024, and developed by Fortra under contract to IBM.
What is Db2 Mirror for i and when does it make sense?
Db2 Mirror for i (5770-DBM) is an active-active, synchronous replication layer inside Db2 for i: both nodes accept work and every eligible write commits on both before completing, over an RDMA over Converged Ethernet (RoCE) link. It is a continuous availability play for campus distances (RoCE v2 supports up to roughly 10 km, per IBM and IT Jungle), not a distance DR product, and it has carried the highest cost and complexity of the options; IT Jungle reported a $20,000 per core list price at its 2019 launch, so verify current pricing with IBM. Most adopters pair it with logical replication or storage replication for out-of-region DR.
Who are the logical replication vendors for IBM i in 2026?
Precisely sells Assure MIMIX, Assure iTERA, and Assure QuickEDD (Vision Solutions and Trader's lineage; Precisely is owned by a private equity consortium led by Clearlake Capital and TA Associates as of this writing). Maxava, a privately held New Zealand company, sells Maxava HA. Rocket Software sells Rocket iCluster, the former IBM and DataMirror product, with 9.4.0 shipped in December 2025. Fortra sells Robot HA, the former Bug Busters RSF-HA. Smaller options include Shield Advanced Solutions' HA4i. All use IBM i journaling to replicate objects in near real time to a live, usable target.
Is PowerHA better than logical replication?
They are different tradeoffs, not a ranking. PowerHA replicates everything in the IASP with low ongoing administration and a recovery point of zero in synchronous modes, but it requires moving applications into an IASP, and the storage-based options require IBM external storage; the target copy is not a live usable system. Logical replication needs no IASP work, spans any distance and mixed OS or storage levels, and the replica can serve backups and queries, but you manage object selection, auditing, and sync health. IT Jungle wrote in 2017 that the vast majority of IBM i HA deployments used logical replication.
Can I get IBM i high availability as a managed service?
Yes. Managed service providers such as Connectria run managed replication (commonly MIMIX) from customer systems into their data centers with 24x7 monitoring. Maxava's Fully Managed DR program delivers planning, implementation, monitoring, role swap testing, and crisis support through partners. Skytap on Azure announced a turnkey Assure MIMIX integration in 2023, and PowerHA 7.6 automates storage-based HA and DR inside IBM Power Virtual Server. Managed HA makes sense when there is no in-house appetite for replication administration and swap drills.
How often should we test a role swap?
Often enough that it is routine. Vendors and trade press both flag installed-but-untested HA as the most common failure mode: an August 2025 IT Jungle article reported many shops had not tested a full role swap in months or years. Use simulated role swaps, which Maxava and others offer, for low-risk rehearsal, but schedule genuine swaps so the secondary actually carries production periodically. Treat any HA investment without a tested swap runbook as DR at best.
Sources
- IBM Documentation: PowerHA SystemMirror for i overview (IBM i 7.6)
- IBM Support: PowerHA LUN Level Switching
- Fortra: Ask An Engineer, PowerHA FAQ (RPO and distance figures)
- IBM announcement: subscription licensing for Db2 Mirror (5770-DBM) and PowerHA (5770-HAS)
- TechChannel (Steve Will): Announcing IBM i 7.6 and 7.5 TR6
- IBM Redpaper REDP-5575: Db2 Mirror for i Getting Started
- IT Jungle: Drilling Down Into Db2 Mirror for IBM i (2019 pricing)
- IT Jungle: IBM Delivers a Db2 Mirror Update (RoCE v2 distances)
- IT Jungle: IBM Unveils Migrate While Active, HA Subscriptions (October 2024)
- Precisely: Assure MIMIX product page
- IT Jungle: Clearlake Re-Acquires Precisely In $3.5 Billion Deal
- Maxava: About Maxava (company history)
- Rocket Software community: iCluster 9.4.0 release announcement (December 2025)
- Fortra: Robot HA product page
- Fortra blog: Five Steps for Successful IBM i Role Swaps
- IT Jungle: Is Your IBM i HA/DR Actually Tested, Or Just Installed? (August 2025)
- Connectria: IBM Power Systems Managed Services (managed MIMIX)
- Business Wire: Skytap integrates Precisely Assure MIMIX on Azure (October 2023)
Not Sure Which HA Approach Fits Your IBM i Estate?
Get an independent, directional read on your recovery targets, IASP readiness, and vendor shortlist before you sign anything.