Trusted Since 2005| +202 2705 2005| [email protected]| 1 to 10 Year Warranty| Ships Worldwide to 100+ Countries| Every Part Tested & Warranted| 500,000+ Enterprise Parts| Dell · HPE · IBM · Lenovo · Cisco|Trusted Since 2005| +202 2705 2005| [email protected]| 1 to 10 Year Warranty| Ships Worldwide to 100+ Countries| Every Part Tested & Warranted| 500,000+ Enterprise Parts| Dell · HPE · IBM · Lenovo · Cisco

Migrating from HPE ProLiant DL385 Gen10 to DL385 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. AMD path: Naples/Rome → Genoa delivers 96-core density per socket (Bergamo 128 cores), the largest single-socket core count jump HPE has ever shipped.

Why this migration

HPE has retired the DL385 Gen10 from sale and has published no end-of-support date. Beyond end of support, HPE post-warranty pricing escalates, SPP firmware bundle cadence drops, and iLO CVE patches tail off. DL385 Gen11 resets the lifecycle clock, brings DDR5 bandwidth, AVX-512 on Zen 4 cores, and — critically in 2026 — aligns you with HPE’s active security train (iLO 6).

OEM support timeline

HPE has published no end-of-support date for the DL385 Gen10, 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 DL385 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.

SubsystemDL385 Gen10DL385 Gen11Carry-over
CPU socketSP3SP5No — full CPU replacement
Memory (DDR4 → DDR5)4TB DDR4-26666TB DDR5-4800No — DDR4 not pin-compatible with DDR5
Storage backplaneSmart Array P408i-aMR216i-p / MR416i-oNo — controller family change (Smart Array → MR)
Drive carriers 2.5″ SFFHPE Gen10 carrierHPE Gen11 carrierCheck per drive — order the carrier HPE QuickSpecs lists for the target server
Power supplies500W-1600W800W-2200W Flex Slot (Platinum and Titanium)Partial — Flex Slot form factor preserved
Rails + CMAHPE Gen10 rail kitHPE Gen11 rail kitPartial — most 2U Gen10 rails accept Gen11 chassis with adapter
iLO generationiLO 5iLO 6Advanced 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:

  1. 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.
  2. Array metadata format changes. You cannot physically move an array built on a Smart Array P408i-a 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.
  3. 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 DL385 Gen10, 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 DL385 Gen11 alongside the cluster, add it as a node, evacuate one DL385 Gen10, retire the DL385 Gen10, 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 DL385 Gen11 becomes the standby, then failover during a planned window. This protects RPO strictly and lets you roll back if the DL385 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 (DL385 Gen11): AMD EPYC 9004 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 (DL385 Gen10) for ICD Care+ bridge: P00922-B21 (16GB RDIMM DDR4-2933), P00924-B21 (32GB RDIMM DDR4-2933), 804331-B21 (P408i-a SR Gen10), 804338-B21 (P816i-a SR Gen10)

Budget reality in USD

Get a free infrastructure audit and custom proposal. Our team responds within 24 hours.

Tel: +202 27052005Email: [email protected]

Migration phases and next steps

  1. Baseline (week 1). Export current iLO configs, HPE OneView inventory, Smart Array drive maps, BIOS settings, and firmware levels for every DL385 Gen10 node in scope. ICD provides a free export script on request.
  2. BOM design (week 1-2). RFQ to ICD for BTO DL385 Gen11 configs. ICD returns a cost-audited BOM in 24 hours with HPE part numbers, warranty posture, and lead-time visibility.
  3. Pilot (week 3-5). Deploy one DL385 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.
  4. Rolling production cutover (week 5-12). Phased migration by application window. Each DL385 Gen10 node evacuated, retired, optionally repurposed for DR or returned to ICD under buy-back credit.
  5. 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.
ICD Care+ is the safety net. If your budget approval slips by a quarter, ICD Care+ TPM covers your DL385 Gen10 at 40-60% below HPE post-warranty cost, with tested HPE parts and on-site SLA levels by tier (Silver NBD / 8H, Gold 4H, Platinum 2H response) — so you never lose maintenance coverage while the migration is on the roadmap.

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 Quote
Tel: +202 27052005Email: [email protected]

Frequently Asked Questions

What core density does the DL385 Gen11 AMD path offer over Gen10?

Moving from Naples or Rome to Genoa delivers up to 96 cores per socket, with Bergamo reaching 128 cores. Memory also moves from DDR4-2666 on the Gen10 to DDR5-4800 on the Gen11.

What happens in the first two weeks of a DL385 migration project?

In week 1 you export current iLO configs, OneView inventory, Smart Array drive maps, BIOS settings and firmware levels for every DL385 Gen10 node, and a free export script is available on request. In weeks 1 to 2 you send an RFQ for BTO Gen11 configs, and a BOM comes back in 24 hours with part numbers, warranty posture and lead-time visibility.

When does vendor support stop for the DL385 Gen10?

HPE has retired the DL385 Gen10 from sale and has published no end-of-support date. After end of support, parts availability becomes best-effort, SPP firmware bundles arrive less often and iLO CVE patches tail off, while the DL385 Gen11 is on HPE's current product line.

Last updated

Worldwide Shipping

Fast delivery to 100+ countries

Tested & Warranted

Every part fully tested before shipping

Enterprise Grade

Dell, HPE, Lenovo & Cisco parts

Dedicated Support

Expert team for quotes & technical help