McAfee EPOLICY ORCHESTRATOR 4.5 - Guía de instalación descargar pdf (Pagina 30)

In the small office in India you could add a repository but you must replicate the DAT file from the

McAfee ePO server to the repository. This file replication uses approximately 70 MB of bandwidth per

day over a slow WAN link could negatively impact the WAN link to India since it would occur all at once.

Instead have the agents connect across the WAN link to the next closest repository to download their

DAT file updates. The next office might be in a larger office, for example the Tokyo. The agents can

randomly pull their DAT files throughout the day, and their total bandwidth use is only 40 MB. See

Client task to configure the download.

In this case do not use a repository in India.

Example 2 — A large office in Tokyo

The large office in Tokyo needs to download the 200 Kb per day for DAT files to its 4,000 nodes, using

the formula:

(200 Kb) x (4,000 nodes) = 800 MB of data randomly pulled per day to Tokyo

In the large office in Tokyo with 4,000 nodes uses 800 MB of bandwidth per day just to update the

DAT files alone. Since replication of the DAT file to Tokyo only uses 70 MB of bandwidth per day it is

much more efficient to have a repository in the Tokyo office so all DATs can be pulled across the LAN

instead of across the slower WAN link.

Example 3 — A large office in New York City

The large office in New York City needs to download a 23 MB patch update for VirusScan Enterprise to

its 1,000 nodes. Using the formula:

(23 MB) x (1,000 nodes) = 23 GB of data pulled to the New York City office

This 23 MB patch is significantly larger than the 200 Kb daily DAT files. You probably have a repository

in New York depending on the speed of the WAN link to New York and how quickly the patch needs to

be pushed out. You might find a balance if you carefully craft your client tasks to pull updates and

patches at a gradual pace instead of deploying the patch to all nodes in one day. See Deploying

products for detailed information.

Conclusions

Some ePolicy Orchestrator users put a repository at geographic sites that have only a few dozen

nodes. If your site does not have at least 200 to 300 nodes it cannot benefit from the bandwidth

saved using a repository. If there is no local repository, the agents will go to the next nearest

repository for their updates. This repository might be across a WAN link but it will still use less

bandwidth since you don’t have to replicate the entire repository across the WAN.

The exception to this rule is if you are deploying a larger software package. For example, the

VirusScan Enterprise client software is 23 MB. In this case it would be more efficient to place a

repository temporarily at a smaller site so the clients software can download the 23 MB file locally.

Then disable this repository once the client is rolled out.

Using distributed repositories to keep your security software up to date

How many repositories do you need

McAfee

ePolicy Orchestrator

Best Practices Guide for use with ePolicy Orchestrator versions 4.5.0 and 4.0.0

1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 109 110

Sin comentarios

McAfee EPOLICY ORCHESTRATOR 4.5 - Guía de instalación Pagina 30