McAfee EPOLICY ORCHESTRATOR 4.5 Product Manual page 131

Creating Repositories
Repository types and what they do
Distributed repositories
Distributed repositories host copies of your master repository's contents. Consider using
distributed repositories and placing them throughout your network strategically to ensure
managed systems are updated while network traffic is minimized, especially across slow
connections.
As you update your master repository, ePolicy Orchestrator replicates the contents to the
distributed repositories.
Replication can occur:
• Automatically when specified package types are checked in to the master repository, as long
as global updating is enabled.
• On a recurring schedule with Replication tasks.
• Manually, by running a Replicate Now task.
A large organization can have multiple locations with limited bandwidth connections between
them. Distributed repositories help reduce updating traffic across low bandwidth connections,
or at remote sites with a large number of client systems. If you create a distributed repository
in the remote location and configure the systems within that location to update from this
distributed repository, the updates are copied across the slow connection only once — to the
distributed repository — instead of once to each system in the remote location.
If global updating is enabled, distributed repositories update managed systems automatically,
as soon as selected updates and packages are checked in to the master repository. Update
tasks are not necessary. However, you do need to be running SuperAgents in your environment
if you want automatic updating. You must still create and configure repositories and the update
tasks.
CAUTION: If distributed repositories are set up to replicate only selected packages, your newly
checked-in package is replicated by default. To avoid replicating a newly checked-in package,
deselect it from each distributed repository or disable the replication task before checking in
the package. For additional information, see Avoiding replication of selected packages and
Disabling replication of selected packages .
Source site
The source site provides all updates for your master repository. The default source site is the
McAfeeHttp update site, but you can change the source site or create multiple source sites if
you require. McAfee recommends using the McAfeeHttp or McAfeeFtp update sites as your
source site.
NOTE: Source sites are not required. You can download updates manually and check them in
to your master repository. However, using a source site automates this process.
McAfee posts software updates to these sites regularly. For example, DAT files are posted daily.
Update your master repository with updates as they are available.
Use pull tasks to copy source site contents to the master repository.
McAfee update sites provide updates to detection definition (DAT) and scanning engine files,
as well as some language packs. You must check in all other packages and updates, including
service packs and patches, to the master repository manually.
Fallback site
The fallback site is a source site that's been enabled as the backup site, from which managed
systems can retrieve updates when their usual repositories are inaccessible. For example, when
network outages or virus outbreaks occur, accessing the established location might be difficult.
McAfee ePolicy Orchestrator 4.5 Product Guide 131