Migrating from HPE ProLiant DL360 Gen9 to DL360 Gen11 — Parts, Timeline and Budget Guide
Written for IT leaders planning an HPE ProLiant refresh in 2026. All specs and part numbers come from HPE QuickSpecs and ICD’s live catalog. Dense 1U deployments with tight rack budgets get the biggest ROI from this migration — the Gen11 DL360 offers 2x memory density in the same 1U footprint.
Why this migration
HPE has retired the DL360 Gen9 from sale and publishes no end-of-support date for it. Beyond end of support, HPE post-warranty pricing escalates, SPP firmware bundle cadence drops, and iLO CVE patches tail off. DL360 Gen11 resets the lifecycle clock, brings DDR5 bandwidth, AMX AI tile instructions, and — critically in 2026 — aligns you with HPE’s active security train (iLO 6).
OEM support timeline
HPE publishes no end-of-support date for the DL360 Gen9, so check your coverage with HPE by serial number. After end of support, HPE parts availability becomes best-effort, OneView firmware bundles ship less frequently, and critical CVE patches for iLO/BIOS taper off.
Your DL360 Gen11 is on HPE’s current product line. New HPE SPP (Service Pack for ProLiant) drops land first on the active platforms, which means your security posture improves measurably post-migration.
Compatibility analysis
The DDR4 → DDR5 transition is the single biggest compatibility barrier. DDR5 UDIMM/RDIMM uses 288 pins at 1.1V versus DDR4 at 1.2V; notch positions differ; PMIC is on-DIMM rather than on-motherboard. Zero mechanical carry-over. Expect full memory replacement for this path.
| Subsystem | DL360 Gen9 | DL360 Gen11 | Carry-over |
|---|---|---|---|
| CPU socket | LGA2011-3 | LGA4677 | No — full CPU replacement |
| Memory (DDR4 → DDR5) | 3TB DDR4-2400 | 8TB DDR5-4800 | No — DDR4 not pin-compatible with DDR5 |
| Storage backplane | Smart Array P440ar | MR216i-p / MR416i-o | No — controller family change (Smart Array → MR) |
| Drive carriers 2.5″ SFF | HPE Gen8/9 carrier | HPE Gen11 carrier | No — new drive tray |
| Power supplies | 500W-1400W | 500W-2200W Flex Slot | Partial — Flex Slot form factor preserved |
| Rails + CMA | HPE Gen8/9 rail kit | HPE Gen11 rail kit | No — new rail kit |
| iLO generation | iLO 4 | iLO 6 | Advanced license transferable with HPE-assisted entitlement move |
Smart Array → MR controller implications
The controller line change from HPE Smart Array to Broadcom-based MR (MegaRAID) controllers on Gen11 is more than a rebrand. Three operational impacts matter in a migration:
- Cache protection hardware changes. The HPE Smart Storage Battery kit (for example 871264-001 with a 145 mm cable or P01367-B21 with a 260 mm cable) depends on the controller and chassis — order the kit HPE QuickSpecs lists for the target controller.
- Array metadata format changes. You cannot physically move a Smart Array P840ar-flashed array into an MR216i-p and expect it to import. The data must be migrated via replication (storage vMotion, DB log shipping, rsync, etc.) — not drive-pulled and re-inserted.
- Management tooling changes. HPE Smart Storage Administrator (SSA) scripts and Ansible modules do not target MR controllers. Rewrite or port to storcli64 / Redfish MR schemas.
Data migration path
Depending on what sits on the DL360 Gen9, the data path varies. For hypervisor hosts (VMware vSphere, Nutanix, KVM, Hyper-V) the cleanest path is live workload migration — vMotion, Nutanix Move, Live Migration — node-by-node. Provision one DL360 Gen11 alongside the cluster, add it as a node, evacuate one DL360 Gen9, retire the DL360 Gen9, repeat. ICD has delivered 40+ of these phased VMware refreshes in the region with near-zero downtime.
For bare-metal databases (Oracle, MSSQL, PostgreSQL) use native replication: Oracle Data Guard, SQL Server AG, PG streaming replication. Target DL360 Gen11 becomes the standby, then failover during a planned window. This protects RPO strictly and lets you roll back if the DL360 Gen11 hits an unexpected issue during burn-in.
For file servers, backup targets, and archive the classic rsync or Robocopy approach works — but plan for longer windows if you are moving from 12G SAS SFF to NVMe E3.S, as the target can ingest 4-10x faster than the source can read.
Parts shopping list (real PNs in ICD’s catalog)
- Target CPU (DL360 Gen11): Xeon Scalable Gen4/Gen5 processors (kit part numbers are specific to each chassis, quoted for your exact server)
- Target memory (DDR5): P43328-B21 (32GB RDIMM DDR5-4800), P43331-B21 (64GB RDIMM DDR5-4800), P50311-B21 (32GB 2Rx8 DDR5-4800), P50312-B21 (64GB 2Rx4 DDR5-4800), P43334-B21 (128GB DDR5-4800 3DS)
- Target controller: P26324-B21 (MR216i-a 12G), P26279-B21 (MR416i-a 12G), P06367-B21 (MR416i-p 12G), P04220-B21 (SR416i-a 24G Tri-Mode), P12688-B21 (SR416i-a 24G)
- Target PSU: P38995-B21 (800W FS Platinum), P18224-B21 (800W FS Titanium)
- Source spares available (DL360 Gen9) for ICD Care+ bridge: 726718-B21 (8GB RDIMM DDR4-2133), 774172-001 (16GB RDIMM DDR4-2133), 726736-B21 (P440ar / 2GB FBWC), 749974-B21 (P440ar / 2GB, Fio kit)
Budget reality in USD
Get a free infrastructure audit and custom proposal. Our team responds within 24 hours.
Migration phases and next steps
- Baseline (week 1). Export current iLO configs, HPE OneView inventory, Smart Array drive maps, BIOS settings, and firmware levels for every DL360 Gen9 node in scope. ICD provides a free export script on request.
- BOM design (week 1-2). RFQ to ICD for BTO DL360 Gen11 configs. ICD returns a cost-audited BOM in 24 hours with HPE part numbers, warranty posture, and lead-time visibility.
- Pilot (week 3-5). Deploy one DL360 Gen11 pilot node. Migrate one non-critical workload (typically a dev/test VM, a secondary DB replica, or a file-server target). Validate performance under load, iLO Redfish scripts, and your backup integration.
- Rolling production cutover (week 5-12). Phased migration by application window. Each DL360 Gen9 node evacuated, retired, optionally repurposed for DR or returned to ICD under buy-back credit.
- Post-migration (week 13+). Turn off HPE support on the retired fleet (or keep it if you are holding as cold spares), re-baseline capacity plans against the new platform headroom, and document the new BOM for next-cycle planning.
Get a migration BOM + TCO model
ICD returns a full BOM, pilot-node quote, phased migration plan, and optional ICD Care+ bridge pricing within 24 hours.
Request a Migration QuoteFrequently Asked Questions
Can Smart Array drives from a DL360 Gen9 be moved into a Gen11 MR controller?
No. The array metadata format changes, so a Smart Array set will not import into an MR216i-p if you simply pull and re-insert the drives. Data must be migrated by replication, such as storage vMotion, database log shipping or rsync. The Gen11 also uses new drive carriers, so the Gen9 trays do not carry over.
Do DL360 Gen9 power supplies fit into a DL360 Gen11?
Only partially. The Gen9 used 500W to 1400W Flex Slot supplies and the Gen11 takes 500W to 2200W Flex Slot units; supplies are validated per platform, so order the units HPE QuickSpecs lists for the Gen11. Gen11 target units include P38995-B21 (800W FS Platinum) and P18224-B21 (800W FS Titanium).
How do we move bare-metal databases off a DL360 Gen9 with minimal risk?
Use native replication such as Oracle Data Guard, SQL Server AG or PostgreSQL streaming replication. The DL360 Gen11 becomes the standby, and you fail over during a planned window. This protects RPO strictly and lets you roll back if the new node hits an unexpected issue during burn-in.
