4.2.4. Importing Content to a Disconnected Satellite Server
Ensure that the directory and filesystem containing the exports has enough space to expand out the archives. For example, if your export is 40GB, the disconnected Satellite Server directory and filesystem where you are importing the content will need an extra 40GB of space to expand it on the same filesystem.
- Copy the exported contents of the external media to a directory on the disconnected Satellite.
Note
If the exported content was placed in different external media devices, ensure that you copy all the contents in one directory on the disconnected Satellite. - Run the
expand_export.shscript copied along with your exported content:# ./expand_export.sh *** Done expanding archives. ***
Warning
The disconnected Satellite needs to have equal to the same space as the exported archive before you expand the exported content. The script will fail otherwise.The script will expand the archive into a directory. - Move the expanded directory tree's content to
/var/www/htmlon the Satellite Server and restore the SELinux contexts on the moved files:# mv var/tmp/export/* /var/www/html/ # cd /var/www/html # restorecon -r *
Note
The Satellite is now acting as its own CDN with the files located inhttp://localhost/content. This is not a requirement. The CDN can be hosted on a different machine inside the same disconnected network as long as it is accessible to the Satellite server via HTTP. - Add the CDN address to the Satellite web interface:
- Log in to the Satellite web interface.
- Click → and then click .
- On the Subscription Manifest information screen, scroll to Red Hat Provider Details. Click the edit icon on the Repository URL entry and change the entry to the CDN's repository URL.
- Click to choose the manifest file.
- Click to import your manifest.
- Enable the repositories from the local CDN:
- Click →
- Enable the repositories that were enabled and synchronized in the Synchronizing Content section.
- Click → .
- Select the repositories you want to synchronize and click .

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.