NAS Codex › QNAP › QNAP snapshot failed or you can't take snapshots: what QNAP says
QNAP snapshot failed or you can't take snapshots: what QNAP says
Snapshots on a QNAP NAS live inside the storage pool, so most failures come down to the model, the pool's free space, or how busy the NAS is. QNAP's FAQs list the reasons a snapshot or Snapshot Replica job fails and what to change for each. They also explain why old snapshots can disappear on their own.
Written against: QTS and QuTS hero Storage & Snapshots (QNAP FAQs last modified 2022-06-24, 2024-03-05 and 2024-08-08). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Check four things QNAP lists: that your model supports snapshots (x51 or later with an Intel or AMD CPU and at least 4 GB of memory, on QTS), that the volume or LUN has not hit its snapshot limit, that the storage pool has free space, and that CPU and memory use are not above 90%. If old snapshots are disappearing, QNAP points to pool guaranteed snapshot space.
Why a snapshot fails
- The model does not support snapshots: on QTS, QNAP says snapshots need an x51 model or later with an Intel or AMD CPU and at least 4 GB of memory, and are supported only on thick volumes, thin volumes and block-based LUNs. Legacy models do not support snapshots, and you need to have created a storage pool, since snapshots can only be taken of storage objects inside a pool.
- The snapshot limit is reached: QNAP's QTS figures are up to 256 snapshots per volume or LUN and 1,024 per NAS, or 64 per volume or LUN and 256 per NAS on x51 models. QNAP says the number you can take depends on the CPU model and installed memory.
- Not enough storage pool space: snapshots need free space in the storage pool. QNAP says to delete unwanted snapshots, and that setting pool guaranteed snapshot space to at least 10% may help prevent the problem.
- The NAS is too busy: if someone is accessing data on the volume or LUN, or memory and CPU use are over 90%, the snapshot may temporarily fail. Wait until the load is lower, or disable resource-intensive apps first.
Thick volumes and LUNs
QNAP says a snapshot of a thick volume or LUN reserves space so it can be reverted later, so it can fail even when the volume still shows free space. On QuTS hero, check the pool's Allocated size and Unallocated size under Storage Manager > Storage Space (right-click the pool > Manage). QNAP's fixes are to delete old snapshots, expand the storage pool, or (QuTS hero only) convert the thick volume or LUN to thin. Its general FAQ adds that new data written to a thick object grows snapshot usage by the same amount, which is why QNAP recommends thin storage objects for snapshots.
Snapshot Replica jobs that fail
- Both the source and destination NAS need enough space, CPU and memory.
- If you expanded the source volume or LUN after the first replica job, the copy on the remote NAS cannot store new snapshots. QNAP says to delete the snapshot vault on the destination and create a new Snapshot Replica job.
- Snapshot Replica uses SSH port 22 and bbcp data ports 50000 to 62700, so make sure they are not blocked.
Snapshots disappearing or not as expected
- Old snapshots removed: without pool guaranteed snapshot space, QNAP says snapshots sit directly in the pool and may be removed automatically when the system needs space, for example for thin provisioning.
- Stop at the maximum instead of overwriting: go to Storage & Snapshots > Global Settings > Snapshots > When the number of snapshots reaches maximum, select Stop taking snapshots and click Apply.
- Snapshots still taken with "smart snapshot" on: QNAP says the system may change data blocks in the background for storage optimization, which counts as a change.
- Moved pool, still no snapshots: a pool created on a NAS that did not support snapshots will not support them after migration; QNAP says to back up the data, create a new pool on the new NAS, and copy the data back.
When to stop and get help
QNAP is clear that snapshots are not independent backups: they depend on the storage pool and cannot be moved elsewhere. For a degraded pool, see RAID group degraded or read-only. If space is the issue, see expanding a storage pool.
Questions
Why can't I take snapshots on my QNAP NAS?
QNAP lists an unsupported or legacy model (on QTS: x51 or later, Intel or AMD CPU, at least 4 GB memory), no storage pool, the snapshot limit reached, not enough storage pool space, or CPU and memory use over 90%.
How many snapshots can a QNAP NAS keep?
QNAP's QTS figures are 256 per volume or LUN and 1,024 per NAS, or 64 and 256 on x51 models. It says the actual number depends on the CPU model and installed memory.
Why are my old QNAP snapshots being deleted?
QNAP says that without pool guaranteed snapshot space, snapshots are stored directly in the pool and may be removed automatically when the system needs space. You can also set the NAS to stop taking snapshots at the maximum instead of overwriting old ones.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.