Installing Windows Server takes an hour. Living with the hardware choices underneath it takes five years. The RAID level, the drives, the controller and the disk layout are all decisions that are cheap on day one and expensive to change later - so decide them before the installer runs, not after.
Most office server pain is not caused by Windows. It is caused by decisions made before Windows was installed: a RAID level picked by habit, desktop drives in a 24x7 box, a data volume carved too small, no spare drive anywhere in the building. This guide walks through the decisions in the order you should make them - roles first, then RAID, then the controller and drives, then memory and power, and the layout written on paper - so the install you do once is the install you can live with. One line runs through every section, and it is worth saying at the start: RAID is not a backup. RAID keeps the server running when a drive dies. It does nothing at all when data is deleted, encrypted by ransomware or the building itself has a problem. Backup is a separate decision, and it gets its own section below.
Hardware questions have no answer until the role question is answered. A domain controller is a light job: it answers logon and DNS requests and sips resources. A file server cares about disk and network, not CPU. A Hyper-V host is the sum of every virtual machine it will carry, plus something for itself. A database server - SQL Server, or the database behind your accounting package - eats memory and disk speed all day. Write the roles down as a list, including the ones planned for next year. Almost every undersized server in a small office was bought for the roles of the day it was ordered, and every oversized one was bought from a brochure. The list also decides what comes later in this guide: RAID 10 earns its cost under a database, and is a luxury under a plain file share.
RAID joins several physical drives into one logical drive that Windows sees. The levels differ in what you trade: space, speed, or safety. RAID 0 stripes data across drives for speed and gives you zero protection - one dead drive takes everything, so it has no place under server data. RAID 1 mirrors two drives: half the space, simple, and the rebuild is quick. RAID 5 spreads data plus parity across three or more drives and survives one failure, but its rebuild on today's very large drives is a long, risky window. RAID 6 adds a second parity and survives two failures, which makes rebuilds far calmer with big drives. RAID 10 mirrors pairs and stripes across them: half the space, the best speed, the fastest rebuilds, and the standard answer for databases. The full honest tour of each level, with the failure stories, is in our companion guide on RAID levels. Capacity, so you can plan volumes before buying:
4 x 4 TB in RAID 5 = (4 - 1) x 4 TB = 12 TB usable4 x 4 TB in RAID 6 = (4 - 2) x 4 TB = 8 TB usable4 x 4 TB in RAID 10 = 4 x 4 TB / 2 = 8 TB usable2 x 4 TB in RAID 1 = 4 TB usableTwo quiet components decide most real-world server behaviour. The controller runs the array: a proper hardware RAID card carries its own processor and cache, and the cache is only safe with battery or flash protection behind it - an unprotected write-back cache can corrupt data the moment power fails. Windows Storage Spaces is the software alternative built into the server: no special card, and your drives stay readable on another Windows machine, but parity spaces write slowly and there is no cache safety net beyond a good UPS. The drives matter just as much. Desktop drives are built and rated for one PC working office hours; server and NAS drives are rated for 24x7 work, spinning neighbours and far larger yearly workloads, and they give up on a bad sector quickly (an error-recovery limit of a few seconds) instead of hanging for a minute or more - a hang that makes a RAID controller declare the drive dead. Buy drives rated for the job, and buy the spare at the same time as the array.
For most small-office roles, CPU is the least interesting number and memory is the one to get right. Working rules: a domain controller is comfortable with 8 to 16 GB; a file server wants enough for its cache, 16 to 32 GB in a busy office; a Hyper-V host needs the sum of its virtual machines' memory plus 4 to 8 GB for the host itself; and SQL Server will happily use every gigabyte you give it unless you set its maximum, which is by design. Leave roughly a third of your memory unassigned on day one - the roles always grow. On the ECC question, be honest about the grades: ECC memory corrects the single-bit errors that otherwise become silent corruption or a random crash, and on a machine that runs the whole office around the clock it is cheap insurance, provided the processor and board support it. It is not magic - it will not save you from a failing drive or a bad backup - but silent data corruption is a real, documented thing, and ECC is the standard server answer to it.
A server that loses power badly can lose the data being written at that moment, and dirty shutdowns are how filesystems and databases get hurt. Two layers protect you. A UPS sized for the server plus its switch - and set up to shut the server down cleanly when the battery runs low - turns a power cut into a non-event. Many real server chassis also offer dual power supplies: two independent PSU modules, so one can fail (or be replaced) while the server keeps running, ideally fed from two different circuits. Add hot-swap drive bays to the same thinking - a dead drive you can pull and replace without opening the box or powering down is the difference between a ten-minute job and an evening of downtime. None of this is glamorous, and all of it is cheaper than the first recovery bill.
Say it plainly, because this is the most expensive misunderstanding in small-office IT: RAID protects you from exactly one thing - a dead drive. Delete the wrong folder and RAID replicates the deletion across every drive instantly. Ransomware encrypts the array as happily as it encrypts a single disk. Fire, theft or a burst pipe takes the whole box, array and all. And if the RAID controller itself dies, a healthy set of drives can sit unreadable until a compatible controller is found. Backup is a different thing entirely: separate copies of the data, with older versions kept, with at least one copy outside the server - the classic shape is three copies, on two different media, with one offsite or offline. A NAS in another room, a cloud copy, or a rotated USB drive that is unplugged most of the time all count. Decide the backup target while you are planning the hardware, because the array layout and the budget both change once backup is real.
The last step costs nothing and saves the most regret. Before the Windows Server setup starts, write down the layout: which arrays exist, what volume each becomes, the size of the C: drive (be generous - 200 GB class for the OS volume is a comfortable modern default, because updates and logs only grow), where the data and the virtual machines live, and the drive letters and share names you will use. Changing a volume size later ranges from annoying to a full rebuild, and the time to discover that the data volume needed to be twice as big is now, on paper, where it is free. Keep the sheet with the server: model, serial numbers, warranty dates, RAID configuration, firmware versions. The next engineer - who may be you, at 2 AM, two years from now - will be grateful.
Server hardware and RAID explained live - the roles, the levels and the layout decisions - before the Windows Server install begins.
Watch Full VideoNo. RAID keeps the server running when a drive fails - that is all. It instantly replicates deletions and corruption to every drive, ransomware encrypts the whole array, and fire or theft takes the entire box. A backup is a separate copy of the data, with older versions, kept apart from the server - ideally one copy offsite or offline.
For most: RAID 1 (mirror) for a pair of SSDs holding the operating system, and RAID 10 for data drives when a database or virtual machines are involved - it is fast and rebuilds quickly. RAID 6 is the honest choice for large-capacity HDD arrays, because it survives two failures during the long rebuild. RAID 5 with very large modern drives leaves a long, risky rebuild window, and RAID 0 should never hold server data.
It is strongly recommended rather than strictly required. ECC corrects single-bit memory errors that otherwise cause silent data corruption or unexplained crashes, and it costs little more when the processor and board support it. For a machine the whole office depends on around the clock, it is cheap insurance - but it does not replace good drives or a real backup.