Product SiteDocumentation Site

Chapter 6. Inter-Satellite Sync (ISS)

6.1. Required Environment for ISS
6.2. Recommended Models for Inter-Satellite Sync
6.3. Configuring the Master RHN Satellite Server
6.4. Configuring the Slave RHN Satellite Servers
6.5. Using Inter-Satellite Sync
6.5.1. Syncing between a Development Staging Server and a Production Satellite
6.5.2. Bi-directional sync
6.6. Synchronizing by Organization
As an organization grows, so does complexity of the deployed systems. Red Hat Network Satellite deployment can grow with your IT infrastructure. One capability that assists with managing scale and complexity is the deployment of multiple RHN Satellites configured to communicate with each other. Each Satellite manages a segment of an organization's deployment, minimizing the inefficiencies of both massive scaling and dispersed data centers. With multiple Satellites, an organization can infinitely scale upward, allow semi-autonomous management of IT segments, and ensure maximum management performance of systems closest to the managing Satellite while enforcing content standardization and life-cycle best practices.
RHN Satellite 5.3 supports synchronization between two Satellites. This synchronization, also called Inter-Satellite Sync, allows administrators to simplify the process of coordinating content from one RHN Satellite source to another or several others.

6.1. Required Environment for ISS

The following are the basic requirements for Inter-Satellite Sync.
  • At least two RHN Satellite 5.3 servers
  • At least one RHN Satellite populated with at least one channel
  • Master RHN Satellite SSL certificate available on each of the slave RHN Satellites for secure connection