Novell Doc: Novell Filr 1.0.1 Planning and Deployment Best Practices Guide - Large Filr-Clustered Deployment Overview

3.1 Large Filr-Clustered Deployment Overview

No two organizations’ large Filr-clustered deployments are identical, but Figure 3-1 illustrates the components that are common to many of them.

Figure 3-1 Typical Components of a Large Filr Deployment

Letter	Details
	Workstations and devices running Filr software can access Filr from anywhere on the Internet. L4 switches provide load balancing and security.
	Multiple Filr appliances service incoming requests for access to the organization’s files and folders. Because the appliances use shared storage, they all have access to the same data and configuration settings.
	Two Filr Search appliances provide content indexing of data and folders. They also help with the synchronization of files between the file servers and various Filr clients. Filr leverages existing MySQL database services for storing and retrieving configuration settings and user/group identities. Filr doesn’t require any changes to the organization’s NetWare, OES, or Windows file servers.

Letter

Details

Workstations and devices running Filr software can access Filr from anywhere on the Internet.

L4 switches provide load balancing and security.

Multiple Filr appliances service incoming requests for access to the organization’s files and folders. Because the appliances use shared storage, they all have access to the same data and configuration settings.

Two Filr Search appliances provide content indexing of data and folders. They also help with the synchronization of files between the file servers and various Filr clients.

Filr leverages existing MySQL database services for storing and retrieving configuration settings and user/group identities.

Filr doesn’t require any changes to the organization’s NetWare, OES, or Windows file servers.