- Hardware limitations
Snapshots are only supported on thick volumes, thin volumes and block-based LUNs. The NAS must be model x51 or above, with an Intel or AMD-based CPU and at least 4GB of memory.
Each volume or LUN can support a maximum 256 snapshots, with a limit of 1024 snapshots for the whole NAS. For x51 NAS models, each volume or LUN can support up to 64 snapshots, with a limit of 256 snapshots for the whole NAS.
- Insufficient storage pool space
Snapshots require free storage pool space. If there is insufficient space, delete unwanted snapshots. Setting snapshot reserved space to at least 10% may prevent this problem
- Insufficient memory or CPU resources
If someone is accessing data on the volume or LUN, or if the NAS CPU and memory usage is too high (over 90%), snapshots may temporarily fail. Wait until the NAS is under less load or disable resource-intensive applications before continuing to use snapshots.
- Insufficient resources on destination NAS
When using snapshot replica, both source and destination NAS must have sufficient space, CPU resources and memory for a snapshot to be taken and replicated. Check resources on both source and destination NAS if a replication job fails.
- Source volume or LUN was expanded
When using snapshot replica, the source volume or LUN is replicated to the remote NAS as a base copy. If the source volume or LUN is then expanded, the copy on the remote NAS will not be able to store new snapshots. After expanding a volume or LUN, delete the snapshot vault on the target NAS and create a new replication job.
- Network ports are being blocked
Snapshot replica uses SSH port 22 and bbcp data ports 50000 to 62700. Ensure that these ports are not being blocked.
Release date: 2016-08-30
Was it helpful?
50% of people think it helps.