Installation guide

Example 1.5. Synchronized Slaves
In this example, the master satellite provides data directly to the slaves and changes are regularly
synchronized.
Example 1.6. Slave Custom Content
This example uses the master satellite as a development channel, from which content is distributed to
all production slave satellites. Some of the slave satellites have extra content that is not present in the
master satellite channels. These packages are preserved, but all changes from the master satellite
are synchronized to the slaves.
Example 1.7. Bi-directional sync
In this environment, two Red Hat Satellite servers act as both master and salve to each other and can
synchronize content between them. T he Satellite server where the command satellite-sync is
run will pull the content from the other Satellite server and the synchronized data will depend on the
options run with satellite-sync. Without any options, the synchronization will attempt to update
everything that was previously synchronized.
See Section 1.3.1.1, “Manual Configuration” for configuring a Master Satellite. Configuring both
Satellite servers as a Master will create a bi-directional sync.
Chapter 1. Red Hat Satellite Information
4 1