Configure NAS Capacity Alerts Before Storage Runs Out

A NAS can appear healthy while its available space steadily disappears. Photos from phones, surveillance recordings, virtual machines, media libraries and backup versions often grow quietly until a volume reaches a critical level. When that happens, uploads may fail, applications can stop, and database or backup jobs may become unreliable.

Configuring a NAS to alert you when a drive nears capacity gives you time to investigate and respond. The process is straightforward on current Synology and QNAP systems, but effective monitoring depends on choosing sensible thresholds, sending notifications to an address you actually read, and understanding the difference between a disk, storage pool and usable volume.

Understand What Is Filling Up

NAS capacity can be reported at several levels. A physical drive has a raw size, while a RAID group or storage pool combines several drives. A volume, shared folder or iSCSI LUN then consumes space from that pool. The alert you need usually concerns the volume or pool that applications use, rather than the individual disk alone.

RAID does not create unlimited storage. RAID 1 mirrors data, so two 8 TB drives provide roughly 8 TB of usable capacity. RAID 5 sacrifices space equivalent to one drive for parity, while RAID 6 uses the equivalent of two. Filesystem overhead, snapshots and reserved system space reduce the practical amount further.

Before setting alerts, inspect the largest shared folders and packages. On Synology, Storage Manager and Storage Analyzer can reveal volume usage, snapshots and directory growth. QNAP users can review Storage & Snapshots, Resource Monitor and QuLog-related notifications. Look for surveillance retention, download folders, Docker containers, Plex libraries and Hyper Backup or HBS backup versions.

Choose Practical Warning Thresholds

A single 95 percent warning is often too late. Large NAS volumes can take hours or days to clean, and some systems become less responsive as free space falls. A staged approach gives you an early reminder, a serious warning and an emergency trigger.

For many home systems, useful starting points are 70 percent for review, 80 percent for action and 90 percent for urgent intervention. Business systems may need lower limits if they host databases, virtual machines, surveillance workloads or rapidly changing backup repositories. A 100 TB pool growing by several terabytes each month needs more advance notice than a small family NAS.

Use both percentage and absolute free-space thinking. Ten percent free on a 4 TB volume is about 400 GB, while ten percent on a 100 TB volume is 10 TB. Applications may require a minimum amount of free space regardless of the percentage, so combine percentage alerts with a fixed threshold where the operating system permits it.

Configure Synology Notifications

In DSM, open Control Panel and locate Notification settings. Add an email account, push notification destination or supported messaging integration, then send a test message. Use a mailbox that is monitored outside the NAS; storing alerts only inside the system defeats the purpose if the volume becomes unavailable.

Storage Manager generally provides the information needed to identify volume and storage pool status. DSM versions differ, so the exact menu names can change, but capacity warnings are commonly managed through notification rules, system events or storage-related settings. Enable alerts for low capacity, abnormal volume status, degraded storage pools and snapshot exhaustion.

Synology can also report drive health through S.M.A.R.T. tests and Storage Manager warnings. Capacity alerts and disk-failure alerts address different risks: a full volume concerns available logical space, while a failing drive concerns hardware reliability. Enable both, and make sure repeated alerts are consolidated rather than silently filtered as spam.

Configure QNAP Alerts

QNAP systems use Notification Center to manage email, push services and other delivery methods. After configuring an account, run a test and confirm that the message reaches a phone or external mailbox. In business environments, send a copy to an administrator group rather than relying on one employee’s address.

Storage & Snapshots shows storage pools, static volumes, thick volumes and thin volumes. Review the alert policies associated with the relevant pool and volume, then enable low-capacity warnings. QNAP installations can differ significantly depending on QTS or QuTS hero, so check the terminology displayed by your firmware rather than copying settings from an unrelated model.

QuTS hero uses ZFS features such as pool reservations and snapshots, making free-space planning especially important. Snapshot retention can consume substantial capacity over time. Set a retention policy, monitor snapshot usage and ensure that alert rules cover both the main storage pool and any cache or application volume.

Make Alerts Reliable In Australia

Australian households and small offices often have intermittent NBN connections, router reboots or power interruptions during storms. A NAS in Brisbane, Sydney or Darwin may also operate in a hot environment, increasing the value of remote notifications and regular health checks. Put the NAS and network equipment on a suitable UPS where practical, especially if an unexpected shutdown could interrupt a storage task.

Email delivery can be affected by spam filtering, ISP changes and authentication requirements. Push notifications through the Synology or QNAP mobile applications are useful as a second channel, while a dedicated monitoring address provides an auditable record. Test delivery after changing your internet provider, router, DNS settings or mail provider.

Capacity planning should reflect local habits and services. Family photos may be synchronised from several iPhones, while Australian businesses may retain CCTV footage for longer than expected because of insurance or workplace policies. A Melbourne design studio, a Perth trades business and a Sydney apartment may all need different thresholds based on upload patterns, available internet speed and how quickly extra disks can be sourced from the local market.

For broader background on NAS hardware, storage features and archived technical material, the WhichNAS storage guides can provide useful context before changing a pool or purchasing replacement drives.

Pair Capacity Alerts With Cleanup Policies

An alert should start a defined response rather than trigger a hurried deletion. First identify what grew, when it grew and whether the data is protected elsewhere. A sudden increase may come from a runaway log, a failed backup rotation, duplicate media or a snapshot retaining files that users believe they deleted.

Review recycle bins, version history and snapshot schedules. Synology Drive, QNAP Qsync, surveillance applications and backup tools can each retain older versions. Set sensible retention periods, but do not remove historical copies until you have verified that the remaining backup is usable.

Media servers deserve special attention. Transcoded files, incomplete downloads and duplicate 4K content can consume hundreds of gigabytes. Move archival material to a separate storage tier only after checking restore needs, encryption and access permissions. External USB disks, another NAS or cloud storage can help, but each option has different recovery times and costs.

Monitor Drives, Pools And Backups Together

A capacity warning does not indicate that the disks are healthy. A NAS may have plenty of free space while a drive develops bad sectors, or it may show healthy drives while a storage pool is almost full. Configure S.M.A.R.T. tests, temperature warnings, RAID degradation alerts and filesystem checks alongside free-space notifications.

SSD caching needs its own review. Cache devices can improve metadata or random-access performance, but they do not solve a full data volume. Monitor cache health and endurance, and avoid treating cache space as a substitute for capacity planning. If a cache fails, follow the vendor’s procedure before removing or replacing it.

Backups should report success and failure independently. A full destination can make a backup job fail even when the source NAS has ample free space. Set alerts on both ends of the process, and periodically perform a file restore. A notification that says “job completed” is useful, but a verified restore provides stronger evidence that the backup is dependable.

Recommended Alerting Practices

• Set early, action and critical thresholds instead of relying on one percentage.
• Send notifications through at least two independent channels, such as email and push.
• Check volumes, storage pools, snapshots, recycle bins and backup destinations separately.
• Review growth trends monthly and record which folders or applications are responsible.
• Test alert delivery after firmware, router, DNS or email-account changes.
• Keep enough free space for maintenance tasks, snapshots and temporary application files.

Capacity monitoring works best as a routine. Schedule a monthly review of storage trends and a quarterly restore test, then record the results in an administrator log. If the NAS supports dashboards or scheduled reports, use them to spot gradual growth before the warning threshold is reached.

When a warning arrives, avoid deleting files immediately. Confirm the affected volume, preserve important evidence if the NAS supports business records or surveillance footage, and check that a current backup exists. For technical references outside the NAS vendor ecosystem, additional online resources may also help with documenting systems and maintaining a broader reference library.

Set the alerts today, send a test notification, and write down the first three actions to take when the warning appears. A few minutes of configuration can prevent an avoidable storage outage and give you time to expand, archive or reorganise data safely.