Scalability Parameters; Deployment Scenarios; Load Balancing - Novell IFOLDER 3.8 - DEPLOYMENT Deployment Manual

3.3 Scalability Parameters

The scalability parameters for a multi-server (master-slave) deployment are as follows:
The multi-server (master-slave) deployment is scalable to 1000 users.
If an exclusive Web Access server is not deployed, the Web Access users are also considered in
this scalable parameter. An independent Web Access server can handle 1000 users at any given
point in time. If there are more than 1000 Web users connecting at any given point in time,
consider the deployment scenario in
Access Load," on page
The Enterprise iFolder server must have Web Admin and Web Access capability.
Web Access usage must be minimal to ensure guaranteed response time.
Clients must have a dedicated NIC of at least 100 Mbps.
Web-based access must be low, and thick client access must be moderate with 500 active
connections.
The data transfer (synchronization of user data) rate must be at least 10 MB per hour per client.
Both SSL and non-SSL communication is supported.
The synchronization interval must be no more than 10 minutes.
If the master and slave iFolder servers are in two different geographical locations, individual
Web Access servers are beneficial to improve the response time.

3.4 Deployment Scenarios

The following sections discuss the deployment cases in a multi-sever setup. These deployment cases
indicate how a multi-server (master-slave) setup can be used for load balancing and data
synchronization in an organization where the employee storage requirement is growing in terms of
size and frequency of access. In a situation where an organization's employee storage requirement is
increasing, an organization needs a reliable response time for users. Also, data synchronization in
such a situation needs strict time constraints.
Section 3.4.1, "Load Balancing," on page 21
Section 3.4.2, "Data Synchronization," on page 22

3.4.1 Load Balancing

Consider the case of a global manufacturing firm that requires its component plans and drawings to
be saved in a secure place. The workforce involved in the manufacturing division of the organization
needs this confidential information to be accessed, updated, added, or shared with peers in other
departments for various actions to be taken, such as approval of plans.
In this case, you can deploy Novell iFolder in a multi-server setup so that the manufacturing
divisions can share the plans and other documents in a secure manner. Because the number of units
manufactured might be time-sensitive and limited, the plans and drawings must reach the respective
divisions on time, and the operators must be able to retrieve, update, and synchronize them within
the required response time. A multi-server configuration is very useful in managing this kind of load
in a timely manner.
Chapter 5, "Master-Slave Deployment for a High Web
27.
Multi-Server (Master-Slave) Deployment 21