The Ultimate Server Buying Guide for Australian Businesses

Choosing the right server can feel like decoding alphabet soup - CPU, RAM, RAID, VMs, Hyper‑V - but the decision you make will shape your business’s uptime, productivity, and security for years to come. To cut through the noise, we’ve created a practical guide tailored for Australian businesses.

We’ll break down the key factors to consider when selecting a server for the next five years from remote access and virtualisation to backups and the physical environment so you can make an informed choice with confidence.

Start with the Job Description: What Will the Server Do?

Before you compare specs, it is best to start by listing the services you’ll run. Most small and mid‑sized businesses use servers for core roles such as:

  • Active Directory (AD) for user identities and sign‑ons
  • DHCP for issuing network addresses to devices
  • IIS (or another web platform) for internal/external apps
  • File server duties for shared folders and documents

If you plan to virtualise these into virtual machines (VMs) - common for flexibility and isolation - your compute (CPU/RAM) and storage needs should be sized around the number of VMs and any line‑of‑business apps (accounting, ERP, databases, etc.).

Lifecycle

Servers run 24/7, so a well‑planned lifecycle is essential. The ideal lifecycle for a server is five years. Over time, components such as drives, fans, and power supplies face higher failure risk; vendors also wind down support for older models and operating systems, making patches and security updates harder to come by. Planning a five‑year refresh smooths budgets, lowers unplanned downtime, and keeps your platform within supported software windows.

Remote Access

Two flavours of remote access matter:

1) User access to apps/desktops
Staff can securely reach remotely accessible desktops or applications via VPN, Remote Desktop gateways, or virtual desktop infrastructure. That means no need to be physically in the office—handy for hybrid and multi‑site teams.

2) Administrative “out‑of‑band” access
Choose server hardware with a dedicated management interface (e.g., Dell iDRAC or HPE iLO) that works even if the operating system won’t boot. This lets you reach BIOS/UEFI, power cycle, mount ISO media, and recover after‑hours without driving to site.

The Two Big Specs: Compute and Storage

Most sizing boils down to compute (CPU and RAM) and storage (capacity, performance, protection).

Compute
  • RAM is often the first bottleneck in virtualised environments; each VM reserves memory. 
  • CPU cores/threads handle concurrent workloads; heavier apps (databases, analytics) and multiple VMs benefit from more cores.

List your initial VM roles (AD, DHCP, IIS, file server, line‑of‑business apps), then add a buffer for growth (test VMs, new tools). Err on the side of extra RAM at purchase; upgrading later is costlier and can be disruptive, especially with the current RAM shortage causing prices to skyrocket thanks to the demand from AI.

Storage
  • Headroom: Maintain ≥20% free space so routine maintenance (snapshots, updates, temp files) doesn’t push volumes into the red.
  • Media mix: Use SSDs for OS/app/VM disks (speed), HDDs for bulk file shares (economy).
  • Protection: In business servers, RAID is non‑negotiable—it protects against disk failure.

Common RAID options:

  • RAID 1 (mirroring): Simple redundancy; great for Operating systems volumes.
  • RAID 5 (striping with parity): Good capacity and single‑disk fault tolerance; rebuilds can be lengthy on large arrays.
  • RAID 10 (striped mirrors): Strong performance and resilience; ideal for VM/databases. 

Many vendors offer hardware RAID controllers (best for performance/reliability) and software RAID options (managed by the OS). Your choice depends on budget and workload—but for RAID 5/6, hardware controllers typically win.

Operating Systems

Chasing the very latest Operating System isn’t always best, a safer path is adopting a mature, supported release, then upgrading before end‑of‑life (EoL) to stay within the window for critical and security updates. This avoids early‑release bugs while keeping you protected.

If you’re still on older releases (e.g., Windows Server 2012/2012 R2), plan your migration proactively as there are several security flaws being exploited by hackers 

Virtualisation

If you run multiple Windows VMs, Microsoft Hyper‑V pairs neatly with Windows Server licensing:

  • Windows Server Standard includes rights for up to two Windows Server VMs per fully licensed host; Datacenter grants unlimited Windows Server VMs when all cores are licensed. This can significantly simplify costs in virtualisation‑heavy environments.
  • Management is approachable with Windows Admin Center and familiar tooling - handy for small teams.
Backups

A reliable backup you can actually restore is vital. A practical, layered plan:

  • Backup software: Veeam Backup & Replication is widely adopted and strong for VM‑level and file‑level backups.
  • Primary backup target: Use a NAS (e.g., QNAP) as your repository they are cost‑effective and fast for restores.
  • Offsite copies: Replicate backups offsite. QNAP’s QuObjects supports S3‑compatible object storage with immutability (Object Lock), which pairs well with Veeam to harden backups against ransomware.
Admin Remote Access

When a server hangs or won’t boot, out‑of‑band management lets you work below the OS:

  • Access BIOS/UEFI remotely, update firmware, and change boot order
  • Power cycle or hard reboot a stuck system
  • Mount remote media (ISO) to repair or reinstall

Set this up on day one, isolate it on a secure network, and keep firmware current—it’s the difference between a quick recovery and a long night.

The Physical Environment

A server isn’t just specs - it lives in a real room, with heat, dust, power fluctuations, and people.

Air-conditioning and temperature

Modern servers tolerate warmer conditions, but controlled temperature still matters. Ideally you want 18–27 °C inlet temperature ranges for IT equipment; targeting ~25 °C in a small server room or cabinet is practical for SMBs. Avoid unconditioned, enclosed spaces where temps spike. And don’t mount the indoor A/C unit directly above the rack - take this one from us - we have helped a client recover from disaster after a aircon unit leaked water over their server equipment.

Rack, power (UPS), and cabling
  • Rack: Keeps gear organised, secures equipment, and improves airflow.
  • UPS: Smooths power, protects from surges/outages, and enables clean shutdowns.
  • Cabling: Label and dress cables to avoid accidental disconnects and make diagnostics faster.
Networking

Ensure your switches, firewall, and Wi‑Fi match the server’s needs (Gigabit or better uplinks, VLANs for segmentation, and reliable internet if remote access is required). MFA on remote access is a must have default setting.

NAS and backups

Place your NAS near the server but consider separate power and, where feasible segmented networking for resilience. Schedule offsite replication, and test restores quarterly so that you know the backups work.

Noise and security

Rackmount servers are louder than tower units. Where possible, keep equipment in a locked rack it not only reduces office noise, it prevents accidental cable bumps, and keeps inquisitive fingers off power buttons.

A Simple Checklist

1. Start with what you’ve got
Before you dive into specs and shopping lists, take stock of your current setup. List out the services and VMs you’re running—Active Directory, DHCP, IIS, file servers, and any line-of-business apps. This baseline helps you understand what’s essential and what can evolve.
2. Think ahead
Growth happens fast. Will you need space for new apps? Test environments? Larger file shares? Estimating future needs now saves you from scrambling later.
3. Choose hardware with breathing room
When choosing CPU and RAM, don’t cut it too close. A little extra capacity goes a long way. And remember - RAM usually becomes the bottleneck before CPU does.
4. Design storage smartly

  • SSDs for speed, HDDs for bulk storage.
  • Protect your data with RAID: RAID 10 for performance-critical workloads, RAID 5 or 6 for capacity.
  • Keep at least 20% free space - your future self will thank you.

5. Backups matter Set up a solid chain: Veeam → QNAP NAS → Offsite with immutability. No shortcuts here.
6. Secure out‑of‑band management Enable it, lock it down, and make sure it’s not an open door.
7. OS strategy Stick with a mature version, patch monthly, and upgrade before end‑of‑life.
8. Don’t forget the room Rack, UPS, tidy cabling, and air-con. A clean, well-organized space isn’t just nice to look at—it prevents headaches down the road.

Common Pitfalls (and How to Dodge Them)
  • Under‑spec’d RAM: VMs crawl; prioritise memory headroom.
  • No RAID: A single‑disk failure shouldn’t take you offline.
  • Running too hot: Small rooms heat up quickly; monitor and cool 
  • Untested backups: A backup that can’t be restored isn’t a backup.
  • Latest OS on day one: Stick with stable releases; plan upgrades before they reach End of Life.
  • No out‑of‑band access: Set up iDRAC/iLO from the start.

If you are looking for a new server for your business, you can rely on FortiTech to get these fundamentals right meaning your team can get on with their jobs while we and your server do ours.