IBM Power Servers
IBM Power buyers arrive with very different problems and one shared question: which option keeps the business running without overpaying. Your workload, your IBM i release, and your tolerance for downtime decide that long before a model number does.
Decide which IBM Power option fits the workload you have to protect, then judge whether a provider can actually deliver it.
What You Need to Sort First
- The real requirement is usually not a new server. It is someone who can hold the current IBM i system steady while the refresh gets planned.
- AS400, iSeries, P Series and Power Systems are usually the same buying conversation wearing four different names. Ask which name the customer uses internally, because that is the phrase their budget is written against.
- Your next step should be obvious: compare systems, understand pricing, find hosting, or talk to a partner who knows the platform.
- Do not let this turn into a generic server pitch. On Power the deal is decided by the application stack and the support window, not by the spec sheet.
This Page Helps You With...
- ERP workloads
- Database servers
- Business-critical applications
- Virtual machine hosting
- Legacy AS400 modernization
What You Need to Know Before You Ask for IBM Power Quotes
Use these questions to keep the first conversation practical. IBM Power decisions usually go wrong when the quote starts before the workload, operating system level, support window, and migration plan are understood.
What IBM Power models are currently supported for my workload?
Start with the workload
Do not start by asking for a model number. Start with what the system actually has to run.
- The operating system, whether that is IBM i, AIX or Linux
- The business application, such as ERP, a database or custom AS400 code
- Virtualization and high availability, if either is in play
- Test and disaster recovery environments
Model choice falls out of that. Workload size, operating system level, adapter needs and the support window you have to protect all follow from knowing the answer first.
Check IBM i compatibility before you quote
IBM keeps a system-to-IBM i mapping that shows which IBM i levels run on which Power processors. That mapping is the practical source of truth for a refresh conversation. IBM i 7.5 is the one that catches people out.
- Supported on selected IBM Power servers with Power 11, Power 10 and Power 9 processors
- Not supported on Power 8 or any earlier system
So a customer sitting on Power 8 who wants IBM i 7.5 is buying hardware, not just a software upgrade. Find that out early.
Use machine type, not memory
Memory and disk size feel like the answer, and they prove nothing about compatibility. A supportable answer needs the machine's real identity.
- Machine type and model
- Serial number
- Processor generation
- IBM i or AIX release
- Firmware level
- Installed feature codes
Ask the reseller to read those off the system itself before they name a supported target.
Separate current, refurbished, and hosted options
Four answers are all defensible here. What separates them is what the business is buying, not what the hardware is.
- A new Power system, when ownership and a long support window matter
- Refurbished Power hardware, as a bridge that buys planning time
- Hosted IBM Power, when predictable monthly cost wins over capital spend
- Power as a service, when the goal is leaving the data center
Pick the business outcome first. The model list gets short very fast after that.
How do I migrate from an older AS400 to a modern IBM Power system?
Inventory before architecture
A clean migration starts with an inventory, not a sales quote. The surprises live in the parts nobody thought to write down.
- IBM i release and applications
- Custom code, and who understands it
- Printers, users and job schedules
- Third-party tools and integrations
- Backup method and high availability setup
- Old devices or workflows still wired into the system
That last line is where projects slip. A label printer or a nightly file transfer nobody documented will stop a cutover just as hard as a failed restore.
Test application fit
The biggest risk is rarely the new server. It is whether everything hanging off it still behaves after the move.
- The application and its database files
- Reports and printers
- EDI and other interfaces
- The processes users follow every day
Make application testing a required line in the project, not a favour someone does at the end. Custom RPG, COBOL or CL code raises the stakes, and so does an old vendor ERP nobody supports anymore.
Plan the cutover window
Ask how the data moves, how long the final cutover takes, and how rollback works. Then ask who confirms the first production day is clean, by name.
- Backup checks and a tested restore
- Application testing
- User acceptance
- A stated downtime expectation
- A named owner for each step
A plan with no names in it is a wish. The owner column is the part that makes the rest real.
Choose the destination carefully
There are five plausible destinations, and picking one early is how projects end up in the wrong place.
- A new on-premises IBM Power server
- Refurbished Power hardware
- Hosted IBM Power
- Power Virtual Server
- A managed services environment
Do not pick from that list yet. Decide what the business is actually after, and the destination narrows itself.
- Ownership of the asset
- Lower capital spend
- Less internal administration
- Stronger disaster recovery
- An exit from old dependencies
What support options are available for IBM i environments?
Hardware support keeps the machine covered
Hardware support covers the physical or hosted infrastructure underneath everything else.
- Parts availability and response time
- Firmware and service eligibility
- Disks, power supplies and adapters
- HMC and tape
- A replacement strategy when a part is no longer made
On an older system, the honest question is which of those a provider can still deliver. Ask whether IBM support, third-party maintenance or refurbished parts coverage is realistic for that machine type.
IBM i support keeps the operating system healthy
IBM i support is the operating system layer, and it is the one that keeps the environment controlled day to day even when the hardware is perfectly healthy.
- Releases and PTFs
- Security and user profiles
- Jobs and printers
- Backup and performance
- Licensing and system administration
A machine under warranty with nobody watching this layer is still an at-risk system.
Application support keeps the business running
Application support is a separate contract, and buyers discover that at the worst possible moment.
- ERP and accounting
- Warehouse and manufacturing
- Custom RPG programs
- EDI and reporting
If the business runs any of those on the system, a hardware-only provider will not be enough. Confirm who answers the phone when the application breaks rather than the server.
Managed services give you ongoing coverage
Managed IBM i or AS400 services hand the daily routine to someone whose job it is.
- Monitoring and backup checks
- Day-to-day administration
- Patch planning
- Documentation
- Escalation and regular review
This is the right option when there is no internal IBM i depth, or when the business quietly depends on a system only one person understands. Documentation alone often justifies it.
What is the typical cost range for an IBM Power server refresh?
A useful estimate needs a configuration
There is no honest single price for an IBM Power refresh without a configuration. Anyone who gives you one is guessing, and the guess moves with every line below.
- Processor capacity and memory
- Internal and external storage
- Adapters, tape and HMC
- Operating system licensing
- High availability and backup
- Maintenance and migration services
- Whether the system is new, refurbished, hosted or financed
That last one alone can move the total by a factor of several. Get the configuration written down before you compare numbers.
The quote should separate hardware and services
Ask the reseller to break the quote into named lines.
- Hardware
- Software and licensing
- Maintenance
- Migration
- Project management
- Optional managed services
A low hardware price becomes an expensive project when migration, backup redesign or support was never in the number. The break-out is what lets you compare two quotes honestly.
Compare scenarios, not just totals
A good refresh quote often includes scenarios: keep the system on-premises, move to hosted IBM Power, buy refurbished hardware as a bridge, or use a managed services option. The best answer may not be the cheapest number. It is the option that lowers operational risk without overspending.
Watch the hidden cost
The hidden cost is almost never the hardware.
- Downtime nobody budgeted for
- Software that turns out to be unsupported
- Backups that were failing quietly
- Application surprises during testing
- Licensing gaps
- A migration priced too thin to finish
Make the provider say out loud what is included, what is assumed, and what happens if the cutover does not go cleanly. The answer to that last one tells you how many of these they have lived through.