Dll files in mirror?

[Glitch 3]

We normally always used antivirus and just upgraded to Ees. Few things we noticed:

1. The mirror is around 400MB of data! Why is this so large?

2. There is a dll folder in the mirror folder which is again around 400MB. What is the purpose of this folder? We have not seen this folder with antivirus and updates created on version 5 or era  5 creating updates for v6.

3. Are all those updates needed? Can’t we reduce the size?

how large are the updates after this first update?

 

 

[Marcos 5,235]

1, My mirror is 740 MB in size. It's created by Endpoint 6.6 and therefore contains both dll and nup update files so that both older and newer versions of ESET's products can update from it.

2, The dll files are downloaded by Endpoint 6.6 and newer.

3, We strongly recommend using an http proxy to cache update files instead of using a mirror. In this case, only files that are actually needed by clients will be downloaded. Moreover, they will be cached so if another client will request them, they will be provided from the http proxy cache.

You can use a v6.5 product which does not mirror dll update files but newer products won't be able to update from it.

We have only a comparison of http proxy vs direct update at https://support.eset.com/kb3639/. I would like to emphasize that this test was performed with Endpoint 6.5. Now the number of files downloaded to the mirror has virtually doubled due to the new format of update files that Endpoint 6.6 started to use:

When to start using Apache HTTP Proxy?

Based on our practical tests, we recommend you deploy Apache HTTP Proxy if you have a network of 37 or more computers. Review the simple comparison below of downloaded update data in a month's time using direct internet connection in comparison to Apache HTTP Proxy:

Number of PCs in your corporate network	15	36	50	100	500	1000
Direct connection to internet (MB/month)	375	900	1250	2500	12500	25000
Apache HTTP Proxy (MB/month)	30	50	60	150	600	900