Frequently Asked Question
Hyper Backup reports insufficient destination quota even though the remote NAS has free space. What should I check?
QUICK ANSWER
A destination can have free physical space while the backup account or shared folder has reached its quota. Check the destination assigned to this task, not just its total volume capacity.
Applies to: Hyper Backup file/folder jobs, especially backups to another Synology NAS. Cloud providers may apply different account or bucket limits.
Work through these checks
- Identify the real destination. Open the affected task and note its destination type, folder and account. A different account or an older archive can have a different limit on the same NAS.
- Ask the destination administrator to check limits. Compare available volume space with the backup user's quota and, where supported, the shared-folder quota. Review the permissions of the account used by the job.
- Review retention in the application. Check stored versions and the configured retention policy. Removing source files or changing a folder in File Station is not a controlled way to trim a versioned backup archive.
- Retry after an agreed correction. Arrange an authorised quota increase or application-managed retention change, then run the task and verify a small restore.
Confirm the result
A new backup completes under the intended account and a sample file can be restored, rather than only the warning disappearing.
Before going further: Do not manually delete files inside an .hbk archive or assume a successful connection means enough destination capacity is available.
If you need help
Include these details in your ticket: Task/destination type, quota message, account category and storage/quota figures without passwords or private file names.
Related guidance: Why does deleting a Synology Hyper Backup version free less space than expected? · Hyper Backup cannot connect to its destination even though the remote NAS opens in a browser. What should I check?
Updated 261110