The important question is not simply whether a drive is labelled HDD. The drive should be appropriate for the system, workload and storage architecture in which it will operate.
Practical example: NAS, DAS or SAN?
For shared office files, NAS is often the natural architecture to evaluate first.
Scenario: A 25-user office needs shared departmental files, central backup storage and controlled user access.
A NAS is a natural candidate because it provides file services over the existing network. A directly attached enclosure would tie the storage more closely to one host. A SAN would make more sense where servers require shared block storage, for example in a more complex virtualisation environment.
Decision: For this example, start by evaluating NAS capacity, drive type, network speed, snapshots and backup replication. Do not deploy SAN architecture merely because it sounds more enterprise.
Common mistakes and selection checklist
Common mistakes
- Choosing NAS, DAS or SAN because one architecture sounds more enterprise rather than because it fits the workload.
- Sizing storage only by terabytes and ignoring IOPS, throughput, network speed, snapshots and backup.
- Using one storage system as both primary data and the only backup copy.
What happens if you get it wrong?
Users can experience slow file access or applications can be constrained by the wrong storage path. More importantly, a storage failure or data-loss event can affect both production data and the supposed recovery copy.
Selection checklist
- Decide whether applications need file storage, block storage or storage attached to one host.
- Estimate current usable capacity and realistic growth.
- Identify performance, network and concurrency requirements.
- Check drive type, RAID options, snapshots and expansion.
- Design backup and off-system recovery independently.
Server storage
Server environments can involve multiple drives, storage controllers, RAID configurations and workloads that operate continuously. Drive selection therefore needs to consider the server platform and controller as well as capacity.
NAS storage
NAS drives are designed for storage systems that manage multiple drives and provide network-accessible storage. The intended NAS platform and its drive compatibility should be checked.
Capacity is not enough
Two drives with the same capacity can have different characteristics. Interface, performance characteristics, workload suitability and platform compatibility can all matter.
Check the complete storage system
The drive is only one part of the storage system. Consider the enclosure, controller, RAID configuration, cooling and backup strategy as well.
- Is the drive supported by the intended platform?
- What interface is required?
- What capacity is required?
- What workload will the drive support?
- Will the drive be part of a RAID array?
- What backup strategy protects the data?
Compatibility and intended use should be confirmed before selecting a drive.
Confirm the exact product specification, supported configuration and compatibility before ordering. Platform generation, firmware, licences and optional components can change what a product supports.