File Director


Sizing and monitoring your deployment

The Ivanti File Director platform is enterprise ready and can be scaled to accommodate the syncing requirements of any organization.

Unless deploying to a test environment, we recommend that all production deployments are configured with at least 2 nodes (for resiliency / redundancy purposes).

A question that is often asked is how many appliances do I require to service x number of users. Unfortunately this is not a straightforward calculation since every environment is different, both in terms of the features used, and the end user data and usage patterns. There are many factors which can influence this figure, as detailed below.

Features which may contribute to platform load, thereby impacting scalability:

Kerberos Single Sign-On

Shared map points (server locking)

Platform Notifications (disabled by default in 2018.1 onwards)

In-location Sync / Mapped Drives configuration

PST sync

Delta syncs

Manual vs Automatic map points

Environmental considerations which may impact scalability:

SMB version in use on file server (SMB3 is more efficient than SMB2)

Usage pattern / concurrency of end users (E.g. users in same timezone / working hours vs distributed)

Number of files

Frequency of file changes (churn)

Size of files

Performance (throughput/latency) of storage

Performance of hypervisor

Performance (throughput/latency) of network

Number of map points

Max size of Kerberos token configured (where Kerberos SSO used - smaller the better)

Number of concurrent onboarding users (syncing for the first time, or receiving replacement hardware) – This is the more important consideration when scaling File Director.

The most accurate way to size a deployment is to deploy a pilot to a sample number of users, against a small number of appliances, and monitor appliance utilization to evaluate how close to capacity the platform is. Then plan the final number of appliances using this data.

Real-time monitoring of your appliance health

The best way to monitor your appliance health and load in real-time is to use software such as Splunk or the ELK stack.

File Director can be configured to point to a syslog server in the Admin Console (under Configuration > Advanced). Once configured with the dashboards you require, a graphical representation of your cluster performance is available. It can show the status of all nodes - including metrics such as connections, threads, CPU, memory usage and API response time.

From this information you can then make an informed decision on whether you will need more or less appliances or whether you have enough capacity to onboard more users.

Example dashboards from the ELK stack:

See also:

Monitoring File Director with Splunk

File Director Performance Monitoring

Related topics

Was this article useful?