The FlashSystem 5600 is the practical starting point for smaller mixed workloads, the 7600 is the balanced choice for larger consolidated environments, and the 9600 is built for the highest capacity and transaction demands. For an IBM i shop, the right choice depends on measured latency, IOPS, throughput, usable capacity, growth, attachment design, and recovery requirements rather than the Power server model alone.
That is the short answer. The useful answer is in the differences.
FlashSystem 5600, 7600, and 9600 at a Glance
| Model | System | Effective Capacity | Read Bandwidth | Maximum IOPS | Practical Workload Fit |
|---|---|---|---|---|---|
| FlashSystem 5600 | 5127-A20, 1U, 12 NVMe slots | Up to 2.4 PBe | Up to 30 GB/s | Up to 2.6 million | Smaller mixed workloads, compact deployments, secondary systems, and focused IBM i environments |
| FlashSystem 7600 | 5075-A30, 2U, 32 NVMe slots | Up to 7.2 PBe | Up to 55 GB/s | Up to 4.3 million | Larger mixed workloads, consolidated applications, virtualization, analytics, and growing IBM i estates |
| FlashSystem 9600 | 5078-A40, 2U, 32 NVMe slots | Up to 11.8 PBe | Up to 86 GB/s | Up to 6.3 million | Mission-critical databases, large consolidation, core business systems, and the most demanding transaction workloads |
Those numbers are ceilings, not a sizing recommendation. IBM reports maximum IOPS using a 4 KB read-hit workload, and effective capacity depends on the data reduction a real dataset can achieve. A system should be sized from the workload it will run, not from whichever column contains the largest number.
What the Three Systems Share
The 5600, 7600, and 9600 are the three enterprise systems IBM introduced together in February 2026. All three use IBM Storage Virtualize, active-active controller designs, FlashCore Module 5 support, data reduction, replication, immutable snapshot options, and hardware-assisted ransomware detection. IBM made the systems generally available on March 6, 2026.
The common software layer matters to IBM i buyers because the model decision is not a choice between three unrelated storage products. It is a capacity, performance, connectivity, and resiliency decision inside the same FlashSystem family.
When the FlashSystem 5600 Fits
The FlashSystem 5600 puts 12 NVMe devices into a 1U control enclosure. IBM positions it for smaller mixed workloads that still need the availability and data services of the enterprise FlashSystem family.
For IBM i, that can make the 5600 a sensible candidate for a focused production environment, a secondary system, development and test, remote locations, or an organization replacing an older entry or midrange array without needing the capacity and port scale of the 7600. It is also the model to examine first when rack space and power are real constraints.
The mistake would be treating "entry-level" as a complete sizing answer. A compact system can still be the wrong choice if several IBM i partitions, aggressive batch windows, replication traffic, or fast growth compete for the same resources.
When the FlashSystem 7600 Fits
The FlashSystem 7600 is the middle system, but "middle" undersells what it is for. Its 2U enclosure supports 32 NVMe devices, up to 55 GB/s of published read bandwidth, and up to 4.3 million IOPS. IBM positions it for larger mixed and transactional workloads.
This is likely to be the comparison point for many established IBM i shops: multiple partitions, mixed IBM i and AIX workloads, broader server consolidation, heavier database activity, or a storage refresh expected to absorb growth for several years. It has materially more capacity, memory, connectivity, and performance headroom than the 5600 without automatically moving the project to the largest system.
When the FlashSystem 9600 Fits
The FlashSystem 9600 is the high-end choice for large consolidated and mission-critical workloads. IBM publishes up to 11.8 PBe of effective capacity in one enclosure, up to 86 GB/s of read bandwidth, and up to 6.3 million IOPS.
An IBM i environment should consider the 9600 when the storage layer supports a large number of systems or partitions, demanding OLTP databases, critical ERP workloads, tight recovery objectives, or growth that would make a smaller system a short-lived decision. It should not be selected simply because it is the fastest model. Unused headroom is still part of the bill.
Where FlashSystem 5000 and C300 Fit
IBM's current family comparison also includes FlashSystem 5000 and FlashSystem C300. The 5000 serves smaller mixed workloads and backup use cases. The capacity-dense C300 is aimed at backup, sequential, and archival workloads. They are legitimate choices, but they answer different questions than the three new systems compared here.
If the requirement is primarily backup capacity or sequential data rather than transactional IBM i performance, include those systems in the evaluation. If the requirement is a current enterprise array for mixed and transactional work, begin with the 5600, 7600, and 9600.
IBM i Compatibility Has to Be Checked by Configuration
FlashSystem family branding does not certify every IBM i configuration. IBM's System Storage Interoperation Center now organizes FlashSystem interoperability by Storage Virtualize code level and connection protocol rather than model name alone.
Before approving a configuration, verify the exact IBM i release, Technology Refresh level, Power server generation, Fibre Channel adapter, direct or switched attachment, VIOS or native design, SAN switch, multipathing, and Storage Virtualize level in the IBM System Storage Interoperation Center. If the intended combination is not listed, the next step is an IBM SCORE or RPQ review rather than an assumption.
A Better IBM i Sizing Conversation
- Measure the current workload. Collect usable and allocated capacity, peak IOPS, read and write mix, latency, throughput, batch-window behavior, replication traffic, and growth.
- Separate capacity from performance. A database can be small and latency-sensitive. A backup repository can be large and mostly sequential. Those are not the same storage problem.
- Define resiliency. Decide whether the design needs local high availability, immutable snapshots, replication, a second site, or integration with the existing recovery process.
- Validate interoperability. Check the exact host, adapter, protocol, switch, operating-system, and Storage Virtualize combination in SSIC.
- Price the lifecycle. Include enclosure configuration, FlashCore Modules or industry-standard drives, adapters, software, support, migration work, and expected expansion instead of comparing base hardware alone.
Replacing Storwize V7000
A shop moving from an IBM Storwize V7000 is already familiar with the software lineage behind Storage Virtualize. That can make FlashSystem the natural family to evaluate, but it does not make the migration automatic. Confirm the existing V7000 generation and code level, host mappings, volume design, attachment method, replication, capacity, and performance before deciding whether the 5600, 7600, or 9600 is the right replacement.
Common FlashSystem Questions
Which FlashSystem is best for IBM i?
The 5600 fits smaller focused workloads, the 7600 fits larger mixed and consolidated environments, and the 9600 fits the highest-capacity and most demanding transaction workloads. Final sizing requires measured workload data and an SSIC-validated configuration.
Does every IBM i environment need a FlashSystem 9600?
No. The 9600 provides the most headroom, but many IBM i environments will fit the 5600 or 7600. Buying unused maximum performance is not a substitute for sizing.
Can IBM i connect directly to FlashSystem?
Some direct and SAN-attached configurations are supported, but support depends on the IBM i release, adapter, protocol, and Storage Virtualize level. Check the exact combination in IBM SSIC before ordering.
Can a Storwize V7000 migrate to FlashSystem?
FlashSystem is the successor family and uses IBM Storage Virtualize, but the migration method depends on the V7000 generation, software level, host design, and target configuration. Inventory those details before committing to a migration method.
What does FlashCore Module 5 change?
IBM's fifth-generation FlashCore Module adds computational storage functions, hardware-assisted data reduction, telemetry, and ransomware anomaly detection. IBM reports detection in under one minute under its documented test conditions, but actual results depend on software, hardware, and workload configuration.
Start With the Workload
The useful question is not "Which FlashSystem is biggest?" It is "Which system meets this IBM i workload's requirements with enough room for growth, recovery, and support?" Midland can use the current environment, the growth plan, and the IBM support matrix to turn that into a configuration instead of a guess.