Synology

What we configure on Synology NAS devices

On Synology NAS devices we set up Hyper Backup for scheduled backups of files and shared folders, with version rotation and retention configured around the business's real needs, not left on a default value. For protecting virtual machines we use Active Backup for Business, which runs incremental backups of VMware and Hyper-V VMs directly to the NAS, with no agent to install on every single machine. For Proxmox VMs the native tool remains Proxmox Backup Server, which can use the NAS as its datastore.

Where a second synchronised copy is needed, for instance between the main office and a branch, we configure Snapshot Replication: near-instant volume snapshots that can be restored in minutes after human error or ransomware encryption, well before you would need to fall back on a full backup. We also set up DSM user permissions consistently with Active Directory, when the business already runs one.

• Hyper Backup for files and shared folders, with configured retention
• Active Backup for Business for VMware and Hyper-V VMs, agentless
• Snapshot Replication for near-instant restores
• DSM permissions integrated with existing Active Directory

When a Synology NAS is the right choice, and when it is not enough

A Synology NAS is the right choice as dedicated backup storage, kept separate from production servers: if the main server is hit by ransomware, data on the NAS stays protected only if the connection between the two systems is properly isolated, something we always check during setup. It is also a solid centralised file server for small and mid-sized offices, with access control and file version history.

On its own, a Synology NAS is not a complete backup strategy: it needs an off-site or cloud copy alongside it, following the 3-2-1 rule, otherwise a fire or theft at the office would compromise both the original data and the local backup. For very heavy virtualisation workloads, with dozens of virtual machines and high-performance storage, a NAS remains a backup solution, not the system production should run on.

How we run a Synology project

We size the NAS around the volume of data to protect and the required recovery speed: number of bays, disk type, RAM for deduplication and network connectivity, avoiding both under-sizing and overspending on features the business will never use. We configure the RAID level that best balances redundancy and usable capacity, and schedule backup jobs outside working hours so they do not load the network during production.

After installation, in our Melzo lab or directly on site, we check that backup jobs actually complete successfully and that a test restore genuinely works, not just that it is scheduled. We keep supporting the NAS with ongoing maintenance: periodic disk health checks, scheduled DSM updates and recurring backup verification, so a silent disk fault is caught before it turns into a real problem.

Security, updates and end of life for NAS devices

We plan DSM updates in agreed maintenance windows, because Synology regularly releases security patches for an operating system exposed on the network. We enable two-factor authentication on administrative access and limit direct internet exposure of the NAS, preferring VPN access when remote operation is needed. For businesses in scope for NIS2 we support backup management adequacy work.

The disks in a NAS have a defined lifecycle: we monitor SMART indicators and plan replacement before a disk actually fails, not after. When the whole NAS reaches end of life, we plan the migration of data and configuration to the new hardware without interrupting backup jobs in progress, checking that every backup copy stays accessible during the switch.