Table of Contents
Advertisement
Importing and Synchronizing
After installing the RHN Satellite Server, you must provide it with the packages and chan-
nels to be served to client system. This chapter explains how to import that data and keep
it up to date whether the content is from RHN's central servers, local media, or from one
Satellite within your organization to another.
Two tools, RHN Satellite Exporter and RHN Satellite Synchronization Tool, come in-
stalled as part of the
6.1. Exporting with RHN Satellite Exporter
The RHN Satellite Exporter (
in an XML format that can then be imported into another identical Satellite. The content
is exported into a directory specified by the user with the -d option. Once that directory
has been transported to another Satellite, the RHN Satellite Synchronization Tool may
be used to import the contents, synchronizing two Satellites.
6.1.1.
rhn-satellite-exporter
The RHN Satellite Exporter can export the following content:
Channel Families
•
Architectures
•
Channel metadata
•
Blacklists
•
RPMs
•
RPM metadata
•
Errata
•
Kickstarts
•
The amount of time it takes
on the number and size of the channels being exported. Using the
--no-kickstarts
required for
rhn-satellite-exporter
information from being exported. For that reason, these options should only be used when
you are certain that you will not need the content that they exclude. Additionally, you
must use the matching options for
rhns-sat-tools
rhn-satellite-exporter
rhn-satellite-exporter
,
, and
--no-errata
package.
options reduces the amount of time
--no-rpms
to run, but will also prevent potentially useful
satellite-sync
Chapter 6.
) tool exports Satellite content
to export data is dependent
--no-packages
when importing the data. For
,
Advertisement
Table of Contents
