High Availability (Enterprise)

For enterprise environments (for example, 100,000 clients), additional ERA components should be employed. One is RD Sensor, which helps to search your network and discover new computers. We also recommend a layer of ERA Proxy. ERA Agents connect to the ERA Proxy, thereby balancing the load on the master server which is important for performance. Using this configuration it is still possible for ERA Agents to connect directly to the main server. A SQL database is also implemented on a Failover Cluster to provide redundancy.

ds_high_availability_enterprise


Best practices for deployment scenarios for Enterprise environments

Number of clients

50 000 - 100 000 clients

100 000+ clients **

ERA Server & Database Server on the same machine

No

No

Use of MS SQL Express

No

No

Use of MS SQL

OK

OK

Use of MySQL

No

No

Use of ERA Virtual Appliance

No

No

Use of VM server

No

No

Use of ERA Proxy (not direct replication)

YES (one ERA Proxy per 20.000 clients)

YES (one ERA Proxy per 20.000 clients)

Recommended replication interval (during deployment)

20 minutes

20 minutes

Recommended replication interval (after deployment)

60 minutes (agent-proxy)*

240 minutes (agent-proxy)*

* Recommended replication interval of connection between ERA Proxy and ERA Agent.

** See recommendations for optimal hardware requirements in the Infrastructure building and sizing chapter