Administrator Guide

• There are many snapshot creation/deletion requests being currently processed.
• Another snapshot request for the NAS volume is currently being executed.
• The total number of snapshots reached the system limit.
• The wrong IP address was specified in the backup job.
Workaround
• For a manual request failure, retry taking or deleting the snapshot after a minute or two.
• If the request originated from the snapshot scheduler, wait another cycle or two. If the failure persists, try
taking or deleting the snapshot manually on the same NAS volume.
• If the system is under a heavy workload, wait until the workload decreases and reissue the snapshot
request.
• Check the snapshot schedule. A very dense snapshot schedule has a negative impact on the overall
performance of the system. The accumulated snapshot rate must not exceed 20 snapshots per hour per
system.
• Check the total number of snapshots in the system. If the number is in the thousands, delete a few
snapshots and retry.
• Ensure the client VIP is specified in the backup job.
• Check if a recent delete of a big volume (TB) was executed. If so, wait for some time and retry the
activity.
Troubleshooting an NDMP Internal Error
Description Backup or restore fails with an internal error.
Cause NDMP internal errors are indicators of a file system not being accessible or a NAS volume not being available.
Workaround If the backup application cannot connect to a FluidFS cluster:
1. Verify that NDMP is enabled.
2. Verify that the backup application IP address is configured in NDMP.
If the backup appliance can connect to a FluidFS cluster, but cannot log in:
1. Use the default user name “backup_user” configured in Storage Manager for the NDMP client while
setting up the NDMP backup/restore in your backup application.
2. Use the password configured in Storage Manager for the NDMP client while setting up the NDMP
backup/restore in your backup application.
If the backup application can log into the FluidFS cluster, but no NAS volumes are available for backup, verify
that the FluidFS cluster has NAS volumes created on it.
Troubleshoot SMB Issues
This section contains probable causes of and solutions to common SMB problems.
Access to SMB File Denied Due to Unavailable AV Server
Description
When a file on an SMB share is opened by a client application, the FluidFS cluster sends the file to an anti-
virus server to be scanned.
If no anti-virus server is available, access to the file and to the whole SMB share is disallowed.
Cause Because the anti-virus servers are not available on the FluidFS cluster, files cannot be opened on an anti-virus
enabled SMB share.
Workaround Ensure that the problem appears only on anti-virus enabled SMB shares, while clients accessing other SMB
shares do not experience such problems.
Check the status of the anti-virus servers and the network path between the FluidFS cluster and the anti-
virus servers.
Access to SMB File/Folder Denied Due to Permissions
Description
SMB access to a file or folder is denied.
Cause A client without sufficient permissions performs an operation on a file/folder.
458 FluidFS Administration