Table of Contents
Advertisement
58
For RHN Satellite Server systems that may not be connected to the Internet, the packages
themselves may be retrieved using a customer account at https://rhn.redhat.com. Then, they
can be applied manually by the customer according to instructions in the Errata Advisory.
Warning
It is very important to read the Errata Advisory before applying any RHN Satellite Server
Errata Updates. Additional configuration steps may be required to apply certain RHN
Satellite Server updates, especially if they involve the database. In such cases, the ad-
visory will contain specific and detailed information about necessary steps that may be
required.
If instead of installing new Satellite packages, you are attempting to update the server's
RHN Entitlement Certificate, such as to increase its number of client systems, refer to
Chapter 5 Entitlements for instructions.
8.3. Backing Up the Satellite
Backing up an RHN Satellite Server can be done in several ways. Regardless of the method
chosen, the associated database also needs to be backed up. For the Stand-Alone Database,
consult your organization's database administrator. For the Embedded Database, refer to
Section 8.4 Using RHN DB Control for a complete description of this process and the op-
tions available.
Here are the minimum files and directories Red Hat recommends backing up:
- Embedded Database only (never to be backed up while the database is
•
/rhnsat/
running - refer to Section 8.4.2 Backing up the Database)
•
/etc/sysconfig/rhn/
•
/etc/rhn/
•
/etc/tnsnames.ora
•
/var/www/html/pub/
•
/var/satellite/redhat/1
•
/etc/pxtdb.conf
•
/root/ssl-build/
If possible, back up
will
save
lengthy
- custom RPMs
- pertains only to RHN Satellite Server 1.1.x.
/var/satellite/
download
time.
Chapter 8. Maintenance
, as well. In case of failure, this
Since
/var/satellite/
(specifically
Advertisement
Table of Contents
