Speccing a Small-Business File and Directory Server

Most small businesses do not need a data center — they need one dependable machine that signs users in, serves files quickly, hosts a line-of-business application, and never becomes the day's emergency. That job description has not changed in twenty years, and it maps beautifully onto refurbished enterprise hardware, because the machine that does it well is defined by redundancy and memory, not by benchmark scores.

Start from the workloads

A directory service (Active Directory or an equivalent) is feather-light. File serving is I/O and network, barely CPU. A typical line-of-business app — accounting package, practice management, a small SQL database — wants memory and disk latency. Sum it up for a 10–50 seat office and the honest requirement is: 8–16 modern-ish cores, 64–128GB ECC RAM, mirrored fast storage for the app and VMs, larger protected storage for files, two power supplies, and a way to manage the machine when it is misbehaving at 7 a.m.

Why a tower usually wins here

Small offices rarely have a rack or a dedicated room, so acoustics decide the form factor. A Dell T630 or T430, or an HPE ML350 Gen9/Gen10, delivers full enterprise internals — dual sockets, ECC RDIMMs, hot-swap bays, redundant PSUs, iDRAC/iLO — with big slow fans that let it live in a storage room or under a counter without announcing itself.

The reference spec

CPU: one or two mid-range Xeons (an E5-2640 v4 class part per socket is ample; a single CPU is genuinely fine for 10–25 users). Memory: 64GB minimum, 128GB if the LOB app runs SQL. Storage: two enterprise SSDs in RAID1 on a cache-backed controller (H730/P440ar) for the OS, VMs and database; four to eight LFF drives in RAID6 for the file shares. Network: the built-in quad 1GbE is enough for most offices; add 10GbE only if the switch already speaks it. Power: dual PSUs on separate circuits if the building allows, feeding from a line-interactive UPS sized for a clean shutdown.

Virtualize even if there is one box

Run the roles as two or three VMs on a free hypervisor rather than directly on metal. The payoff is recovery: a failed application update rolls back with a snapshot, and if the chassis itself dies, the VMs restore onto any replacement hardware instead of requiring a same-model rebuild. One box, several small blast radii.

Backups are part of the server spec

Give backups their own storage that ransomware on the file share cannot casually reach: a separate backup server or NAS, plus an offsite or cloud copy of the irreplaceable sets. A common refurbished pattern is buying a second, cheaper chassis — an R440 or the previous tower — purely as the backup target. It is unglamorous and it is the part everyone thanks themselves for later.

Configured this way, a refurbished tower runs a small company for five-plus years, with every part — PSU, fan, drive, even a whole replacement motherboard — available cheaply the whole time. Boring, in the best possible sense.