In this guide, the term clustering
is used in two different ways:
Filr-Clustering:
Filr appliances can be configured to store configuration settings and data that is not appliance-specific in the same storage location. Each appliance accesses the storage through a mount point named /vashare. The dialogs used to configure Filr to use shared storage refer to this as clustering.
Shared storage provides fault tolerance and high availability in the sense that, if one Filr appliances goes down, other Filr appliances have access to the same settings and data.
This guide refers to shared storage configurations as Filr-clustering.
Of course, shared storage locations themselves are neither fault-tolerant protected nor highly available unless traditional cluster services are utilized. This leads to the second usage of "clustering" as it is used in this guide.
Figure 3-2
Traditional Clustering: In an enterprise environment, fault tolerance and high availability are important for the shared storage that Filr appliances access. The MySQL server and database that Filr appliances access should be protected as well.
The following design provides the maximum resilience and performance for enterprise environments. Although Figure 3-2 shows OES Servers and Clusters, these could be replaced by Microsoft Active Directory Servers or Linux Servers to provide the High Availability components for NFS and MySQL.
Figure 3-3 Filr HA Design