How Dual‑Mode IT Is Redefining Disaster Recovery in Banking

1. The Battle Between New and Old Business under Dual‑Mode IT

Signals from customer demand and new competitors show that banks are leveraging fintech to cut costs, increase efficiency, and shift to new growth drivers. Traditional services prioritize reliability, low cost, and structured data, while new services involve unpredictable, exploratory demands and unstructured data.

Both legacy and innovative services face business continuity challenges; IT architectures can guarantee long‑term or short‑term continuity but cannot ensure perpetual operation for all workloads.

Recent high‑profile outages, such as the 24‑hour outage of BNP Paribas, illustrate the frequency of banking IT incidents and the regulatory scrutiny they attract.

2. Evolution of Disaster Recovery Architecture

To maintain continuous operation amid growing business demands, banks must adopt robust disaster‑recovery plans, evolving from cold standby to hot standby, from local to remote and cloud‑based solutions. Two common models are highlighted:

Active‑Active (Dual‑Active)

Unlike simple backup, active‑active deploys two parallel IT systems that share the workload. If one system fails, the other takes over instantly, maximizing availability and capacity. However, logical errors such as accidental deletions can cause “double‑death” scenarios, prompting the need for continuous data protection (CDP).

Two‑Site Three‑Center

This model extends active‑active by adding a third site, ensuring real‑time data replication across locations. When the primary site fails, the secondary site assumes operations without interruption. Challenges include long switchover times, operational risk, and high construction costs.

Both approaches often suffer from “vertical silos” where each business line requires a dedicated disaster‑recovery system, leading to duplicated environments, complex maintenance, and high personnel costs.

3. The Path to Integrated Disaster Recovery

Dual‑mode IT does not replace legacy systems; each serves different scenarios. Effective disaster recovery should prioritize resource efficiency, risk reduction, elastic deployment, and rapid delivery.

A case study of a bank adopting an integrated solution from a vendor demonstrates this approach. The solution includes:

Using i2Move to quickly provision virtualized disaster‑recovery servers in a local data center.

Deploying i2Availability for automatic failover and real‑time data replication.

Implementing i2CDP to centrally protect data against accidental deletion and ransomware, reducing production read/write load.

Leveraging i2Active database semantic replication for queryable active‑active databases.

The integrated platform unifies disaster recovery and backup into a single “pool” of data, supporting both traditional large‑scale applications and agile, rapidly iterated services from the ground up.

In the era of big data, ensuring data security and business continuity is critical, especially for the financial sector, making the re‑design of banking disaster‑recovery architectures under dual‑mode IT both timely and essential.