The Friday Payroll Day Failover - How Active/Active Saved the Bank
It was the last thursday of the month salary day.
At 9:17 AM, my friend's bank main data center had a serious problem. The cooling system failed, and temperatures started rising quickly.
The disaster recovery plan said to switch to the backup site.
But there was a problem.
Most systems were set up in an active-passive way, meaning the backup site was not running live. Switching over would take around four hours.
This meant 40,000 employees might not receive their salaries on time. However, a few critical banking services were already running on IBM LinuxONE using GDPS Parallel Sysplex.
This setup works in an active-active mode, meaning both data centers are running at the same time.
When the issue happened, something important took place. The system automatically shifted the workload to the second data center.
There was:
- no data loss
- no manual intervention
- no delay in processing
The failover completed in just 47 seconds.
Employees received their salaries on time. Even though other systems in the bank were down for hours, the most critical payments continued without interruption.
This incident changed the bank’s thinking.
What was once a long-term plan for active-active setup became an urgent priority especially to meet requirements from Saudi Central Bank.
The same setup also helps in other areas:
- Near-zero recovery time: Systems recover almost instantly
- Payment resilience: Critical systems like Mada continue working during failures
- Dependency visibility: The system identified hidden issues, like tools that still depended on the failed data center
These problems were fixed before the next audit.
The Bottom Line
Near-zero recovery is not just a goal it is built into the design. With IBM LinuxONE, banks can keep critical services running even during major failures.
Is your core banking system running in active-active mode today? Let me know below.
👇 Read more: https://community.ibm.com/community/user/blogs/imran-jalil
#IBMLinuxONE #GDPS #ActiveActive #NearZeroRTO #SAMA