Administrator Guide

Configuring Branch Cache
Branch cache must be properly configured on each client that supports branch cache on the branch office site.
About this task
On Windows 7 or 8, set the appropriate group policies: Computer Configuration > Policies > Administrative Templates > Network
> Turn on BranchCache > Enabled.
On Windows 8.1, you can also configure branch cache using PowerShell cmdlets such as Enable-BCHostedClient -ServerNames
hosted_cache_server_name.
Branch cache is disabled by default. This procedure enables (or disables) branch cache.
Steps
1. In the Storage view, select a FluidFS cluster.
2. Click the File System tab.
3. In the File System view, select SMB Shares.
4. In the SMB Shares panel, select an SMB share and click Edit Settings.
The Edit SMB Share Settings dialog box opens.
5. Click Advanced.
6. Select or clear the Enable branch cache checkbox.
7. Click Apply > OK.
For more information about branch cache configuration, refer to the technet article located at http://technet.microsoft.com/en-us/
library/hh848392.aspx.
Accessing an SMB Share Using UNIX or Linux
Mount the SMB share from a UNIX or Linux operating system using one of the following commands:
# mount -t smbfs -o user_name=user_name,password=password//client_vip_or_name/smb_share_name/
local_folder
# smbmount //client_vip_or_name/smb_share_name/local_folder -o user_name=user_name
Managing NFS Exports
Network File System (NFS) exports provide an effective way of sharing files across a UNIX or Linux network with authorized clients. After
creating NFS exports, NFS clients then need to mount each NFS export. The FluidFS cluster fully supports NFS protocol version 3 and all
requirements of NFS protocol versions 4.0 and 4.1.
• Supported NFSv4 features:
• File and byte-range locking
NOTE:
Starting with FluidFS v6, if the multitenancy feature is enabled, NAS administrators can configure NFSv4
to switch from mandatory to advisory byte-range locks at the tenant level using the CLI.
• Kerberos v5 security using an AD server
• AUTH_SYS legacy weak authentication
• UID translation using an LDAP server (UNIX or AD) or a NIS server
• UTF-8 file and directory names
• Unsupported NFSv4 features:
• Delegation of file locks to clients
• Full interoperability between NFSv3 and NFSv4 (for example, conflict resolution for locks from clients using different protocols)
• Antivirus scanning and result caching
• LIPKEY and SPKM-3 security (not mandatory in NFSv4.1)
• Kerberos UNIX server
398
FluidFS Administration