{"title":"Proliant DL560 Gen 10","description":"\u003cdiv class=\"flex flex-col text-sm pb-25\"\u003e\n\u003carticle data-turn=\"assistant\" data-scroll-anchor=\"true\" data-testid=\"conversation-turn-32\" data-turn-id=\"request-WEB:75984428-1564-4813-98ae-112929435150-85\" dir=\"auto\" class=\"text-token-text-primary w-full focus:outline-none [--shadow-height:45px] has-data-writing-block:pointer-events-none has-data-writing-block:-mt-(--shadow-height) has-data-writing-block:pt-(--shadow-height) [\u0026amp;:has([data-writing-block])\u0026gt;*]:pointer-events-auto scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]\" tabindex=\"-1\"\u003e\n\u003cdiv class=\"text-base my-auto mx-auto pb-10 [--thread-content-margin:var(--thread-content-margin-xs,calc(var(--spacing)*4))] @w-sm\/main:[--thread-content-margin:var(--thread-content-margin-sm,calc(var(--spacing)*6))] @w-lg\/main:[--thread-content-margin:var(--thread-content-margin-lg,calc(var(--spacing)*16))] px-(--thread-content-margin)\"\u003e\n\u003cdiv class=\"[--thread-content-max-width:40rem] @w-lg\/main:[--thread-content-max-width:48rem] mx-auto max-w-(--thread-content-max-width) flex-1 group\/turn-messages focus-visible:outline-hidden relative flex w-full min-w-0 flex-col agent-turn\" tabindex=\"-1\"\u003e\n\u003cdiv class=\"flex max-w-full flex-col gap-4 grow\"\u003e\n\u003cdiv class=\"min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+\u0026amp;]:mt-1\" data-message-model-slug=\"gpt-5-3\" dir=\"auto\" data-message-id=\"bb75132d-870a-4a64-9900-c78af5e7c39b\" data-message-author-role=\"assistant\"\u003e\n\u003cdiv class=\"flex w-full flex-col gap-1 empty:hidden\"\u003e\n\u003cdiv class=\"markdown prose dark:prose-invert w-full wrap-break-word dark markdown-new-styling\"\u003e\n\u003cp data-end=\"572\" data-start=\"523\"\u003e\u003cstrong data-end=\"572\" data-start=\"523\"\u003eHPE ProLiant DL560 Gen10 Custom Server Builds\u003c\/strong\u003e\u003c\/p\u003e\n\u003cp data-end=\"985\" data-start=\"574\"\u003eFor organizations running large virtualization clusters or data-intensive applications, the \u003cstrong data-end=\"694\" data-start=\"666\"\u003eHPE ProLiant DL560 Gen10\u003c\/strong\u003e delivers exceptional compute density in a \u003cstrong data-end=\"764\" data-start=\"737\"\u003e4-socket 2U rack server\u003c\/strong\u003e platform. Built for enterprise environments, it supports \u003cstrong data-end=\"856\" data-start=\"822\"\u003eIntel Xeon Scalable processors\u003c\/strong\u003e and massive \u003cstrong data-end=\"893\" data-start=\"869\"\u003eDDR4 memory capacity\u003c\/strong\u003e, making it ideal for analytics platforms, ERP systems, and high-performance virtualization.\u003c\/p\u003e\n\u003cp data-end=\"1267\" data-start=\"987\"\u003eOur \u003cstrong data-end=\"1029\" data-start=\"991\"\u003eBuild-Your-Own DL560 Gen10 servers\u003c\/strong\u003e allow you to tailor the hardware to your exact requirements. Select the processors, memory configuration, RAID controllers, and storage options needed to power demanding business workloads while maintaining scalability for future growth.\u003c\/p\u003e\n\u003cp data-is-only-node=\"\" data-is-last-node=\"\" data-end=\"1590\" data-start=\"1269\"\u003eWith strong performance, advanced security features, and enterprise-class reliability, the DL560 Gen10 is a powerful foundation for modern IT infrastructure.\u003c\/p\u003e\n\u003cp data-is-only-node=\"\" data-is-last-node=\"\" data-end=\"1590\" data-start=\"1269\"\u003eAt \u003cstrong data-end=\"1451\" data-start=\"1430\"\u003eWholesale Servers\u003c\/strong\u003e, each system is professionally tested and prepared for deployment in \u003cstrong data-end=\"1589\" data-start=\"1521\"\u003edata centers, enterprise networks, and advanced lab environments\u003c\/strong\u003e.\u003c\/p\u003e\n\u003c\/div\u003e\n\u003c\/div\u003e\n\u003c\/div\u003e\n\u003c\/div\u003e\n\u003cdiv class=\"z-0 flex min-h-[46px] justify-start\"\u003e\u003cbr\u003e\u003c\/div\u003e\n\u003cdiv class=\"mt-3 w-full empty:hidden\"\u003e\n\u003cdiv class=\"text-center\"\u003e\u003cbr\u003e\u003c\/div\u003e\n\u003c\/div\u003e\n\u003c\/div\u003e\n\u003c\/div\u003e\n\u003c\/article\u003e\n\u003c\/div\u003e\n\u003cdiv class=\"pointer-events-none h-px w-px absolute bottom-0\" data-edge=\"true\" aria-hidden=\"true\"\u003e\u003cbr\u003e\u003c\/div\u003e","products":[{"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"}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/collections\/proliant-dl560-gen-10-110629.webp?v=1765540187","url":"https:\/\/wholesaleservers.com\/collections\/hpe-proliant-dl560-gen10-build-your-own.oembed","provider":"Wholesale Servers","version":"1.0","type":"link"}