A business server should be selected around what it needs to do, how many users or systems depend on it, and how the environment is expected to grow.
Practical example: small business virtualisation server
Choose the exact server only after balancing the workload and required resilience.
Scenario: A 35-user business wants one physical server for directory services, an accounting application, file services and three small virtual machines.
The design starts with the workload rather than a model number. Memory is budgeted for the hypervisor, each virtual machine and growth. Storage is separated into performance and capacity requirements. RAID is selected for availability, while a separate backup target is retained for recovery. Dual power supplies and multiple network interfaces are considered if the required server supports them.
Decision: The final server should be chosen only after checking processor capacity, DIMM population rules, drive bays and backplane, RAID controller, network interfaces, PSU configuration and the supported expansion path.
Common mistakes and selection checklist
Common mistakes
- Choosing a server from the processor model alone and treating memory, storage, networking and resilience as secondary details.
- Sizing only for today's workload and leaving no practical memory, drive or expansion path.
- Assuming RAID, redundant power supplies or virtualisation removes the need for a separate backup and recovery plan.
What happens if you get it wrong?
The server can be technically functional but still perform poorly, run out of expansion capacity early, or have a single failure that interrupts several business services at once.
Selection checklist
- List the workloads, users, applications and virtual machines the server must support.
- Check CPU sockets and cores, memory capacity and population rules, drive bays and backplane, RAID controller and network interfaces.
- Decide what must remain operational after a drive, PSU or network-path failure.
- Confirm backup, restore and recovery requirements separately from server redundancy.
- Check warranty, supported expansion and the expected three-to-five-year growth path.
Start with the workload
Identify whether the server will support file sharing, applications, databases, virtual machines, storage services or a combination of workloads. Different workloads place different demands on CPU, memory and storage.
Choose the processor around the workload
CPU core count, clock behaviour and the requirements of the software should be considered together. More cores are not automatically better if the workload does not use them effectively.
Plan memory carefully
RAM can become a limiting resource, particularly when a server hosts multiple applications or virtual machines. Consider current requirements and expected growth.
Plan storage around performance and resilience
Storage capacity is only one part of the decision. Drive type, performance, RAID configuration and backup strategy also affect the overall solution.
Consider networking
The server network interface should match the network and workload. Higher-speed networking may be appropriate where large amounts of data move between servers, storage and users.
Think about redundancy
For important workloads, redundant power supplies, storage protection and appropriate networking can reduce the impact of component failures.
- Workload
- CPU requirements
- Memory requirements
- Storage capacity and performance
- RAID and resilience
- Network connectivity
- Power redundancy
- Future expansion
A balanced server is usually more useful than an oversized server with resources that the workload cannot use.
Confirm the exact product specification, supported configuration and compatibility before ordering. Platform generation, firmware, licences and optional components can change what a product supports.