Novell IFOLDER 3.7 - SECURITY ADMINISTRATION, Administration Manual

Page: 26 / 216

26 OES 2 SP1: Novell iFolder 3.7 Administration Guide
no
vd
ocx
(e
n)
13
Ma
y 20
09
Š
The number of files in the iFolder.
Š
How frequently files change in the file.
Š
How much data actually changes.
Š
How frequently files are synchronized.
Š
The available bandwidth and throughput of network connections.
We recommend that you set up a pilot program to assess your operational needs and performance
based on your equipment and collaboration environment, then design your system accordingly.
The following is a suggested baseline configuration for an iFolder 3.7 server with a workload
similar to a typical iFolder 2.1
x server. It is based on an example workload of about 12.5 GB of data
throughput (up and down) each 24 hours, including all Ethernet traffic and protocol overhead. Your
actual performance might differ.
Table 2-1
Suggested Baseline Configuration for an iFolder Enterprise Server
If iFolder server is serving large number of requests, it is possible that for some requests you may
receive HTTP 500 error. To manage this and to enable iFolder to serve more requests, do the
following:
1
Edit the
/etc/security/limits.conf file
add the following lines:
* soft nofile 100000
* hard nofile 110000
2 Save the
limits.conf
file and reboot the server.
2.3 Naming Conventions for Usernames and
Passwords
Š
Section 2.3.1, “LDAP Naming Requirement,” on page 27
Š Section 2.3.2, “Length and Format Considerations for an LDAP Object,” on page 27
Š
Section 2.3.3, “Multilingual Considerations,” on page 27
Component Example System Configuration
Hardware 1.8 GHz Single processor
1.2 GB RAM
300 GB hard drive
iFolder Services 500 users per server (multi-server configuration)
500 MB user account quota per user
1 iFolder per user that is not shared with other users
5% change in each user’s data per 24-hour period