How to Choose a NAS: Bays, NVMe, Network and Platform

Choosing a NAS usually starts with a list of bays, cores and network speeds. The result is often a machine that does not match the workload. A better order is to define how long the data must stay online, how many clients read and write at the same time, and what is likely to be added in the next two years. Bays and ports are outcomes of those answers.

Calculate usable capacity first

Bays serve capacity and redundancy, not a headline number. A four-bay array using RAID 5 or RAID 6 loses capacity to parity, and a hot-spare drive reduces it further. Add the current data set, two years of growth, snapshots and backup space before choosing a chassis. A second copy on the same NAS is not a backup; it is another copy in the same failure domain.

The Y104A is an example of a mixed layout: four 2.5-inch or 3.5-inch bays plus four M.2 NVMe positions. Hard drives carry capacity and archive data; NVMe can hold hot data, virtual machines, metadata or a separate all-flash pool. The value is the mix of media, not the claim of eight drive positions.

Is NVMe a cache or a pool?

NVMe used as a read cache, write cache, metadata device and independent pool has four different failure and recovery paths. A read cache can often be removed; a write cache may hold data that has not reached the array. Plan the recovery path before adding flash.

For photo archives, documents and family backups, hard drives plus a small NVMe cache are usually enough. For virtual machines, databases or 4K editing proxies, a separate NVMe pool is a better fit. Check PCIe lanes, airflow and sustained write behaviour, not only the number of M.2 sockets.

Network ports shape daily use

2.5GbE has a line-rate ceiling of 2.5Gbps, about 312.5MB/s. 10GbE reaches about 1.25GB/s. Those are protocol-level figures; real file transfers are also limited by drives, SMB or NFS, switches, client NICs and concurrent access. For many homes and small offices, 2.5GbE already removes the gap between a mechanical array and a gigabit network. If the client is still on 1GbE, a 10GbE NAS will not make that client faster.

Dual 2.5GbE can provide link aggregation or separate management and storage traffic. Aggregation does not double a single connection, and its usefulness depends on the switch and operating system. Draw the network before choosing between 2.5GbE, 10GbE and 10G SFP+.

Platform and operating system

Low-power N100 and N150 platforms suit always-on file services, home clouds and light containers. An LGA1700 platform is a better fit for more virtual machines, transcoding or parallel work. If ZFS, ECC memory or heavier virtualisation is planned, verify CPU and board support instead of counting DIMM slots.

The operating system matters too. TrueNAS, Unraid, DSM and Proxmox with a virtual NAS have different requirements for disk passthrough, NIC drivers and boot devices. Select the software stack before the hardware, or you may discover that the NIC is unsupported, the HBA cannot be passed through, or the BIOS lacks the required boot option.

A practical selection order

1. List the current data, backup copies and two-year growth.
2. Choose the redundancy layout and calculate usable capacity.
3. Decide whether NVMe is cache, a system drive or a separate pool.
4. Choose 2.5GbE or 10GbE around the clients and switch, not the NAS alone.
5. Select the operating system and virtualisation stack before the platform.
6. Compare chassis, noise, power and delivery only after the first five steps.

If the bay count, network and software stack are already defined, send the requirement to service@maiyunda.com. We will check the complete configuration rather than quote a model in isolation.