Infrastructure building and sizing

hmtoggle_plus0validation-status-icon-infoSMB users? Click here...

Before installing ESET Remote Administrator, it is important to understand the ESET Remote Administrator architecture and what affects the performance of ERA Server and your SQL database:

Hardware used for ERA Server

We strongly recommend that you review the minimum hardware requirements before proceeding. Based on our practical deployment examples and the following table, you can spec your hardware for optimal performance of ESET Remote Administrator.

Sizing table for small and medium businesses

Clients

icon_computer ERA Server + SQL database server

CPUs

RAM (GB)

HDD (GB)

Up to 1000

2

4

100

1000 - 5000

4

4 - 8

150

5000 - 10.000

4

4 - 8

200

These recommendations are for a configuration with an appropriate client connection interval.

Sizing table for medium business and enterprise solutions

Clients

icon_computer ERA Server

icon_computer SQL database server*

icon_computer ERA Proxy**

CPUs

RAM (GB)

HDD (GB)

CPUs

RAM (GB)

HDD (GB)

Number of Proxies

CPUs

RAM (GB)

HDD (GB)

10.000 - 50.000

4+

4+

40

8+

8+

250+

2 - 3

2 - 4

8

20 - 40

50.000 - 100.000

8+

4+

80

8+

16+

250+

3 - 6

2 - 4

8

20 - 40

100.000+

8+

8+

80

8+

32+

250+

6+

2 - 4

8

20 - 40

These recommendations are for a configuration with an appropriate client connection interval.

* SQL server instance can share resources with ERA Server to maximize utilization and minimize latency.Combine the values for CPU and RAM required for optimal performance when using this method.

** Enterprise grade SSD with high IOPS is necessary.

*** ERA Proxy must not share resources with ERA Server and its database. If there are enough resources for ERA Server, direct connections from ERA Agents can be used.

 

SQL database server

Although the database hardware requirements for ESET Remote Administrator are defined, you need to decide whether to install a SQL database server on the same machine as ERA Server, or to use a dedicated server for installation of a SQL database server.

We recommend that you use a dedicated machine(s) with reserved resources if you wish to manage more than 10,000 clients.

Database

SMB customer

Enterprise customer

Clients limit

Windows

Linux

MS SQL Express

X

(optional)

5.000

X

 

MS SQL Server

X

X

None (up to 100.000)

X

 

MySQL

X

X

10.000

X

X

Network architecture and speed of your Internet connection

See Network requirements and Differences between Apache HTTP Proxy, Mirror Tool and direct connectivity.

Client connection interval

The time between client connections to ERA Server (or ERA Proxy) affects performance as well. See Client connection interval for more details on how to configure this setting.

Average number of events reported by clients

If a server is overloaded or there is a malware outbreak (for example, we connect 20,000 clients to a server that is only able to service 10,000 clients at an interval of every ten minutes), it will skip some of the connected clients. Not connected clients will try to connect to ERA Server (or ERA Proxy) later.

Network traffic impact by ERA Server and ERA Agent communication

Applications on client machines do not communicate with ERA Server directly, ERA Agent facilitates this communication. This solution is easier to manage and less demanding on data transferred over network. Network traffic depends on the client connection interval and types of tasks performed by clients. Even if no task is executed or scheduled on a client, ERA Agent communicates with ERA Server once in each connection interval. Each connection generates traffic. See the table below for examples of traffic:

Task type

Traffic in a single connection interval

Scan without cleaning

4 kB

Modules update

4 kB

SysInspector Log Request

300 kB

ERA Agent replication interval

Daily traffic generated by idle ERA Agent

1 minute

16 MB

15 minutes

1 MB

30 minutes

0.5 MB

1 hour

144 kB

1 day

12 kB

To estimate the overall traffic generated by ERA Agents, use the following formula:

Number of clients * (Daily traffic of idle agent + (Traffic for certain task * daily occurrence of the task))

Number of ERA Agents and endpoints on your network

See Deployment scenarios - best practices.