Administrator Guide

If the backup appliance can connect to a FluidFS cluster, but cannot log in:
1. Use the default user name “backup_user” congured in Storage Manager for the NDMP client while
setting up the NDMP backup/restore in your backup application.
2. Use the password congured 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 le on an SMB share is opened by a client application, the FluidFS cluster sends the le to an
anti-virus server to be scanned.
If no anti-virus server is available, access to the le and to the whole SMB share is disallowed.
Cause Because the anti-virus servers are not available on the FluidFS cluster, les 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 le or folder is denied.
Cause A client without sucient permissions performs an operation on a le/folder.
Workaround Check the permissions on the le/folder and set the required permissions.
SMB ACL Corruption
Description
SMB ACLs are corrupt.
Cause
• ACLs were accidentally changed by a user or script.
• ACLs are corrupted after an anti-virus application accidentally quarantined corresponding les.
• ACLs got corrupted after data recovery by a backup application due to compatibility issues.
• ACLs got corrupted after migrating data from a dierent location by using a third-party application,
for example, RoboCopy.
Workaround Check the current ACL setting in the Windows client. Redene the ACLs for the les by using a Windows
client the same way you initially dened it. Verify that you set the ACLs as the owner of the les,
directories, and SMB shares. If you cannot redene your ACLs because you currently do not have
permissions, perform the following steps:
1. Restore the les from snapshots or a backup.
2. If you have migrated the data from a dierent location, for example, using the RoboCopy
application, there is a good chance you can restore ACLs by copying only ACLs metadata, instead of
re-copying the whole data.
3. If all le system ACLs are corrupted you can restore all data from a NAS replication partner.
FluidFS Troubleshooting
649