In an enterprise environment, it is important to ensure that the Filr appliances’ shared storage (the /vashare mount point) is protected by traditional clustering to provide for high availability.
Ensure /vashare is always up for the functioning of the Filr server.
Monitor and clean up the /vashare/filr/cachefilestore area as needed.
Cached files are automatically deleted on an appliance restart when they exceed 10 GB in size.
Windows NFS services are not supported.
The NFS or CIFS server should be on or near the same subnet as the Filr deployment. Filr is not latency tolerant.
When exporting the remote NFS directory, you must specify the rw and no_root_squash export options.
To secure NFS server access, as you specify the export options for the exported directory, make sure to create a DNS entry for each Filr appliance that needs access.
Otherwise, any NFS client on the network will be able to mount the exported directory.
The allocation for /vashare is calculated in “Worksheet 25 - Storage Planning Summary” based on information you entered previously as explained in Table 14-4.
Table 14-4 Filr Appliance Sizing Guidelines
|
Item |
Recommendations and Guidelines |
Planning Worksheet Example |
|---|---|---|
|
You must create an external NFS of CIFS share for this. It must be large enough to accommodate the following:
|
The worksheet calculates this as follows:
|