Skip to content

Servers, Backup & Disaster Recovery

NAS & File Servers

We build central file storage on NAS or a file server, with permissions at group level rather than per person, drive redundancy, and snapshots for fast recovery. Central storage does not replace backup: the offsite copy stays necessary, because redundancy protects against drive failure only.

Who it is for

  • Businesses with files scattered across user machines
  • Companies with large file volumes such as drawings or video
  • Organisations needing permissions per department
  • Sites where applications require a shared network path

When we are NOT the right choice

  • If all files can live in SharePoint without constraints
  • If there is no space with power and physical protection
  • If a NAS is wanted as the only backup copy

PROCESS

The process

Indicative times from signature of the proposal, subject to hardware availability. Every project is shaped to the size and the needs of the client.

  1. 01File and group inventory

    We record where files are, how much space they occupy, how fast they grow, and who should see what.Time: 2-5 working daysDeliverable: Data and permission map

  2. 02Sizing

    We calculate capacity with growth allowance and choose a redundancy scheme according to how critical the data is.Time: Alongside the studyDeliverable: Capacity and redundancy proposal

  3. 03Installation and permissions

    We build the structure and assign permissions to groups, never to individuals, because individuals change roles and leave.Time: 2-5 daysDeliverable: Folder structure with group permissions

  4. 04Snapshots and backup

    We enable snapshots for fast recovery from human error, and an offsite copy for the serious scenarios.Time: During implementationDeliverable: Snapshots and an offsite copy

  5. 05Migration and handover

    We migrate files preserving their structure, verify permissions, and hand over documentation and access instructions.Time: Outside working hoursDeliverable: Migrated files and documentation

What is includedWhat is not included
Inventory of files, volumes and permissionsHardware and drive costs
Capacity and redundancy sizingContent cleanup and decisions on what to delete
Installation and folder structureRecovery from physically damaged media
Group level permissionsElectrical work at the installation location
Snapshots and an offsite copy
Migration of existing files and documentation

Technology and equipment

  • Synology
  • Windows Server
  • Veeam
  • Proxmox
  • Microsoft 365

From practice

The most common finding is not a lack of space. It is that critical files live on user machines, on desktops, covered by no backup at all.

Central storage solves that. It does not solve backup, and that is where the most expensive misunderstanding happens: drive redundancy protects against a failed drive, not against the user who deleted a folder or the ransomware that encrypted everything it could see on the network.

Prerequisites

  • A space with power and controlled access
  • Network connectivity of adequate speed
  • Groups and permissions defined per department
  • A decision on the offsite copy

Cost

Implementation is quoted as a project with equipment and labour itemised. Ongoing monitoring, snapshots and backup verification sit within the support agreement at a monthly charge.

We do not publish a price list. Every proposal follows a site survey and separates hardware from labour.

What moves the cost

  • Capacity and drive redundancy scheme
  • Volume of files to migrate
  • Permission complexity per department
  • Whether an offsite copy is included

Frequently asked questions

Is a NAS a backup?

No. Drive redundancy protects against a drive failing, not against deletion, ransomware or fire. Central storage needs its own offsite copy.

NAS or SharePoint?

Often both. SharePoint serves collaboration and access from anywhere, a NAS serves large volumes and applications that need a network path. The decision is made per data type.

What do snapshots give me?

Recovery within minutes after human error or a local incident, without starting a restore from backup. In practice it is the most frequently used tool of the set.

How much capacity do I need?

It follows from current volume, growth rate and snapshot retention. We calculate it during the study, because undersizing costs more than the original difference.

NEXT STEP

Centralise your files properly

We start with a data and permission map, then propose capacity, redundancy and a copy strategy.

GET IN TOUCH

Tell us what you need

Four fields. An engineer replies, not a sales desk.

Fields marked * are required.

By sending this form you accept the processing of your details under our Privacy Policy.