
To download the daily DAT file randomly from the central ePO server to the system agents takes the
following bandwidth: 100 Agents * 200 KB file = 20 MB of bandwidth
Example 2: Downloading the DAT file to the local repository
For the McAfee ePO server to replicate the DAT file to each repository every day takes at least 70 MB
of bandwidth.
In the previous examples, it is a waste to use 70 MB of bandwidth to download a DAT file to a
repository for only 100 system agents. Those 100 system agents can download the same file using
only 20 MB of bandwidth.
How many repositories do you need
How many repositories you need depends on the hardware where the repository is installed. Most
repositories can serve out files to several thousand nodes. If you are using clients as SuperAgents,
they are more efficient if they are dedicated to your clients instead of sharing the SuperAgent client
hardware with other applications.
There is no hard technical limit to how many nodes a repository can handle, but with a properly
crafted update task for your clients, repositories can update a significant number of nodes.
The following table is an estimate of the updates a repository can handle and the hardware needed.
These specifications can be influenced by many factors, for example how you update content,
products, and patches.
Server hardware Nodes updated Dedicated or shared
client hardware
Single 3 Ghz processor with 4 GB of memory 3,000 Shared with other
applications
3,000 – 7,000 Dedicated
Server class hardware, dual-quad processor and 8
GB of RAM
5,000 – 7,000 Dedicated
Disk space needed for a repository is rarely a concern with today’s storage standards. Even if you
checked in several McAfee endpoint products, for example Endpoint Encryption, SiteAdvisor, and Policy
Auditor, your repository disk space would be in the 1 GB range.
To find out the exact size of your repository you can check the
installation folder where the McAfee ePO server is located under C:
\Program Files\McAfee\ePolicy Orchestrator\DB\Software.
The following sections provide some examples of three common organization sizes and their repository
size.
Example 1 — Small Organization with One Office
The small organization example has approximately 3,000 nodes of workstations and servers. It uses
McAfee VirusScan Enterprise, Host Intrusion Prevention System, Encryption, and Host Data Loss
Protection. It has a small data center in the same building where the devices reside so there are no
WAN links and all clients are on a 100 MB LAN.
In this example you can use the primary ePO server to act as the only repository. the McAfee ePO
server is always the master repository by default. For 3,000 clients, the McAfee ePO server can handle:
3
Using distributed repositories to keep your security software up to date
How many repositories do you need
26
McAfee
®
ePolicy Orchestrator
®
Best Practices Guide for use with ePolicy Orchestrator versions 4.5.0 and 4.0.0
Comentarios a estos manuales