Red Hat NETWORK SATELLITE 5.0.0 -, Руководство по установке

Страница: 66 / 84

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 advisory 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.
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 4, “Using RHN DB Control” for a complete description of this process and the options
available.
Here are the minimum files and directories Red Hat recommends backing up:
•
/rhnsat/
- Embedded Database only (never to be backed up while the database is running -
refer to Section 4.2, “Backing up the Database” )
•
/etc/sysconfig/rhn/
•
/etc/rhn/
•
/etc/tnsnames.ora
•
/var/www/html/pub/
•
/var/satellite/redhat/1
- custom RPMs
•
/etc/pxtdb.conf
- pertains only to RHN Satellite Server 1.1.x.
•
/root/ssl-build/
If possible, back up
/var/satellite/
, as well. In case of failure, this will save lengthy
download time. Since
/var/satellite/
(specifically
/var/satellite/redhat/NULL/
) is
primarily a duplicate of Red Hat's RPM repository, it can be regenerated with
satellite-sync
.
Red Hat recommends the entire
/var/satellite/
tree be backed up. In the case of
disconnected satellites,
/var/satellite/
must be backed up.
Chapter 8. Maintenance
60