BLOG

In IBM i environments, high availability and disaster recovery are rarely optional. For many organizations, the IBM i platform underpins order processing, financial transactions, manufacturing execution, logistics, billing, and regulatory reporting. When those systems are unavailable, the business does not simply slow down. It stops. Yet despite decades of experience with IBM i High Availability and Disaster Recovery, there is still confusion about what actually matters when

Replication latency is one of the most frequently discussed topics in IBM i disaster recovery, yet it remains one of the most misunderstood. It is often reduced to a single number on a dashboard, quoted as evidence that a system is protected, without sufficient consideration of what that number actually represents or whether it reflects real business exposure. Latency is not just a technical performance metric. It is the practical expression of Recovery Point Objective. At an

IBM i disaster recovery is often discussed in terms of features and technologies. In practice, effective DR comes down to a small number of non-negotiable requirements. If any one of these is missing, risk remains, regardless of how advanced the solution appears. 1. Proven recoverability Disaster recovery must be demonstrable. The organization must be able to show that systems can be recovered, applications can run, and data integrity can be verified. Assumptions are not enou

IBM i organizations often ask whether their HA and DR strategy is “good enough.” A more useful question is how mature it is. This readiness framework describes five levels of HA and DR maturity, helping organizations assess their current posture and identify what is required to improve resilience. Level 1: Replication exists (HA and DR Readiness Framework) Data is replicated, but recovery confidence is low. RTO and RPO are assumed rather than measured, and testing is infreque

Selecting a high availability and disaster recovery solution for IBM i is rarely a purely technical exercise. It is a decision that affects business risk, operational confidence, regulatory posture, and long-term cost. Yet many evaluations still focus on surface-level criteria, whether replication exists, how fast it is, or how the initial pricing compares. Those questions matter, but they are not enough. IBM i environments are long lived, business critical, and deeply integr

This checklist is designed to help IBM i organizations evaluate high availability and disaster recovery solutions in a consistent, evidence-based way. Each criterion is measurable and can be validated through testing, observation, or documentation. Data Integrity and Consistency Can the solution guarantee transactional consistency at recovery time? Is replication aware of IBM i journals, commitment control, and object dependencies? Can recovered systems be proven to represent