Chapter 8. Maintenance
63
Database may be run as active, as well as standby. This is entirely up to your network
topology and is independent of the steps listed here.
To establish this redundancy, first install the primary Satellite normally, except the value
specified in the Common Name field for the SSL certificate must represent your high-
availability configuration, rather than the hostname of the individual server. Then:
1. Prepare the Stand-Alone Database for failover using Oracle’s recommendations for
building a fault-tolerant database. Consult your database administrator.
2. Install RHN Satellite Server with Stand-Alone Database (and a base install of Red
Hat Enterprise Linux AS) on a separate machine, skipping the database configura-
tion, database schema, SSL certificate, and bootstrap script generation steps. Include
the same RHN account and database connection information provided during the
initial Satellite install and register the new Satellite.
If your original SSL certificate does not take your high-availability solution into
account, you may create a new one with a more appropriate Common Name value
now. In this case, you may also generate a new bootstrap script that captures this new
value.
3. After installation, copy the following files from the primary Satellite to the secondary
Satellite:
•
/etc/rhn/rhn.conf
•
/etc/tnsnames.ora
•
/var/www/rhns/server/secret/rhnSecret.py
4. Copy and install the server-side SSL certificate RPMs from the primary Satellite to
the secondary. Refer to the Sharing Certificates section of the
RHN Client Config-
uration Guide
for precise instructions. Remember, the Common Name value must
represent the combined Satellite solution, not a single machine’s hostname.
If you generated a new SSL certificate during Satellite installation that included a
new Common Name value, copy the SSL certificate RPMs from the secondary to
the primary Satellite and redistribute the client-side certificate. If you also created
another bootstrap script, you may use this to install the certificate on client systems.
5. If you did not create a new bootstrap script, copy the contents of
/var/www/html/pub/bootstrap/
from the primary Satellite to the secondary. If
you did generate a new one, copy that directory’s contents to the primary Satellite.
6. Turn off the
RHN Task Engine
on the secondary Satellite with the following com-
mand:
/sbin/service taskomatic stop
