Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

9.5. Cloning the Satellite with Embedded DB

You may limit outages caused by hardware or other failures by cloning the Satellite with Embedded Database in its entirety. The secondary Satellite machine can be prepared for use if the primary fails. To clone the Satellite, perform these tasks:
  1. Install Red Hat Network Satellite with Embedded Database (and a base install of Red Hat Enterprise Linux) on a separate machine, skipping the SSL Certificate generation step.
  2. Back up the primary Satellite's database daily using the commands described in Section 9.4.2, “Backing up the Database”. If this is done, only changes made the day of the failure will be lost.
  3. Establish a mechanism to copy the backup to the secondary Satellite and keep these repositories synchronized using a file transfer program such as rsync. Copying is not necessary if using a SAN.
  4. Use RHN DB Control's restore option to import the duplicate data.
  5. If the primary Satellite fails, transfer the SSL key pair RPM package in /root/ssl-build from the primary to the secondary Satellite, and install the package. This ensures that Red Hat Network clients can authenticate with and securely connect to the secondary Satellite.
  6. Change DNS to point to the new machine or configure your load balancer appropriately.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top