Backup Server Build Guide: Hardware for Veeam and Proxmox Backup Server

Why a Backup Server Has Inverted Priorities

A production server is optimised for fast random access to a working set of data. A backup server is optimised for swallowing large volumes of data sequentially during a nightly window, holding it safely for weeks or months, and reading it back in bulk during a restore. Almost every decision follows from that.

Veeam and PBS Want Different Storage Layers

This is the decision that has to be made before ordering the server, because it determines which RAID controller goes in it. The two most common backup platforms for small and mid-sized businesses have opposite storage preferences.

Putting ZFS on top of hardware RAID, or Veeam on a raw HBA with no cache, are both mistakes that produce a working but underperforming or fragile backup target. Our PERC guide and RAID versus ZFS comparison cover the reasoning; the practical point is to decide on the software first and specify the controller to match.

Sizing for Proxmox Backup Server

PBS is deceptively light on paper and genuinely demanding in practice, for one reason: deduplication. Every backup is split into chunks, hashed, and compared against an index of everything already stored. That index lives in RAM, and the chunk store on disk is accessed randomly rather than sequentially.

• RAM: 4GB base plus 1GB per terabyte of datastore. This is Proxmox's own guidance and it is the most under-provisioned resource on PBS builds. A 40TB datastore wants around 44GB before ZFS ARC is counted. Under-provision it and garbage collection and verify jobs take days.
• CPU: 4 cores minimum, 8 recommended. Chunk hashing during backup, verification, and garbage collection are all CPU-bound. More cores shorten the backup window when jobs run concurrently.
• If the datastore is on hard drives, add a ZFS special device. A mirrored pair of enterprise SSDs holding the pool's metadata turns the random-access chunk lookups from an HDD seek storm into SSD reads. Proxmox describes this as highly recommended for HDD pools; in practice it is the difference between a usable PBS and one that grinds.
• OS on separate disks. A small mirrored boot pair, never on the backup pool. A BOSS card with two M.2 drives is the clean solution on Dell hardware.
• RAIDZ2 for pools above roughly 24TB usable. Mirrors for smaller pools where restore speed matters more than capacity.

Sizing for Veeam

Veeam separates the backup server (the management and job engine) from the repository (where backups land). On a small deployment they're the same machine, and it's the repository that drives hardware choice.

• CPU: 8 cores minimum for the backup server role, 16GB RAM plus around 500MB per concurrent job. Small environments under five workloads can run on 6 cores and 16GB.
• Hardware RAID with battery-backed write cache. This is Veeam's stated recommendation for both performance and reliability. RAID 6 for the repository volume, with the controller's write-back cache enabled.
• ReFS on Windows or XFS on Linux for the repository filesystem. Both support Veeam's fast clone feature, which makes synthetic full backups near-instant and dramatically reduces the storage a retention chain consumes.
• A Linux hardened repository is the current best practice for ransomware resistance: immutable backups that even an administrator account can't delete inside the retention window. It runs on the same hardware, just with Linux instead of Windows on the repository.
• Veeam now backs up Proxmox VE directly via its Proxmox plug-in, so a Veeam repository can serve a mixed VMware, Hyper-V, and Proxmox estate from one place.

How Much Storage You Actually Need

The mistake is sizing to the data you're protecting. A backup server holds multiple restore points, and the retention policy determines how many. The working rule:

Then convert usable to raw. RAID 6 or RAIDZ2 across eight drives loses two to parity, so 30TB usable needs roughly 40TB raw, which is eight 6TB drives or six 8TB drives. Leave headroom: both ZFS and ReFS degrade badly above 80 percent full, and a backup pool that fills up stops backing up.

Network: The Backup Window Bottleneck

A nightly backup window has a fixed length. If the data doesn't fit through the network in that time, the job runs into production hours. On 1GbE, sustained throughput tops out around 100MB/s, which moves about 350GB an hour. Adequate for a handful of small VMs; not for a 10TB estate.

• 10GbE for anything beyond about 20 VMs, on both the backup server and the hosts it pulls from
• A dedicated backup VLAN, so nightly bulk traffic doesn't compete with anything else. Our switch guide covers the segmentation.
• Restore speed is the network too. The day you need a full VM back, the same link that took all night to back it up is what you're restoring through. Size for the restore, not just the backup.

Three Reference Builds

The Off-Site Copy

One backup server on-site satisfies two of the 3-2-1 rule's three requirements. The off-site copy is what survives fire, theft, flood, or ransomware that reaches the backup server. Three practical patterns for a business in Qatar:

• A second, smaller backup server at another site, receiving nightly replication. PBS remote sync and Veeam backup copy jobs both do this natively. For a business with two locations, this is the most controllable option.
• Object storage in a local or regional cloud region, as a backup copy target. Both platforms support S3-compatible targets, and immutable object storage adds a ransomware-resistant layer.
• Rotated removable media, for businesses without a second site or suitable bandwidth. Less elegant, but a drive in a safe at a director's home is a genuine off-site copy.

Backup Servers in Qatar

• A dozen large hard drives generate real heat. A 12-bay LFF chassis full of 7,200rpm disks draws more power and runs warmer than the same chassis with SSDs. Hard drives are the component most sensitive to sustained heat, so this server belongs in the conditioned space, not the storeroom. Our cooling guide covers placement.
• The backup server needs the UPS too. A write interrupted mid-backup by a power cut can corrupt a chain. Size the UPS to include it, and configure shutdown so the backup server closes cleanly.
• Keep two spare drives on the shelf. Drives are the component that fails on a backup server, RAID 6 buys time for one replacement, and a spare in Doha beats a spare on a container ship.

Frequently Asked Questions

Can I use an old server as a backup server?

Yes, and it's one of the best uses for one. Backup workloads favour capacity and sequential throughput over clock speed, so a previous-generation 2U chassis with plenty of LFF drive bays is often better suited than a current 1U. Fit fresh drives, populate both PSU bays, and it will serve for years.

Should I use hardware RAID or ZFS for a backup server?

It depends on the software. Veeam wants hardware RAID with a battery-backed cache, presented as a block volume. Proxmox Backup Server is built on ZFS and needs an HBA with raw disk access. Decide the platform first, then specify the controller. Putting ZFS on hardware RAID or Veeam on a cacheless HBA both work badly.

How much RAM does Proxmox Backup Server need?

4GB for the OS plus roughly 1GB per terabyte of datastore, before ZFS cache. A 40TB datastore wants around 44GB or more. RAM is the most commonly under-provisioned PBS resource, and under-provisioning makes verify and garbage collection jobs run for days.

Do I need SSDs in a backup server?

For the boot drives, yes, a small mirrored pair. For PBS on hard drives, a mirrored pair of enterprise SSDs as a ZFS special device for metadata is strongly recommended. The bulk backup capacity itself is usually large-capacity SAS hard drives, since capacity per dirham matters more than IOPS in this role.

RAID 5 or RAID 6 for backups?

RAID 6 or RAIDZ2, without exception. Backup pools use the largest drives available, rebuilds on 12TB and larger disks take a day or more, and a second failure during that window on single-parity loses the array. Dual parity is the minimum for a pool whose whole purpose is to be the copy you fall back on.

Where can I buy a backup server in Qatar?

ServerDove supplies refurbished Dell and HPE LFF chassis configured for Veeam or Proxmox Backup Server, with the correct controller, enterprise SAS drives, and networking, delivered in Doha and across Qatar with local warranty.

Final Thoughts

A backup server is the one machine whose job is to be boring for years and then perform perfectly on the worst day. That argues for a simple design: a previous-generation chassis with many drive bays, large SAS drives in dual-parity, the controller your software actually wants, enough RAM for deduplication if you're running PBS, and a network fast enough to restore through.

Decide the software first. Everything else, from the controller to the drive layout, follows from whether the target will run Veeam or Proxmox Backup Server.