Compute, storage and continuity

Capacity you can actually use

Raw disk totals mislead. We size on usable capacity after protection overhead, against the performance your applications need and the growth you expect, so the first expansion is planned rather than forced.

Enterprise storage drives in a disk array

RAID is availability. Backup is recovery.

This distinction causes more data loss than any technical failure. RAID keeps a volume online when a disk dies. It does nothing about accidental deletion, file corruption, ransomware or the loss of the array, the rack or the building. Every storage design we produce treats protection and backup as two separate requirements with two separate budgets.

What the design accounts for

  • Usable capacity after RAID or other protection overhead
  • Performance required by the applications and databases using it
  • Expected growth over the planned service life
  • Retention and archive obligations
  • Recovery requirements and how they will be tested
  • Criticality of the data and what its loss would cost
What we do

Storage services

Sizing and architecture

NAS or SAN selected on capacity, performance and how it will be accessed.

Installation and configuration

RAID levels and storage pools configured deliberately, with the trade-offs explained.

Shares and permissions

Shared folders with role-based permissions rather than inherited sprawl.

Capacity and health monitoring

Disk health and utilisation tracked, with alerts before thresholds become incidents.

Replication

Replication to a secondary location where the recovery requirement justifies it.

Secure remote access

Where remote access to storage is required, configured without exposing it to the internet.

Common questions

NAS or SAN?

For most organizations of this size, a well-specified NAS is sufficient and far simpler to operate. SAN becomes worth its complexity when you have virtualization hosts needing shared block storage or performance requirements a NAS cannot meet. We will say plainly which applies.

What RAID level should we use?

It depends on capacity efficiency, rebuild risk and the performance profile. With large drives, rebuild times matter more than people expect, which affects the answer. We explain the trade-off rather than defaulting.

How much usable capacity will we get?

Less than the raw total, and the design states the real number. Protection overhead, filesystem overhead and the headroom needed for performance all reduce it.

Size your storage properly

Tell us roughly how much data you hold, how fast it grows and what has to be kept.

  • Reply within one working day
  • Usable capacity stated, not raw

We use your details only to reply to you. See our privacy policy.

Need a consultation?

Tell us what you are building.

Share the problem, the platform and the deadline. We will come back with an approach, a team and an estimate.