{"title":"HPE Gen 10 Servers","description":"\u003cp data-start=\"485\" data-end=\"515\"\u003e\u003cstrong data-start=\"485\" data-end=\"515\"\u003eHPE Gen10 ProLiant Servers\u003c\/strong\u003e\u003c\/p\u003e\n\u003cp data-start=\"517\" data-end=\"871\"\u003e\u003cstrong data-start=\"517\" data-end=\"547\"\u003eHPE ProLiant Gen10 servers\u003c\/strong\u003e deliver the performance, security, and scalability required for modern IT infrastructure. Built on \u003cstrong data-start=\"647\" data-end=\"681\"\u003eIntel Xeon Scalable processors\u003c\/strong\u003e, the Gen10 platform supports high core counts, large DDR4 memory capacities, and advanced storage technologies designed for virtualization, cloud platforms, and data-intensive applications.\u003c\/p\u003e\n\u003cp data-start=\"873\" data-end=\"1274\"\u003eThe Gen10 family includes widely used enterprise systems such as the \u003cstrong data-start=\"942\" data-end=\"1001\"\u003eDL360 Gen10, DL380 Gen10, DL560 Gen10, and BL460c Gen10\u003c\/strong\u003e, offering options for dense rack deployments, blade environments, and large-scale virtualization clusters. These servers are commonly deployed in \u003cstrong data-start=\"1148\" data-end=\"1226\"\u003edata centers, private cloud environments, and enterprise business networks\u003c\/strong\u003e where performance and reliability are critical.\u003c\/p\u003e\n\u003cp data-start=\"1276\" data-end=\"1593\" data-is-last-node=\"\" data-is-only-node=\"\"\u003eAt \u003cstrong data-start=\"1279\" data-end=\"1300\"\u003eWholesale Servers\u003c\/strong\u003e, we provide \u003cstrong data-start=\"1313\" data-end=\"1356\"\u003eprofessionally tested HPE Gen10 servers\u003c\/strong\u003e that deliver enterprise performance at a fraction of the cost of new hardware. Whether you’re upgrading your data center or building a virtualization lab, HPE Gen10 systems offer the flexibility and power to support demanding workloads.\u003c\/p\u003e","products":[{"product_id":"hp-proliant-dl380-g10-3-5-12-bay-server","title":"HPE ProLiant DL380 Gen10 12-Bay 3.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 12-Bay 3.5\" is the LFF capacity configuration of HPE's 2U dual-socket Gen10 platform: twelve large-form-factor 3.5\" SAS\/SATA hot-swap bays on the same Purley dual-socket motherboard, same memory architecture, same iLO 5 management, and same Smart Array RAID family as the 16-Bay 2.5\" canonical. This page covers the LFF chassis and its bulk-capacity storage profile.\u003c\/p\u003e\u003cp\u003eFor the full platform-fact story (processors, memory architecture, FlexibleLOM networking, PCIe expansion, iLO 5 management, Smart Array controllers, power supplies, physical specs), see the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\" canonical page\u003c\/a\u003e. Everything documented there applies to this 12-Bay LFF variant; this page focuses on what's different about the LFF chassis and the workloads it serves.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhat's Different About This Chassis\u003c\/h2\u003e\u003cp\u003eThe 12-Bay 3.5\" is the bulk-capacity variant of the DL380 Gen10 family. Three things define it relative to the SFF siblings:\u003c\/p\u003e\u003col\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF drive support.\u003c\/strong\u003e Twelve 3.5\" hot-swap bays accept 7,200 RPM NL-SAS \/ SATA enterprise capacity drives at up to 20 TB each (current generation). The platform also accepts 3.5\" SAS HDDs at 10K or 15K RPM (legacy choice, rarely deployed today) and 3.5\" enterprise SATA HDDs. SFF 2.5\" drives are NOT supported in the 12-Bay 3.5\" backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBulk-capacity workload profile.\u003c\/strong\u003e The 12-Bay LFF is sized for NAS, file serving, backup repository, archive, object storage, and Ceph capacity-tier OSD nodes. The storage profile is high-capacity, sequential-throughput-optimized; random IOPS per drive (150 to 200 on 7,200 RPM NL-SAS) is intentionally modest. This is bulk capacity in a 2U enterprise chassis.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e240 TB raw at maximum density.\u003c\/strong\u003e 12 x 20 TB NL-SAS = 240 TB raw, approximately 180 TB usable at RAID 6. This is the largest single-server capacity envelope in the Gen10 lineup and one of the densest 2U LFF capacities in the broader market.\u003c\/li\u003e\n\u003c\/ol\u003e\u003cp\u003eThe 12-Bay LFF is the right chassis when capacity-per-dollar drives the design and high random IOPS is not the binding constraint. When the workload is random-IOPS-bound or NVMe-latency-sensitive, the SFF chassis (16-Bay or 24-Bay 2.5\") is the right call.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Architecture\u003c\/h2\u003e\u003cp\u003eTwelve 3.5\" SAS\/SATA hot-swap front bays. Optional mid-plane adds 4 LFF (16 LFF total) and optional rear 3LFF + 2 SFF on appropriate Gen10 12-Bay variants, totaling up to 19 LFF + 2 SFF drives on flagship configurations. The 12-Bay base configuration (twelve front bays only) is the most common WS-stocked variant.\u003c\/p\u003e\u003cp\u003eCommon 12-Bay 3.5\" configurations we deploy:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNAS \/ file serving at scale:\u003c\/strong\u003e 12 x NL-SAS HDDs at 16 TB or 20 TB each. 12 x 20 TB NL-SAS at RAID 6 = 200 TB raw \/ approximately 160 TB usable. Suitable for general-purpose enterprise file shares, SMB\/CIFS departmental shares, NFS exports, and Windows Storage Server deployments. Memory at 128 GB to 256 GB is the practical range; file system caching from DRAM meaningfully improves read throughput on spinning disk arrays.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBackup repository (Veeam, Commvault, NetBackup):\u003c\/strong\u003e 12 x NL-SAS HDDs at RAID 6 or RAID 60 (when expanded with optional mid-plane to 16 LFF). The DL380 Gen10 12-Bay is widely deployed as Veeam ReFS repository or XFS landing for backup workloads where high write throughput and high capacity matter more than random IOPS. Pair with 25 GbE FlexibleLOM for backup ingestion at line rate.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCeph capacity-tier OSD nodes:\u003c\/strong\u003e 12 OSDs per node with NL-SAS HDDs, paired with separate flash-tier nodes for cache and metadata. The 12-Bay LFF is the right HPE platform for Ceph capacity tiers where cost-per-TB drives the design. Plan memory at 6 GB per OSD plus 16 GB overhead (96 GB to 128 GB per node typical).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eArchive and tier-3 storage:\u003c\/strong\u003e Long-retention cold storage where data is written once and read rarely. 12 x 20 TB NL-SAS at RAID 6 with low memory and minimal CPU. Often deployed with HSM (hierarchical storage management) software that tiers data between this and faster storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eObject storage nodes (S3-compatible: MinIO, Scality, Cloudian, OSNexus):\u003c\/strong\u003e Software-defined object storage with the 12 LFF bays as the storage layer. The DL380 Gen10 12-Bay is a common building block for on-premises S3 deployments where the workload economics favor LFF over SFF.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed SAS SSD + NL-SAS tiered storage:\u003c\/strong\u003e 1 to 2 SAS SSDs in the optional mid-plane SFF bays for metadata or hot-data tier alongside 12 NL-SAS HDDs for bulk; tiered approach meaningfully improves effective NAS throughput for frequently-accessed data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eRAID Strategy for LFF Capacity\u003c\/h2\u003e\u003cp\u003eRAID strategy on 12-Bay LFF is the most consequential choice in the configuration because rebuild times on 16 TB to 20 TB drives are long enough that single-parity is not safe:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 6 mandatory for all NL-SAS \/ capacity configurations.\u003c\/strong\u003e Rebuild times on 16 TB to 20 TB NL-SAS HDDs at the 12-bay level commonly exceed 24 to 30 hours per drive; two-drive fault tolerance is non-negotiable. RAID 5 at this drive capacity is not a supportable production configuration.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 60 for backup repositories and Veeam ReFS:\u003c\/strong\u003e Two RAID 6 sets striped (6 + 6 drives) provides redundancy per set with aggregate throughput approaching dual-controller bandwidth. Strong fit for Veeam ReFS where the underlying file system contributes additional resilience.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eJBOD \/ HBA mode for software-defined storage:\u003c\/strong\u003e Smart Array E208i-a (HBA mode) is the controller for Ceph, ZFS, and similar software-defined stacks that require direct disk access. RAID handled at the software layer (Ceph replication, ZFS RAIDZ, etc.).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB FBWC) is the production hardware-RAID default for NAS and backup workloads.\u003c\/strong\u003e The 4 GB write cache absorbs burst writes meaningfully on NL-SAS arrays; sustained write throughput is bounded by spinning disk bandwidth.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot configuration: HPE M.2 enablement kit installs 1 or 2 M.2 SATA SSDs in a dedicated bay outside the 12 LFF data bays. We strongly recommend M.2 boot; capacity nodes should have all 12 LFF bays available for data.\u003c\/p\u003e\u003ch2\u003eMemory and Networking for Bulk Storage\u003c\/h2\u003e\u003cp\u003eFor NAS and file serving, plan memory at 128 GB to 256 GB per node. File system caching from DRAM is the primary lever to improve effective read throughput on spinning disk arrays; more memory equals more hot data served from cache rather than disk seeks. Workloads with high read-to-write ratios benefit disproportionately from large caches.\u003c\/p\u003e\u003cp\u003eFor Veeam repository and backup workloads, 128 GB is the practical minimum for serious repository nodes; 256 GB is common for high-concurrency backup environments. Veeam ReFS metadata caching benefits from substantial memory; XFS-based Linux repositories similarly benefit.\u003c\/p\u003e\u003cp\u003eFor Ceph capacity-tier OSDs, 96 GB to 128 GB per node (12 OSDs at 6-8 GB each plus daemon overhead). BlueStore deployments at this capacity benefit from the higher end of that range.\u003c\/p\u003e\u003cp\u003eNetworking: the FlexibleLOM is the right slot for the primary network. For backup ingestion or NAS serving at production scale, 2 x 25 GbE SFP28 via the HPE 631FLR-SFP28 is the typical fit. For smaller-scale deployments, 2 x 10 GbE BASE-T or SFP+ FlexibleLOMs are adequate. 100 GbE FlexibleLOMs exist but are bandwidth-bound by PCIe Gen3 at the x8 mezzanine; for true 100 GbE throughput, the platform is Gen10+ with PCIe Gen4.\u003c\/p\u003e\u003ch2\u003ePower Sizing for LFF Capacity Workloads\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eConfiguration\u003c\/th\u003e\n\u003cth\u003ePSU Recommendation\u003c\/th\u003e\n\u003cth\u003eEst. Peak Draw\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLight (2x Silver 4214, 64 GB, 12 NL-SAS HDDs, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 500W Platinum (hot-plug redundant)\u003c\/td\u003e\n\u003ctd\u003e~360W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBalanced NAS (2x Gold 5218, 256 GB, 12 NL-SAS HDDs, P816i-a, 2 x 10 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~440W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVeeam repository (2x Gold 5218, 256 GB, 12 NL-SAS HDDs, P816i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~460W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCeph capacity-tier OSD (2x Gold 5218, 128 GB, 12 NL-SAS HDDs, E208i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~420W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003cp\u003eLFF configurations draw meaningfully less peak power than SFF SSD configurations because spinning disks have lower steady-state power than enterprise SSDs at full load. 2 x 800W Platinum is the recommended PSU for production LFF deployments; the headroom over typical draw supports startup spin-up surge and accommodates fan ramp on high-temperature deployments.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen to Pick a Different Chassis\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSFF SAS SSD storage:\u003c\/strong\u003e The \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e or \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003e24-Bay 2.5\"\u003c\/a\u003e siblings are the right chassis for SAS SSD database storage, vSAN, and any workload bound by random IOPS or SSD-class latency.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVMe-bound workloads:\u003c\/strong\u003e Gen10 LFF chassis has no native NVMe path. For NVMe storage tiers, evaluate the DL380 Gen10 Plus with NVMe-capable backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN hybrid or all-flash:\u003c\/strong\u003e The 12-Bay LFF is not the right chassis for vSAN; the SFF siblings (16-Bay or 24-Bay 2.5\") are the vSAN platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHigher per-node bay count:\u003c\/strong\u003e When 12 LFF bays is not enough, the optional mid-plane (up to 16 LFF) and rear-drive cage (up to 19 LFF + 2 SFF) configurations are available on flagship 12-Bay variants. Verify configuration at quote time.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e1U dense compute:\u003c\/strong\u003e The DL360 Gen10 1U pair-partner with 4 LFF bays is denser per rack U for workloads where 12 bays per node is excess.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eProduction greenfield past 2028:\u003c\/strong\u003e For long-horizon deployments, the DL380 Gen10 Plus 12-Bay LFF or Gen11 12-Bay LFF brings PCIe Gen4 \/ Gen5 and current-gen processor support.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 12-Bay 3.5\" LFF is the right HPE platform for bulk-capacity storage workloads where cost-per-TB drives the design: large-scale NAS, backup repository infrastructure, Ceph capacity-tier OSD nodes, object storage, and archive. The platform's PCIe Gen3 limitation is largely irrelevant for spinning disk bulk storage workloads (the binding constraint is drive bandwidth, not interconnect bandwidth). The DDR4-2933 memory ceiling and Cascade Lake CPU envelope are similarly well-matched to bulk storage workloads where compute and memory are sized to the workload, not the platform ceiling.\u003c\/p\u003e\u003cp\u003eFor HPE-standardized shops, the 12-Bay LFF is the natural fit for storage capacity workloads at refurbished-market economics. The Dell PowerEdge R740xd 12-Bay 3.5\" is the cross-vendor tier-equivalent; choice between platforms is typically driven by which vendor the shop is standardized on, not by capability deltas.\u003c\/p\u003e\u003cp\u003eBottom line: For bulk capacity storage on the Gen10 platform, the 12-Bay 3.5\" LFF delivers proven enterprise reliability at meaningfully lower acquisition cost than current-generation alternatives. We deploy it most often as Veeam backup repository nodes, departmental NAS infrastructure, Ceph capacity-tier OSDs, and object storage building blocks.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eExcels at ✅\u003c\/th\u003e\n\u003cth\u003eWhere to look elsewhere ❌\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLarge-scale NAS \/ file serving (up to 240 TB raw)\u003c\/td\u003e\n\u003ctd\u003eRandom-IOPS-bound workloads (use SFF SSD siblings)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVeeam, Commvault, NetBackup repository nodes\u003c\/td\u003e\n\u003ctd\u003evSAN hybrid or all-flash (use 16-Bay or 24-Bay)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCeph capacity-tier OSD clusters\u003c\/td\u003e\n\u003ctd\u003eNVMe storage tiers (use DL380 Gen10+ with NVMe)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eObject storage (MinIO, Scality, Cloudian)\u003c\/td\u003e\n\u003ctd\u003eDatabase storage tiers (use SAS SSD on SFF chassis)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eArchive and tier-3 cold storage\u003c\/td\u003e\n\u003ctd\u003eProduction greenfield past 2028 (consider Gen10+ \/ Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMixed SSD + NL-SAS tiered storage\u003c\/td\u003e\n\u003ctd\u003eMore than 16 LFF needed without flagship riser config\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure\u003c\/h2\u003e\u003cp\u003eTell us your capacity target, workload type (NAS, backup, Ceph, object), memory target, networking requirements, and unit quantity. We respond within 24 hours. Volume pricing applies at 5 units and above. Every Wholesale Servers DL380 Gen10 12-Bay LFF ships after a 12+ hour burn-in test covering every PCIe slot, every memory channel, and every drive bay. Standard 180-day warranty included; 1-Year, 2-Year, and 3-Year Premium warranty options available. Call 1-800-778-1545 or use the quote form on this page.\u003c\/p\u003e\u003cp\u003eIf your deployment has a 3+ year production horizon, we will also quote the DL380 Gen11 or Gen10 Plus 12-Bay LFF for comparison on request.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241617607,"sku":"BP-013608","price":1326.73,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-g10-12-bay-35-drives-737679.png?v=1765539623"},{"product_id":"dl380-g10-2-5-16-bay-server","title":"HPE ProLiant DL380 Gen10 16-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 16-Bay 2.5\" is the canonical SFF configuration of HPE's 2U dual-socket flagship, the platform that anchored mid-decade enterprise infrastructure for HPE shops the way the Dell R740 did for Dell shops. Sixteen 2.5\" hot-swap SAS\/SATA bays on the full Purley dual-socket platform with up to 24 DDR4 RDIMM\/LRDIMM slots, dual 1st or 2nd Generation Intel Xeon Scalable processors (Skylake-SP \/ Cascade Lake-SP, LGA 3647), HPE iLO 5 management with Silicon Root of Trust, and HPE Smart Array Gen10 RAID. This page anchors the canonical DL380 Gen10 platform-fact documentation at Wholesale Servers; the 24-Bay 2.5\" and 12-Bay 3.5\" LFF sibling pages reference this page for shared platform vocabulary.\u003c\/p\u003e\u003cp\u003eThe DL380 Gen10 is the HPE-shop equivalent of the Dell R740 in tier and target workloads: 2U, dual-socket, broad chassis flexibility (LFF and multiple SFF densities), strong I\/O envelope, iLO 5 management. The Gen10 was widely deployed across mid-tier enterprise from 2017 through 2022 as the VMware standard, the database tier workhorse, and the vSAN hybrid cluster node of choice. In 2026, the Gen10 platform is widely deployed with excellent parts availability and deep institutional operating knowledge. For dev\/test infrastructure, expanding existing Gen10 estates, vSAN OSA clusters on vSphere 6.x or 7.x, lab environments, and budget-conscious production where current-gen Sapphire\/Emerald Rapids genuinely is not required, the DL380 Gen10 16-Bay is the cost-correct call.\u003c\/p\u003e\u003cp\u003eThe 16-Bay 2.5\" is the canonical DL380 Gen10 chassis at Wholesale Servers because it is the storage-flexibility anchor of the family: enough bays for vSAN hybrid OSA with proper cache-to-capacity ratios, enough bays for all-SSD database storage tiers, enough bays for mixed SSD\/HDD tiered storage, and small enough to remain economical per-node for scale-out cluster designs. The 24-Bay 2.5\" sibling adds bay count for vSAN all-flash multi-disk-group architectures and Ceph OSD nodes; the 12-Bay 3.5\" LFF sibling shifts the storage profile to bulk capacity for NAS, backup, and object storage. We deploy the 16-Bay 2.5\" most often as VMware vSAN hybrid nodes, SQL Server and PostgreSQL database tiers with SSD storage, virtualization hosts with substantial local storage, and converged infrastructure workloads where the storage-to-compute ratio fits within 16 SFF bays.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 uses Intel's Purley platform with the LGA 3647 socket and supports both 1st Generation Xeon Scalable (Skylake-SP, 14 nm, 2017) and 2nd Generation Xeon Scalable (Cascade Lake-SP, 14 nm refresh, 2019). Both generations are drop-in compatible in the same socket; a Gen10 originally shipped with Skylake silicon can be upgraded to Cascade Lake without a motherboard swap. The 2nd gen Cascade Lake is the typical refurbished-market silicon today and is what we usually recommend.\u003c\/p\u003e\u003cp\u003eCPU ceiling on Cascade Lake reaches 28 cores per socket on the Xeon Platinum 8280 (205W TDP). The mainstream-deployed envelope is 16 to 24 cores per socket on Gold 6230, 6240, 6248, 6252 SKUs. Memory speed depends on processor SKU: Gold 6200 and 5222 reach DDR4-2933 at 1 DPC; remaining Gold 5200 series, Gold 6100, Gold 5100, and Silver 4100 series cap at DDR4-2666. AVX-512 is supported across the Xeon Scalable line; 6200-series and the 5222 support 2x 512-bit FMA units, while 5200-series (other than 5222), 5100, 6100, and Silver SKUs support 1x 512-bit FMA. This affects HPC-style FP-heavy throughput; for typical virtualization and database workloads, it is rarely the deciding factor.\u003c\/p\u003e\u003cp\u003eOur default recommendation for general-purpose virtualization is 2x Gold 6242 (16C \/ 32T at 2.8 GHz, 150W TDP, 22 MB cache) or 2x Gold 6248 (20C \/ 40T at 2.5 GHz, 150W TDP, 27.5 MB cache). For higher-density VDI or container workloads, 2x Gold 6230 (20C \/ 40T at 2.1 GHz) balances core count with thermal envelope. For SQL Server licensed by core, fewer faster cores work best: 2x Gold 6244 (8C \/ 16T at 3.6 GHz) or 2x Gold 6246 (12C \/ 24T at 3.3 GHz) deliver clock speed at lower license counts.\u003c\/p\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots, twelve per CPU, six channels per CPU at 2 DPC. Mainstream maximum is 1.5 TB dual-socket with 64 GB RDIMMs (24 x 64 GB). Higher capacity is achievable with LRDIMMs: 128 GB LRDIMM x 24 = 3 TB dual-socket. NVDIMM-N is supported on the DL380 Gen10 but is restricted to 1st Generation Xeon Scalable (Skylake) only; if your workload needs NVDIMM-N, verify the CPU SKU. Intel Optane Persistent Memory 100-series (Apache Pass) is supported with Cascade Lake (2nd Gen Xeon Scalable) on M-suffix CPU SKUs (e.g., Gold 6240M, 6242M, 8260M); these are required for the high per-socket memory ceilings (4.5 TB per socket with L-series, 2 TB per socket with M-series).\u003c\/p\u003e\u003cp\u003eHPE memory rules: DIMMs must be installed in even quantities for balanced operation. Mixing of RDIMM and LRDIMM is not supported in the same configuration. HPE DDR4 Smart Memory is required to achieve rated speeds; third-party DIMMs will operate at reduced speed even if compatible. We populate memory in matched sets of 12 (one per channel per CPU, balanced across both sockets) for production deployments. Asymmetric configurations work for limited-budget builds but trade off bandwidth.\u003c\/p\u003e\u003cp\u003eFor VMware vSAN hybrid nodes, 256 GB to 512 GB per node is the practical range; vSAN 7.x with 16 SFF bays at 4-6 disk groups uses memory aggressively for caching and metadata. For database workloads, plan for 75-90% of working set in memory plus headroom; SQL Server and PostgreSQL benefit significantly from large buffer pools.\u003c\/p\u003e\u003ch2\u003eStorage\u003c\/h2\u003e\u003cp\u003eThe 16-Bay 2.5\" SFF configuration provides sixteen front-mounted 2.5\" hot-swap bays accepting SAS, SATA, and (with the Universal Media Bay option and Premium SFF backplane) up to 2 NVMe drives via the optional bays. Native NVMe in the 16-Bay configuration is limited compared to Gen10+ or 11; for substantial NVMe storage, the platform of record is HPE ProLiant DL380 Gen10 Plus or DL380 Gen11 with the appropriate NVMe backplane.\u003c\/p\u003e\u003cp\u003eCommon 16-Bay storage configurations we deploy:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVMware vSAN hybrid OSA (vSphere 6.x \/ 7.x):\u003c\/strong\u003e 2 to 4 SAS SSDs (1.6 TB to 3.84 TB write-intensive) for cache tier, 12 to 14 NL-SAS HDDs (4 TB to 16 TB) for capacity tier. The classic Gen10 vSAN hybrid deployment, fully supported on vSphere 7.x, proven to scale across hundreds of hybrid OSA clusters. vSAN 8.x ESA is NOT supported on Gen10; for ESA you need Gen10+ or Gen11.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAll-SAS SSD performance storage:\u003c\/strong\u003e 16 x SAS SSDs at RAID 10 yields 8 drives of usable capacity with strong write performance and predictable rebuild times. The typical fit is SQL Server, Oracle, PostgreSQL, MySQL, and other relational database storage tiers where NVMe latency is not the binding constraint and SAS endurance and dual-port redundancy matter.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed SSD + HDD tiered storage:\u003c\/strong\u003e 4 to 6 SAS SSDs for hot data alongside 10 to 12 NL-SAS HDDs for bulk; cost-effective tiering for general file serving, application data, and modest databases.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN all-flash OSA (smaller clusters):\u003c\/strong\u003e 4 SAS SSD cache + 12 SAS SSD capacity. For larger vSAN all-flash with multiple disk groups per node, the 24-Bay 2.5\" sibling provides better cluster economics.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot configuration: HPE M.2 boot via the optional M.2 enablement kit installs 1 or 2 M.2 SATA SSDs in a dedicated bay outside the 16 data bays. We strongly recommend M.2 boot rather than consuming a data bay for OS. The HPE NS204i-p (Gen10+) NVMe boot device is not native to Gen10 (it's a Gen10+ option); on Gen10 the SATA M.2 enablement kit is the boot path of record.\u003c\/p\u003e\u003ch2\u003eSmart Array Controllers (HPE RAID)\u003c\/h2\u003e\u003cp\u003eHPE's Gen10 Smart Array lineup replaces the Dell PERC analogy: same role, different naming. The relevant controllers for DL380 Gen10 16-Bay are:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB FBWC):\u003c\/strong\u003e Flexible Smart Array slot, dual-controller, supports all 16 internal SFF bays plus external SAS expansion. The default recommendation for hardware-RAID production workloads with substantial write activity. Flash-backed write cache survives power loss. FBWC battery is a wear item; check status on used inventory.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a (2 GB FBWC):\u003c\/strong\u003e Lower-cache version of the P816i-a, internal-only. Adequate for many production workloads without the cost of the 4 GB cache.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a (HBA mode):\u003c\/strong\u003e 8-port HBA, no on-controller RAID. Required for vSAN OSA, Ceph, ZFS pass-through, and any software-defined storage stack that requires direct disk visibility. The HPE equivalent of Dell's HBA330.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array S100i (software RAID):\u003c\/strong\u003e SATA-only software RAID via Intel VROC-equivalent. Acceptable for boot drives in M.2 slots; we do not deploy it on production data arrays.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eOur default for production virtualization with hardware RAID is the P816i-a; the FBWC and 4 GB cache pay off on mixed workloads. For vSAN OSA the E208i-a is mandatory; vSAN requires direct disk access. For Ceph and ZFS the E208i-a is similarly the right choice.\u003c\/p\u003e\u003ch2\u003eNetworking\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 ships with an embedded 4 x 1 GbE NIC on most BTO configurations (HPE 331i \/ Broadcom BCM5719). Higher-performance networking is delivered via the HPE FlexibleLOM slot, which accepts a wide range of LOM adapters: 4 x 1 GbE, 2 x 10 GbE BASE-T, 2 x 10 GbE SFP+, 2 x 25 GbE SFP28, and 2 x 100 GbE on appropriate FlexibleLOM cards. The FlexibleLOM does NOT consume a PCIe slot; it occupies a dedicated mezzanine slot on the riser. This is the HPE equivalent of Dell's rNDC and serves the same purpose: dense networking without sacrificing PCIe expansion.\u003c\/p\u003e\u003cp\u003eFor 10 GbE deployments, the typical FlexibleLOM is the HPE 562FLR-SFP+ (Intel X710, 2 x 10 GbE SFP+) or 562FLR-T (Intel X550, 2 x 10 GbE BASE-T). For 25 GbE the 631FLR-SFP28 (Mellanox ConnectX-4 LX) is standard. For VMware deployments, verify driver support against the FlexibleLOM you order; older Mellanox FlexibleLOMs have specific ESXi support matrices.\u003c\/p\u003e\u003cp\u003eFor dense networking beyond the FlexibleLOM, add-in PCIe NICs occupy the PCIe slots described below. 4 x 10 GbE on a single FlexibleLOM is achievable; for 4 x 25 GbE plan for a FlexibleLOM plus a single PCIe NIC.\u003c\/p\u003e\u003ch2\u003ePCIe Expansion\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 supports up to 8 PCIe Gen3 slots distributed across three risers. Standard riser is the Primary Riser (slots 1-3); optional Secondary Riser (slots 4-6) requires a second CPU; optional Tertiary Riser (slots 7-8) can also be configured. Slot widths depend on the riser SKU chosen: HPE offers multiple riser SKUs from the standard x8 \/ x16 \/ x8 to the GPU-capable x16 \/ x16 \/ x16 configurations.\u003c\/p\u003e\u003cp\u003ePCIe Gen3 is a meaningful limitation versus Gen10+ (PCIe Gen4) and Gen11 (PCIe Gen5). For NVMe SSDs operating at Gen4 link speeds, Gen3 caps the link to half-bandwidth; for 100 GbE NICs, Gen3 x8 is at the bandwidth ceiling. For most virtualization, database, and general-purpose workloads, PCIe Gen3 remains adequate; for AI inference with high-bandwidth GPUs or Gen4 NVMe-bound storage, this is where Gen10 hits its ceiling.\u003c\/p\u003e\u003cp\u003eGPU support: the DL380 Gen10 with the x16 \/ x16 \/ x16 Primary and Secondary risers (HPE P14374-B21 and P14373-B21) supports up to 7 NVIDIA T4 16 GB single-width 70W GPUs, or 6 T4s balanced across both processors. Double-width GPUs are limited to 3 cards per platform on appropriate riser configurations; the platform supports up to 3 x 300W double-width accelerators (V100, RTX 6000, A30, A40) in flagship riser SKUs. The Gen10's GPU envelope is genuinely strong for a 2U rack; the limit is PCIe Gen3 bandwidth more than power or physical slots.\u003c\/p\u003e\u003ch2\u003ePower Supplies\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies, hot-plug, redundant. Wattage options span 500W to 1600W in 94% Platinum and Titanium efficiency tiers. Dual PSU is standard for production deployments.\u003c\/p\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eConfiguration\u003c\/th\u003e\n\u003cth\u003ePSU Recommendation\u003c\/th\u003e\n\u003cth\u003eEst. Peak Draw\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLight (2x Silver 4214, 128 GB, 4 SAS SSDs, P408i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 500W Platinum (hot-plug redundant)\u003c\/td\u003e\n\u003ctd\u003e~280W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBalanced (2x Gold 6242, 384 GB, 12 SAS SSDs + 4 NL-SAS, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~480W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eHeavy (2x Gold 6248, 768 GB, 16 SAS SSDs vSAN AF, P816i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 1000W Platinum\u003c\/td\u003e\n\u003ctd\u003e~640W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMaximum (2x Platinum 8280, 1.5 TB, 16 SAS SSDs, 3 x V100 GPUs)\u003c\/td\u003e\n\u003ctd\u003e2 x 1600W Titanium\u003c\/td\u003e\n\u003ctd\u003e~1450W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003cp\u003eFor most 16-Bay 2.5\" deployments without GPUs, 2 x 800W Platinum is the recommended PSU. GPU configurations require 2 x 1600W Titanium. Single-PSU configurations are technically supported but we do not deploy single-PSU in production.\u003c\/p\u003e\u003ch2\u003eManagement and Security: iLO 5\u003c\/h2\u003e\u003cp\u003eHPE iLO 5 is the integrated remote management controller on Gen10, the HPE counterpart to Dell iDRAC9. iLO 5 brought a major security upgrade over iLO 4: Silicon Root of Trust validates firmware integrity at the hardware level during boot, preventing firmware-level attacks via a hardware-anchored chain of trust. This is a meaningful security feature for production environments; it is the HPE equivalent of Dell's iDRAC9 System Lockdown \/ Silicon-Based Security on 14th gen.\u003c\/p\u003e\u003cp\u003eiLO 5 supports HTML5 remote console (no Java required), Redfish REST API, IPMI 2.0, virtual media via web upload, remote KVM, full server power and thermal telemetry, and integration with HPE OneView for fleet management. Standard iLO 5 includes remote console and basic management; iLO Advanced license unlocks virtual media via integrated remote console, directory services integration, and several enterprise features. Most refurbished Gen10 units arrive with iLO Standard; we can include iLO Advanced licenses on request at quote.\u003c\/p\u003e\u003cp\u003eFor VMware shops, iLO 5 integrates cleanly with vCenter Server via HPE OneView for vCenter. For broad fleet management, HPE OneView 5.x or 6.x is the management plane; OneView 8.x and InfoSight integration are also available.\u003c\/p\u003e\u003ch2\u003ePhysical Specs and Platform Notes\u003c\/h2\u003e\u003cp\u003e2U rack, approximately 27.83\" deep (708 mm). Weight 73.6 lbs (33.4 kg) at typical fully-loaded configuration. Standard EIA 19\" rack mount via HPE Easy Install rail kit (679368-001 \/ 728437-001 for SFF, 679365-001 \/ 737412-001 for variant configurations). Rail kits are not included with bare server purchase; verify at quote time.\u003c\/p\u003e\u003cp\u003eChassis is welded and not field-convertible between LFF and SFF; the 16-Bay 2.5\" backplane is fixed at the chassis level. To convert between bay counts or form factors, the chassis itself must be replaced (a separate chassis SKU).\u003c\/p\u003e\u003cp\u003eCooling: six hot-plug fans in the standard configuration; high-temperature fans optional for sustained 35°C ambient deployments. Acoustic envelope is typical 2U rack server, not designed for office use.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 16-Bay 2.5\" is HPE's mid-decade 2U workhorse and remains a workhorse: widely deployed, well-understood, with mature firmware and broad parts availability. For HPE-standardized shops running VMware vSphere 7.x with vSAN hybrid OSA, the DL380 Gen10 16-Bay is the cost-correct platform when current-generation is genuinely not required. For database tiers with all-SAS SSD storage where NVMe latency is not the binding constraint, this platform delivers strong performance at meaningfully lower acquisition cost than Gen10+ or Gen11.\u003c\/p\u003e\u003cp\u003eWhere the platform falls short: vSAN 8.x ESA is not supported (no native NVMe backplane on 16-Bay; ESA requires Gen10+ or Gen11 with NVMe). PCIe Gen3 limits NVMe and high-speed networking ceilings. The platform's CPU support tops out at Cascade Lake (28 cores per socket maximum); modern Sapphire Rapids and Emerald Rapids workloads with high core counts and DDR5 bandwidth needs are outside the platform's envelope. HPE official support is winding down for Gen10; OneView and InfoSight continue, but HPE TAC engagement for Gen10-specific issues has narrowing horizons.\u003c\/p\u003e\u003cp\u003evs DL360 Gen10 1U pair-partner: the DL360 is the 1U sibling with the same processor lineup, memory architecture, iLO 5, and Smart Array compatibility. The choice is form factor and storage profile: DL360 Gen10 8-Bay or 10-Bay 2.5\" for dense 1U deployments where storage requirements stay below 10 bays; DL380 Gen10 16-Bay where the storage-to-compute ratio needs the larger chassis.\u003c\/p\u003e\u003cp\u003evs DL380 Gen10+ (Plus): the Gen10+ moves to 3rd Gen Xeon Scalable (Ice Lake, LGA 4189), PCIe Gen4, DDR4-3200, and native NVMe backplane options. For greenfield deployments running production beyond 2028, or for vSAN ESA, the Gen10+ is the right platform. For existing Gen10 estates or shorter lifecycle builds, the Gen10 economics are compelling.\u003c\/p\u003e\u003cp\u003evs Dell PowerEdge R740 16-Bay 2.5\" (Dell tier-equivalent): same architectural tier, same Skylake\/Cascade Lake processor generation, same DDR4 generation. The Dell R740 has 24 DIMM slots versus Gen10's 24 DIMM slots (parity), Dell PERC vs HPE Smart Array (parity in function, different naming), iDRAC9 vs iLO 5 (parity in capability). The choice between R740 and DL380 Gen10 is typically driven by which vendor the shop is standardized on, not by capability deltas.\u003c\/p\u003e\u003cp\u003eBottom line: For HPE-standardized environments where the workload fits the platform envelope, the DL380 Gen10 16-Bay 2.5\" delivers proven enterprise capability at refurbished-market economics. We deploy it most often as VMware vSAN hybrid OSA nodes, SQL Server database tiers with SAS SSD storage, and general-purpose 2U virtualization hosts where the 16-bay storage profile fits.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eExcels at ✅\u003c\/th\u003e\n\u003cth\u003eWhere to look elsewhere ❌\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVMware vSAN hybrid OSA on vSphere 6.x \/ 7.x\u003c\/td\u003e\n\u003ctd\u003evSAN 8.x ESA (use DL380 Gen10+ or Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSQL Server, Oracle, PostgreSQL with SAS SSD storage\u003c\/td\u003e\n\u003ctd\u003eNVMe-latency-bound databases (use DL380 Gen10+)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGeneral-purpose 2U virtualization for HPE shops\u003c\/td\u003e\n\u003ctd\u003eWorkloads requiring DDR5 or Sapphire Rapids cores\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMixed SSD + HDD tiered storage in 16 SFF bays\u003c\/td\u003e\n\u003ctd\u003eMore than 16 SFF bays needed (use 24-Bay sibling)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGPU inference with up to 6 NVIDIA T4 cards\u003c\/td\u003e\n\u003ctd\u003eLFF bulk capacity workloads (use 12-Bay LFF sibling)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDev\/test, lab, training infrastructure at low cost\u003c\/td\u003e\n\u003ctd\u003eProduction workloads running beyond 2028 (consider Gen10+ or Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eExpansion of existing Gen10 estates\u003c\/td\u003e\n\u003ctd\u003evSAN with all-NVMe disk groups (use Gen10+ with NVMe backplane)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe Gen3 only.\u003c\/strong\u003e 48 lanes per CPU at Gen3 speeds. Gen4 NVMe SSDs operate at half-link bandwidth; 100 GbE NICs at x8 are at the Gen3 ceiling. For Gen4-bound workloads, Gen10+ is the platform of record.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNo native NVMe backplane on 16-Bay.\u003c\/strong\u003e NVMe in Gen10 16-Bay is via Universal Media Bay (up to 2 NVMe bays) or PCIe AIC; not native 16-bay NVMe. For substantial NVMe storage, the platform is Gen10+ or Gen11 with appropriate backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN 8.x ESA not supported.\u003c\/strong\u003e vSAN OSA on vSphere 7.x is fully supported. ESA requires NVMe storage and is platform-restricted to Gen10+ or newer with NVMe backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDDR4 generation, 2933 MT\/s ceiling.\u003c\/strong\u003e Gold 6200-series and 5222 reach 2933 at 1 DPC; the rest of the lineup caps at 2666. Modern bandwidth-heavy workloads benefit from DDR5; for those, Gen11 is the platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCPU ceiling at Cascade Lake 28 cores per socket.\u003c\/strong\u003e Workloads benefiting from 32, 40, 48, or 64 cores per socket (Ice Lake, Sapphire Rapids, Emerald Rapids) are outside the platform's envelope.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVDIMM-N restricted to Skylake (1st gen Xeon Scalable).\u003c\/strong\u003e Cascade Lake CPUs require Optane PMem 100-series (Apache Pass) on M-suffix SKUs for persistent memory; NVDIMM-N is a Skylake-only path.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed RDIMM\/LRDIMM not supported.\u003c\/strong\u003e The platform requires homogeneous DIMM technology; mixing in the same configuration is unsupported.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHPE official support narrowing.\u003c\/strong\u003e Gen10 OneView and InfoSight integration continues, but HPE TAC engagement for Gen10-specific issues has decreasing horizons. Critical production workloads on multi-year horizons should evaluate the upgrade path.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eiLO Advanced license typically not included.\u003c\/strong\u003e Most refurbished Gen10 ship with iLO Standard. iLO Advanced (for integrated remote console virtual media, directory services, and several enterprise features) is licensed separately. We can include iLO Advanced licenses at quote.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFBWC battery is a wear item.\u003c\/strong\u003e Smart Array P816i-a and P408i-a use flash-backed write cache with a capacitor pack. The capacitor is a wear item with a service life of approximately 5 years; refurbished units may have aged capacitors. We test FBWC health during burn-in and replace when out of spec.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWelded chassis.\u003c\/strong\u003e Bay configuration is fixed at the chassis level. Converting between 8-bay, 16-bay, 24-bay SFF, or 12-bay LFF requires chassis replacement, not field reconfiguration.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHPE-only parts and firmware.\u003c\/strong\u003e Gen10 firmware updates require HPE Service Pack for ProLiant (SPP) and an active HPE account in most cases. Third-party drives and DIMMs may operate at reduced speed or with warning indicators in iLO 5.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eGeneration Context\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen9 is the immediate predecessor: same 2U tier on the Intel Grantley platform (E5-2600 v3 Haswell \/ v4 Broadwell), DDR4-2400, iLO 4. The Gen9 is meaningfully older and operates at lower memory bandwidth, PCIe Gen3 (same as Gen10), and lacks Silicon Root of Trust. For workloads sized to Gen9 cost economics, the DL380 Gen9 16-Bay or 24-Bay variants at Wholesale Servers are options; the Gen10 brings Skylake\/Cascade Lake compute, iLO 5 security, and broader OS support.\u003c\/p\u003e\u003cp\u003eThe DL380 Gen10 Plus is the successor: same 2U chassis form factor, but new motherboard architecture with the LGA 4189 socket for 3rd Generation Xeon Scalable (Ice Lake, 10 nm). The Gen10 Plus brings PCIe Gen4, DDR4-3200, native NVMe backplane options, and the Silicon Root of Trust security model carried forward. For greenfield production with extended lifecycle, the Gen10 Plus is typically the right call. For cost-primary deployments fitting the Gen10 envelope, the Gen10 saves meaningful acquisition cost.\u003c\/p\u003e\u003cp\u003eThe DL380 Gen11 is the current-generation: 4th Gen Sapphire Rapids and 5th Gen Emerald Rapids Xeon Scalable, DDR5, PCIe Gen5, iLO 6, completely new platform. For workloads requiring current-gen capability (DDR5 bandwidth, CXL, PCIe Gen5 NVMe, very high core counts), the Gen11 is the platform of record.\u003c\/p\u003e\u003cp\u003eCross-family pair-partner (1U sibling): The HPE ProLiant DL360 Gen10 is the 1U platform pair-partner, same processor lineup, same memory architecture, same iLO 5 and Smart Array compatibility, in the denser 1U form factor with fewer drive bays (4 LFF, 8 SFF, or 10 SFF). For dense rack deployments where 16 SFF bays per node is excess, the DL360 Gen10 is the right call.\u003c\/p\u003e\u003cp\u003eCross-vendor tier-equivalent: Dell PowerEdge R740 is the architectural counterpart in the Dell catalog: same Purley platform, same processor support, same DDR4 generation, same tier positioning. Choice between R740 and DL380 Gen10 is typically driven by vendor standardization. Both are available at Wholesale Servers; if your shop is mixed-vendor, we can quote both for comparison.\u003c\/p\u003e\u003cp\u003eFamily siblings (DL380 Gen10):\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e24-Bay 2.5\" SFF:\u003c\/strong\u003e Higher-density SFF for vSAN all-flash multi-disk-group nodes, Ceph OSD clusters, and large SAS SSD storage tiers where 24 bays per node improves cluster economics.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e12-Bay 3.5\" LFF:\u003c\/strong\u003e Bulk capacity for NAS, backup, archive, and object storage. Up to 240 TB raw with 20 TB NL-SAS drives.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eRequest a Quote\u003c\/h2\u003e\u003cp\u003eTell us your workload, vSAN or storage design (if applicable), drive type and quantity, memory target, networking requirements, and unit quantity. We respond within 24 hours. Volume pricing applies at 5 units and above. Every Wholesale Servers DL380 Gen10 ships after a 12+ hour burn-in test covering every PCIe slot, every memory channel, and every drive bay. Standard 180-day warranty included; 1-Year, 2-Year, and 3-Year Premium warranty options available. Call 1-800-778-1545 or use the quote form on this page.\u003c\/p\u003e\u003cp\u003eIf your deployment has a 3+ year production horizon, we will also quote the DL380 Gen11 or Gen10 Plus for comparison on request.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241650375,"sku":"BP-013609","price":804.68,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-16-bay-25-drives-874519.png?v=1765539623"},{"product_id":"hpe-dl380-g10-2-5-24-bay-chassis","title":"HPE ProLiant DL380 Gen10 24-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 24-Bay 2.5\" is the maximum SFF density configuration of HPE's 2U dual-socket Gen10 platform: twenty-four 2.5\" SAS\/SATA hot-swap bays on the same Purley dual-socket motherboard, same memory architecture, same iLO 5 management, and same Smart Array RAID family as the 16-Bay canonical. This page covers the 24-Bay storage architecture and when this chassis is the right call versus the 16-Bay 2.5\" canonical or the 12-Bay 3.5\" LFF sibling.\u003c\/p\u003e\u003cp\u003eFor the full platform-fact story (processors, memory architecture, FlexibleLOM networking, PCIe expansion, iLO 5 management, Smart Array controllers, power supplies, physical specs), see the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\" canonical page\u003c\/a\u003e. Everything documented there applies to this 24-Bay variant; this page focuses on what's different about the 24-bay chassis and the storage-design implications that follow from the higher bay count.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhat's Different About This Chassis\u003c\/h2\u003e\u003cp\u003eThe 24-Bay 2.5\" is the storage-flagship variant of the DL380 Gen10 family. Three things define it relative to the 16-Bay canonical:\u003c\/p\u003e\u003col\u003e\n\u003cli\u003e\n\u003cstrong\u003eEight additional SFF bays.\u003c\/strong\u003e Twenty-four front-mounted 2.5\" hot-swap bays versus sixteen on the canonical, with no change to the memory, processor, or PCIe envelope. The chassis is the same external dimensions; the additional bays come from the dense backplane configuration (Box 1, Box 2, and Box 3 each populated with 8 SFF bays).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCluster-economics workloads.\u003c\/strong\u003e The 24-bay configuration is sized for vSAN all-flash with multiple disk groups per node, Ceph OSD nodes where per-node OSD count drives cluster economics, and SAS SSD database tiers requiring substantial local storage. These workloads benefit from the additional bays in ways that 16-bay configurations cannot accommodate.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSame Gen10 platform ceilings.\u003c\/strong\u003e The 24-Bay does not unlock additional capability beyond storage: same PCIe Gen3, same DDR4-2933 ceiling, same Cascade Lake processor lineup, same iLO 5, same Smart Array P816i-a \/ P408i-a \/ E208i-a options. Workloads that need PCIe Gen4, DDR4-3200, or Ice Lake compute should evaluate the DL380 Gen10 Plus, not the 24-Bay Gen10.\u003c\/li\u003e\n\u003c\/ol\u003e\u003chr\u003e\u003ch2\u003eStorage Architecture\u003c\/h2\u003e\u003cp\u003eTwenty-four 2.5\" SAS\/SATA hot-swap bays in three Box configurations (Box 1, Box 2, Box 3 at 8 bays each). The Smart Array P816i-a (4 GB FBWC) is the natural RAID controller for hardware-RAID configurations across all 24 bays; the E208i-a HBA is the natural controller for vSAN OSA, Ceph, and ZFS deployments requiring direct disk access.\u003c\/p\u003e\u003cp\u003eCommon 24-Bay configurations we deploy:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVMware vSAN all-flash OSA with multiple disk groups (vSphere 6.x \/ 7.x):\u003c\/strong\u003e Up to 5 disk groups per node, each with 1 SSD cache + up to 4 SSD capacity drives. 24 bays supports 5 disk groups (5 cache + 19 capacity) or 4 disk groups (4 cache + 20 capacity). Multiple disk groups per node increases vSAN storage parallelism linearly; this is the canonical Gen10 vSAN all-flash node configuration. vSAN 8.x ESA is NOT supported on Gen10; for ESA the DL380 Gen10 Plus with NVMe backplane is the platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCeph OSD nodes (24 OSDs per node):\u003c\/strong\u003e With the E208i-a HBA in pass-through mode, each of the 24 bays becomes an independent OSD. The DL380 Gen10 24-Bay is widely deployed as Ceph OSD nodes in Red Hat Ceph Storage and SUSE Enterprise Storage clusters; the high OSD-per-node count and the secondary-market acquisition cost make compelling cluster economics. Plan memory at 6 GB per OSD plus 16 GB overhead (192 GB per node typical) and dedicated 25 GbE or 100 GbE cluster networking.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAll-SAS SSD database storage:\u003c\/strong\u003e 24 x SAS SSDs at RAID 10 yields 12 drives of usable capacity. With 3.84 TB SAS SSDs, that's 46 TB usable; with 7.68 TB, 92 TB usable. The typical fit is large SQL Server, Oracle, or PostgreSQL instances requiring substantial local SSD capacity with high endurance and dual-port redundancy.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eTiered SSD + HDD at 24-bay density:\u003c\/strong\u003e 6 to 8 SAS SSDs for hot tier (cache or storage tier) alongside 16 to 18 NL-SAS HDDs for bulk capacity. With 16 TB NL-SAS HDDs and 7.68 TB SAS SSDs, this yields substantial tiered storage in a single 2U chassis: roughly 60 TB SSD raw and 280 TB HDD raw for a combined 340 TB before RAID overhead.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eVeeam repository \/ backup target node:\u003c\/strong\u003e 24 NL-SAS HDDs at RAID 60 (two RAID 6 sets striped) provides high-capacity backup landing with two-drive fault tolerance per set. The Gen10's bandwidth envelope is well-matched to Veeam's typical backup throughput targets.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe 24-bay storage configuration is where the Gen10 platform's PCIe Gen3 limitation becomes meaningful: aggregated throughput from 24 high-performance SAS SSDs can saturate Gen3 lanes to the Smart Array controller in some workloads. For workloads where this is the binding constraint, the DL380 Gen10 Plus with PCIe Gen4 is the upgrade path.\u003c\/p\u003e\u003ch2\u003eRAID and Controller Guidance\u003c\/h2\u003e\u003cp\u003eRAID strategy at 24-bay scale matters more than at 16-bay because rebuild times and parity-group fault tolerance scale with array size:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 6 mandatory for NL-SAS HDD arrays.\u003c\/strong\u003e Rebuild times on 16-20 TB NL-SAS drives at 24-bay density commonly exceed 36 hours; two-drive fault tolerance is non-negotiable. Never RAID 5 at this drive count and capacity.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 10 for SAS SSDs.\u003c\/strong\u003e Fast rebuild times, predictable write performance, fault tolerance per mirrored pair. Half the usable capacity, but the operational characteristics are correct for production database storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 60 for backup targets.\u003c\/strong\u003e Two RAID 6 sets striped: 12 + 12 across 24 drives. Survives two drive failures per set; rebuilds happen in parallel per set; aggregate throughput meets Veeam-class backup repository requirements.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB FBWC) is the production hardware-RAID default.\u003c\/strong\u003e The 4 GB write cache pays off at 24-bay scale where Smart Array battery-backed write reordering meaningfully improves random write performance. FBWC battery health is a wear item; we verify at burn-in.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a HBA mode for software-defined storage.\u003c\/strong\u003e vSAN, Ceph, and ZFS require direct disk access; the E208i-a is the supported HBA for these workloads on Gen10.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot configuration: HPE M.2 enablement kit installs 1 or 2 M.2 SATA SSDs outside the 24 data bays. We strongly recommend this rather than consuming a data bay for OS, especially at 24-bay configurations where every data bay contributes to cluster or capacity economics.\u003c\/p\u003e\u003ch2\u003eMemory Sizing for 24-Bay Workloads\u003c\/h2\u003e\u003cp\u003eThe 24-Bay platform's storage workloads typically require more memory than general-purpose 16-Bay configurations:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN all-flash, 5 disk groups per node:\u003c\/strong\u003e 384 GB to 768 GB per node. vSAN memory overhead grows with disk group count and capacity drive count; 5-disk-group nodes are at the high end of vSAN memory consumption.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCeph OSD nodes, 24 OSDs:\u003c\/strong\u003e 192 GB to 256 GB per node. Roughly 6 GB per OSD plus daemon overhead; some workloads benefit from 8 GB per OSD on BlueStore deployments with substantial capacity drives.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAll-SAS SSD database, 12-drive RAID 10:\u003c\/strong\u003e Memory sized to the workload, not the storage. SQL Server with 92 TB usable benefits from 768 GB to 1.5 TB depending on working-set size; PostgreSQL similar.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eVeeam repository node:\u003c\/strong\u003e 128 GB to 256 GB. Veeam repository memory scales with concurrent backup jobs and ReFS \/ XFS cache requirements; 128 GB is the practical minimum for serious repository nodes.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eHPE memory rules from the 16-Bay canonical apply identically: DIMMs in even quantities, no RDIMM\/LRDIMM mixing, HPE DDR4 Smart Memory required for rated speeds, matched sets of 12 for balanced production deployment.\u003c\/p\u003e\u003ch2\u003ePower Sizing for 24-Bay Workloads\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eConfiguration\u003c\/th\u003e\n\u003cth\u003ePSU Recommendation\u003c\/th\u003e\n\u003cth\u003eEst. Peak Draw\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBalanced (2x Gold 6242, 384 GB, 24 SAS SSDs, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum (hot-plug redundant)\u003c\/td\u003e\n\u003ctd\u003e~580W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eHeavy (2x Gold 6248, 768 GB, 24 SAS SSDs vSAN AF, P816i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 1000W Platinum\u003c\/td\u003e\n\u003ctd\u003e~740W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eStorage-heavy (2x Gold 6230, 256 GB, 24 NL-SAS HDDs RAID 60, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~520W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMaximum (2x Platinum 8280, 1 TB, 24 SAS SSDs, FlexibleLOM, 2 PCIe NICs)\u003c\/td\u003e\n\u003ctd\u003e2 x 1600W Titanium\u003c\/td\u003e\n\u003ctd\u003e~1100W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003cp\u003eFor typical 24-bay deployments, 2 x 1000W Platinum is the recommended PSU. Heavily-populated all-SSD configurations with 2 x 25 GbE networking can push toward 800W steady-state; 1000W gives headroom for transient peaks. Single-PSU configurations are not deployed in production at this storage density.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen to Pick a Different Chassis\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e16 SFF bays sufficient:\u003c\/strong\u003e The \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\" canonical\u003c\/a\u003e is meaningfully lower-cost per node and is the right call when storage requirements stay below 16 SFF bays. vSAN hybrid OSA with 1-2 disk groups, all-SSD database tiers with 8-12 drives, and general-purpose 2U virtualization fit comfortably in the 16-bay envelope.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF capacity drives needed:\u003c\/strong\u003e The \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\" LFF sibling\u003c\/a\u003e is the right chassis for bulk NAS, backup, archive, and object storage workloads where 7,200 RPM NL-SAS capacity drives at 16 TB to 20 TB each deliver the storage economics.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN 8.x ESA target:\u003c\/strong\u003e The DL380 Gen10 platform (any chassis) does not support vSAN ESA. For ESA, the DL380 Gen10 Plus or Gen11 with NVMe backplane is the platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVMe-bound workloads:\u003c\/strong\u003e The 24-Bay 2.5\" Gen10 SAS backplane does not support native NVMe across all 24 bays. For NVMe storage tiers, evaluate the DL380 Gen10 Plus 24-Bay NVMe configurations.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe Gen4 NICs or accelerators required:\u003c\/strong\u003e Gen10 is PCIe Gen3 only. 100 GbE NICs operate at the Gen3 x8 ceiling; AI accelerators expecting Gen4 bandwidth are bottlenecked. The DL380 Gen10 Plus is the upgrade.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e1U form factor:\u003c\/strong\u003e The DL360 Gen10 1U pair-partner is denser per rack U, with bay options up to 10 SFF. For dense 1U deployments where 24 bays per node is excessive, the DL360 Gen10 is the right form factor.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 24-Bay 2.5\" is the storage-density specialist of the Gen10 family. For HPE-standardized shops building vSAN all-flash OSA clusters with multiple disk groups per node, Ceph OSD clusters with high per-node OSD count, or large SAS SSD database tiers, the 24-Bay 2.5\" is the right chassis. The economics are particularly compelling for Ceph deployments and Veeam repository nodes where per-node storage density drives total infrastructure cost.\u003c\/p\u003e\u003cp\u003eThe Gen10 platform constraints (PCIe Gen3, no native NVMe backplane, vSAN OSA only, Cascade Lake CPU ceiling) apply identically to the 24-Bay as to the 16-Bay canonical; the 24-Bay does not unlock new platform capability beyond storage. For workloads where those constraints are binding, the DL380 Gen10 Plus or Gen11 is the platform of record.\u003c\/p\u003e\u003cp\u003eFor storage-density workloads on Gen10's PCIe Gen3 envelope, the 24-Bay delivers production-proven capability at meaningfully lower acquisition cost than current-generation alternatives. We deploy it most often as vSAN all-flash OSA nodes with 4-5 disk groups, Ceph OSD nodes at 24 OSDs per node, and Veeam backup repository nodes at high NL-SAS capacity.\u003c\/p\u003e\u003cp\u003eBottom line: When 16 SFF bays per node is not enough and you can accept the Gen10 platform envelope, the 24-Bay 2.5\" delivers the storage density at proven enterprise quality. When you can fit in 16 bays, the 16-Bay canonical is the cost-correct call.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eExcels at ✅\u003c\/th\u003e\n\u003cth\u003eWhere to look elsewhere ❌\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003evSAN all-flash OSA with multiple disk groups per node\u003c\/td\u003e\n\u003ctd\u003evSAN 8.x ESA (use DL380 Gen10+ with NVMe)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCeph OSD clusters at 24 OSDs per node\u003c\/td\u003e\n\u003ctd\u003e16 OSDs sufficient (16-Bay lower cost)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLarge SAS SSD database storage tiers\u003c\/td\u003e\n\u003ctd\u003eNVMe-bound database tiers (use DL380 Gen10+)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVeeam repository nodes with 24 NL-SAS HDDs\u003c\/td\u003e\n\u003ctd\u003eLFF capacity drives needed (use 12-Bay LFF)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eTiered SSD + HDD at high density in 2U\u003c\/td\u003e\n\u003ctd\u003eWorkloads bottlenecked on PCIe Gen3\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eExpansion of existing Gen10 vSAN estates\u003c\/td\u003e\n\u003ctd\u003eProduction greenfield with 3+ year horizon (consider Gen10+ or Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure\u003c\/h2\u003e\u003cp\u003eTell us your vSAN, Ceph, or backup design, drive type and quantity, memory target, networking requirements, and unit quantity. We respond within 24 hours. Volume pricing applies at 5 units and above. Every Wholesale Servers DL380 Gen10 24-Bay ships after a 12+ hour burn-in test covering every PCIe slot, every memory channel, and every one of the 24 drive bays. Standard 180-day warranty included; 1-Year, 2-Year, and 3-Year Premium warranty options available. Call 1-800-778-1545 or use the quote form on this page.\u003c\/p\u003e\u003cp\u003eIf your deployment has a 3+ year production horizon, we will also quote the DL380 Gen11 or Gen10 Plus 24-Bay for comparison on request.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241683143,"sku":"BP-013610","price":878.48,"currency_code":"USD","in_stock":false}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-g10-24-bay-25-drives-694439.png?v=1765539623"},{"product_id":"dl360-g10-chassis","title":"HPE ProLiant DL360 Gen10 8-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL360 Gen10 8-Bay 2.5\" is the mainstream 1U SFF configuration in the Gen10 lineup and the most-deployed DL360 variant across HPE customer sites. Eight 2.5\" SAS\/SATA hot-swap bays, dual-socket Intel Xeon Scalable (Skylake-SP or Cascade Lake-SP), 24 DDR4 DIMM slots, iLO 5 with Silicon Root of Trust, and the same Smart Array storage controller family as the rest of the Gen10 line. For virtualization hosts, application servers, scale-out compute nodes, and most workloads where 8 SFF bays cover the storage design, this is the standard 1U HPE pick - and almost always the right one over the 10-Bay variant.\u003c\/p\u003e\u003cp\u003eThis is the sibling page to the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\"\u003c\/a\u003e canonical. The full platform vocabulary - Purley socket support, memory architecture, controller comparisons, iLO 5 details, FlexibleLOM networking, GPU constraints, generational positioning - lives on that page and applies identically here. This page focuses on what's specific to the 8-Bay configuration: when it's the right pick, how the bay count maps to common workloads, and the cost-versus-flexibility tradeoff against the 10-Bay.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhy the 8-Bay Is the Right Default\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SFF bays in 1U is the configuration HPE built the DL360 around. The 10-Bay is a density variant for specific workloads where two extra bays measurably change the cluster math; the 8-Bay is the version that fits the bulk of real-world 1U deployments. If you're not running Ceph at scale, vSAN with two disk groups per host, or a distributed database that genuinely wants 10 drives per node, the 8-Bay covers your storage design with no compromise.\u003c\/p\u003e\u003cp\u003eThe cost difference is modest but real - the 10-Bay backplane and additional drive cage carry a premium, plus two more drives in your bill of materials if you're filling the bays. For a virtualization host running 4-6 SSDs for local datastore plus an M.2 boot device, the 8-Bay is the right answer. For an application server with 2-4 SSDs and primary data on SAN, the 8-Bay has surplus capacity. The 10-Bay earns its premium when the extra bays land in a specific cluster math problem; the 8-Bay wins everywhere else.\u003c\/p\u003e\u003cp\u003eBay-count map for common 8-Bay deployments:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003evSphere host with local SSD datastore:\u003c\/strong\u003e 2 drives RAID 1 for OS + 4-6 SSDs RAID 10 for datastore, 0-2 bays held back for spares. Comfortable fit.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHyper-V cluster node with CSV on iSCSI\/FC:\u003c\/strong\u003e 2 drives RAID 1 for OS + 4 SSDs for Hyper-V Replica or Cluster Shared Storage cache, remaining bays unused or M.2 boot frees all 8 bays for data. Plenty of room.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eKubernetes worker with local PV provisioning:\u003c\/strong\u003e M.2 boot + 4-8 SSDs for CSI-attached persistent volumes. Bays scale with the per-node PV workload.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN single-disk-group host:\u003c\/strong\u003e 1 cache SSD + 4-7 capacity drives is a single vSAN disk group, perfectly served by 8 bays. Two disk groups per host pushes you toward the 10-Bay, which is exactly why the 10-Bay exists.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eApplication server with local SSD storage:\u003c\/strong\u003e 2 drives RAID 1 OS + 2-4 SSDs for application\/log volumes. 8 bays is more than enough.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eVeeam proxy or distributed component:\u003c\/strong\u003e 2 drives RAID 1 + 2-4 SSDs for staging or cache. Typical proxy build fits cleanly in 8 bays.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eStorage and Controllers\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA hot-swap bays on the standard backplane. SAS SSDs, SATA SSDs, SAS HDDs at 10K and 15K, and NL-SAS SFF drives are all supported. Controller options are the full Smart Array Gen10 family covered on the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical page\u003c\/a\u003e: P408i-a SR (2 GB FBWC, mainstream production controller), P816i-a SR (4 GB FBWC, write-heavy or tri-mode requirements), E208i-a SR (HBA mode for vSAN, Ceph, S2D, ZFS), and S100i SR (software RAID, boot-only).\u003c\/p\u003e\u003cp\u003eFor 8-Bay deployments specifically, the P408i-a is the right controller in 90%+ of cases. Its 2 GB FBWC is sized appropriately for the I\/O patterns 8 SFF drives produce in a 1U chassis. The P816i-a's larger cache earns its place at higher drive counts (16+ bays in the DL380 platform) where cache pressure becomes a real bottleneck; in the 1U 8-Bay envelope, the P408i-a almost always covers the working set. The E208i-a HBA is the right pick for any software-defined storage workload, and S100i should only be used for OS boot mirroring when no Smart Array P-series is in the build.\u003c\/p\u003e\u003cp\u003eFBWC battery is a wear item with roughly 5-year service life - same caveat that applies to every P-series Smart Array, documented on the canonical page and disclosed on every build quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eBoot Drive Options\u003c\/h2\u003e\u003cp\u003eHPE M.2 enablement kit is the cleanest boot solution on the DL360 Gen10 8-Bay. It mounts in a PCIe slot, takes a SATA M.2 drive (typically 480 GB), and frees all 8 SFF bays for data. Strongly recommended when you're using all 8 bays for the workload's data tier.\u003c\/p\u003e\u003cp\u003eAlternative: 2x SFF SAS or SATA SSDs in two of the 8 bays under hardware RAID 1, consuming 2 bays for OS. This is the right approach when the M.2 kit isn't available or when you're not using all 8 bays for data and don't mind giving up two of them for OS mirroring. For a build with 4-6 data drives, the 2-bay OS mirror is perfectly reasonable.\u003c\/p\u003e\u003cp\u003eHPE NS204i-p (the dedicated dual-NVMe M.2 boot device) is a Gen10 Plus and Gen11 feature, not a Gen10 option. If you need NVMe boot specifically on Gen10, it's via the M.2 enablement kit (SATA M.2) or via a PCIe-attached NVMe drive routed to a specific bay - not via NS204i-p.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors, Memory, and Networking\u003c\/h2\u003e\u003cp\u003eSame as the canonical: dual-socket LGA 3647 Purley platform, 1st Gen and 2nd Gen Xeon Scalable drop-in compatible, 24 DDR4 DIMM slots, DDR4-2933 on Gold 6200\/5222 (DDR4-2666 on the rest), up to 1.5 TB RDIMM or 3 TB LRDIMM dual-socket, HPE Smart Memory required for rated speed operation. The full processor and memory documentation lives on the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical page\u003c\/a\u003e.\u003c\/p\u003e\u003cp\u003eNetworking: HPE FlexibleLOM mezzanine slot (does not consume PCIe) for the primary network interface, 3 PCIe Gen3 slots in the standard riser configuration for HBAs, additional NICs, or up to two single-width T4-class GPUs. The 1U PCIe constraint is the same as the 10-Bay; the bay-count difference doesn't change the PCIe layout.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eThe 8-Bay vs. 10-Bay Decision\u003c\/h2\u003e\u003cp\u003eThree questions decide it:\u003c\/p\u003e\u003col\u003e  \u003cli\u003e\n\u003cstrong\u003eDoes your storage design fit in 8 bays?\u003c\/strong\u003e If yes - and for most virtualization, application, and compute-primary deployments, yes - the 8-Bay is the right choice. The 10-Bay's premium isn't justified.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eAre you running vSAN with two disk groups per host, or Ceph at 10 OSDs per 1U?\u003c\/strong\u003e If yes, the 10-Bay's two extra bays land in a specific cluster math problem. Take the 10-Bay.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eIs the per-node data-drive count in your design 9 or 10?\u003c\/strong\u003e This usually means a distributed database or storage workload with explicit 1U density requirements. Take the 10-Bay.\u003c\/li\u003e\n\u003c\/ol\u003e\u003cp\u003eIf the answer to all three is no, the 8-Bay is the cleaner pick. Same processors, same memory, same management, same controllers - just two fewer bays and a slightly lower price.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Standard 1U virtualization hosts (vSphere, Hyper-V, KVM)\u003c\/td\u003e    \u003ctd\u003e❌ vSAN 2-disk-group hosts (use 10-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Application servers with local SSD datastores\u003c\/td\u003e    \u003ctd\u003e❌ Ceph at 10 OSDs per 1U (use 10-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Kubernetes worker pools with M.2 boot + 4-8 PVs\u003c\/td\u003e    \u003ctd\u003e❌ LFF drive requirements in 1U (use 4-Bay 3.5\")\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Scale-out compute clusters in HPE shops\u003c\/td\u003e    \u003ctd\u003e❌ More than 8 SFF bays needed (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Veeam proxies and distributed backup infrastructure\u003c\/td\u003e    \u003ctd\u003e❌ GPU compute beyond 2x T4 (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SAN-connected compute with minimal local storage\u003c\/td\u003e    \u003ctd\u003e❌ PCIe Gen4 NVMe bandwidth required (use Gen10 Plus)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cp\u003eSame generational caveats as the rest of the DL360 Gen10 family: PCIe Gen3 (modern Gen4 NVMe runs at half rated bandwidth), DDR4-2933 maximum memory speed (Ice Lake-SP and Sapphire Rapids beat it), 1U thermal envelope constrains top-bin Platinum CPUs, FBWC battery is a wear item, iLO Advanced licensing is typically separate on refurbished units, HPE Smart Memory required for rated DIMM speed. The \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical\u003c\/a\u003e covers each of these in detail. Same platform, same generation, same constraints - the only thing that changes between 8-Bay and 10-Bay is the bay count itself.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 10 SFF bays at 1U density?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\" (canonical)\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed LFF drives in 1U?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server\"\u003eDL360 Gen10 4-Bay 3.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed more PCIe slots, more bays, or GPU compute?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative?\u003c\/strong\u003e → \u003ca href=\"\/products\/dell-poweredge-r640-8bay-2-5-build-your-own\"\u003eDell PowerEdge R640 8-Bay 2.5\"\u003c\/a\u003e - architectural counterpart on the Dell side\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, CPU SKU preference (or per-socket core count and clock target), memory capacity, storage configuration including controller preference, network topology and FlexibleLOM choice, and quantity. We respond within 24 hours, every refurbished unit ships with the 180-day warranty and 12+ hour burn-in, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242862791,"sku":"BP-013618","price":460.84,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl360-gen10-8-bay-25-drives-885647.png?v=1765539623"},{"product_id":"hpe-proliant-dl360-g10-10-bay-2-5-chassis","title":"HPE ProLiant DL360 Gen10 10-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL360 Gen10 10-Bay 2.5\" is the densest 1U SFF configuration in the Gen10 family and the canonical 1U HPE Gen10 page on our site. Ten 2.5\" hot-swap bays, dual-socket Intel Xeon Scalable (Skylake-SP first generation or Cascade Lake-SP second generation), 24 DDR4 DIMM slots, iLO 5 with Silicon Root of Trust, and the HPE Smart Array storage controller family in a 1U chassis optimized for compute density. This is HPE's 1U workhorse for IT teams standardized on the ProLiant line and the architectural counterpart to the Dell PowerEdge R640 - choose by your shop's vendor standardization, not by capability gaps, because at this tier the two platforms trade blows feature for feature.\u003c\/p\u003e\u003cp\u003eFor HPE shops running vSphere clusters, Hyper-V deployments, scale-out application infrastructure, Kubernetes worker pools, or any compute-primary workload where rack density and per-node power efficiency matter more than per-chassis storage capacity, the DL360 Gen10 10-Bay is the right answer. Pair it with its 2U sibling, the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e, when storage flexibility or PCIe expansion requires the larger chassis. Same processors. Same memory. Same iLO 5. Different chassis-level constraints.\u003c\/p\u003e\u003cp\u003eTo talk through a configuration, call 1-800-778-1545 or use the quote form below. We respond within 24 hours, every refurbished unit ships under our 180-day warranty, and every server runs through 12+ hour burn-in testing before it leaves the bench. Volume pricing kicks in at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePlatform Overview - Purley in 1U\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 sits on Intel's Purley platform with the LGA 3647 socket, identical to the DL380 Gen10. That means the same dual-generation processor support: 1st Gen Intel Xeon Scalable (Skylake-SP) for the original Gen10 launch, and 2nd Gen Xeon Scalable (Cascade Lake-SP) added mid-lifecycle as a drop-in upgrade with no board respin required. If you're sourcing CPUs separately or planning a future upgrade path, this matters: any Cascade Lake-SP processor in the supported TDP range works in a Skylake-era DL360, and any Skylake-SP processor works in a later-production Cascade Lake-era DL360, subject to BIOS revision compatibility.\u003c\/p\u003e\u003cp\u003eThe 1U thermal envelope is the meaningful constraint versus the 2U DL380. Both chassis support the same processor SKUs in principle, but the DL360 has tighter heatsink options and less airflow headroom. Processors above 165W TDP - Platinum 8260, 8268, 8280 territory - require careful confirmation of heatsink configuration and ambient inlet temperature. The DL360 ships with two heatsink variants: a standard heatsink for processors up to roughly 150W, and a high-performance heatsink for processors above that. For Gold 6230 (20 cores, 125W), Gold 6240 (18 cores, 150W), and similar mainstream dual-socket SKUs, the DL360 is comfortable. For top-bin Platinum parts where you genuinely need every core at every clock, the DL380 2U is the safer thermal envelope. We'll confirm the heatsink and ambient guidance at quote time based on the CPU SKU you specify.\u003c\/p\u003e\u003cp\u003eMemory architecture is identical to the DL380: 24 DDR4 DIMM slots total across both sockets, six memory channels per CPU at two DIMMs per channel. The supported DIMM speeds depend on the processor: Gold 6200-series and Gold 5222 SKUs run DDR4-2933 at 1 DIMM per channel, the rest of the Skylake and Cascade Lake lineup runs DDR4-2666. RDIMM capacity goes up to 64 GB per slot for 1.5 TB per dual-socket system; LRDIMM goes to 128 GB per slot for 3 TB total. Intel Optane Persistent Memory 100-series is supported with M-suffix Cascade Lake CPUs (Gold 6230M, Platinum 8260M, etc.) in the documented ratios. HPE NVDIMM-N is supported on Skylake-only platforms - not Cascade Lake - and that's a vendor product matrix limitation, not an Intel one.\u003c\/p\u003e\u003cp\u003eHPE's memory population rules apply identically to the DL360 and the DL380: DIMMs must be installed in even quantities per CPU, RDIMM and LRDIMM cannot be mixed, and only HPE DDR4 Smart Memory is qualified to run at the rated speeds. Third-party memory will physically work but typically drops to DDR4-2400 regardless of the CPU's rated speed. If you have a DDR4-2933 workload requirement, you need HPE Smart Memory. We stock HPE Smart Memory and will spec the kit at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 10 SFF Bays, the Density Pick\u003c\/h2\u003e\u003cp\u003eTen 2.5\" SAS\/SATA hot-swap bays in 1U is the maximum SFF density on the DL360 Gen10 platform. Two additional bays over the more common 8-Bay configuration. The 10-Bay backplane is fully SAS\/SATA-capable across all ten slots, and NVMe is supported on the original Gen10 only via dedicated NVMe expansion - native backplane NVMe across all bays is a Gen10 Plus and Gen11 feature, not original Gen10. If you need direct-attached NVMe storage at meaningful capacity, the Gen10 supports it through PCIe expansion cards routing to specific NVMe-capable bays, not as a backplane-wide capability.\u003c\/p\u003e\u003cp\u003eThe 10-Bay configuration earns its place over the 8-Bay in three specific scenarios:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eCeph OSD nodes at 1U density.\u003c\/strong\u003e Ten OSDs per 1U node is a meaningful density improvement over eight when you're sizing a Ceph cluster for object storage or RBD workloads. The math at scale matters: a 12-node Ceph cluster with 10 OSDs per node is 120 OSDs; the same cluster at 8 OSDs per node is 96 OSDs. That 25% capacity difference per rack at the same rack-U cost is the reason this configuration exists.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN hybrid configurations.\u003c\/strong\u003e vSAN hybrid wants one SSD cache device per disk group and up to seven HDDs per group, with two disk groups per host as a common configuration. Ten bays gives you 2x (1 cache + 4 capacity) cleanly with two bays held back, or 2x (1 cache + 4 capacity) with the remaining two used for OS boot if you're not using M.2. vSAN all-flash configurations benefit similarly: 2x (1 cache + 4 capacity) all-SSD at 1U is a genuine vSAN ReadyNode-class density point.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDistributed databases and Kubernetes persistent volumes.\u003c\/strong\u003e Cassandra nodes, MongoDB replica set members, Elasticsearch data nodes, or Kubernetes CSI-backed persistent volume hosts all benefit from the extra two bays when the workload's per-node storage requirement is in the 6-10 drive range. Eight bays is tight when you also need OS boot drives in the bay count; ten bays gives breathing room.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf your storage design fits in 8 bays comfortably and you're using HPE's M.2 enablement kit or a single boot drive in a bay, the \u003ca href=\"\/products\/dl360-g10-chassis\"\u003e8-Bay variant\u003c\/a\u003e is the simpler and slightly less expensive choice. The 10-Bay premium is modest but it's a real cost - pay it when the bays earn their place, not by default.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen10 portfolio: SAS SSDs from 480 GB through 15.36 TB across read-intensive, mixed-use, and write-intensive endurance classes; SATA SSDs in mixed-use and read-intensive for cost-sensitive workloads; SAS HDDs at 10K and 15K from 600 GB through 2.4 TB for moderate-IOPS workloads; and NL-SAS in SFF form factor up to 2.4 TB for capacity tiers in SFF chassis. We carry the full HPE-branded drive line and will spec the right tier and endurance class based on your workload's read\/write profile and the controller's queue depth tolerance.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers - Smart Array Family\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10's controller options are identical to the DL380 Gen10's, configured for the 1U chassis:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 with 2 GB FBWC.\u003c\/strong\u003e The mainstream production controller: RAID 0\/1\/5\/6\/10\/50\/60, 2 GB flash-backed write cache, full hardware RAID acceleration. This is the right pick for hardware-RAID storage where the OS sees a single logical drive per RAID group. The FBWC battery is a wear item with roughly a 5-year service life under typical conditions - plan a battery replacement somewhere in years 4 through 5, and watch iLO for cache module health alerts. We disclose this on every quote; a refurbished P408i-a's battery may have meaningful runtime already on it, and we either replace the cache module up front or document the battery's measured state at burn-in.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 with 4 GB FBWC.\u003c\/strong\u003e The premium controller: same RAID modes, 4 GB FBWC, higher port count, and tri-mode SAS\/SATA\/NVMe support on supported drives. Specify the P816i-a when the workload is write-heavy at scale (transactional databases, write-mostly logging, video ingest) and the 2 GB cache on the P408i-a is the bottleneck. For most 1U DL360 deployments, the P408i-a is plenty; the P816i-a is the right call when you've actually measured cache pressure on a comparable workload or you need NVMe drive support alongside SAS\/SATA.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a SR Gen10 (HBA mode).\u003c\/strong\u003e The HBA controller for software-defined storage: vSAN, Ceph, Storage Spaces Direct (S2D), ZFS-based appliances. No hardware RAID, just clean SAS HBA pass-through to the OS or hypervisor. This is the right pick for any storage-defined-in-software architecture where the hardware RAID controller would actually interfere with the SDS layer's drive-level visibility.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eS100i SR Gen10 (software RAID).\u003c\/strong\u003e The chipset-integrated software RAID solution. Adequate for boot-drive mirrors on Windows or Linux but not appropriate for production data RAID. Use it for OS boot if you don't have an M.2 enablement kit installed; use a real Smart Array P-series or HBA for data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot drive options on the DL360 Gen10 are the HPE M.2 enablement kit (PCIe-attached M.2 carrier with SATA M.2 drive support, typically 480 GB) or a SAS\/SATA SSD pair in two of the front bays under hardware RAID 1. The HPE NS204i-p NVMe boot device that ships standard on Gen10 Plus and Gen11 is not natively supported on original Gen10 - that's a generational platform line, not a configuration option. If you need NVMe boot specifically on Gen10, it's via the M.2 kit or via a PCIe-attached NVMe drive in a bay, not via NS204i-p.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 provides 3 PCIe Gen3 slots in a 1U chassis - a meaningfully tighter constraint than the DL380's 8 slots, and the single most important architectural difference between the 1U and 2U chassis at this tier. Slot 1 and slot 2 are full-height half-length, slot 3 is low-profile. The standard riser configuration supports two x16 slots; an alternative riser provides three slots with a x16\/x8\/x8 layout.\u003c\/p\u003e\u003cp\u003eHPE's FlexibleLOM mezzanine slot is separate from the PCIe slots and does not consume one. This is HPE's equivalent of Dell's rNDC (network daughter card) on the R640 - a dedicated mezzanine for the primary network interface that leaves all three PCIe slots free for HBAs, GPUs, or additional NICs. FlexibleLOM options span 1 GbE quad-port, 10 GbE SFP+ dual-port and quad-port, 10 GbE RJ45 dual-port and quad-port, 25 GbE SFP28 dual-port, and 100 GbE QSFP28 dual-port. For HCI workloads (vSAN, S2D, Ceph) where 25 GbE has become the standard interconnect, the 25 GbE SFP28 FlexibleLOM plus a 25 GbE SFP28 PCIe NIC in slot 1 is the standard high-bandwidth configuration. We'll spec the FlexibleLOM and any additional PCIe NICs at quote time based on your network topology.\u003c\/p\u003e\u003cp\u003eGPU support in 1U is sharply constrained relative to the DL380. The DL360 Gen10 supports a maximum of two single-width low-profile GPUs - typically NVIDIA T4 or A2 in the inference\/light-compute class. Double-width GPUs (V100, A100, A40, A30) and full-height cards do not fit the 1U chassis at all. If you need GPU compute beyond two T4-class cards, this is not the right chassis - the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10\u003c\/a\u003e supports up to seven T4s or three V100s with the GPU riser kit. The DL360 is a CPU compute platform first; GPU is a secondary capability bounded by the 1U thermal and slot envelope.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 5 with Silicon Root of Trust\u003c\/h2\u003e\u003cp\u003eiLO 5 is HPE's out-of-band management processor, the architectural equivalent of Dell's iDRAC9 on R640\/R740 generations. Full remote KVM, virtual media mounting (mount an ISO over the network for OS install), serial-over-LAN, hardware health monitoring, power and thermal telemetry, REST API (Redfish-compliant), HPE OneView integration, and Active Health System logging. iLO is on a dedicated management network port - segregate it on a management VLAN; never expose iLO to the production network or the public internet without VPN. Both have full filesystem access to the host and full power control.\u003c\/p\u003e\u003cp\u003eSilicon Root of Trust is HPE's Gen10-and-later platform security baseline. It's a hardware-anchored chain of trust starting from the iLO 5 silicon, verifying iLO firmware, then BIOS, then OS bootloader against cryptographic measurements baked into the silicon at manufacture. This is functionally equivalent to Dell's iDRAC9 System Lockdown plus Intel Boot Guard, just architected differently. For environments with security audit requirements - PCI DSS, HIPAA, FedRAMP-aligned, or any environment where firmware tampering is a documented threat - Silicon Root of Trust is a meaningful differentiator from older Gen9 hardware that predates it.\u003c\/p\u003e\u003cp\u003eOne important note on refurbished units: iLO Advanced licensing is typically not included on refurbished Gen10 hardware. iLO Advanced unlocks the full feature set - remote KVM in particular, plus integrated remote console, video record\/replay, virtual folder, and email alerting. The base iLO 5 license that ships with the hardware includes health monitoring, IPMI, and basic remote access but not the full graphical remote KVM. We can include iLO Advanced licensing on builds where it's required - call this out at quote time so we spec the license correctly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies in the standard hot-plug redundant configuration. Wattages span 500W, 800W, 1600W, and 1600W -48V DC. Platinum efficiency on the 500W and 800W; Titanium efficiency on the 1600W (96% efficiency at 50% load, the highest 80 PLUS tier). For a typical dual-socket Gold-class DL360 with 16 DIMMs and 10 SFF SSDs, the 800W Platinum redundant pair is the standard sizing - generous headroom for any reasonable configuration and excellent efficiency at typical load. For high-TDP Platinum-CPU builds, top-bin DIMM populations, or single-PSU operation with redundancy as the failover path, step to the 1600W Titanium pair. We size the PSUs to the build and document the expected peak draw at quote time.\u003c\/p\u003e\u003cp\u003eFans are dual-rotor, fully redundant, hot-swappable. Inlet temperature spec is 10°C to 35°C ambient for standard operation; ASHRAE A3 (10°C to 40°C) supported on most configurations and A4 (5°C to 45°C) on specific reduced-CPU configurations. For colocation environments running ASHRAE A2 or stricter, the DL360 has plenty of thermal margin in any dual-socket Gold-class build. For high-density racks running hot, confirm the inlet spec at quote time - particularly for Platinum-CPU configurations approaching the 165W per-socket envelope.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL360 Gen10 Fits in 2026\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 launched in 2017 and was Cascade Lake-refreshed in 2019. By 2026, it's two platform generations behind current: Gen10 Plus (Ice Lake-SP, PCIe Gen4, 2020) and Gen11 (Sapphire Rapids \/ Emerald Rapids, DDR5, PCIe Gen5, 2023-2024). That generational gap is real and we won't pretend otherwise. What it means in practice:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003ePer-core performance is solid; per-socket maximums are dated.\u003c\/strong\u003e A Cascade Lake Gold 6230 at 20 cores per socket \/ 40 cores dual-socket is still a competitive virtualization host in 2026 - VMware vSphere 8 supports it, Windows Server 2025 supports it, modern Linux supports it, container workloads run fine. What's dated is socket-level scaling: Ice Lake-SP hit 40 cores per socket, Sapphire Rapids hit 60, Emerald Rapids hit 64. If your workload's bottleneck is socket-level core count, Gen10 is behind.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe Gen3 is the I\/O limit.\u003c\/strong\u003e NVMe drives, 100 GbE NICs, and modern GPUs are all Gen4 or Gen5 internally. They work in Gen3 slots at reduced lane bandwidth - a Gen4 x4 NVMe drive runs at Gen3 x4 speeds, which is roughly half its rated throughput. For storage-intensive or networking-intensive deployments where Gen4 bandwidth actually matters, Gen10 Plus or Gen11 is the right platform. For compute-primary workloads where Gen3 NVMe bandwidth is sufficient, the limit doesn't bite.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMemory bandwidth ceilings are real.\u003c\/strong\u003e DDR4-2933 maxes out at roughly 23.5 GB\/s per channel, six channels per socket, ~141 GB\/s per socket peak. Ice Lake-SP brought eight channels and DDR4-3200; Sapphire Rapids brought DDR5-4800. Memory-bandwidth-bound workloads (in-memory databases, HPC, certain analytics) see meaningful uplift on newer platforms. General-purpose virtualization and application serving rarely hit the memory bandwidth ceiling on Gen10.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThat said, Gen10 is widely deployed across the enterprise installed base in 2026. HPE supports Gen10 firmware updates through 2027 under standard lifecycle policy, and parts availability for both new and refurbished components is broad - this is the most-deployed ProLiant generation in service today. For HPE shops standardized on Gen10 and looking to expand existing clusters with matching hardware, the platform makes complete sense. For greenfield deployments where budget allows, Gen10 Plus or Gen11 will get you Ice Lake or newer with PCIe Gen4\/5 and more headroom for the next five years.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cp\u003eThe points worth saying out loud before you buy:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eThe Smart Array FBWC battery is a wear item.\u003c\/strong\u003e Cache module batteries have a service life of roughly 5 years under typical operating conditions, often less in hot environments. A refurbished P408i-a or P816i-a's battery may have meaningful runtime already. We replace cache modules on builds where the battery is past spec, and we document the measured battery state on every unit shipped with a P-series controller.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eiLO Advanced licensing is usually not included.\u003c\/strong\u003e Refurbished Gen10 units typically ship with the base iLO 5 license, not iLO Advanced. If you need integrated remote console KVM (the graphical remote console most people associate with iLO), the iLO Advanced license is a real cost. We'll quote it explicitly when it's required.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eThe DL360 is a CPU compute platform, not a GPU compute platform.\u003c\/strong\u003e Two single-width T4-class cards is the practical ceiling. If you need GPU compute at scale, the DL380 Gen10 or a purpose-built GPU server is the right answer.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eOriginal Gen10 is PCIe Gen3.\u003c\/strong\u003e Modern NVMe and 100 GbE cards work but at reduced bandwidth versus their Gen4\/Gen5 native platforms. For PCIe-Gen3-bandwidth-bound workloads specifically, this matters.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE memory rules are strict.\u003c\/strong\u003e Third-party DDR4 will run at DDR4-2400 regardless of the CPU's rated speed. HPE DDR4 Smart Memory is required for rated DDR4-2666 or DDR4-2933 operation. This is documented HPE behavior, not a defect.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ VMware vSphere \/ Hyper-V compute clusters at 1U density\u003c\/td\u003e    \u003ctd\u003e❌ Workloads requiring 24 SFF bays or 12 LFF bays\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Ceph OSD nodes at 10 OSDs per 1U\u003c\/td\u003e    \u003ctd\u003e❌ GPU compute beyond 2x T4-class single-width\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ vSAN hybrid or all-flash with 2 disk groups per host\u003c\/td\u003e    \u003ctd\u003e❌ More than 3 PCIe expansion cards needed\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Kubernetes worker pools with local persistent volumes\u003c\/td\u003e    \u003ctd\u003e❌ Memory-bandwidth-bound HPC (Gen10 Plus \/ Gen11 better)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Scale-out application infrastructure in HPE shops\u003c\/td\u003e    \u003ctd\u003e❌ PCIe Gen4 NVMe bandwidth as a hard requirement\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Distributed databases (Cassandra, MongoDB, Elasticsearch)\u003c\/td\u003e    \u003ctd\u003e❌ Top-bin Platinum CPUs in dense racks (DL380 thermal headroom)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eCross-Vendor Notes - DL360 Gen10 vs. Dell R640\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 and the Dell PowerEdge R640 are direct architectural counterparts. Both are 1U dual-socket Purley-platform servers. Both support 1st Gen and 2nd Gen Xeon Scalable. Both top out at 24 DDR4 DIMM slots. Both have integrated BMC-class management (iLO 5 vs. iDRAC9) with full remote console capability. Both have a dedicated network mezzanine slot (FlexibleLOM vs. rNDC) that doesn't consume a PCIe slot. Both have similar storage controller families (Smart Array P-series vs. PERC H730\/H740\/H840). The DL360 has 3 PCIe slots vs. the R640's 3 PCIe slots - identical. Drive bay configurations align closely (HPE 8-bay and 10-bay vs. Dell 8-bay and 10-bay).\u003c\/p\u003e\u003cp\u003eThe differences are at the vendor-ecosystem level: management software (iLO + OneView vs. iDRAC + OpenManage), licensing models for advanced features, the vendor's installed-base relationships, parts ecosystem and refresh cadence, and support contract pricing. None of these is a capability gap. Pick by your shop's vendor standardization and your existing tooling investments. If you're an HPE shop running OneView and Insight, the DL360 is the right answer. If you're a Dell shop running OpenManage Enterprise, the \u003ca href=\"\/products\/dell-poweredge-r640-10bay-2-5-build-your-own\"\u003eR640 10-Bay\u003c\/a\u003e is the right answer. We sell both and we'll quote both honestly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eFrequently Asked\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eDoes the DL360 Gen10 support Cascade Lake processors?\u003c\/strong\u003e Yes. The platform supports both 1st Gen Xeon Scalable (Skylake-SP) and 2nd Gen Xeon Scalable (Cascade Lake-SP) as drop-in compatible processors with appropriate BIOS revision. Cascade Lake brings hardware Spectre\/Meltdown mitigations, slightly higher core counts at the top of the stack, support for Optane Persistent Memory 100-series, and minor power efficiency improvements. Most production refurbished DL360 Gen10 units we ship are Cascade Lake-equipped.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eIs the DL360 Gen10 the same as the DL360 Gen10 Plus?\u003c\/strong\u003e No. Gen10 Plus is a different platform: Ice Lake-SP processors on LGA 4189, PCIe Gen4, eight memory channels per socket, and the HPE NS204i-p NVMe boot device standard. Gen10 is Purley\/Skylake-Cascade Lake\/PCIe Gen3. They look similar externally and share the DL360 chassis lineage, but the motherboard, processor socket, and I\/O are different generations. If you've been told \"DL360 Gen10\" and you need PCIe Gen4 or Ice Lake, confirm the actual SKU before purchase.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eCan I run VMware vSphere 8 on the DL360 Gen10?\u003c\/strong\u003e Yes. vSphere 8 supports both Skylake-SP and Cascade Lake-SP processors and HPE certifies Gen10 ProLiant hardware against vSphere 8. There are no platform-level blockers. vSphere 9 deprecates some older hardware - check VMware's HCL at the time of deployment for current support status. As of early 2026, Gen10 is fully on the vSphere 8 HCL.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhat about Windows Server 2025?\u003c\/strong\u003e Supported. HPE has Gen10 firmware and driver updates qualified against Windows Server 2025; the platform meets all of WS2025's hardware baseline requirements including TPM 2.0 (optional but available on Gen10 via the HPE TPM 2.0 module). Standard build.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eDoes the DL360 Gen10 support NVMe drives?\u003c\/strong\u003e Yes, via the NVMe expansion kit on specific bay positions. Native NVMe across all bays is a Gen10 Plus and Gen11 feature; the original Gen10 supports NVMe on a subset of bays through PCIe lane routing from a Smart Array P816i-a (tri-mode) or a dedicated NVMe-bay enablement kit. If NVMe is core to your storage design, we can spec it; if NVMe is the dominant storage tier, Gen10 Plus is the more native platform.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eDo you ship the iLO Advanced license?\u003c\/strong\u003e Optional. The base iLO 5 license that ships with refurbished Gen10 hardware does not include integrated remote console (graphical KVM), remote media, or some of the advanced telemetry features. iLO Advanced unlocks all of these. Call it out at quote time and we'll include the license SKU.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhat's the warranty?\u003c\/strong\u003e 180-day Wholesale Servers warranty on every refurbished unit, covering parts and labor. Pre-shipment burn-in testing is 12+ hours minimum on every server. Extended warranty options are available; ask at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, the CPU SKU (or the per-socket core count and clock target - we'll recommend the SKU), memory capacity, storage configuration including controller preference, network topology and FlexibleLOM choice, and quantity. We respond within 24 hours, every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below to start a conversation.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242961095,"sku":"BP-013619","price":693.07,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl360-gen10-10-bay-25-drives-207415.png?v=1765539623"},{"product_id":"hp-proliant-dl160-g10-4-bay-3-5-build-your-own-server","title":"HPE ProLiant DL160 Gen10 4-Bay 3.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL160 Gen10 4-Bay 3.5\" is HPE's value-tier 2P 1U platform in the Gen10 lineup - a dual-socket Xeon Scalable server in a 1U chassis built for SMB and service-provider workloads where the cost difference versus the DL360 matters more than the memory ceiling and DIMM count. Four 3.5\" LFF hot-swap bays, 16 DDR4 DIMM slots (eight per CPU, two fewer per CPU than the DL360), iLO 5 with Silicon Root of Trust, HPE Smart Array controller support, and dual embedded 1 GbE for primary networking - in a chassis that trades the DL360's memory headroom and FlexibleLOM-standard configuration for a lower entry cost.\u003c\/p\u003e\u003cp\u003eThis is the HPE architectural counterpart to the Dell PowerEdge R440 - 2P 1U value-tier in the same Purley generation. For HPE customers running branch office workloads, distributed compute clusters where per-node cost is the design driver, edge file servers, or any deployment where the DL360's 24 DIMM slots and 1.5-3 TB memory ceiling are surplus to requirements, the DL160 delivers the same processor family and same management architecture at a meaningfully lower price point. It's not a stripped-down DL360 - it's a different chassis built around different cost-versus-capacity tradeoffs.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL160 Gen10 Fits in the Family\u003c\/h2\u003e\u003cp\u003eHPE positions the DL160 Gen10 as \"2P 1U at compelling price point for SMB and service providers.\" That's accurate. The DL160 is genuinely a 2P server - both sockets are populated in production builds, dual-socket scaling works as designed, and the Purley platform is identical to the DL360 and DL380. What's different is what HPE designed the chassis to economize on:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e16 DIMM slots total versus 24 on the DL360.\u003c\/strong\u003e Eight DIMMs per CPU instead of twelve. With 64 GB RDIMMs that's a 1 TB maximum versus the DL360's 1.5 TB. The eight DIMMs per CPU still cover six memory channels (each at one DIMM per channel plus two channels at two DIMMs), so the bandwidth architecture is unchanged - what's gone is the headroom to populate larger memory configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x embedded 1 GbE standard, FlexibleLOM optional.\u003c\/strong\u003e The DL160 ships with two 1 GbE ports built into the chassis. A FlexibleLOM mezzanine can be added via the FlexibleLOM riser kit, but it's not standard - and adding it consumes one of the available riser positions. The DL360, by contrast, has FlexibleLOM as a standard mezzanine that doesn't consume any PCIe slot.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eRiser-based PCIe configuration.\u003c\/strong\u003e Up to 3 PCIe slots maximum with the optional secondary riser, fewer in default configurations. The riser kit options determine the slot count, and some configurations (e.g. the FlexibleLOM riser) trade slots for I\/O capability.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eBronze\/Silver CPU sweet spot.\u003c\/strong\u003e The DL160 supports Bronze 3100, Silver 4100, Gold 5000\/6000, and lower-bin Platinum SKUs. Where the DL360 is comfortable with Gold-class dual-socket as the typical build, the DL160's price point is optimized around Bronze and Silver for the SMB and service-provider markets HPE designed it for. Top-bin Platinum CPUs are supported but the economics rarely justify them in this chassis - if you need top-bin Platinum, you usually also need the DL360's DIMM headroom.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThis is the right platform when those four constraints - 1 TB memory ceiling, embedded 1 GbE, modest PCIe expansion, Bronze\/Silver-tier CPU sweet spot - are acceptable for the workload. Pay the DL360 premium only when one of those constraints actually bites your design.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 4 LFF Bays\u003c\/h2\u003e\u003cp\u003eFour 3.5\" SAS\/SATA hot-swap bays in the front of the chassis. Drive options span the full LFF portfolio: NL-SAS HDDs for bulk capacity (4 TB through 20 TB), SAS HDDs at 10K and 15K for moderate-IOPS workloads, and SAS or SATA SSDs in LFF carriers for performance in LFF form factor. RAID-at-4-drives guidance is the same as the DL360 4-Bay 3.5\" - RAID 6 strongly preferred for large-capacity NL-SAS, RAID 10 when write performance is the priority, RAID 5 only with explicit discussion of risk tolerance.\u003c\/p\u003e\u003cp\u003eBay-count map for common DL160 4-Bay deployments:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eBranch office file server (SMB-scale).\u003c\/strong\u003e 4x 8 TB or 12 TB NL-SAS in RAID 6 gives 16-24 TB usable for branch NAS, AD-integrated file shares, or shared user storage at remote sites. The DL160's lower acquisition cost matters when you're deploying across many branches.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eService provider compute node with local storage.\u003c\/strong\u003e Bronze or Silver dual-socket compute, 256-512 GB RAM, and 4 LFF bays for tenant storage or VM datastores. Service providers running many small-scale tenants benefit from the per-node cost optimization.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eVeeam backup target at remote site.\u003c\/strong\u003e 4 large-capacity NL-SAS drives for remote backup repositories. The lower compute spec is fine - Veeam Backup \u0026amp; Replication's CPU requirement on a remote proxy is modest. Spend the savings on more drives.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDistributed Ceph or MinIO node at small scale.\u003c\/strong\u003e 4 OSDs per 1U node for capacity-tier storage with modest per-node compute. The DL160's economics work well at scale when you're deploying many nodes.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSMB primary application server.\u003c\/strong\u003e Single dual-socket build with 4 LFF drives for OS + application + local data. The Bronze\/Silver-tier CPU is sufficient for SMB application workloads.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eThe HPE Universal SATA HHHL M.2 Kit is the cleanest boot solution on the DL160 Gen10 - it mounts in a PCIe slot, takes one or two SATA M.2 drives, and frees all 4 LFF bays for data. Strongly recommended given the 4-bay constraint. Note that the M.2 kit requires the DL160\/120 Gen10 M.2 SATA Cable Kit as an additional part - HPE breaks this into separate SKUs, which we handle on the BoM at quote time. The alternative is 2x SFF SAS\/SATA SSDs in a RAID 1 OS mirror occupying two of the 4 LFF bays via LFF-to-SFF adapter brackets, but this consumes half the bay count for OS alone.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL160 Gen10 supports the same Smart Array Gen10 controller family as the DL360 and DL380, sourced as PCIe plug-in cards rather than as type-a modular controllers in some configurations:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 (2 GB FBWC).\u003c\/strong\u003e The mainstream production RAID controller. 2 GB flash-backed write cache, full hardware RAID 0\/1\/5\/6\/10\/50\/60. Right pick for NL-SAS RAID 6 in a production build. The FBWC battery is a wear item with roughly 5-year service life - we disclose battery state on every quote and replace cache modules on builds where the battery is past spec.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 (4 GB FBWC).\u003c\/strong\u003e Premium controller. Same RAID modes, larger cache, tri-mode SAS\/SATA\/NVMe support. Specify when write workload is heavy enough to pressure the 2 GB cache on the P408i-a - rarely needed at 4 drives, but available when the I\/O profile justifies it.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-p SR Gen10 (HBA mode, PCIe plug-in).\u003c\/strong\u003e The HBA controller for software-defined storage workloads (Ceph, ZFS, S2D). No hardware RAID; clean SAS pass-through.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eS100i SR Gen10 (software RAID).\u003c\/strong\u003e Chipset-integrated software RAID. Acceptable for OS boot mirroring, not appropriate for production data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required when any P-series performance RAID controller is installed - this is a separate part from the FBWC cache module on the controller itself. We include the battery in every quote that specifies a P-series controller.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors and Memory\u003c\/h2\u003e\u003cp\u003eDual-socket LGA 3647 Purley platform, identical to the DL360 and DL380. Both 1st Generation Intel Xeon Scalable (Skylake-SP) and 2nd Generation (Cascade Lake-SP) are supported as drop-in compatible processors. The DL160's CPU sweet spot is the Bronze 3100 series (4-8 cores, low TDP, DDR4-2133 max memory speed at the bottom of the stack) and Silver 4100\/4200 series (8-12 cores, DDR4-2400 to DDR4-2666). Gold 5200\/6200 series are supported and run their full rated DDR4-2933 with HPE Smart Memory; Platinum is supported but rarely the right economic call in this chassis.\u003c\/p\u003e\u003cp\u003eMemory: 16 DDR4 DIMM slots total (8 per CPU), supporting RDIMM and LRDIMM (no UDIMM at production scale). Six memory channels per CPU with the eight DIMM slots arranged as six channels at one DPC plus two channels at two DPC - the bandwidth architecture is identical to the DL360, the difference is the headroom for additional memory beyond a balanced six-channel population. Maximum 1 TB with 64 GB RDIMMs at dual-socket. HPE DDR4 Smart Memory required for rated speed operation - third-party DDR4 drops to DDR4-2400 regardless of CPU rated speed, same documented HPE behavior as the rest of the Gen10 line. RDIMM and LRDIMM cannot be mixed; even DIMM quantities per CPU required.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eThe DL160 Gen10 ships with 2x embedded 1 GbE ports on the chassis as standard. For shops with 10 GbE or higher requirements:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eFlexibleLOM riser kit.\u003c\/strong\u003e Adds a FlexibleLOM mezzanine to one of the riser positions, enabling 10 GbE SFP+, 10 GbE RJ45, 25 GbE SFP28, or other FlexibleLOM options. This consumes one PCIe slot's worth of riser capacity.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe plug-in NICs.\u003c\/strong\u003e Standard PCIe NIC cards in available slots - 10 GbE, 25 GbE, or 100 GbE depending on the riser configuration and slot count.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eMaximum 3 PCIe slots with the optional secondary riser installed (requires second CPU populated). Default configurations have fewer. The slot budget on the DL160 is tight - allocate carefully between storage controller, FlexibleLOM\/NIC, and any additional cards. Standard production builds for branch-office workloads usually need just a P408i-a Smart Array and either FlexibleLOM riser or PCIe NIC - that fits comfortably in the available slots.\u003c\/p\u003e\u003cp\u003eGPU support is limited to single-width low-profile cards at most, and the DL160 is not designed for GPU workloads. If GPU compute is a requirement, the DL360 Gen10 or DL380 Gen10 is the right answer.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 5 with Silicon Root of Trust\u003c\/h2\u003e\u003cp\u003eSame iLO 5 management architecture as the DL360 and DL380, with the same caveat: iLO Standard ships with the hardware on refurbished units, and iLO Advanced licensing is typically a separate cost when needed for full graphical remote KVM, virtual media mounting, and advanced telemetry. The base iLO 5 license covers health monitoring, IPMI, and basic remote access. We'll quote iLO Advanced explicitly when the deployment requires it.\u003c\/p\u003e\u003cp\u003eSilicon Root of Trust is standard - the same hardware-anchored chain of trust starting from iLO 5 silicon, verifying iLO firmware, BIOS, and OS bootloader against cryptographic measurements. This is the same Gen10 security baseline that applies across the DL line. For SMB and branch-office deployments where firmware tampering is a documented concern (any environment subject to compliance audit, plus any deployment in physically-accessible locations like retail back-of-store), Silicon Root of Trust is real value at this price point.\u003c\/p\u003e\u003cp\u003eSecure Recovery is also Gen10-baseline: the firmware can detect compromised firmware and roll back to a known-good state automatically. Combined with iLO 5's signed firmware update model, the security posture on a DL160 is identical to a much more expensive DL380 - one of the genuine value points of buying into the Gen10 family at the entry tier.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies in single or redundant configurations. Redundant PSU operation requires the HPE DL160\/180 Gen10 Redundant Power Supply Enablement Kit - this is not standard on every model and we'll spec it when redundant power is a requirement. Wattages span 500W and 800W for typical Bronze\/Silver-tier builds; higher-wattage Flex Slot PSUs are supported for Gold-class configurations.\u003c\/p\u003e\u003cp\u003eSingle-PSU operation is acceptable for non-production or branch-office workloads where the cost savings matter and the deployment is not mission-critical at the single-server level. For production HA workloads, take the redundant PSU kit - it's a modest add to the BoM and protects against the most common cause of single-server downtime.\u003c\/p\u003e\u003cp\u003eInlet temperature spec is 10°C to 35°C standard, with ASHRAE A3 support on most configurations. For branch-office deployments in environments without dedicated server-room cooling (closets, equipment rooms, retail back-of-store), the wider ambient operating range matters. Confirm the inlet spec for the specific CPU SKU and configuration at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL160 Gen10 Fits in 2026\u003c\/h2\u003e\u003cp\u003eSame generational positioning as the rest of the Gen10 line. Launched in 2017, Cascade Lake-refreshed in 2019, two generations behind Gen10 Plus (Ice Lake-SP, PCIe Gen4, 2020) and Gen11 (Sapphire Rapids \/ Emerald Rapids, DDR5, 2023-2024). The platform is widely deployed and supported - HPE firmware updates through 2027 under standard lifecycle, broad parts availability for both new and refurbished.\u003c\/p\u003e\u003cp\u003eWhat's specific to the DL160 in 2026: the value proposition is sharper now than at launch because the DL160's \"sufficient for SMB and branch workloads\" hardware envelope still genuinely covers those workloads. SMB file server requirements haven't grown dramatically; branch-office compute workloads haven't transformed. The DL160's hardware is dated but its workload fit isn't. For HPE shops adding capacity to existing fleets or standardizing on Gen10 for cost-controlled deployments, the DL160 4-Bay 3.5\" delivers genuine work at meaningful cost savings versus a DL360-class deployment.\u003c\/p\u003e\u003cp\u003eThat said, if the deployment is greenfield and the budget allows, Gen10 Plus or Gen11 will get you Ice Lake or newer with PCIe Gen4\/5 and more headroom for the next five years. The DL160 Gen10 is the right call when budget is the design constraint - which is exactly what HPE built the chassis for.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e16 DIMM slots, 1 TB memory ceiling.\u003c\/strong\u003e Two fewer DIMMs per CPU than the DL360. If your workload's per-node memory requirement is above 1 TB, this isn't the right platform - step to the DL360.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x embedded 1 GbE only by default.\u003c\/strong\u003e Anything more requires the FlexibleLOM riser kit (which consumes riser capacity) or PCIe NICs. The DL360's standard FlexibleLOM is a meaningful differentiator if 10 GbE+ is a baseline requirement.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eTight PCIe slot budget.\u003c\/strong\u003e Maximum 3 slots with the optional secondary riser. Allocate carefully between storage controller, networking, and any additional cards.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eRedundant PSU is optional, not standard.\u003c\/strong\u003e Single-PSU operation is the default. For production HA, add the redundant PSU enablement kit - we'll include it explicitly when specified.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eBronze CPUs cap memory speed at DDR4-2133.\u003c\/strong\u003e If you take the price-optimized Bronze 3100 series, memory bandwidth drops below what Silver\/Gold deliver. For memory-bandwidth-sensitive workloads, Silver is the minimum reasonable CPU tier.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSame Gen10 generational caveats apply.\u003c\/strong\u003e PCIe Gen3, DDR4-2933 ceiling (with appropriate CPU), iLO Advanced licensing separate, FBWC battery as a wear item. The DL360 canonical covers these in detail and they apply identically here.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SMB primary servers (file, AD, applications)\u003c\/td\u003e    \u003ctd\u003e❌ Memory requirement above 1 TB (use DL360)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Branch office file servers in 1U LFF\u003c\/td\u003e    \u003ctd\u003e❌ More than 4 LFF bays needed (use DL380 12-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Service provider compute at price-point optimization\u003c\/td\u003e    \u003ctd\u003e❌ 10 GbE+ as baseline networking requirement (DL360 better)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Remote Veeam backup targets at branch sites\u003c\/td\u003e    \u003ctd\u003e❌ Top-bin Platinum CPU workloads (DL360\/DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Distributed Ceph capacity-tier at scale\u003c\/td\u003e    \u003ctd\u003e❌ GPU compute requirements\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Cost-controlled HPE shop deployments\u003c\/td\u003e    \u003ctd\u003e❌ Many PCIe expansion cards needed\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 24 DIMM slots and full DL360 memory\/networking?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server\"\u003eDL360 Gen10 4-Bay 3.5\"\u003c\/a\u003e - same Purley platform, 24 DIMMs, FlexibleLOM standard\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed more than 4 LFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e - 3x the bays in 2U\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed SFF drives instead of LFF?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\" (canonical)\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same tier?\u003c\/strong\u003e → Dell PowerEdge R440 - 2P 1U value-tier on the Dell side, same generation\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, CPU tier preference (Bronze\/Silver\/Gold), memory target, storage configuration including RAID and controller, network requirement (embedded 1 GbE vs. FlexibleLOM riser vs. PCIe NIC), PSU redundancy, and quantity. We respond within 24 hours, every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951272091847,"sku":"BP-013621","price":706.47,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl160-gen9-4-bay-35-drives-523949.png?v=1765539688"},{"product_id":"server-design-lab-hpe-dl560-g10-8-bay-2-5-drives","title":"HPE ProLiant DL560 Gen10 8-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL560 Gen10 8-Bay 2.5\" is HPE's 4-socket flagship in the Gen10 lineup - a dense quad-socket Xeon Scalable platform in a 2U chassis (not 4U; HPE engineered the DL560 as a high-density 2U 4S server, which is one of its primary differentiators against competitors). Up to four 1st or 2nd Generation Intel Xeon Scalable processors, 48 DDR4 DIMM slots, 6 TB maximum memory with LRDIMMs, eight 2.5\" SFF hot-swap bays, up to 8 PCIe Gen3 slots with full riser configuration, FlexibleLOM networking, iLO 5 with Silicon Root of Trust, and up to 4 HPE Flex Slot power supplies. Built for scale-up workloads that have genuinely exhausted dual-socket compute and memory headroom.\u003c\/p\u003e\u003cp\u003eThis is the HPE architectural counterpart to the Dell PowerEdge R840 - 2U 4-socket Purley on the Dell side, same generation, same workload positioning. For SAP HANA scale-up, Oracle Database Enterprise consolidation, mission-critical virtualization at extreme VM density, or Microsoft SQL Server Enterprise at maximum core-license consolidation, the DL560 Gen10 is the right HPE platform. The 8-Bay 2.5\" variant is the standard configuration: maximum 4-socket compute paired with 8 SFF bays for OS, application data, and hot dataset staging, expecting primary bulk storage on SAN or distributed file systems.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units. DL560 configurations benefit from a design conversation early - workload architecture, Oracle\/SAP licensing implications, power budget at 4-socket TDP, and thermal validation all matter before hardware selection.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL560 Gen10 Fits in the Family\u003c\/h2\u003e\u003cp\u003eThe DL560 Gen10 is a fundamentally different platform from the DL360 and DL380. Where the DL380 Gen10 tops out at 56 cores dual-socket (28+28) and 3 TB memory, the DL560 Gen10 carries up to 112 cores across four sockets and up to 6 TB memory with LRDIMMs (12 TB with HPE Persistent Memory on L-series Cascade Lake CPUs). It is the HPE Gen10 platform for workloads that don't scale horizontally - the workloads where you need a single OS instance to see all the cores and all the memory.\u003c\/p\u003e\u003cp\u003eHonest framing on the 4-socket decision: most enterprise workloads don't require 4-socket servers. Dual-socket platforms (DL380, DL360) handle the vast majority of virtualization, database, and application serving workloads at materially lower cost and complexity. The DL560 makes sense when:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eA specific workload requires scale-up rather than scale-out.\u003c\/strong\u003e SAP HANA on a single certified appliance. Oracle Database Enterprise where licensing economics favor fewer sockets with more cores each. Microsoft SQL Server Enterprise where per-core licensing makes a single high-core-count server cheaper than multiple smaller ones.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eThe application is not horizontally scalable.\u003c\/strong\u003e Legacy enterprise applications, in-memory analytics platforms, or single-instance databases that cannot be sharded across nodes.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMaximum single-chassis memory capacity is a genuine architectural requirement.\u003c\/strong\u003e 6 TB in a 2U chassis is meaningful when the working set has to fit in a single server's RAM.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePer-socket Oracle\/SQL licensing creates the right economics.\u003c\/strong\u003e Oracle Database Enterprise charges per physical core; a 4-socket server with 4x 24-core CPUs licenses 96 cores under one server count. Two 2-socket servers with the same cores license the same 96 cores but count as two servers - a discussion to have with your Oracle licensing team before committing to architecture.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf your workload can run across multiple dual-socket nodes without licensing penalty or architectural friction, the DL380 Gen10 is almost always more cost-efficient. The DL560 is a precision tool for specific scale-up requirements, not a default upgrade from DL380.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 8 SFF Bays\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA\/NVMe hot-swap bays in the front of the chassis (Drive Box 1). The DL560 Gen10 chassis supports field upgrades to 16 or 24 SFF via additional Drive Box 2 and Box 3 kits - if your build needs more than 8 bays, the 24-Bay variant is the right starting point rather than upgrading later. The 8-Bay configuration is correctly sized for the common 4-socket workload pattern: OS plus application binaries plus hot dataset staging, expecting primary data to live on SAN, NFS, or distributed file system.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen10 SFF portfolio: SAS SSDs in mixed-use and read-intensive endurance tiers (480 GB through 7.68 TB), SATA SSDs for cost-optimized boot\/OS roles, SAS HDDs at 10K and 15K for moderate-IOPS data, NVMe SSDs via the 6SFF+2NVMe drive cage option, and self-encrypting drive (SED) variants for compliance-regulated deployments.\u003c\/p\u003e\u003cp\u003eCommon DL560 8-Bay storage profiles in production:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSAP HANA appliance.\u003c\/strong\u003e 2x SATA SSDs in RAID 1 for OS, 6x mixed-use SAS SSDs in RAID 10 for HANA log and shared volumes. Primary HANA data volumes mirror to external NetApp or HPE Primera storage; local SSDs handle log persistence and warm-data staging.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eOracle Database with ASM on SAN.\u003c\/strong\u003e 2x SAS SSDs in RAID 1 for OS plus Oracle Grid Infrastructure binaries, 6 bays available for local Fast Recovery Area or archive log staging. Primary database storage on Fibre Channel or iSCSI SAN via the HPE FC HBA in PCIe expansion.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMission-critical VMware cluster node.\u003c\/strong\u003e 2x SSDs in RAID 1 for ESXi boot. Remaining 6 bays unused or populated for vSAN cache tier. Primary VM storage on shared SAN datastore. The DL560's 4-socket compute drives high VM density per host with the storage layer abstracted via vSphere.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSQL Server Enterprise consolidation host.\u003c\/strong\u003e 2x SSDs in RAID 1 for OS, 2x SSDs in RAID 1 for tempdb, 4x SAS SSDs in RAID 10 for log files. Primary SQL data on SAN. The 8-bay configuration is sufficient for SQL's local-disk patterns when primary data is networked.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMicrosoft Hyper-V or VMware HCI candidate.\u003c\/strong\u003e When 8 SSDs are configured as the storage tier for a 4-socket HCI host, expect to provision high-endurance SAS SSDs and pair with an HBA-mode controller (E208i-a) rather than hardware RAID. The DL560's 4-socket compute justifies the per-node cost when extreme VM density requires fewer, larger HCI nodes.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eThe HPE M.2 SSD enablement option mounts boot drives in a PCIe slot or on the CPU mezzanine board, freeing all 8 SFF bays for data. For DL560 production builds, M.2 boot is the recommended pattern - the 8-bay storage budget is already tight against scale-up workload patterns and consuming 2 bays for OS boot mirroring is wasteful. We include the M.2 enablement kit by default on DL560 quotes unless customer specifies otherwise.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL560 Gen10 supports the full Gen10 Smart Array family plus the MR-series controllers that are specific to higher-drive-count and high-IOPS workloads:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 (2 GB FBWC).\u003c\/strong\u003e The mainstream production controller. Full hardware RAID 0\/1\/5\/6\/10\/50\/60, 2 GB flash-backed write cache. Right pick for the 8-bay configuration when traditional hardware RAID is the storage model. FBWC battery is a wear item with roughly 5-year service life - we disclose battery state on every quote.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 (4 GB FBWC).\u003c\/strong\u003e Premium controller. Same RAID modes, larger cache, supports tri-mode SAS\/SATA\/NVMe lanes. Specify when write workload is heavy enough to pressure the 2 GB cache - common for SQL Server log files or Oracle redo logs on local storage.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P824i-p MR Gen10 (4 GB cache, CacheCade).\u003c\/strong\u003e MR-series controller introduced with Gen10 for high-drive-count and CacheCade-accelerated workloads. 24 internal SAS lanes, 12G SAS, CacheCade SSD acceleration for HDD pools. Relevant on the 24-Bay DL560 more than the 8-Bay; available here for builds that anticipate later expansion to 16 or 24 SFF.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a SR Gen10 (HBA mode).\u003c\/strong\u003e The HBA controller for software-defined storage workloads (vSAN, Ceph, ZFS, Storage Spaces Direct). No hardware RAID; clean SAS pass-through. Right pick when the storage abstraction is the hypervisor or distributed file system, not the controller.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eS100i SR Gen10 (chipset software RAID).\u003c\/strong\u003e Acceptable for OS boot mirroring; not appropriate for production data on a 4-socket platform.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required when any P-series performance RAID controller is installed. We include the battery in every quote that specifies a P-series controller. On a DL560 build with the P824i-p MR, confirm CacheCade SSD requirements at quote time - the MR controller's value depends on the CacheCade configuration matching the workload.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors and Memory\u003c\/h2\u003e\u003cp\u003e1, 2, or 4 sockets of Intel Xeon Scalable in the LGA 3647 Purley platform. The 4-socket configuration requires the HPE DL5x0 Gen10 CPU Mezzanine Board Kit (872222-B21 for 1st Gen, P07991-B21 v2 for 2nd Gen support) - this is a separate board carrying sockets 3 and 4 plus 24 additional DIMM slots. Production DL560 deployments are almost always 4-socket; 2-socket DL560 configurations exist but the platform's value proposition is the 4S scale-up. If the design only needs 2 sockets, the DL380 Gen10 is a better fit at significantly lower cost.\u003c\/p\u003e\u003cp\u003eBoth 1st Generation Intel Xeon Scalable (Skylake-SP) and 2nd Generation (Cascade Lake-SP) are supported. Mixing 1st and 2nd Generation CPUs is not supported - all installed processors must be from the same generation. Cascade Lake brings DDR4-2933 support (vs. DDR4-2666 on Skylake), HPE Persistent Memory support, and the M and L series CPUs with extended memory ceiling capability.\u003c\/p\u003e\u003cp\u003eCPU options for production 4-socket builds:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eGold 6230 (20 cores, 125W, DDR4-2933).\u003c\/strong\u003e Common production sweet spot - 80 cores total at 4S, manageable thermal envelope, balanced single-thread performance. Right pick for general 4-socket virtualization and database consolidation.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eGold 6248 (20 cores, 150W, DDR4-2933).\u003c\/strong\u003e Higher base frequency than 6230 at the cost of higher TDP. 80 cores total. Good fit for Oracle and SQL Server where single-thread performance matters within the per-core licensing model.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eGold 6248R (24 cores, 205W, DDR4-2933).\u003c\/strong\u003e 96 cores total at 4S. Higher TDP - 4x 205W in a 2U chassis is thermally aggressive and requires confirmation of inlet temperature spec and PSU sizing. We validate thermal headroom on every 6248R-class quote.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePlatinum 8280 (28 cores, 205W, DDR4-2933).\u003c\/strong\u003e 112 cores total - the maximum core count for DL560 Gen10. Same thermal considerations as 6248R. Right pick when maximum cores in a single server is the requirement, typically driven by Oracle or SQL Server licensing economics.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePlatinum 8276M \/ 8276L (28 cores, M\/L SKUs).\u003c\/strong\u003e Extended memory ceiling - M-series enables 2 TB per socket (8 TB platform), L-series enables 4.5 TB per socket with Persistent Memory. Required for memory configurations beyond the standard 6 TB LRDIMM ceiling.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eMemory: 48 DDR4 DIMM slots total - 12 per CPU across 4 sockets. Six memory channels per CPU at 2 DPC. Maximum 3 TB with 64 GB RDIMMs, 6 TB with 128 GB LRDIMMs, up to 12 TB with HPE Persistent Memory on L-series CPUs. HPE DDR4 Smart Memory required for rated speed operation - third-party DDR4 drops to DDR4-2400 regardless of CPU rated speed, same documented HPE behavior as the rest of the Gen10 line. RDIMM and LRDIMM cannot be mixed; balanced symmetric population across all populated sockets required for optimum performance.\u003c\/p\u003e\u003cp\u003eFull 48-DIMM population at 2 DPC drops memory speed by one bin under DIMM-population rules (DDR4-2933 capable DIMMs run at DDR4-2666 at 2 DPC on supported CPUs). For maximum memory bandwidth, populate at 1 DPC (24 DIMMs total, 6 per CPU) - this is the configuration HPE recommends for SAP HANA and other bandwidth-sensitive workloads.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eFlexibleLOM mezzanine for primary networking - same architecture as the DL360 and DL380 Gen10. Networking options span 1 GbE quad-port, 10 GbE SFP+ dual or quad-port, 10 GBASE-T dual-port, 25 GbE SFP28 dual-port, and 10 GbE plus 100 GbE converged. The DL560 has FlexibleLOM standard (not via consumable riser like the DL160), and it doesn't consume any PCIe expansion slot - this is one of the platform's value points against alternatives.\u003c\/p\u003e\u003cp\u003ePCIe expansion: up to 8 PCIe 3.0 slots maximum with primary + secondary + tertiary risers installed. The slot map depends on CPU count and riser configuration:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003ePrimary riser - 3 slots, always available.\u003c\/strong\u003e Standard with the chassis.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSecondary riser - 3 slots, requires 2nd CPU populated.\u003c\/strong\u003e Standard riser kit options include x8\/x8\/x8 or x8\/x16\/x8 configurations. Slimline riser variant (873418-B21) provides NVMe slimline connections but no additional PCIe slots.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eTertiary riser - 2 slots, requires 2nd CPU populated AND only 2 PSUs installed.\u003c\/strong\u003e The tertiary riser physically conflicts with the 3rd and 4th PSU positions - 4-PSU configurations cannot accommodate the tertiary riser. For 4-PSU builds, the maximum is 6 PCIe slots; for 2-PSU builds, the full 8 slots are available.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThis PSU-vs-tertiary-riser tradeoff is specific to the DL560 chassis and matters at design time. For workloads that need both 4 PSUs (high-TDP 4-socket configurations) AND 8 PCIe slots (many adapters), the DL560 cannot deliver both - this is one of the few hard architectural limits on the platform. Most production builds prioritize the 4-PSU redundancy and accept 6 slots.\u003c\/p\u003e\u003cp\u003eGPU support: the DL560 Gen10 supports 1-2 single-width GPU accelerators in the right riser configurations. It is not a primary GPU compute platform - if AI training or heavy GPU virtualization is the workload, the HPE Apollo or DL380 Gen10 with 2x double-width GPU is a better fit. The DL560's GPU support is for selective acceleration alongside its 4-socket CPU workload, not as a primary GPU host.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 5 with Silicon Root of Trust\u003c\/h2\u003e\u003cp\u003eSame iLO 5 management architecture as the rest of the Gen10 line. iLO Standard ships with the hardware on refurbished units; iLO Advanced licensing is typically a separate cost when needed for full graphical remote KVM, virtual media mounting, Active Health System telemetry, and Workload Advisor recommendations. On a 4-socket mission-critical platform, iLO Advanced is rarely optional - we'll quote it explicitly with any DL560 build.\u003c\/p\u003e\u003cp\u003eSilicon Root of Trust is standard - the same hardware-anchored chain of trust starting from iLO 5 silicon, verifying iLO firmware, BIOS, and OS bootloader against cryptographic measurements. For SAP HANA, Oracle, and SQL Server deployments subject to compliance audit (SOC 2, PCI-DSS, HIPAA, FedRAMP), Silicon Root of Trust delivers documented platform-attestation evidence that's required in modern compliance frameworks. This is one of the genuine value points of buying into Gen10 at the 4-socket tier.\u003c\/p\u003e\u003cp\u003eNUMA topology visibility through iLO 5 and HPE OneView is meaningful on a 4-socket platform. Workload placement across 4 sockets is consequential - cross-socket memory access (CPU 1 reading CPU 4's memory) incurs latency penalty versus same-socket access. iLO 5 provides the topology data; the workload (hypervisor NUMA scheduling, database affinity settings, OS process binding) does the actual placement. For SAP HANA and Oracle in particular, NUMA tuning is a standard part of production deployment.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies, 1 to 4 PSUs depending on configuration. A fully-populated DL560 with 4x Gold 6248 (4x 150W = 600W CPU), 48 DDR4 DIMMs (approximately 150-200W), and 8 SAS SSDs (approximately 80W) plus fans and overhead draws approximately 1,200-1,500W sustained. With 4x Platinum 8280 at 205W each (820W CPU alone), the draw rises to approximately 1,500-1,800W sustained.\u003c\/p\u003e\u003cp\u003ePSU sizing recommendations by configuration:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 800W Flex Slot PSU (low-TDP 4-socket).\u003c\/strong\u003e Adequate for 4x 125W CPU configurations (Gold 6230 class) with modest memory and storage. Marginal headroom; not recommended for production HA.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 1600W Flex Slot Titanium PSU (typical production).\u003c\/strong\u003e Standard production redundant configuration for most DL560 builds. 1600W PSUs require high-line input (200-240VAC) - confirm rack PDU and circuit capacity. Provides full redundancy at all common CPU configurations including 205W Platinum.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e4x 1600W Flex Slot Titanium PSU (maximum redundancy).\u003c\/strong\u003e 2+2 redundancy at high TDP. Required when high availability and high TDP combine. Trades off the tertiary PCIe riser as discussed in the Networking section.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003ePower redundancy at 4-socket scale matters more than at dual-socket scale - the workloads that justify a DL560 (SAP HANA, Oracle, mission-critical SQL) are workloads where unplanned downtime has documented cost. Take the redundant PSU configuration on every production DL560 build.\u003c\/p\u003e\u003cp\u003eInlet temperature spec: 10°C to 35°C standard, with ASHRAE A3 (40°C) and A4 (45°C) support on selected configurations. At 4-socket high-TDP, the thermal envelope is real - confirm rack cooling and inlet temperature for the specific CPU SKU at quote time. We validate thermal configurations as part of every DL560 quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL560 Gen10 Fits in 2026\u003c\/h2\u003e\u003cp\u003eSame generational positioning as the rest of the Gen10 line. Launched in 2017, Cascade Lake-refreshed in 2019, two generations behind DL560 Gen11 (Sapphire Rapids \/ Emerald Rapids 4-socket, DDR5, 2023-2024). The platform is widely deployed in production at scale across enterprise SAP HANA, Oracle, and mission-critical virtualization deployments - HPE firmware updates continue under standard lifecycle, broad parts availability for both new and refurbished.\u003c\/p\u003e\u003cp\u003eWhat's specific to the DL560 in 2026: the platform is mature, the workloads it serves haven't fundamentally changed (SAP HANA still scales up, Oracle licensing economics still favor fewer sockets with more cores, SQL Server Enterprise per-core licensing still benefits from consolidation), and the per-core acquisition cost is meaningfully lower than Gen11 for the same workload envelope. For organizations adding 4-socket capacity to existing SAP HANA, Oracle, or SQL Server consolidation deployments where standardization on Gen10 reduces operational complexity, the DL560 Gen10 8-Bay delivers genuine work at significantly reduced cost versus the Gen11 alternative.\u003c\/p\u003e\u003cp\u003eThe framework is the same as the rest of HPE Gen10: this is mature platform with one generation of headroom in front of it, deployed widely, well-understood. Not the newest, not obsolete, the right tool for specific workload patterns when budget is a meaningful design constraint.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e4-socket configurations require the CPU Mezzanine Board Kit.\u003c\/strong\u003e This is a separate part (872222-B21 for 1st Gen, P07991-B21 for 2nd Gen support). A 2-socket DL560 without the mezzanine board is supported but rarely the right design choice - if 2 sockets are sufficient, use a DL380.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e4x 1600W PSU and tertiary PCIe riser are mutually exclusive.\u003c\/strong\u003e Maximum 6 PCIe slots with 4 PSUs, maximum 8 PCIe slots with 2 PSUs. Production HA builds typically take 4 PSUs and accept 6 slots.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e48 DIMM slots at 2 DPC drop memory speed by one bin.\u003c\/strong\u003e Full 48-DIMM population runs DDR4-2933 capable DIMMs at DDR4-2666. For HANA or bandwidth-sensitive workloads, populate at 1 DPC (24 DIMMs) for full speed.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMixing 1st and 2nd Gen Xeon Scalable not supported.\u003c\/strong\u003e All four sockets must be same-generation CPUs. This applies across the Gen10 platform and is enforced at boot.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSame Gen10 generational caveats apply.\u003c\/strong\u003e PCIe Gen3 (not Gen4), DDR4-2933 ceiling, iLO Advanced licensing typically separate, FBWC battery as a wear item, third-party DDR4 limited to DDR4-2400 regardless of CPU. The DL380 Gen10 canonical covers these in detail and they apply identically here.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e4-socket TDP and thermals require validation.\u003c\/strong\u003e 4x 205W Platinum in a 2U chassis is thermally aggressive. Confirm inlet temperature spec, rack cooling capacity, and rack PDU sizing before deployment. We validate thermal configurations as part of every quote.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNot a GPU compute platform.\u003c\/strong\u003e The DL560's PCIe slot map and thermal budget are not designed for primary GPU workloads. For GPU compute, the HPE Apollo or DL380 Gen10 with double-width GPU is the right answer.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SAP HANA scale-up appliances (HANA-certified)\u003c\/td\u003e    \u003ctd\u003e❌ Workloads that scale horizontally (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Oracle Database Enterprise large-instance consolidation\u003c\/td\u003e    \u003ctd\u003e❌ General-purpose virtualization (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SQL Server Enterprise per-core consolidation\u003c\/td\u003e    \u003ctd\u003e❌ Large local storage requirement above 8 SFF (use DL560 24-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Mission-critical extreme VM density per host\u003c\/td\u003e    \u003ctd\u003e❌ Budget-constrained dual-socket-sufficient projects\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ In-memory analytics requiring 4-6 TB single-server RAM\u003c\/td\u003e    \u003ctd\u003e❌ Primary GPU compute workloads (use Apollo)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Per-socket licensing economics (Oracle, SQL Server)\u003c\/td\u003e    \u003ctd\u003e❌ Workloads requiring PCIe Gen4\/Gen5 (use Gen10+ or Gen11)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 24 SFF bays for high-density local storage alongside 4-socket compute?\u003c\/strong\u003e → \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-24-bay-2-5-drives\"\u003eDL560 Gen10 24-Bay 2.5\"\u003c\/a\u003e - same 4-socket platform, 3x the SFF bay count\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDual-socket is sufficient?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e - significantly lower cost and complexity at the dual-socket tier\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same 4-socket 2U tier?\u003c\/strong\u003e → Dell PowerEdge R840 - 2U 4-socket Purley on the Dell side, same generation, equivalent workload positioning\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed PCIe Gen4 and DDR5 at 4-socket?\u003c\/strong\u003e → Contact us for DL560 Gen11 availability when budget allows the generational step\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eDL560 configurations start with a design conversation. Tell us the workload (SAP HANA \/ Oracle \/ SQL Server \/ virtualization \/ in-memory analytics), licensing context (per-core, per-socket, ULA), CPU and core target, memory target including any Persistent Memory requirement, storage configuration (local SSD pattern plus external SAN\/NFS), PSU redundancy preference, PCIe expansion requirements, and quantity. We respond within 24 hours with a validated configuration including thermal and power-budget confirmation. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951273074887,"sku":"BP-013622","price":984.9,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-dl560-gen10-8-bay-25-drives-736155.png?v=1765539690"},{"product_id":"server-design-lab-hpe-dl560-g10-24-bay-2-5-drives","title":"HPE ProLiant DL560 Gen10 24-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL560 Gen10 24-Bay 2.5\" pairs HPE's 4-socket flagship compute platform with maximum SFF storage density - twenty-four 2.5\" hot-swap bays in a 2U chassis alongside up to four Intel Xeon Scalable processors, 48 DDR4 DIMM slots, 6 TB memory ceiling with LRDIMMs, FlexibleLOM networking, iLO 5 with Silicon Root of Trust, and up to 4 HPE Flex Slot power supplies. This is a deliberately specialized configuration: 4-socket compute for scale-up workloads combined with 24-bay SFF storage for high-density database, analytics, or HCI data that lives locally rather than on a SAN.\u003c\/p\u003e\u003cp\u003eFor the full DL560 Gen10 platform documentation - including the honest framing on when 4-socket compute is and isn't the right call, Section 12 platform vocabulary (CPU\/memory\/PCIe\/management), and Dell PowerEdge R840 cross-vendor reference - see the \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eDL560 Gen10 8-Bay 2.5\"\u003c\/a\u003e canonical. This page focuses on what's specific to the 24-bay variant: when 24 SFF bays alongside 4-socket compute is the right tool, the bay-count-driven workload patterns, and the storage controller and power decisions that change at 24 bays.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units. The 24-bay configuration benefits from extra design discussion - 4-socket compute plus 24 SSDs in 2U is genuinely dense and the architectural choices have downstream operational consequences worth getting right at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen 24 SFF Bays + 4-Socket Makes Sense\u003c\/h2\u003e\u003cp\u003eThe 24-Bay DL560 is a deliberately narrow configuration. Most 4-socket workloads (SAP HANA, Oracle Database, mission-critical virtualization, SQL Server Enterprise) don't need 24 local SFF drives - they either use a SAN for primary storage or a smaller number of high-performance local SSDs alongside networked storage. The DL360-class 8-Bay DL560 is the right answer for most of those builds.\u003c\/p\u003e\u003cp\u003eThe 24-Bay DL560 earns its place when both 4-socket compute AND high-density local SSD storage are genuine requirements. The specific scenarios:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSAP HANA with large local SSD persistence layer.\u003c\/strong\u003e HANA in-memory databases benefit from local NVMe\/SSD for log persistence and warm-data tiering rather than depending on SAN latency for log writes. 24 SFF bays alongside HANA-scale memory (3-6 TB DDR4 + up to 12 TB Persistent Memory on L-series CPUs) enables a complete in-memory plus fast-persistence architecture in a single chassis. The persistence layer fits in the chassis instead of crossing the SAN, which matters for HANA savepoint and log-replay latency.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eOracle Database with local ASM diskgroups.\u003c\/strong\u003e Oracle RAC or large-instance Oracle databases where the design choice is local SSD storage rather than SAN. 24 SAS SSDs in ASM disk groups deliver high IOPS and predictable latency without the SAN dependency. Common when SAN is unavailable, undesirable for licensing\/cost reasons, or simply when the database team has decided ASM-on-local-SSD is the operational pattern they want to standardize on.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSQL Server Enterprise with extensive tempdb and log staging on local SSDs.\u003c\/strong\u003e Per-core SQL Server licensing economics already favor consolidation on 4-socket compute; pairing with 24 high-endurance SSDs lets the entire tempdb plus transaction log infrastructure live on local NVMe\/SAS rather than crossing the SAN. Datafile-on-SAN plus tempdb-and-logs-on-local-SSD is a documented Microsoft pattern for performance-sensitive SQL Server deployments.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHigh-density VMware HCI or vSAN ReadyNode at 4-socket scale.\u003c\/strong\u003e vSAN ReadyNode configurations at 24 SFF bays with 4-socket compute deliver high VM density per host. Fewer, larger HCI nodes reduce vSphere license count (which is per-CPU socket) and rack footprint. The 24-bay DL560 is at the high end of the vSAN ReadyNode footprint and works well when the goal is consolidating to the fewest hosts possible.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eIn-memory analytics with large local hot-data tier.\u003c\/strong\u003e Analytics workloads (Splunk, Elasticsearch hot-tier, in-memory data grids) that need both maximum processing capacity (4-socket) and large local SSD datasets that don't fit entirely in DRAM but are too latency-sensitive for SAN. 24 SAS SSDs as a tiered hot-data layer behind in-memory analytics is a meaningful configuration.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMicrosoft Storage Spaces Direct (S2D) at 4-socket scale.\u003c\/strong\u003e S2D requires HBA-mode storage and benefits from high drive counts per node for performance scaling. 24 NVMe or SAS SSDs in a 4-socket S2D node delivers a high-density HCI design with the per-node compute headroom to host many workloads.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf either the 4-socket compute or the 24-bay storage capacity is more than the workload actually needs, a different platform delivers better economics. The DL380 Gen10 24-Bay covers high-density storage at the dual-socket tier; the DL560 Gen10 8-Bay covers 4-socket compute with modest local storage. Pay for both 4-socket and 24-bay only when both are genuine requirements.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 24 SFF Bays\u003c\/h2\u003e\u003cp\u003eTwenty-four 2.5\" SAS\/SATA\/NVMe hot-swap bays across three drive boxes (Box 1, Box 2, Box 3) in the front of the chassis. With the full 24-bay configuration populated, the optional Universal Media Bay (front display port plus optical drive) is not supported - the media bay occupies the same physical position as one of the drive boxes. Production 24-bay builds typically don't need the media bay; remote iLO 5 access covers the operational requirements that the media bay served on earlier platforms.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen10 SFF portfolio: SAS SSDs (mixed-use and read-intensive endurance tiers, 480 GB through 7.68 TB), SATA SSDs for cost-optimized roles, SAS HDDs at 10K and 15K for moderate-IOPS data, NVMe SSDs via specific drive cage and riser combinations (see NVMe section below), and self-encrypting drive variants for compliance-regulated deployments. Per-drive type mixing is supported subject to controller capability.\u003c\/p\u003e\u003cp\u003eRAID guidance at 24 SFF bays: RAID 6 is appropriate for capacity-optimized SAS\/SATA SSD pools where rebuild windows on individual drive failure need to be tolerated; RAID 10 is appropriate for write-intensive workloads where the 50% capacity overhead is acceptable in exchange for write performance and shorter rebuild windows; RAID 50 or RAID 60 across multiple sub-pools (e.g. 2x RAID 6 of 12 drives, striped) balances rebuild scope against usable capacity. We discuss RAID layout in every 24-Bay quote.\u003c\/p\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eM.2 boot via the HPE M.2 SSD enablement option is strongly recommended at 24 bays - consuming 2 bays for OS boot mirroring wastes meaningful storage capacity in a configuration that exists specifically for high-density local SSD. M.2 boot mounts in a PCIe slot or on the CPU mezzanine board and frees all 24 SFF bays for data. Standard on our 24-Bay DL560 quotes unless customer specifies otherwise.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers at 24-Bay Scale\u003c\/h2\u003e\u003cp\u003eAt 24 SFF bays, the storage controller decision matters more than at 8 bays - controller capability, RAID overhead, and write-cache sizing become primary design factors rather than secondary considerations:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 (4 GB FBWC).\u003c\/strong\u003e The standard production controller for the 24-Bay configuration. 4 GB flash-backed write cache absorbs burst writes across the larger drive pool, tri-mode SAS\/SATA\/NVMe support handles mixed drive types. Full hardware RAID 0\/1\/5\/6\/10\/50\/60. Right pick for traditional hardware RAID across 24 SAS SSDs.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P824i-p MR Gen10 (4 GB cache, CacheCade).\u003c\/strong\u003e MR-series controller with 24 internal SAS lanes - the controller is purpose-designed for 24-drive configurations. CacheCade SSD acceleration accelerates HDD pools when the drive mix includes both SSD and HDD. The right controller when the deployment uses dedicated CacheCade SSDs to front a larger HDD pool, or when maximum lane count matters for sustained throughput.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a SR Gen10 plus additional E208 (HBA mode).\u003c\/strong\u003e For software-defined storage workloads (vSAN, Ceph, ZFS, Storage Spaces Direct) at 24-bay scale. Multiple HBA controllers may be required to deliver pass-through for all 24 bays; we'll spec the right combination at quote time based on backplane configuration.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 (2 GB FBWC).\u003c\/strong\u003e Supported on the 24-bay configuration but the 2 GB cache is smaller than ideal for 24 SSDs under heavy write load. Acceptable for primarily read-heavy or moderate-write workloads; for write-intensive workloads the P816i-a is the better default.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required when any P-series performance RAID controller is installed. At 24 bays the battery is essentially mandatory - write workload at this drive count makes write-cache protection a hard requirement. We include the battery on every 24-Bay quote with a P-series controller. On P824i-p MR builds, confirm CacheCade SSD requirements at quote time - the MR controller's value depends on the CacheCade SSD configuration matching the workload's read\/write profile.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNVMe at 24 Bays\u003c\/h2\u003e\u003cp\u003eThe DL560 Gen10 supports up to 12 NVMe SSDs (half of the 24-bay backplane) with the right combination of NVMe drive cages, PCIe risers, and Smart Array controllers. NVMe at this drive count requires PCIe lane budget that competes with other expansion (the 4-port NVMe Mezzanine card on the CPU mezzanine board doesn't consume PCIe slots but is limited to 8 NVMe drives; beyond that requires PCIe slot consumption).\u003c\/p\u003e\u003cp\u003eCommon NVMe configurations on the 24-Bay DL560:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e8 NVMe + 16 SAS\/SATA SFF.\u003c\/strong\u003e NVMe via the mezzanine card (no PCIe slot consumption), remaining 16 bays via SAS\/SATA on a P816i-a or HBA. Typical hot\/warm storage tiering pattern.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e12 NVMe + 12 SAS\/SATA SFF.\u003c\/strong\u003e Maximum NVMe configuration via PCIe slot consumption for additional NVMe lanes. Higher-bandwidth tier for performance-critical local storage paired with bulk SAS\/SATA. Verifies feasibility at quote time given competing PCIe demand.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e24 SAS\/SATA SFF.\u003c\/strong\u003e All-SAS or all-SATA configuration with no NVMe. Simpler PCIe planning; appropriate when NVMe-tier performance isn't the design requirement.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eFor most production 24-Bay DL560 workloads, all-SAS-SSD is the right answer - the per-drive performance of modern SAS SSDs is high enough that the NVMe step-up isn't required, and the SAS-only configuration simplifies PCIe planning meaningfully. If NVMe is a genuine workload requirement, we'll engineer the riser and controller combination at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling at 24-Drive Scale\u003c\/h2\u003e\u003cp\u003eA fully-populated DL560 Gen10 24-Bay with 4x Gold 6248 (4x 150W = 600W CPU), 48 DDR4 DIMMs (approximately 150-200W), and 24 SAS SSDs (approximately 240W) plus fans and overhead draws approximately 1,400-1,700W sustained. With 4x Platinum 8280 at 205W each (820W CPU alone) and 24 NVMe SSDs, the draw rises to approximately 1,800-2,000W sustained.\u003c\/p\u003e\u003cp\u003eAt this power envelope, 1600W Titanium PSUs are mandatory and 4-PSU configurations are typically required for production HA. Recall from the canonical that 4x 1600W PSUs and the tertiary PCIe riser are mutually exclusive - on the 24-Bay configuration, 4-PSU is typically the right choice (high TDP plus production HA) and the platform delivers 6 PCIe slots maximum rather than 8.\u003c\/p\u003e\u003cp\u003e1600W Flex Slot Titanium PSUs require high-line input (200-240VAC) - confirm rack PDU and circuit capacity before deployment. We validate power budgets including PDU phase balance for every 24-Bay DL560 quote.\u003c\/p\u003e\u003cp\u003eThermal envelope: 24 SAS SSDs plus 4 high-TDP CPUs in 2U is thermally aggressive. Inlet temperature spec of 10°C to 35°C standard applies but at the upper limit (32-35°C inlet), confirm specific CPU SKU support against the HPE thermal matrix. ASHRAE A3\/A4 support is configuration-specific at this density; we validate thermal headroom on every quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSame 4-socket platform limitations as the canonical 8-Bay.\u003c\/strong\u003e 4x 1600W PSU and tertiary PCIe riser mutually exclusive; full 48-DIMM population drops memory speed one bin; 1st and 2nd Gen Xeon Scalable cannot be mixed; 4-socket TDP requires thermal validation; not a primary GPU compute platform. See the DL560 Gen10 8-Bay canonical for full Section 12 platform vocabulary.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eUniversal Media Bay not supported with full 24-bay population.\u003c\/strong\u003e The media bay occupies the same physical position as one of the three drive boxes. Production 24-bay builds don't typically need the media bay; remote iLO 5 access covers the same operational requirements.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNVMe at full 24-bay scale is PCIe-budget-limited.\u003c\/strong\u003e Maximum 12 NVMe drives requires PCIe slot consumption beyond the 4-port mezzanine card. NVMe beyond 8 drives competes with FlexibleLOM, storage controller, and any other expansion - we engineer this carefully at quote time.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eStorage controller decision matters more at 24 bays.\u003c\/strong\u003e The P408i-a (2 GB cache) is supported but undersized for write-intensive workloads at 24 SSDs. P816i-a (4 GB) is the standard recommendation; P824i-p MR for CacheCade-accelerated workloads. The wrong controller choice at 24 bays produces measurable performance loss under load.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSingle-PSU operation not appropriate.\u003c\/strong\u003e The 24-Bay DL560 draws 1.4-2.0 kW sustained - single PSU is not a production configuration at this power level. Take redundant PSU (2x or 4x 1600W) on every production build.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSame Gen10 generational caveats apply.\u003c\/strong\u003e PCIe Gen3, DDR4-2933 ceiling, iLO Advanced licensing typically separate, FBWC battery as a wear item, third-party DDR4 limited to DDR4-2400 regardless of CPU. The DL380 Gen10 canonical and DL560 Gen10 8-Bay canonical cover these in detail and they apply identically here.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server is right for\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SAP HANA with large local SSD persistence layer\u003c\/td\u003e    \u003ctd\u003e❌ 8 SFF bays sufficient alongside 4-socket (use DL560 8-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Oracle Database with local ASM diskgroups\u003c\/td\u003e    \u003ctd\u003e❌ Dual-socket sufficient with 24 SFF (use DL380 24-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SQL Server Enterprise with local tempdb\/log on SSD\u003c\/td\u003e    \u003ctd\u003e❌ SAN-only storage architecture (use DL560 8-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ vSAN ReadyNode at 4-socket consolidation\u003c\/td\u003e    \u003ctd\u003e❌ Budget-constrained projects\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ High-density in-memory analytics with local hot tier\u003c\/td\u003e    \u003ctd\u003e❌ Workloads requiring more than 12 NVMe drives\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Storage Spaces Direct (S2D) at 4-socket scale\u003c\/td\u003e    \u003ctd\u003e❌ Primary GPU compute workloads (use Apollo)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e8 SFF bays sufficient alongside 4-socket compute?\u003c\/strong\u003e → \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eDL560 Gen10 8-Bay 2.5\" (canonical)\u003c\/a\u003e - same 4-socket platform at lower cost when local storage requirement is modest\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDual-socket with 24 SFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003eDL380 Gen10 24-Bay 2.5\"\u003c\/a\u003e - 24 SFF capacity at the dual-socket tier, significantly lower cost\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 16 SFF bays at dual-socket?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e - the dual-socket sweet spot for medium-density SFF storage\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same 4-socket 2U tier?\u003c\/strong\u003e → Dell PowerEdge R840 - 2U 4-socket Purley on the Dell side, equivalent positioning, supports up to 24 SFF in similar configurations\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed PCIe Gen4 and DDR5 at 4-socket?\u003c\/strong\u003e → Contact us for DL560 Gen11 availability when budget allows the generational step\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003e24-Bay DL560 configurations are sufficiently specialized that we recommend a design conversation before hardware selection. Tell us the workload (SAP HANA \/ Oracle \/ SQL Server \/ vSAN \/ analytics \/ S2D), licensing context, CPU and core target, memory target including any Persistent Memory requirement, storage architecture (drive type mix, RAID layout, NVMe requirement), controller preference (P816i-a vs P824i-p MR vs HBA), PSU redundancy preference, PCIe expansion requirements, and quantity. We respond within 24 hours with a validated configuration including thermal, power-budget, and PCIe-budget confirmation. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951273173191,"sku":"BP-013583","price":2000.6,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/1800x1200_6.png?v=1765539691"},{"product_id":"hpe-proliant-dl380-gen10-8-bay-build-your-own","title":"HPE ProLiant DL380 Gen10 8-Bay 2.5\" Drives","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 is the workhorse of the HPE enterprise server lineup — a 2U dual-socket rack server that has been the most widely deployed HPE platform in enterprise datacenters worldwide for the better part of a decade. Built on Intel Xeon Scalable processors (both 1st Gen Skylake and 2nd Gen Cascade Lake depending on configuration), the DL380 Gen10 covers an exceptional range of workloads: virtualization, database serving, NAS and SAN storage, analytics, and general enterprise application hosting. If you are buying HPE and haven't narrowed down to a specific model, the DL380 Gen10 is almost always where the conversation starts.\u003c\/p\u003e\u003cp\u003eThe 8-Bay 2.5\" configuration is the compute-first variant — eight SFF hot-swap bays for local SSD storage alongside the full dual-socket DL380 platform. It's the right starting point for virtualization hosts, database servers, and compute-primary deployments where moderate local SSD storage is needed but bulk storage lives on a SAN or NAS.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eGen10 vs. Gen10+ vs. Gen9 — the positioning:\u003c\/strong\u003e Gen10 (2017–2019) is the current production-tier secondary market platform — mature, well-supported, excellent ROI. Gen10+ (2021) brings Ice Lake Xeon (3rd gen Scalable), PCIe Gen4, and extended lifecycle — at meaningfully higher acquisition cost. Gen9 (2014–2016) is the previous generation equivalent of the Dell 13th gen — significantly lower cost, but the same platform age caveats apply. We offer all three and will recommend the right one for your lifecycle and budget at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHPE Platform Vocabulary — Key Differences from Dell\u003c\/h2\u003e\u003cp\u003eIf you're more familiar with Dell PowerEdge, the HPE equivalents are:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eiLO (Integrated Lights-Out)\u003c\/strong\u003e = iDRAC. iLO 5 is the Gen10 management controller — equivalent to iDRAC9 in capability. iLO Advanced license = iDRAC9 Enterprise (remote KVM, advanced features). iLO Standard ships by default and lacks remote console access.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Smart Array\u003c\/strong\u003e = PERC RAID controllers. P408i-a (2 GB cache) ≈ PERC H730P. P816i-a (4 GB cache) ≈ PERC H740P. E208i-a (no cache) ≈ PERC H330 \/ HBA330.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eFlexibleLOM (FlexLOM)\u003c\/strong\u003e = OCP mezzanine slot. Primary NIC connectivity goes here — same concept as Dell's OCP 3.0 slot.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Persistent Memory (NVDIMM)\u003c\/strong\u003e = Optane PMem equivalent (supported on Gen10 with 2nd Gen Xeon Scalable).\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eDual Intel Xeon Scalable processors — the DL380 Gen10 supports both 1st Generation (Skylake, launched 2017) and 2nd Generation (Cascade Lake, launched 2019) Xeon Scalable depending on the specific configuration. Up to 28 cores per CPU on Skylake, up to 28 cores per CPU on Cascade Lake (though higher core count SKUs are available). TDP range from 85W Bronze\/Silver through 205W Platinum.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eOur recommendation:\u003c\/strong\u003e 2nd Generation Cascade Lake processors wherever the application profile justifies them — better IPC, hardware-level speculative execution mitigations, higher memory speed support (2933 MT\/s vs. 2666 MT\/s on Skylake at 1 DPC), and Optane PMem compatibility. For workloads where the generation distinction doesn't matter — file serving, backup, dev\/test — 1st Gen Skylake at lower acquisition cost is fully adequate.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eHeatsink requirement for high-TDP CPUs:\u003c\/strong\u003e Processors above 150W require high-performance heatsinks. HPE uses a different heatsink designation than Dell — confirm with our team at quote time for any configuration with 165W+ processors.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots — 12 per CPU, six memory channels per socket. Maximum 3 TB with LRDIMMs. HPE Persistent Memory (NVDIMM-N) supported on Gen10 with 2nd Gen Xeon.\u003c\/p\u003e\u003cp\u003eFull 2 DPC population (2 DIMMs Per Channel) maximizes memory bandwidth — the same channel utilization logic as Dell R640. At 2 DPC on most Cascade Lake SKUs, speed settles at 2666 MT\/s — the bandwidth gain from all six channels running at 2666 MT\/s consistently outperforms partial population at 2933 MT\/s for memory-bound workloads. For 1st Gen Skylake configurations, maximum memory speed is typically 2666 MT\/s at 1 DPC, 2400 MT\/s at 2 DPC.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eiLO Advanced Memory Error Detection:\u003c\/strong\u003e The DL380 Gen10's iLO 5 provides per-DIMM memory error logging and predictive failure analytics — a meaningful advantage for large-memory configurations where early DIMM failure detection avoids unplanned downtime.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 8 SFF Bays\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA hot-swap bays on a Smart Array backplane. Same general storage flexibility as the Dell R640\/R740 8-Bay SFF configurations — SAS SSDs for performance, SATA SSDs for mixed workloads, SAS HDDs for capacity, and mixed configurations for tiered approaches.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eHPE NVMe implementation note:\u003c\/strong\u003e The DL380 Gen10 supports NVMe via PCIe riser expansion (NVMe add-in cards) rather than native backplane NVMe in the standard 8-bay configuration. HPE introduced native backplane NVMe more comprehensively in the Gen10+ generation. For NVMe-primary storage architectures, the Gen10+ configurations or dedicated NVMe PCIe cards are the paths. We'll advise on the best NVMe approach for your specific design at quote time.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eHPE Secure Encryption:\u003c\/strong\u003e The DL380 Gen10 supports drive-level encryption through the Smart Array controller — a compliance feature worth noting for regulated data environments.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eM.2 boot drives:\u003c\/strong\u003e HPE Gen10 supports M.2 SATA\/NVMe boot drives via an optional M.2 enablement kit — the equivalent of Dell's BOSS module. We include this on builds where OS isolation from the data storage pool is a requirement. Confirm at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eSmart Array RAID Controllers\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB Flash-backed Write Cache, FBWC):\u003c\/strong\u003e Our top recommendation for production workloads with meaningful write I\/O. The P816i-a supports up to 16 drives and uses flash-backed write cache — no battery to replace, capacitor-backed with NAND persistence. Equivalent in capability to Dell's H740P. For database workloads, vSAN with hardware RAID, and any application where write latency matters, start here.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a (2 GB FBWC):\u003c\/strong\u003e Standard production recommendation for mixed or read-dominant workloads. Supports up to 8 drives in the internal configuration. The most common controller we quote for general-purpose DL380 Gen10 deployments.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a (no cache, HBA mode):\u003c\/strong\u003e For software-defined storage (vSAN, Ceph, Windows Storage Spaces) where the software layer manages redundancy. Passes drives directly to the OS without hardware RAID. Required for vSAN deployments — same reasoning as Dell's HBA330.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003eHPE FBWC vs. Dell battery-backed cache:\u003c\/strong\u003e HPE uses Flash-Backed Write Cache (FBWC) — capacitor-backed with NAND persistence — instead of Dell's battery-backed NV cache. In practice, both protect cached writes through power events. FBWC has the advantage of no battery replacement cycle (typical HPE battery backup module lifespan is 3 years; FBWC capacitors are rated for the server's lifecycle). We consider them equivalent in production protection capability.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking\u003c\/h2\u003e\u003cp\u003eFlexibleLOM mezzanine slot plus PCIe expansion slots. Standard networking options:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Ethernet 10Gb 2-port 562SFP+ FLR-SFP+ Adapter:\u003c\/strong\u003e Our standard recommendation for most DL380 Gen10 deployments — dual-port 10 GbE via FlexLOM, leaving PCIe slots available for storage and other expansion.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Ethernet 25Gb 2-port 640SFP28 Adapter:\u003c\/strong\u003e For high-throughput virtualization nodes, storage-serving configurations, or environments where 10 GbE is insufficient. Recommended for vSAN all-flash nodes and NVMe-backed storage configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Ethernet 10Gb 4-port 561FLR-T RJ45 Adapter:\u003c\/strong\u003e For environments requiring copper 10 GbE — common in deployments without SFP+ switching infrastructure.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003ePower Supplies\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot hot-swap redundant PSUs. Standard options for the DL380 Gen10:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 500W Flex Slot Platinum:\u003c\/strong\u003e For Silver\/Bronze CPU configurations with moderate drive population and no GPU. Tight headroom for fully-loaded Gold\/Platinum builds.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 800W Flex Slot Platinum:\u003c\/strong\u003e Our standard recommendation for dual Gold\/Platinum builds with full memory and SSD drive population. Adequate for most general-purpose configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 1600W Flex Slot Titanium:\u003c\/strong\u003e For GPU configurations, high-TDP CPU combinations, or fully-loaded storage configurations. Titanium efficiency delivers measurable savings in large-scale deployments.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003ePower planning:\u003c\/strong\u003e A dual Gold 6230 (Cascade Lake) configuration with 24 DIMMs and 8x SAS SSDs draws approximately 420–520W at peak. For GPU-equipped configurations, factor in GPU TDP using the same methodology as Dell builds — CPU TDP × 2 + memory + drives + GPU TDP, sized to 70–75% PSU capacity for longevity.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement — iLO 5\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eiLO 5 Standard\u003c\/strong\u003e ships on all DL380 Gen10 units. It provides basic hardware monitoring, SNMP alerting, and SSH\/REST API access — but without remote KVM console. For production datacenter deployment, iLO 5 Advanced license is required.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eiLO 5 Advanced (required for production):\u003c\/strong\u003e Adds remote KVM console (HTML5 and Java), virtual media, HPE Intelligent Provisioning (OS deployment without physical media), Agentless Management Service integration, Active Health System logging, and Silicon Root of Trust. The equivalent of Dell iDRAC9 Enterprise. We include the iLO Advanced license on every production build we configure.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eSilicon Root of Trust:\u003c\/strong\u003e The DL380 Gen10 introduced HPE's Silicon Root of Trust — firmware signed at the silicon level, preventing unsigned firmware from running. Equivalent in concept to Dell's Silicon Root of Trust in iDRAC9, and a meaningful security advantage over Gen9 and earlier platforms.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eTrusted Platform Module (TPM):\u003c\/strong\u003e Optional TPM 2.0 module — include it. Same compliance framework requirements as Dell deployments (NIST, CMMC, FedRAMP).\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 2U rack — 86.8mm H × 447mm W (slightly wider than Dell 2U), chassis depth approximately 748mm\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe slots:\u003c\/strong\u003e Up to 8 PCIe 3.0 slots depending on riser configuration — comparable to the Dell R740\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eCPU hot-plug:\u003c\/strong\u003e Not supported\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePlatform maturity:\u003c\/strong\u003e Gen10 launched in 2017. Mature platform with stable firmware, strong parts availability, and HPE Pointnext support still available. No immediate end-of-support pressure for most configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eAccessories:\u003c\/strong\u003e HPE Ball Bearing Sliding Rail Kit (Gen8\/9\/10 2U SFF) for rack mounting; HPE Gen10 Security Bezel\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 8-Bay 2.5\" is the right HPE platform for the widest range of enterprise workloads — virtualization hosts, database servers, application serving, and compute-primary deployments where moderate local SSD storage covers the need and bulk storage lives on a SAN or NAS. It's the HPE equivalent of the Dell R640, and for shops standardized on HPE infrastructure and iLO management, it's typically the default recommendation for new workloads that don't have specific requirements driving them to the DL360 (1U), DL380 Gen10+ (newer Xeon), or DL560 (4-socket).\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e VMware vSphere and vSAN nodes, Microsoft Hyper-V clusters, SQL Server and Oracle deployments, general enterprise application serving, VDI workloads, and any compute-primary deployment where HPE is the preferred platform.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 1U?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed more SFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay\u003c\/a\u003e or \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003eDL380 Gen10 24-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed LFF capacity drives?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed Ice Lake Xeon \/ PCIe Gen4?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eBudget-first, shorter lifecycle?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay\u003c\/a\u003e — significantly lower cost, same generational caveats as Dell 13th gen\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003eRefurbished context for 2026:\u003c\/strong\u003e The DL380 Gen10 launched in 2017 and has been in production environments for 7–9 years. Platform maturity is excellent — HPE Pointnext support still active, firmware stable, parts plentiful. For workloads that don't require Ice Lake (Gen10+) or PCIe Gen4, the Gen10 delivers excellent ROI at secondary market pricing. We test every refurbished DL380 Gen10 through HPE's Active Health System diagnostics and verify iLO firmware, Smart Array firmware, and drive health before shipment.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eThis server excels at\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ VMware vSphere \/ vSAN nodes\u003c\/td\u003e\n\u003ctd\u003e❌ 1U form factor required (use DL360 Gen10)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Microsoft Hyper-V clusters\u003c\/td\u003e\n\u003ctd\u003e❌ Ice Lake \/ PCIe Gen4 needed (use Gen10+)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ SQL Server and enterprise databases\u003c\/td\u003e\n\u003ctd\u003e❌ More than 8 SFF bays needed\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ General enterprise application serving\u003c\/td\u003e\n\u003ctd\u003e❌ LFF capacity drives required\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ VDI and high-density virtualization\u003c\/td\u003e\n\u003ctd\u003e❌ Budget-primary shorter lifecycle\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your workload, memory target, storage configuration, iLO Advanced licensing preference, and quantity. Our account team returns a validated configuration with formal pricing within 24 hours. Volume pricing at 5 units and above. We can quote both Gen10 and Gen10+ side-by-side if you want to evaluate the generational premium against your lifecycle requirements.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951302926535,"sku":"BP-013539","price":669.87,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-8-bay-25-drives-589493.png?v=1765539743"}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/collections\/hpe-gen-10-servers-185452.jpg?v=1765540187","url":"https:\/\/wholesaleservers.com\/collections\/hpe-gen10-servers.oembed","provider":"Wholesale Servers","version":"1.0","type":"link"}