Determine the Filr component server hardware configurations and from this the hosting server requirements.
Use the above disk space requirements and Filr installation manual server requirements as guides for determining memory, disk space, and processor requirements.
Ensure that the required disk space and memory are available for the Filr deployment.
Test and monitor your pilot deployment to identify connection usage patterns and determine how many Filr servers are required. Currently, a single Filr server can service approximately 500 concurrent user connections.
For example, you might find that two Filr servers would serve 3,000 users given that all of them are not concurrently connected.
One of the following software virtualization platforms:
VMware
One of the following VMware host servers for hosting the Filr appliance:
Installing VMware Tools on the host server is recommended.
ESXi 5.5.x with the latest update
ESXi 5.1.x with the latest update
ESXi 5.0 with the latest update
ESX 4.1.x and ESXi 4.1.x with the latest update
For the most up-to-date compatibility matrix of supported VMware host servers, refer to the VMware Compatibility Guide that is provided by VMware.
To generate the correct chart from the VMware Compatibility Guide:
Ensure that
is selected in the field.In the
field, select , then in the field, select .Click
, then look at the 64-bit line of the provided table.The versions of ESX and ESXi that are listed in the Supported Releases column of this row are compatible with Filr 1.0.
A VMware vSphere client 4.x or VMware vSphere client 5.x for accessing the host server and appliance for initial configuration.
Not all versions of the vSphere client are compatible with versions of VMware ESX and ESXi. For a complete matrix of compatibility, refer to the VMware Product Interoperability Matrixes that are provided by VMware.
Xen
SLES 11 SP2, 64-bit
SLES 11 SP3, 64-bit
Hyper-V
Windows 2012 Server (as a Role)
Windows 2008 R2 Server (as a Role)
Hyper-V Server 2012 (standalone)
Hyper-V Server 2008 R2 (standalone)
Filr Appliance (each): 8 GB of memory and 2 CPUs. At least half of the memory should be dedicated to the Java heap.
Database Appliance (if no in-house MySQL service is available): 4 GB of memory and 2 CPUs. (More memory is required if there are more than 1,000 users on the system.)
Search Index Appliance (2 required): 4 GB of memory and 2 CPUs. (More memory is required if there are more than 1,000 users on the system.) About 75% of the memory should be dedicated to the Java heap.
Determine whether an L4 switch, NetIQ Access Manager, Apache, or DNS round-robin will be used to front the Filr servers.
Novell recommends having at least two clustered Filr servers for basic performance and high-availability. You can add more as your deployment grows through your initial pilot to a phased-in production rollout.
Novell recommends connecting a third Filr Appliance to the shared storage and not fronting it with a load balancer. This appliance can then be used for dedicated administration and file synchronization purposes.
Novell recommends having two Search/Index servers for redundancy (fault tolerance) purposes. Having more than two is not recommended or needed, because there are no performance gains associated with multiple Filr Search appliances.
Having functional search appliances and the services they provide is vital to the health of the system. If you are using a single search appliance, avoid re-indexing when possible. Re-indexing causes all Windows and Macintosh desktop clients to delete local Filr files and re-download them from the server as the index is recreated.
If you are using two Search Appliances, re-indexing the appliances at separate times prevents the clients from re-downloading all their data.
Where are the likely locations of the Filr appliances and the target data?
Do you have a geographically dispersed network?
If so, what is the bandwidth between sites (including latency)?