Xincuan Server | Enterprise Server Hardware Supplier
The Backup Server That Takes 14 Hours to Complete Is Not a Backup Problem. It Is a Hardware Problem.
A Veeam backup job that runs from 20:00 to 10:00 the next morning is not slow because of the backup software. It is slow because the backup repository server has four 7,200 RPM SATA drives in RAID 5 on a PERC H730 with 1 GB cache. The bottleneck is the hardware, not the software. This guide covers the server hardware decisions that determine whether your backup completes in the overnight window — or overflows into production hours and triggers a page to the infrastructure team.
Backup Server Hardware: The Three Bottlenecks
| Bottleneck | Common Mistake | Correct Configuration | Impact on Backup Window |
|---|---|---|---|
| Storage throughput | SATA HDDs in RAID 5 with 1 GB RAID cache. 200 MB/s write throughput on a 10 TB backup. | NVMe SSDs for the active backup tier. HDDs for the long-term retention tier. PERC H965i with 8 GB NV cache. | 10-hour backup reduced to 2 hours (5x throughput improvement) |
| Network throughput | 10GbE single port. 10 Gbps shared with production traffic. Backup data transfer rate: 800 MB/s. | 25GbE dedicated backup VLAN. Backup data transfer rate: 2.5 GB/s. | 3x throughput improvement on large datasets |
| CPU (deduplication and compression) | Underpowered CPU. Deduplication runs at 200 MB/s per core. 6-core CPU = 1.2 GB/s. | High-core-count CPU. Xeon Gold 6448Y (32 cores). 1 GB/s per core = 32 GB/s dedup throughput. | Dedup bottleneck eliminated. Backup window limited by storage throughput. |
Reference Design: Veeam Backup Repository Server
| Component | Selection | Quantity | Reason |
|---|---|---|---|
| Server | Dell R760 (2U, 24x 2.5-inch) | 1 | Sufficient bays for active + retention tiers |
| Alternative (higher density) | xFusion 5288 V7 (4U, 44x 3.5-inch + 4x NVMe) | 1 | Maximum HDD capacity for long-term retention |
| CPU | 2x Xeon Gold 6448Y (32 cores, 250W) | 2 per node | 32 cores = 32 GB/s Veeam dedup throughput. Matches NVMe write speed. |
| Memory | 256 GB (16x 16 GB DDR5, 1DPC) | 1 per node | Veeam recommends 8 GB + 1 GB per TB of backup data for metadata cache |
| Active Backup Tier (NVMe) | 8x Samsung PM9A3 7.68TB NVMe (RAID 10) | 8 drives | 30.7 TB usable. Backup writes land here at NVMe speed. Aged to HDD tier. |
| Long-Term Retention Tier (HDD) | 12x Toshiba MG10 20TB SAS HDD (RAID 6) | 12 drives | 200 TB raw, 160 TB usable. Backup files aged from NVMe tier. |
| OS Boot | Dell BOSS-N1 (2x 480 GB M.2 NVMe, RAID 1) | 1 | Boot volume does not consume front-panel bays |
| RAID/HBA | PERC H965i (16-port Gen5 tri-mode) | 1 | Single controller for NVMe + SAS HDD |
| Networking | 2x Intel E810-XXVDA2 (25GbE SFP28) | 2 adapters | 1 port dedicated backup VLAN, 1 port management |
| OS | Windows Server 2025 or RHEL 9 (XFS, ReFS 64KB block size) | – | ReFS 64KB for Veeam Fast Clone. XFS for immutable Linux repository. |
Sizing the Backup Server: How Many TB of Backup Data Can This Handle
| Backup Scenario | Source Data (Total VMs) | Full Backup Size (with 2:1 dedup) | Incremental Size (Daily) | Backup Window (This Server) | Retention on 160 TB HDD Tier |
|---|---|---|---|---|---|
| SMB (20 VMs, 5 TB total source) | 5 TB | 2.5 TB | 50 GB (1 percent change rate) | ~17 minutes (2.5 GB/s NVMe write) | ~640 days (160 TB / 250 GB/day incrementals) |
| Mid-Market (50 VMs, 20 TB total) | 20 TB | 10 TB | 200 GB | ~70 minutes | ~800 days |
| Enterprise (150 VMs, 80 TB total) | 80 TB | 40 TB | 800 GB | ~4.5 hours | ~200 days (scale-out to second node for longer retention) |
The NVMe-to-HDD Aging Strategy: Why Not All Backup Data Needs NVMe
The most recent 7 days of backups account for 95 percent of restore requests. Backups older than 30 days are restored less than 1 percent of the time. The NVMe active tier stores the last 7-14 days of backups. Veeam, Commvault, or a simple cron job with rsync ages backup files older than 14 days from the NVMe tier (RAID 10, 30 TB) to the HDD tier (RAID 6, 160 TB). Restores from the HDD tier are slower — 10 minutes vs 2 minutes for a 500 GB VM — but at a 95 percent hit rate on the NVMe tier, 95 percent of restores complete in under 2 minutes. The HDD tier exists for the 5 percent of restores that need data older than 14 days.
Compatible Backup Software
- Veeam Backup and Replication 12.x: ReFS 64KB block cloning (Fast Clone) on Windows Server. XFS reflink (immutable Linux repository) on RHEL 9. Object storage direct to S3-compatible targets for off-site copy.
- Commvault Complete Backup and Recovery: Deduplication database on NVMe tier for fastest synthetic full performance. HDD tier for long-term retention. Commvault supports block-level dedup across all tiers.
- Proxmox Backup Server 3.x: Native ZFS support on the backup server. NVMe Special Allocation Class for metadata and dedup table. HDD tier for bulk data storage. PBS dedup is content-defined chunking — CPU-intensive, scale cores accordingly.
Design Your Backup Infrastructure With Xincuan
We configure backup servers with factory-direct pricing, 3-year warranty, and global shipping. Our engineers can size your backup server based on your Veeam or Commvault deployment data — number of VMs, total source data, change rate, and retention requirements — to deliver a config that completes in your overnight window.
Request a backup server design consultation
Explore: Dell Servers | Storage | BOSS-N1