# File server instead of NAS. With snapshots and a second copy.

Source: https://vetosec.at/en/solutions/fileserver/

Nobody watches the NAS in the back room, and there is often no second copy. We replace it with a file server with snapshots and a copy at a second site. Your network drives stay as they are.

- **Snapshots** at short intervals
- **Copy** at a second site
- **On-prem** or cloud

## Why an old NAS becomes a risk

- **Disks wear out**: A NAS often runs around the clock for five years or more. Disks from the same batch tend to fail shortly after each other, especially while the RAID rebuilds after the first failure.
- **Nobody is watching**: Alerts go to a mailbox nobody reads, or are never sent. The first sign of a problem is then the data loss.
- **Missing updates**: NAS devices have repeatedly been targeted by ransomware waves that hunt for unpatched devices on the internet. One forgotten update is enough.
- **RAID is not a backup**: Mirrored disks protect against a disk failure but not against deletion, encryption, theft or fire. That needs a copy at another site.
- **Requirements have grown**: Remote work, a second site, clear permissions and audit evidence. The device was never built for that.

## Advice first

**Not every NAS has to go. We tell you what is worth it.**

Sometimes it is enough to monitor the existing device and add an offsite copy. Many business applications need a Windows network share, and then it stays. For documents your team also needs on the road, a file cloud is often the better choice. After an assessment you get a clear recommendation.

Request an assessment

## What changes for you

- **Deleted files back in minutes**: Snapshots keep earlier versions. An overwritten folder is restored within minutes.
- **Ransomware cannot encrypt snapshots**: Snapshots cannot be changed or deleted with normal user rights. After an infection we roll back to the last clean state.
- **Disk failure without downtime**: Mirrored drives and a running copy at a second site. If a disk fails, your team does not notice.
- **Clear permissions**: Access via groups instead of one-off shares. Who sees which folder is documented and traceable.

## What runs behind it

- **Self-checking storage**: Every data block carries a checksum. Silent disk errors are detected and repaired from the mirror.
- **Replication to a second site**: Changes go continuously to a second server, in the building or in a data centre.
- [**Immutable copy**](https://vetosec.at/en/solutions/backup/): Where needed an extra backup that nobody can delete for a set time, not even an administrator.
- [**Monitored**](https://vetosec.at/en/services/monitoring/): Disk health, capacity and every replication run are watched on our monitoring platform.

[How we build in general](https://vetosec.at/en/how-we-build/)

## Service or project

**We run it for you, or your team takes over.**

As a managed service for a fixed monthly price, with updates, backup and monitoring. Or as a project with handover of network plan, runbook and all credentials.

## For IT leads

Technical details: Linux · ZFS · SMB · S3 Object Lock

- **File system**: ZFS with per-block checksums, mirroring and regular scrubs of all data.
- **Shares**: SMB like on Windows, permissions via groups from your Active Directory.
- **Snapshots**: ZFS snapshots at short intervals, read-only for users.
- **Replication**: Incremental via ZFS to a second server, on-site or in a data centre.
- **Immutable copy**: Optional in S3-compatible object storage with Object Lock.
- **Monitoring**: Disk health (SMART), capacity, scrubs and every replication run.

## Further reading

More on the topic

- [**The 3-2-1 backup rule**](https://vetosec.at/en/it-security/drei-zwei-eins-regel/): The 3-2-1 rule is a rule of thumb for backups: keep three copies of your important data, on two different types of storage media, with one copy held away from your premises.
- [**Immutable backup**](https://vetosec.at/en/it-security/unveraenderliche-sicherung/): An immutable backup is a backup that can be neither changed nor deleted for a set period.
- [**Souveräne Backups: Sicherungen, die Ihnen wirklich gehören**](https://vetosec.at/en/articles/it-wissen/souveraene-backups/): Backups besser getrennt von Produktivsystemen betreiben: Identitäten, Speicherorte und Wiederherstellungsmöglichkeiten prüfen.
- [**Berechtigungskonzept für KMU: Eine einfache Struktur, die funktioniert**](https://vetosec.at/en/articles/it-wissen/berechtigungskonzept-kmu-vorlage/): A simple, workable access-control model for SMEs.

## Frequently asked questions

### Why not just buy a new NAS?

A NAS can be fine but usually runs without monitoring, updates or a second copy. What matters is the operation around it, and that is what we take on.

### On-prem or in the cloud?

On-prem when large files must be fast on the network, such as plans or imaging. In the cloud when several sites and remote staff need access. Often a mix makes sense.

### Which technology do you use?

Linux servers with ZFS storage, SMB shares like on Windows, snapshots and replication with ZFS, and where needed an immutable copy in S3-compatible storage with Object Lock.

### Who do you offer this to?

For regulated companies, professions bound by confidentiality and anyone processing sensitive data, and for companies of about 30+ staff with critical systems.

## Related

- [Solutions](https://vetosec.at/en/solutions/): Nextcloud, SSO, backup, clusters
- [Managed services](https://vetosec.at/en/services/managed-services/): fixed price per service
- [How we build](https://vetosec.at/en/how-we-build/): security and backup standards

## Replacing a NAS: file servers with snapshots and replication in Austria

vetosec replaces NAS devices with monitored ZFS file servers with snapshots and replication, on-prem, in an EU data centre or hybrid.

Updated: October 19, 2026

Provider: vetosec, Dipl.-Ing. Samuel Ziegler, BSc, Berndorf, Lower Austria, Austria. Contact: https://vetosec.at/en/contact/